Forum Replies Created
-
Posts
-
Hi,
Thank you for the screenshots, however looks like you missed the “Debug Settings” page (#4 on your screenshots) that contains the relevant settings that should explain what is going on. Please post it as well.
Hi,
Thanks, we have just rechecked Preview 5 and the latest Segger package and could not reproduce any problem. Please post a screenshot of the Debug Settings page of your VisualGDB Project Properties or the Debug Settings page of the Embedded Project Wizard so that we could check for common errors.
Hi,
It looks like the debug method package is not working properly. Please try re-downloading the VisualGDB 5.3 Preview 5 installer and re-installing it; then ensure you have the latest Segger debug package via Tools->VisualGDB->Manage VisualGDB Packages.
If nothing helps, please make a screenshot of the Debug Settings page in your VisualGDB Project Properties and attach it here. This should help understand what is causing this.
Hi,
Perhaps Keil/Eclipse enables the hardware FP implicitly or the version of port.c you use with those IDEs contains conditional statements that exclude FP-specific code?
Please try searching the port.c file compiled with Eclipes for “vstmdbeq” and see if it has any #ifdef’s around it. If no, please check the exact command line used to build this file. Does it contain any FP-related settings?
This should be the correct one. Please check the output of the J-Link gdb stub and the entire gdb session log as suggested above. Feel free to post the output here if it does not help.
Hi,
We do run series of automated tests on all released packages, so it should not normally be the problem. However we have recently released an update to the Segger package that requires VisualGDB 5.3 Preview 5 (it will only be shown/installed if you are already using v5.3 Preview). Please check if you are using an older preview build of VisualGDB and update it if this is the case.
Hi,
nRF5x projects store board configuration in pcaXXXX.h files included from boards.h. Hence to port your project to a custom board, you would need to copy one of those files, adjust its contents to reflect the differences between your board and the original board and modify boards.h so that it will include your modified file instead (e.g. by adding a new BOARD_xxxx macro and checking for it in boards.h).
Hi,
This generally could indicate some error during the debugging setup phase. Please check the entire GDB log and also the output from the J-Link stub for more clues. If you are not sure, please post both of them here and we will help you understand them.
Hi,
Yes, please run the esp-idf tool, generate a new partitions.bin file and specify a path to it on the first page of VisualGDB Project Properties.
Hi,
We posted on the mbed forum about this (https://developer.mbed.org/forum/mbed/topic/27899/), but did not get any response from the mbed maintainers. Unless they can confirm that they would be interested in accepting the merge request with this feature, it does not make any sense to move on as mbed is rapidly changing and any stand-alone exporter will quickly become incompatible with the mbed build system.
Hi,
Thanks for your feedback. Currently it looks like Mono is going to get deprecated in favor of .Net Core (and Microsoft might support remote .Net Core debugging natively), so we won’t be targeting Mono on the near future. Hence the only way to support Mono would be via writing a plugin using our high-level frame extension API.
Hi,
Normally the log will be displayed once you click “details”. Most likely this happened because some files from the old toolchain (e.g. the debug plugin) were in use by VisualGDB.
Please try closing all Visual Studio instances and installing the toolchain manually: http://gnutoolchains.com/esp32/
Please also note that the latest toolchain requires VisualGDB 5.3 Preview 5 as it relies on the new mechanism for embedded debug packages.
Hi,
It’s not particularly hard, although the process it not documented and not officially supported. The embedded frameworks come from 2 sources:
- BSP.XML files under %LOCALAPPDATA%\VisualGDB\EmbeddedBSPs define frameworks that come with the BSP
- EFP.XML under %LOCALAPPDATA%\VisualGDB\EmbeddedEFPs define frameworks that can be used for all embedded devices regardless of the BSP
All our code responsible for generating BSPs (including the frameworks) is actually open-source and is available here: https://github.com/sysprogs/BSPTools/, hence you can try modifying some of the existing BSP generators to generate custom framework packages.
Regarding ChibiOS, it currently looks much less popular than other RTOSes like FreeRTOS, so we don’t have any plans of supporting it directly. If it becomes more popular, we will reconsider this. However currently you would need to create the framework manually in order to support this OS out-of-the-box.
Hi,
Yes, the problem happened because the fine-grained indentation of the function arguments happened on the different level than the coarse-grained indentation of the statements.
We have fixed this in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.3.5.1708.msi
Hi,
Sure, we have just released it: http://visualgdb.com/download/ (use the “try preview” button).
After installing we recommend updating the debug packages via Tools->VisualGDB->Manage VisualGDB Packages. This will install updates that significantly improve the OpenOCD and Segger J-Link debug experience.
