Hi,

I'm getting this error:

Uploading 'SimpleNeoPixel01' to 'Nucleo-144' using 'COM29'
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
The uploader process failed
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination: file:///C:/Users/sscholl/Documents/Arduino/sketches/SimpleNeoPixel01/Debug/

For bug reports, read
     http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
embedded:startup.tcl:60: Error: Can't find target/target/stm32f4x.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 60

I've confirmed I have the stm32f4x.cfg in C:\ProgramData\VMicro\tools\openocd-0.10.0.1\scripts\target

I've attached a picture of my vmicro board settings and the board.buildinfo file.


thanks,
steve

---

Reviewing the command line produced in this situation it appears the folder reference is incorrect ("target/target/stm32f4x.cfg")

If you add a Local board.txt to the project (Right Click Project > Add > Local Board.txt), and add the below line to the file, it should work as expected:
[code]menu.pnum.NUCLEO_F429ZI.tools.openocd.upload.openocdscript=target/stm32f4x.cfg[/code]

We will confirm when this has been updated in the released software.

That change got me past the first error. I then encountered a second error.

embedded:startup.tcl:60: Error: Can't find C:\ProgramData\vmicro\tools\openocd-0.10.0.1/scripts/{build.openocdscript}
in procedure 'script'
at file "embedded:startup.tcl", line 60

That error was addressed in other posts on the site. Adding the following to board.txt fixed it.

build.openocdscript=target/stm32f4x.cfg

Debugging is working with those changes. Yay.

I am seeing one other error in the log, though it doesn't seem to have any obvious negative effects.

Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

thanks,
steve

Glad its working in Visual Micro as expected now.

The LIB_USB Error can be safely ignored, and if there are driver issues with debugging there is normally another line stating that "device %VID% %PID% cannot be located".

The latest release of Visual Micro resolves this, so the local board.txt entry should no longer be needed.