[support]

Hi,

You can find the retarget command by right-clicking on the mbed-os library in Solution Explorer.

The build error looks like some of the paths in your project settings might be incorrect. Please let us know the VisualGDB build number you are using (from the About window) that corresponds to the stack trace above and share the diagnostic output from View->Other Windows->VisualGDB Diagnostic Output that is generated when you try to open the project.

[support]

Hi,

Please try right-clicking on the project in Solution Explorer and select Add->Manage Mbed Platforms.

[support]

Hi,

Thanks for confirming this. It looks like an IntelliSense-related error, so please first check if the project builds successfully.

Then try creating a new project from scratch (ensure it uses the same make/cmake tool) and check if the problem persists.

If the problem does not affect build, please try clearing the VisualGDBCache and CodeDB folders when the project is closed and then reopening it. If the problem affects build, please try comparing your project settings with a newly created project that builds.

Finally, if you cannot create any project at all, please try reinstalling the ESP32 toolchain, as it might have gotten corrupt.

[support]

Hi,

Are you using the new advanced ESP-IDF project subsystem, or is it a regular VC++-based project?

[support]

Hi,

Yes, please try marking the sections for the external FLASH memory with the NOLOAD attribute in the linker script. This will prevent the objcopy tool from trying to place them in the same contiguous binary file as the regular FLASH sections.

[support]

Hi,

Thanks for reporting this. It looks like the advanced popup mode was inadvertently activated in some cases where VisualGDB could not fetch the regular QuickInfo text.

We have fixed it in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2571.msi

No change of settings is necessary – the advanced popups will now only appear when activated explicitly.

[support]

Hi,

Sorry for the delay. We have pinpointed and fixed the issue in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2571.msi

[support]

Thanks for renewing your license and good to know it works.

The problem might have been caused by an incompatibility between the Segger software and J-Link firmware, and reinstalling the Segger debug package (or some other component it uses) have likely fixed it.

[support]

Hi,

Sorry, not yet. We will likely support this within the next year though.

[support]

Hi,

No problem, we can help you resolve this, however it looks like your support period has expired. Please renew it first, or let us know the email address associated with your new license, if you have purchased one already.

[support]

Hi,

Please use the following setting: Tools->Options->Text Editor->C/C++ (VisualGDB)->Other->Max. change-driven tags.

Simply set it to 0 in order to disable rename-triggered smart tags.

[support]

Hi,

Strange. Could you please share a screenshot of your settings and the command line shown in the build log?

[support]

Hi,

Thanks for the suggestion. We have done a few quick checks and it looks like we should be able to support it.

We will get back to this and post an update here in the next 1-2 weeks.

[support]

Hi,

Unfortunately, the global mbed setting for the toolchain location overrides the setting passed by VisualGDB. We have updated VisualGDB to clear the global setting when configuring the projects in this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.9.2564.msi

If you would like to have a global toolchain setting nontheless, please define the GCC_ARM_PATH environment variable via System Settings -> Environment.

With the target names, it looks like an issue of mbed-cli. Please try building the project from command line and check if the problem persists. If the build with mbed-cli works, but VisualGDB-based build doesn’t, please let us know and we will help you find the difference between the 2 configurations and will update VisualGDB to work around it.

Regarding the esp8266 component, the Advanced Mbed Project Subsystem delegates the build to the mbed-cli tool, so it does not have control over the low-level details of the build process. Please refer to the mbed documentation and forums for mbed-cli-specific instructions on excluding specific components. On the VisualGDB side, you can use the VisualGDB Project Properties to add arbitrary arguments to mbed-cli used to build your project.

[support]

 

Hi,

Yes, you should be able to customize the build command line via VisualGDB Project Properties -> CMake project settings -> Make Command.

[Author]

Posts