Forum Replies Created
-
Posts
-
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?
Hi,
If this is a reprogrammed ARM-USB-OCD-H or another device, please use the ST-Util to restore the original VID/PID and specify the OpenOCD script accordingly. Please also ensure that you have a WinUSB-based driver installed. You can install it manually using USBDriverTool.
Hi,
If you are using OpenOCD, you can try running the ‘mon flash erase_address’ command in the GDB Session window:
mon flash erase_address pad <start address> <FLASH size>
Hi,
This is strange. What happens if you open command-line prompt in your project directory and run the following commands?
set PATH=C:\Pi\Toolchain\bin;%PATH% make
Do you get the same error message? Is the .elf file created? What if you run “make all” or “make DEBUG/<ELF FILE NAME>.elf”?
Hi,
VisualGDB uses a different build mechanism, so forcing the C++ files to be treated as C would involve adding “-x c” to CXXFLAGS. However, we would recommend simply renaming your .cpp file to a .c file to avoid further problems.
Hi,
Please try updating to VisualGDB 5.0. Alternatively you can try downloading an older OpenOCD package and installing it via the Embedded Tools Manager, e.g.:
http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd090.vgdbxedp
http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd090r2.vgdbxedpHi,
Do you get the ‘testing toolchain’ dialog? If no, try changing an arbitrary line on the Makefile Settings page (e.g. add a space to CFLAGS and remove it back) and clicking “Apply”.
Hi,
OpenOCD needs a libusb-based driver for J-Link that is incompatible with the original J-Link driver. The easiest way to install it is using our USBDriverTool. You can also try configuring OpenOCD debugging with J-Link for an ARM project and click “Test settings” so that VisualGDB configures the driver automatically. We don’t have automatic driver setup for ESP8266 projects yet though.
