[support]

The build with the new Live Watch improvements is ready: VisualGDB-5.6.5.4228.msi. Feel free to try it out and let us know your feedback.

[support]

Hi,

In our quick experiments, the breakpoints didn’t work in QSPI. This could be specific to a particular chip we used and could work differently on your one. You can try manually using the hbreak command in gdb to set a hardware breakpoint at a specific function in QSPI. If it doesn’t work, please consider checking it with ST – it might be completely unsupported, or might require some extra setup (e.g. disabling cache).

[support]

Thanks, this indeed looks like a debug symbol problem. Please see the following tutorial for detailed instructions troubleshooting it: https://visualgdb.com/tutorials/linux/symbols/

[support]

Hi,

Programming external memories with OpenOCD indeed requires building and using a special FLASH programming plugin. You can find more information in this tutorial.

[support]

A custom source path mapping should take care of that. If it doesn’t work, please attach a screenshot of your path mapping settings, the full path of the file on Windows where you are trying to set a breakpoint, and a gdb log showing the command that VisualGDB used to set the breakpoint.

[support]

The -mfloat-abi setting should make it to both compiler and linker settings. The easiest way to ensure it would be to use the Configuration Properties -> ARM Settings -> Floating-point ABI setting.

The “frame not in module” error would typically mean that the CPU stopped outside any code that has symbols. You can double-check it by hardcoding a breakpoint (e.g. asm(“bkpt 255”) followed by asm(“nop”) in main()).  Once it hits, try checking the disassembly view. If it displays the “bkpt 255” and “nop” instructions but doesn’t map them to the main source file, there is a problem with symbols. If the code is stopped on a completely different instruction, the problem is not related to the debugger.

[support]

For mbed projects the list of memories (e.g. m_ivt) is computed by parsing the linker script, since there is no other source for this information. For MSBuild projects it’s taken from the device definition shipped with the BSP.

[support]

Hi,

No problem. We are planning to add a few minor improvements to Live Watch in the next couple of weeks, so we will address this issue as well.

We will post an update here once we get a preview build with the new behavior.

[support]

Hi,

The Embedded Memory Explorer reloads the project file when it finishes building, or when you close and reopen the Memory Explorer window. If you believe it shows incorrect data, please try following the steps below to double-check it:

1. Create a special build of the ELF file with a specific symbol (e.g. test123)
2. Verify that the ELF file actually contains it by running arm-none-eabi-objdump -t [ELF file]
3. Replace the output of the project
4. Fully close Memory Explorer and reopen it via the command in the View menu
5. Recheck whether it shows the newly added symbol

If it still shows the old file layout (e.g. doesn’t show the new symbol), please attach the relevant screenshots and we will help you get it working

[support]

Hi,

The Live Watch scales the graphs automatically based on the selected scaling mode (individual vs. combined). The easiest way to get more detail would be to export the data into a CSV file and plot it in Excel or any other similar tool. See the Live Watch documentation for more details about exporting data.

[support]

Hi,

We have rechecked the NRFConnect SDK 1.6.0 and it worked just fine with our latest toolchain (GCC 9.3.1). Please try deleting the SDK and reinstalling it with VisualGDB. Please make sure the SDK installation succeeds without any errors (e.g. due to insufficient disk space).

If the problem persists, please share the complete steps to reproduce it from scratch per our problem reporting guidelines, including all the relevant screenshots.

[support]

Hi,

The MSP430.DLL file comes from TI and implements the low-level logic for interacting with the TI hardware. In case of any issues with it, we always recommend downloading the latest version directly from TI: https://www.ti.com/tool/MSPDS

[support]

Hi,

Please refer to the following page for more information on path mapping: https://visualgdb.com/documentation/pathmapping/

[support]

Hi,

Please try restarting Visual Studio after you have changed the theme. This will ensure that all VisualGDB components will pick up the updated colors.

[support]

Hi,

Linker script preprocessing could be related to this. Please try linking the MSBuild project using the preprocessed linker script produced by the mbed-cli build.

If it doesn’t help, you can quickly narrow down the problem by combining command lines from different builds. E.g. try linking the object files produced by mbed-cli with the linker command line from msbuild, and vice versa. If the problem appears to be specific to the linker command line, try gradually changing the broken command line until it matches the working one, rechecking the results after every step.

If the problem is triggered by using the object files from MSBuild, please try replacing half of them with the versions built by mbed-cli, and check if it solves the problem. This should help you quickly find the specific object file triggering the problem.

[Author]

Posts