Forum Replies Created
-
Posts
-
Hi,
This could have something to do with the signal handling on the Linux side (incompatible combinations of gdb/kernel/libc). Please try checking if you can force the application to stop via “killall -s INT <application name>”. If yes, you can configure VisualGDB to use this command instead of the regular break-in mechanism via the Custom Debug Steps page (requires Custom edition).
Hi,
The exact FLASH programming sequence is actually handled by gdb and the underlying gdb stub (e.g. OpenOCD). We are somewhat reluctant to change the OpenOCD programming logic as that could introduce bugs and break backward compatibility, so we could advise one of the 3 options:
- Try using Segger J-Link. Their gdb stub is optimized much better than OpenOCD.
- Try hacking OpenOCD at your own risk.
- Instead of embedding the version into the ELF file, save it to a separate file and program it using an OpenOCD command. You can add OpenOCD commands to the “Additional GDB Commands” page of VisualGDB Project Properties as long as you prefix them with “monitor” (e.g. monitor flash program …).
Hi,
If your sysroot contains different versions of system libraries than the toolchain does, the compiled code may not work on the device. Please use the system image listed under “compatible image” for the toolchain you are using here: http://gnutoolchains.com/beaglebone/
Hi,
Sorry, our open-source BSP tools are completely “as is” and don’t come with any tutorials or guarantees. Normally it should be sufficient to open the main .sln file and run the generator exe, but you may need to edit the sources to adjust some paths or settings.
Hi,
OK, this indeed looks like a break-in problem. Please try checking whether this behavior is consistent for all programs on the same Linux machine or if it is specific to one project (or one library used by the project).
Hi,
The unknown code address could be an interrupt handler from the prebuilt esp8266 libraries. Generally, it is possible to do the proper stepping given one hardware breakpoint, however the corresponding part of the the xtensa gdb is very buggy and often gets confused. The reason why this functionality works out-of-the-box for ARM devices is that ARM has been around for decades, so the underlying tools have matured to handle common scenarios flawlessly. ESP8266 is based on a much less popular CPU architecture, the corresponding low-level tools are less developed and behave more sporadically.
Our primary goal with ESP8266/ESP32 is to keep VisualGDB affordable to the hobbyist community, that are the primary users of those devices, so we don’t go very deep in fixing the toolchain issues, instead providing a user-friendly layer on top of the tools. The unfortunate disadvantage of this is that VisualGDB inherits many of the ESP8266 gdb bugs until Espressif fixes the underlying tools.
We are also considering a crowdfinding campaign to fix the most annoying issues in the low-level open-source tools (keeping the fixes open-source of course), but currently it is hard to provide any specific timeframe estimates on that.
Hi,
If your code explicitly manipulates CPU sleep states and power-related registers, you may need the “connect under reset” option as described in the tutorial. If you are not sure, we would suggest editing the OpenOCD scripts as described in the tutorial and checking if it solves the problem.
Hi,
We actually have a detailed tutorial showing how to configure an equivalent of “Connect under reset” with VisualGDB: https://visualgdb.com/tutorials/stm32/sleep/
Let us know if it does not help.
Hi,
Normally VisualGDB shows the license information only in About window and in the GDB Session window, but not in a separate popup.
If your license shows the name of your company’s purchasing person instead of the actual user, simply contact our support and we will update this.
Hi,
This looks like a bug in the STM32 device table on their site (http://www.st.com/en/microcontrollers/stm32l4-series.html?querycriteria=productId=SS1580). Once they fix it, our next BSP will use the updated data.
The wrong value should only affect the device selector, but not the actual linker scripts, so you can simply ignore it.
Hi,
The problem is that ReSharper uses its own IntelliSense engine that does not handle the GCC language extensions. So our best advice would be to use our Clang-based IntelliSense engine that is fully aware of those extensions and also offers advanced refactoring functionality.
Hi,
You can download the previous versions of the BSPs here: http://visualgdb.com/hwsupport/
Then simply install them via “Install a package from file”
Hi,
CC3220S is a different chip from CC3200 and is not supported by us directly (it looks to be much less popular than CC3200, so we currently don’t have plans for supporting it directly).
Please follow our legacy device tutorial to setup a project manually.
