Forum Replies Created
-
Posts
-
Hi,
The log with the manual reset actually looks OK. Does the program fail to start after programming in that case?
Another quick solution would be to try the Olimex ARM-USB-OCD-H programmer. It gives OpenOCD a very low-level control over JTAG and we managed to get relatively reliable debugging experience with it.
Hi,
J-Link might handle resetting differently. Please try connecting reset to SRST instead of TRST (normally pin 15). If this does not help, please try disconnecting reset completely and manually resetting the board before programming it.
Hi,
We have done some further research into ESP-IDF 2.0 and it looks like some changes to it totally break JTAG debugging and FLASH programming, so it may take us some extra time to fully figure it out.
We will have a quick look into the ESP32 tracing functionality and will assess whether it is stable enough to be supported via VisualGDB.
Hi,
It looks like the project you are trying to import contains several versions of vector_nvic.c meant for different targets, so importing all of them won’t work.
For projects with complex build scripts we recommend selecting “Specify a build command line manually” in the VisualGDB Project Wizard. This will tell VisualGDB to run the build script that came with the project, so it will follow all the complex rules defined there.
Another alternative would be to study the build scripts of the project and only import the files that are supposed to build on your target (you would also need to manually specify all the preprocessor macros that the project’s build system specifies). This approach requires more initial effort, but results in better integration between build, IntelliSense and debugger.
Hi,
Looks like your toolchain directory contains spaces in the path. As GNU Make does not support such directories properly, VisualGDB does not support them either. Please try creating a symbolic link (e.g. c:\armgcc) to the toolchain directory and using the short path instead.
Hi,
Sorry, we could not reproduce any IntelliSense problems with the attached project.
The issues you are experiencing could be caused by a corruption of the IntelliSense configuration files or the project file itself.
Please try deleting the <sysgcc>\arm-eabi\*.props files and creating another project via VisualGDB Project Wizard. This should regenerate all the configuration files.
Hi,
Please let us know the exact VisualGDB build number (can be located via file properties for VisualGDB.exe) so that we could check why this window is shown.
This feature is scheduled after the integration with the CMake server, so we would expect a preview build with this feature early this Summer.
It is based on a completely different technology than the embedded profiler, so many of the functionality will be different. Our best advice would be to wait for the first preview build with this feature and then send us your feedback if you find anything to be counter-intuitive or inefficient.
Hi,
Thanks for the explanation. As Intel Edison is not as popular as Raspberry Pi and other modern boards, we don’t ship a separate toolchain for it (the only other option would be to build a custom toolchain under our toolchain building service that usually costs EUR 1000 per toolchain).
Some GCC toolchains are configured in a way that requires their location to be stored in the registry, so just extracting the files for such a toolchain won’t work. We would recommend checking the archives and 3rd-party sites for a usable toolchain; if the toolchain itself is broken and does not work, VisualGDB unfortunately cannot fix this.
Hi,
Sorry, this is not supported yet, although we are researching Valgrind support and will be adding some level of integration with it into VisualGDB 5.3.
