Forum Replies Created
-
Posts
-
Hi,
Are you still using VisualGDB 5.3 Preview 5? If yes, please check that the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp\SeggerEDP.dll file exists. If it does, please check the Debug Settings page again. Does it show any settings below the “Segger J-Link” item?
Hi,
This happens if your PATH variable contains multiple Cygwin directories. ESP32 cygwin binaries would try to load an incompatible version of cygwin1.dll causing this problem.
Please double-check your PATH and remove other Cygwin directories from it.
Hi,
OK, thanks, the issue was caused by the FLASH initialization code timing out. We have fixed this in an update to our OpenOCD package and also updated the flash_drivers examples to specify the timeout values instead of hardcoding them in OpenOCD.
Hi,
Thanks, it looks like the debug plugin failed to load. Please try deleting the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp folder, restarting Visual Studio and creating a new project from scratch. VisualGDB should re-download the plugin. If it does not solve the problem, please check that the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp\SeggerEDP.dll file is present. If not, please check your antivirus logs, it might be removing the DLL during the installation.
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.
