Page 2 of 2
Re: Nucleo-32 boards
Posted: Tue Dec 01, 2015 12:32 pm
by Giovanni
It is the normal launch in ChibiStudio:
-c "telnet_port 4444" -s "/ChibiStudio/tools/openocd/scripts" -f "interface/stlink-v2-1.cfg" -f "${file_prompt}"
Giovanni
Re: Nucleo-32 boards
Posted: Tue Dec 01, 2015 12:45 pm
by Tabulous
Giovanni wrote:It is the normal launch in ChibiStudio:
-c "telnet_port 4444" -s "/ChibiStudio/tools/openocd/scripts" -f "interface/stlink-v2-1.cfg" -f "${file_prompt}"
Giovanni
just get this
Open On-Chip Debugger 0.10.0-dev-00107-ge4848fe (2015-11-13-11:49)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.htmlembedded:startup.tcl:60: Error: Can't find interface/stlink-v2-1.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 60
are you adding the serial number of the debug interface to the stlink interface driver ? because the nucleo32 board have two st-link interfaces
Re: Nucleo-32 boards
Posted: Tue Dec 01, 2015 12:59 pm
by Tabulous
Tabulous wrote:Giovanni wrote:It is the normal launch in ChibiStudio:
-c "telnet_port 4444" -s "/ChibiStudio/tools/openocd/scripts" -f "interface/stlink-v2-1.cfg" -f "${file_prompt}"
Giovanni
just get this
Open On-Chip Debugger 0.10.0-dev-00107-ge4848fe (2015-11-13-11:49)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.htmlembedded:startup.tcl:60: Error: Can't find interface/stlink-v2-1.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 60
are you adding the serial number of the debug interface to the stlink interface driver ? because the nucleo32 board have two st-link interfaces
its working now
