Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Unable to start debugging with STM32F429 (Read 2839 times)
Steve Scholl
Junior Member
**
Offline


Posts: 16
Joined: Jan 29th, 2020
Unable to start debugging with STM32F429
Feb 1st, 2020 at 6:34pm
Print Post  
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
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: Unable to start debugging with STM32F429
Reply #1 - Feb 3rd, 2020 at 10:09am
Print Post  
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
Select All
menu.pnum.NUCLEO_F429ZI.tools.openocd.upload.openocdscript=target/stm32f4x.cfg 



We will confirm when this has been updated in the released software.
  
Back to top
 
IP Logged
 
Steve Scholl
Junior Member
**
Offline


Posts: 16
Joined: Jan 29th, 2020
Re: Unable to start debugging with STM32F429
Reply #2 - Feb 4th, 2020 at 3:44am
Print Post  
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


  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: Unable to start debugging with STM32F429
Reply #3 - Feb 4th, 2020 at 8:44am
Print Post  
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".
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2145
Joined: Feb 13th, 2019
Re: Unable to start debugging with STM32F429
Reply #4 - Feb 5th, 2020 at 11:55am
Print Post  
The latest release of Visual Micro resolves this, so the local board.txt entry should no longer be needed.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint