Forum Replies Created
-
Posts
-
Hi,
There is currently no standard way of doing this, so we would recommend one of the following:
- Use a source control system like Git or SVN to merge the changes from Linux and Windows
- Use SmarTTY to download the entire source folder or individual files from your Linux machine
- Add a custom shortcut via VisualGDB Project properties to download the source folder and then use the VisualGDB toolbar to invoke it quickly (requires Custom or Ultimate edition)
Hi,
The settings from VisualGDB Project Properties are saved in debug.mak/release.mak, while esp8266.mak contains settings that are common for all configurations.
Please double-check the settings in debug.mak and see if they are actually included in compilation command line.
Hi,
It’s hard to guess what exactly went wrong, but reasons could vary from files simply not rebuilding to some typos in the preprocessor macros.
We would recommend something like this:
- Add a static variable pre-initialized to a certain string (e.g. “test123”), use this variable from user_init() so that it gets referenced. At the same time comment out the call to gdbstub initialization.
- Does the binary image contain your string (test123)? If no, it did not get rebuilt properly. Note that the ESP8266 .bin images are only rebuilt when you start debugging with VisualGDB, not when you build the project.
- Do you still get the gdb stub message? If yes, some other code is calling it. Perhaps user_init() is defined in 2 different places and one takes precedence over the other one?
The JTAG debugging would be held by gdbstub because gdbstub essentially installs a handler to some debug-related interrupts, then triggers an interrupt and that interrupt handler waits for a reply via the COM port. The JTAG debugger does not prevent interrupts from being handled, i.e. the stub will still catch it and start waiting for gdb to attach. Once gdb attaches, however, you can still use the JTAG debugger to see what’s going on inside the stub and inside your code.
Hi,
You can try using the OpenOCD’s “cortex_m maskisr” command to disable interrupts during stepping as described here: http://openocd.org/doc/html/GDB-and-OpenOCD.html
However this will not work when using high-level debug adapters like ST-Link.
Hi All,
Normally you don’t need to install any new packages on your Pi as long as your ld.so.conf is set correctly and the /opt/vc directory is synchronized.
We have added troubleshooting instructions to the step 16 of the tutorial: http://visualgdb.com/tutorials/raspberry/qt/embedded/
Let us know if you run into further problems.
Hi,
OK, then the problem must be elsewhere. Please double-check your FLASH type setting (dio/qio/etc) in VisualGDB Project Properties.
Please also try manually programming the <project>-0x40000.bin and <project>-0x00000.bin files from the Debug directory using the bootloader and esptool.py.
If the LED blinks in that case, something goes wrong with programming the FLASH over JTAG. If the LED does not blink (but blinks when you are using the GDB stub), something about the images is corrupt and the next step would be to compare the images produced when using the OpenOCD debug method with the images produced from the same ELF file when using the gdb stub.
Hi,
If your program still contains the gdb stub, the stub will stop at the beginning of the program and wait for gdb to connect. Perhaps this is causing the behavior you are describing. This can be easily checked by pressing the “Break in” button in Visual Studio and examining the call stack.
You can disable this by defining GDBSTUB_BREAK_ON_INIT=0 in VisualGDB Project Properties -> Makefile Settings, but this will prevent you from debugging your program from the very beginning using the stub, as the program will quickly advance beyond user_init() before VisualGDB manages to connect to it.
Hi,
Please use the USBDriverTool to restore the original ST-Link driver. It also looks like the newest OpenOCD works correctly with the stock driver, so you don’t need to install the WinUSB-based one anymore.
Hi,
Sorry, I did not fully understand you. Could you attach some screenshots with setting PATH and building it, showing the PATH setting that breaks and the PATH setting that works?
The transfer to Raspberry Pi happens when you start debugging, so if you get errors during build, they are not related to transfer errors.
Hi,
Almost all inexpensive JTAG adapters are based on the FT2232 chip, so they are pretty much all the same, just differently packaged. Any Olimex one or something like FlySwatter from TinCanTools will do.
Hi,
The logic of automatically detecting that would be probably too complex and error-prone given a fairly simple workaround. We could add a button to trigger retesting manually if that helps.
Hi,
Sorry, we don’t support that yet. We would recommend using the ST-Link utility. We will also monitor the popularity of QSPI-related searches and add a tutorial on it if the topic becomes popular.
Hi,
The ui_MainWindow.h file is generated during build. So if you build the project and re-open it, IntelliSense should it pick it. If this does not happen, please check whether the file actually exists and whether its directory got added to the IntelliSense directories in VisualGDB Project Properties.
Hi,
What exactly is happening to the device? Is the LED blinking? Did the FLASH programming progress window appear? What is the contents of the GDB Session window (if you enable “All commands” view)?
Does changing reset mode in VisualGDB Project Properties help? Have you tried connecting the reset to pin 3 on your JTAG20 as described in the tutorial?
