Forum Replies Created
-
Posts
-
In order to solve the build issues please double-check that the bootloader project is set as a build dependency for the main project (step 19 of the tutorial). Otherwise Visual Studio will try to build both projects in parallel and will indeed not work.
To solve the entry point issue when debugging, please set the “reset after programming FLASH” checkbox in debug settings (step 23 of the same tutorial).
Hi,
Please check the built log (View->Output). It will show the output from ld.exe (GNU linker) that should contain more details about the cause of the error.
Thanks for the very detailed description and repro steps.
Unfortunately, this is a known limitation of VisualGDB. The “Nordic BSP Samples” are automatically converted from the samples included in the Nordic SDK and hence do not follow the regular embedded framework layout used by VisualGDB and would require manual adjustments after conversion to a stand-alone project.
As a workaround, please try creating a project based on the regular VisualGDB-supplied samples that are fully compatible with the stand-alone project format.
Sorry, “extract function” is not yet supported by Clang IntelliSense. It is planned for the next major VisualGDB release, however is not available yet.
The ARM simulator built into gdb is indeed very basic and does not simulate most of the modern devices like STM32. VisualGDB shows it in the debug method list for backward compatibility with older devices where CPU-only simulation would make sense. For STM32 devices we recommend using one of the ST’s development boards with ST-Link.
OK, we have updated VisualGDB to automatically remove the temporary files from the previous ESP-IDF versions when changing the toolchain or the IDF checkout.
Please try this build: VisualGDB-5.4.105.3154.msi
Sorry, we are not the vendor for SimplicityStudio. For generic SimplicityStudio questions, please contact Silabs. If you need help with one of the Sysprogs products, please let us know and we will be happy to help you.
Please double-check that your source file includes the necessary header files.
Plain C supports calling functions without declaring them first. This creates an implicit declaration based on the arguments provided, however as it is not explicitly linked to the actual function, the Clang IntelliSense won’t be able to find it.
Hi,
Good to know it works. BTW, although VisualGDB does not directly support the Keil’s event recorder mechanism, it provides a similar mechanism for tracking various events – real-time watch. Feel free to follow this tutorial to try it out.
Thanks for the suggestion. We can indeed cache the toolchain/IDF version used during the last build and force a full rebuild when it doesn’t match anymore. We will investigate this and get back to you around the middle of the next week.
Hi,
In order to reduce the size of the projects, VisualGDB does not copy all of the shared files (e.g. Nordic SDK) to each project. Instead, it stores them in a shared location (typically under %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs) and references them from the projects. Each time you open such a project, VisualGDB would check if the referenced BSP is available. If not, it would show a dialog allowing you to download it.
Furthermore, as different versions of BSPs are not always compatible, VisualGDB remembers the exact BSP version referenced by the project and shows a warning you described when another BSP version is installed.
You can eliminate the messages when opening the projects in one of 2 ways:
- If you are OK using the same BSP version for all of the projects, please simply click the “Use version XXX” button. This will update the version number stored in the project file, so next time you open it, the message won’t be shown (unless you switch the BSP version again). This will need to be done for each project referencing this BSP. We can also add a setting for automatically upgrading the BSP version, however it may cause weird problems as the BSPs are not always 100% compatible.
- Alternatively, you can install multiple versions of the same BSP (requires the Custom edition or higher). Simply use the checkbox under Tools->VisualGDB->Manage VisualGDB Packages->Installed->BSPs ->Nordic to enable the multi-version mode. Then VisualGDB will keep multiple versions of the same BSP, letting you have multiple projects using different BSP versions. In this mode, clicking “Download” in the window shown when opening a project will download the exact version of the BSP referenced by the project without replacing the previous version you had installed.
We are not sure what you meant with the Microsoft-style include directories. Normally you can set them under VS project properties (MSBuild projects) or VisualGDB project properties. If this is not what you are looking for, please describe what you are looking for using the first 2 steps of the 3-step format described here: http://visualgdb.com/support/reporting/#3step
No problem, we have contacted Whole Tomato with the case details and will update you once we get the tools integrated.
Please ensure that the parameter names after @param are not wrapped with any ‘<>’, e.g.:
@param setting
Sorry, ESP-IDF is not very backward-compatible. Unfortunately, it isn’t something controlled by us – it’s a design choice by Espressif to introduce new features faster at a cost of backward compatibility. Our best advice for porting the project would be to create a new one with the latest IDF/toolchain and then move your code one file at a time, resolving the build issues.
We can help you find the COM port setting if you could post screenshots of the project properties and debug properties page of VisualGDB Project Properties.
