[support]

Hi,

OK, thanks for the log, that explains it. Looks like something is totally wrong with the temporary directory and this breaks the .Net framework. It is surprising it didn’t affect any other programs.

Please try deleting all files in the temporary directory and run chkdsk on the drive containing it.

[support]

OK, sorry about that. We have added another logging layer on top: http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1916.msi (the link will become available in ~10 minutes)

Please open the View->Other Windows->VisualGDB Diagnostics Console window and enable logging before opening VisualGDB Project Properties.

[support]

Hi,

Thanks for confirming this. Looks like some internal VisualGDB component is throwing an exception and VisualGDB is not handling it properly. Please try this build:

http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1915.msi

It should display a meaningful error message in this case.

[support]

Hi,

It could be that your license upgrade did not get applied properly. Please try re-entering the key via Help->About VisualGDB.

[support]

Hi,

Yes, it will be included in the next maintenance release.

[support]

Hi,

Thanks for the updated gif. Looks like you don’t have the “Reformat code when ‘}’ is pressed” enabled in the C++ editor settings, so VisualGDB is using an alternate simplified mechanism to layout the brackets.

We have added a workaround to this build that will fix the location of the closing brace: http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1913.msi

 

[support]

Hi,

We would recommend calling the MessageBox() function from your C++ MinGW code at the beginning of the test. This should pause the test displaying the message box. Then you can use Task Manager to locate the PID of the test process and then simply attach to it with VisualGDB (you can also display the PID in the message box itself).

[support]

Hi,

The ESP8266 images consist of several non-consequent blocks that need to be programmed at different addresses in the FLASH memory following the “<Project Name>-<Offset>.bin” syntax. The “<project name>.bin” file is generated by the regular objcopy tool that is not aware of the ESP8266 specifics and should be ignored.

[support]

Hi,

For a stand-alone project please simply remove “compactcpp” from the list of libraries in the first page of VisualGDB Project properties.

[support]

Hi,

Wow, this looks like something in the installation/configuration gone horribly wrong. We have just re-tested a clean R7 toolchain install, but could not reproduce any crashes. The OpenOCD output also mentions a different build date:

C:\SysGCC\esp32\esp32-bsp\OpenOCD\bin\openocd.exe -c "gdb_port 8786" -c "telnet_port 8787" -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -c "adapter_khz 3000" -f target/esp32.cfg -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.9.0 (2017-08-05)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
adapter speed: 3000 kHz
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
force hard breakpoints
VisualGDB_OpenOCD_Ready
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 3000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : Target halted. PRO_CPU: PC=0x400D0A58 (active)    APP_CPU: PC=0x00000000 
Info : accepting 'gdb' connection on tcp/8786
Info : Use core0 of target 'esp32'
Info : Target halted. PRO_CPU: PC=0x40090FA3 (active)    APP_CPU: PC=0x400803C0 
Info : Auto-detected flash size 4096 KB
Info : Using flash size 4096 KB
Info : dropped 'gdb' connection

It looks like you might have accidentally started an incorrect version of OpenOCD (or accidentally copied it over the version in the R7 toolchain). Our best advice would be to delete the toolchain directory and try installing it again. Please also ensure you are using the latest VisualGDB 5.3R5 (early pre-release v5.3 builds are not compatible with the latest toolchains).

[support]

Hi,

It looks like when you go to the new line with VisualGDB, it inserts double indentation, so the logic that is supposed to remove it when ‘{‘ is typed, only removes a half of it.

It also looks like some other VS extension is highlighting the indentation in red color; perhaps the same extension is responsible for inserting extra spaces?

We have also added extra logging to this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.15.1912.msi

Please try re-running the case shown on Working2.gif and post the output of View->Clang IntelliSense Diagnostics Console here. It will explain what is going on.

[support]

Hi,

This happens because the newer gcc includes optimizations that make the libcompactcpp library unnecessary, so it was removed from the latest release. Please try opening VisualGDB Project Properties and clicking the regenerate button (it it’s not shown, try changing any of the MCU-related settings and restoring it back). This should rebuild all toolchain-specific settings and remove the references to the missing library.

[support]

Hi,

The behavior you are describing could be caused by several different factors:

• USB virtualization slowing down communication with the JTAG probe
• Some very frequently called functions being configured for monitoring, overloading the communication channel
• Unexpected RTOS modifications that cause internal state corruption (real-time watch only supports FreeRTOS currently)

The easiest way to diagnose this would be if you could make a short video showing:

• Your debug settings
• The slowly updating output you mentioned
• Several seconds of the live profiling window (including the ‘statistics’ view)
• Call stack and the context (e.g. the value of s_FastSemihostingState)

This should help us quickly understand what is going on and suggest a fix. If you don’t want to make the video public, you can simply send it via our support form.

Another approach would be to try running the analysis on a “LEDBlink” project and if works normally, start comparing/eliminating the differences between the 2 projects (e.g. switch to use same RTOS, same main() function, etc).

[support]

Hi,

Olimex recommends using the open-source avrdude program with AVR-ISP500. VisualGDB currently doesn’t support it out-of-the-box, so you would need to install and configure it manually. If you can confirm that the command-line programming with avrdude works, we can help you configure your VisualGDB project to run it automatically.

It could be also worth a try checking if the AVaRICE tool shipped with our AVR toolchain can recognize AVRISP MKII. If yes, you would not need to install any extra tools.

[support]

Hi,

Thanks for the exported settings. We have tried loading your settings into our VS2017 test setup, however we could not get the behavior you are demonstrating.

The incorrect formatting could be caused by interference from other plugins. Please try disabling all other extensions via Tools->Extensions and Updates and let us know if you locate a specific extension that causes this. If nothing helps, please try exporting all your Visual Studio settings and then resetting them to defaults.

[Author]

Posts