[support]

Hi,

This looks like a Teensy-specific question rather than VisualGDB-specific one. Please consider asking on the Teensy forum instead.

[support]

Hi,

According to our records, your support period has expired. In order to continue receiving support, please renew your key here: https://sysprogs.com/splm/mykey

P.S. We do release toolchain updates regularly. However, if you decide to not renew your support and keep using an old unsupported version of VisualGDB, the new toolchains may indeed not work with it, as the internal changes to ESP-IDF often require updates on the VisualGDB side as well.

[support]

Hi,

It’s hard to say what exactly is going on here. From VisualGDB’s perspective, the gdb debugger works as expected, just never reports a stop anymore.

From GDB’s perspective, the gdbserver keeps reporting breakpoint events, but never reports any breakpoint being hit.

You can try using VisualGDB Project Properties to run the gdb debugger directly on the target (switch to custom mode and override the gdb command line). This will rule out any possible miscommunication between gdb and gdbserver.

If nothing helps, our best advice would be to try pinpointing a specific function that triggers the problem and try narrowing it down to a single executed line. E.g. some syscall, or some memory-intense operation could be triggering this.

[support]

Hi,

This looks like an ESP32 issue. Please refer to our ESP32 troubleshooting documentation for detailed instructions on resolving ESP32 errors.

[support]

Hi,

This is a generic message coming from Visual Studio that is shown when it doesn’t find any tests in the solution. It’s hard to say why it would be shown in this case, but if you could share the steps we could follow to reproduce the problem on our side, we will be happy to fix it.

[support]

Hi,

It looks like the anti-tampering logic of VisualKernel has engaged and is preventing parts of it from being initialized correctly.

Please make sure you do not change any registry keys related to VisualKernel and do not modify its components.

[support]

Most likely, you are using an incompatible combination of an Arduino core and a debug method. Please make sure you follow our AVR debugging tutorial to configure debugging of your board.

If it doesn’t work, please share the screenshots of all the wizard pages with the choices you make while creating the project, and also the screenshots of all the settings pages where you change any settings so that we could check for common errors.

[support]

Thanks, this looks like gdb fails to initialize.

Please try running the gdb executable shown in the log manually from the command prompt window and see if it’s being blocked by your antivirus or any other component.

You can also try deleting the entire C:\Users\Carlos\Documents\ArduinoData folder and re-creating the project from scratch. This will re-install all the packages and tools, including the up-to-date version of avr-gdb.

[support]

Thanks for reporting this.

We have investigated the issue and found the root cause. The Nordic nRF5x SDK 16.0 indeed does not contain linker scripts for the following MCU/softdevice combinations:

• nRF52810/S113
• nRF52811/S113
• nRF52832/S113

Our BSP generation tool incorrectly substituted the missing linker scripts with the S113 scripts for nRF52833 and other devices, that indeed contained invalid memory sizes.

We have updated our BSP generation tool to skip the missing scripts for now. We have also updated it to generate the correct memory size for the nosoftdev option.

As the issue only affects the device/softdevice combinations that are not directly supported by the Nordic SDK, we will not release an update to the current Nordic BSP, however we will take it into account in the next BSP release based on the 17.0 SDK (expected in a couple of months from now).

You should be able to use the S113 softdevice with nRF52832 by patching the linker script manually, however we generally advise using the device/softdevice combinations that are directly covered by the Nordic SDK examples, as they should behave more reliably.

[support]

No problem. The link was posted in our first reply in this thread.

Either way, here it is again: https://visualgdb.com/support/logsubmit

[support]

Hi,

The path mapping looks correct now. If the problem persists, please send us a screenshot of the problem along with a gdb log and we will help you understand what is going on.

[support]

Hi,

Sorry, this doesn’t look like a gdb log. Please make sure you follow the instructions from the page linked in our previous reply and send us the gdb log described there and not any other logs.

[support]

No problem, you can configure the path mapping between GDB and VS as shown here: https://visualgdb.com/documentation/pathmapping/

[support]

Hi,

No problem. Please try creating a gdb log as shown here and attach it to the thread so that we could see what is going on.

[support]

Yes, it could be related. Please try manually adding the Nordic-specific driver file (ProfilerDriver_Nrf5x.cpp) to the project.

• This reply was modified 5 years, 2 months ago by support.

[Author]

Posts