[support]

Hi,

 

Most likely you have created a project for the nRF51 chip (not nRF52) that was deprecated and removed from the modern Nordic SDKs. We handled this by forking nRF51 support (based on the latest SDK that supports it) into a separate BSP with a different ID.

Please try locating the nrf5x.xml file in your project directory and check the exact MCU ID it mentions. Then create a new project for the same MCU with the VisualGDB project wizard and check the BSP ID it puts in the new project’s nrf5x.xml file. Finally, copy the new ID to your old project and you should be able to build/debug it again (you may need to regenerate MCU-dependent files via VisualGDB Project Properties).

[support]

Hi,

OK, thanks for sharing this. Looks like we know what is going on. Your project likely explicitly stores the ARM toolchain location and VisualGDB is unable to override it with the dummy toolchain that produces a code model. We should be able to add a workaround for this. Would you be able to attach a copy of your mbed configuration files (*.py and *.json from the project’s directory)?

[support]

Hi,

It looks like your project structure might be different from what VisualGDB expects, hence it does not manage to parse it.

VisualGDB handles advanced mbed projects by temporarily replacing the toolchain with a dummy one that pretends to build all the sources, while creating a full log of all gcc/ld invocations, so VisualGDB can reconstruct the project structure from them. Most likely something about your project setup is preventing this from working.

We should be able to update VisualGDB to support it if you could share the following files under your project directory:

• VisualGDBCache\<configuration>\CodeSenseDir\MbedCommandLines.txt
• VisualGDBCache\<configuration>\BuildCommandLines.txt

[support]

Hi,

Thanks for sharing this. We have double-checked the config files from Visual Studio itself and it looks like it also uses the same flag, so we added it to the config file that comes with VisualGDB as well. Hence you won’t need to edit the file next time you update VisualGDB.

[support]

Hi,

Sorry for the confusion. The exact name of the setting is “Excluded Code”.

[support]

Hi,

Just wanted to let you know that we have received more requests for better mbed support recently and were able to add a new advanced mbed project subsystem to VisualGDB.

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2553.msi (use the new mbed wizard).

We will post an official announcement for this tomorrow and a tutorial later this week.

 

[support]

Hi,

No problem, we have added a command to toggle the CodeJumps annotations via Edit->Advanced menu to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

You can assign a keyboard shortcut to it via the Tools->Customize->Keyboard command.

Regarding the references, it indeed looks like some glitch on our side, however unfortunately we were not able to reproduce it on our side. Please try narrowing down a specific sequence of steps that leads to it, or simply capture a video demonstrating the problem. This should help us see what is going on and add a fix for this.

[support]

Hi,

Strange. We have rechecked all the assemblies shipped with VisualGDB and could not find any mixed-mode ones.

The error looks like the .Net runtime is failing to load the VisualGDB settings types. Could it be a corrupt .Net installation? Can you confirm that VisualGDB runs as expected on other machines in the same domain/with the same group policy?

We have also added extra logging to this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

 

Please try reproducing the problem with it (enable verbose mode by adding “/v” to VisualGDB’s arguments). It should show a much more detailed exception report that should help narrow this down.

 

[support]

Hi,

Thanks for the detailed problem description and the screenshot. Looks like it was indeed a remnant from Cygwin-based toolchains on our side.

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

[support]

Hi,

No problem. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2552.msi

[support]

Hi,

Sorry, there isn’t any special command for renaming projects. You can use the VisualGDB template mechanism for some project types (e.g. MSBuild), but otherwise you would need to rename the project manually and update the following files:

• The .vgdbsettings files should be renamed to match the new project name.
• Any explicit references to the .vgdbsettings files inside the .vcxproj file should be updated.

That should be sufficient to get the renamed project to work. Let us know if you encounter any problems and we will help.

[support]

Hi,

OK, thanks for checking this. If updating doesn’t help, there might be a system setting that is blocking the VisualGDB.exe assembly, or the problem is caused by a different assembly.

Please try running the build command line shown in the log manually:

"C:\Program Files (x86)\Sysprogs\VisualGDB\\VisualGDB.exe" /build C:\Code\Linux2015\igc.nisttime.git_linked\igc.nisttime.git_linked\igc.nisttime.git_linked.vcxproj /solution:C:\Code\Linux2015\igc.nisttime.git_linked\igc.nisttime.git_linked.sln  /config:Release /platform:Win32

Do you get the same error? If yes, does running VisualGDB.exe without arguments also result in the same behavior? If no, please try setting the “VISUALGDB_VERBOSE_OUTPUT” environment variable in a command line prompt and running the full build command line again. This should produce a more detailed error log.

Another option would be to try adding the <startup> element to the .config file as shown in this thread: https://stackoverflow.com/questions/6425707/mixed-mode-assembly-is-built-against-version-v2-0-50727-of-the-runtime

[support]

Hi,

Thanks for renewing your license! It looks like your forum email was different from the email used in your order, so our system was not automatically picking up the latest key. We have linked them together now in our system.

Regarding the error, it looks like you are using an older VisualGDB version that does not include a configuration file listing all compatible .Net runtimes. This can be fixed via one of the following options:

• Updating to VisualGDB 5.4 Preview 8.
• Downloading the attached .config file and placing it in the same directory as VisualGDB.exe.
• Installing the .Net 2.0 runtime via Control Panel -> Add/Remove Programs.

Let us know if you encounter any further problems and we will be happy to help.

Attachments:

You must be logged in to view attached files.

[support]

Hi,

We could issue you a trial extension voucher so you could check if the latest VisualGDB 5.4 resolves the problem, but unfortunately we are not able to offer any personalized technical support unless the support period is renewed.

[support]

Hi,

Thanks for contacting us. According to our records, your support period has expired. In order to keep on receiving technical support, please renew your license or let us know the email associated with your new license key.

[Author]

Posts