[support]

Hi,

Generally, Cortex-R devices are somewhat niche, so we are not planning to support them directly unless we see more traction. As a workaround, you can always create a project manually as shown in this tutorial.

We have also developed a tool for converting the projects generated by TI’s HalCoGen into VisualGDB BSPs. However, it was created as a part of a custom paid BSP requested by one of our customers, so we cannot guarantee that it will work with all device families. It could be a good starting point, but it may require some tweaking before you get a fully usable BSP out of it.

[support]

Hi,

No problem, we can help you get it working, however we would first kindly ask you to renew your technical support here as it has recently expired.

[support]

This actually comes from the new ESP-IDF toolchain that does not include the MinGW shell anymore. Please try this VisualGDB build: VisualGDB-5.5.7.3679.msi. We have added a context command to Solution Explorer for launching the “monitor” command. Note that if the monitor settings are inconsistent or missing, the command will exit without printing anything. You can find out its output by dumping the “monitor” command to a batch file (see this page) and running it manually from a Command Prompt window.

[support]

Thanks, we have updated VisualGDB to handle it correctly: VisualGDB-5.5.7.3679.msi

[support]

Hi,

Looks like Espressif has changed the internal structure of the config definitions again. We have updated VisualGDB to handle the new structure in this build [VisualGDB-5.5.7.3679.msi].

That said, ESP-IDF 4.1 is still a pre-release, so it may change again. If you would like to avoid disruptions to your workflow, please consider waiting until it becomes a stable release use the version that we will ship with our toolchain (it will be tested for compatibility and should work out-of-the-box).

[support]

Sorry, we do not have any special GUI for comparing two external projects.

Regarding the differences, it’s hard to say why the numbers would not add up. The difference could be coming from other source files, or library functions that are not associated with any particular source file.

[support]

Hi,

Thanks for reporting this. We have just released an updated version of the STM32 BSP that defines the FPU for all the devices correctly. You can install it via Tools->VisualGDB->Manage VisualGDB Packages.

If you still need help overriding the settings, please let us know.

[support]

Thanks for the detailed repro example. We have reproduced the problem and fixed it in the following build: VisualGDB-5.5.7.3678.msi

[support]

Hi,

Thanks for letting us know. This should normally work out-of-the-box, so it’s likely caused by interference from another plugin.

Please try disabling all other extensions via Extensions->Manage Extensions (or Tools->Extension Manager). If it doesn’t help, please check if the problem persists on a basic MinGW project created from scratch. If not, please try determining if there is any specific component (e.g. a specific toolchain or a specific global variable syntax) that is causing the trouble.

You can also check for suspicious output in View->Other Windows->VisualGDB Diagnostics Console. It may explain what is going on.

[support]

Hi,

Please see the following page for a detailed explanation on supported ESP-IDF versions: https://visualgdb.com/documentation/espidf/#troubleshooting

[support]

Yes, you can use the “Compare the current build to a specific version” button (see step #18 of the tutorial).

[support]

Thanks for sharing this. This is exactly the reason why we release the sources for our BSP-related tools.

[support]

Hi,

No problem. Indeed VisualGDB normally supports only one imported Atmel START SDK per device family (multiple SDKs for different devices can be imported at the same time).
We can show you how to override this by manually editing/moving the definition files, however it looks like your support period has recently expired.

Please renew it here and we will be happy to provide detailed instructions.

[support]

Hi,

Good to know it works. VisualGDB can indeed install a Python environment that was tested on our side with the nRFConnect SDK and should work out-of-the-box (see step #7 of our NRFConnect tutorial). In case of any Python-related problems, we suggest resetting the environment as shown on this page.

[support]

Hi,

VisualGDB actually provides its own mechanism for fast tracing – the advanced semihosting framework. You can reference it via VisualGDB Project Properties -> Embedded Frameworks and then use the regular printf()-like functions to output data. See this tutorial for a detailed example.

If you would like to specifically use SWO, you can configure it manually as shown here (use VisualGDB Project Properties -> Additional GDB Commands) and then use VisualGDB’s raw terminal to connect to the port where J-Link outputs the SWO data.

[Author]

Posts