Forum Replies Created
-
Posts
-
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.
Hi,
Thanks for letting us know. We will consider fixing this in the next release of the STM32 package.
Hi,
Looks like we forgot to mention in the tutorial that you need to upload the Qt libraries from the toolchain to your device. We have updated the tutorial, please upload the files as shown below:
Hi,
Sorry for the confusion, looks like the Beaglebone page contained the wrong toolchain link. We have updated the page, please try downloading it again.
Hi,
VisualGDB rewrites the gcc_Debug.h file when you change some settings (e.g. include directories) in VisualGDB GUI. You can skip this process by changing the include directories/preprocessor macros directly in the debug.mak file.
We are sorry that the Clang engine is causing you troubles. The behavior you are encountering is definitely not by design and it looks like either a conflict between VisualGDB and some other plugin or a bug caused by some rare configuration setting. I have attached a link to a diagonstic build to the other thread, please give it a try and let me know the output it provides. This should help us pinpoint the problem.
OK, strange. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.1.0.581.msi
Open the Clang IntelliSense diagnostics console, clear it, type the opening brace and observe the console output. Does it mention anything about the event being suppressed?
We have also added a fallback mechanism that should fix the indentation even if the auto-pairing did not get invoked.
Hi,
We have recently released a new toolchain containing an improved ESP8266 port of OpenOCD. We recommend using it for new projects instead of the unsupported xt-ocd tool.
OK, we have released a new ESP8266 toolchain that includes the newest SDKs and an improved OpenOCD port. You can update to it via Tools->Embedded Tools Manager.
A detailed tutorial on the new OpenOCD port is available here: http://visualgdb.com/tutorials/esp8266/openocd/
