Problems with OpenOCD
Running OpenOCD on the command line with debug turned on yields this:
Debug: 212 420 command.c:145 script_debug(): command - ocd_ransport ocd_transport init
Debug: 214 420 transport.c:240 handle_transport_init(): handle_transport_init
Debug: 215 420 hla_transport.c:154 hl_transport_init(): hl_transport_init
Debug: 216 420 hla_transport.c:171 hl_transport_init(): current transport hla_swd
Debug: 217 430 hla_interface.c:44 hl_interface_open(): hl_interface_open
Debug: 218 430 hla_layout.c:42 hl_layout_open(): hl_layout_open
Debug: 219 430 stlink_usb.c:1602 stlink_usb_open(): stlink_usb_open
Debug: 220 430 stlink_usb.c:1619 stlink_usb_open(): transport: 1 vid: 0x0483 pid: 0x3748 serial:
Error: 221 566 stlink_usb.c:1632 stlink_usb_open(): open failed
Debug: 222 566 hla_layout.c:49 hl_layout_open(): failed
Debug: 223 566 command.c:628 run_command(): Command failed with error code -4
User : 224 576 command.c:689 command_run_line(): in procedure ‘init’in procedure ‘ocd_bouncer’
Debug: 225 576 command.c:628 run_command(): Command failed with error code -4
User : 226 576 command.c:689 command_run_line():
Debug: 227 576 hla_interface.c:119 hl_interface_quit(): hl_interface_quit
That is the correct USB device, ST-LINK has no problems opening it. I am sure ST-LINK is not running when I run OpenOCD.
Don’t know why the stlink_usb_open would fail.
Another programmer here says he has had problems after running released code (which I did) because the options bits were set to protect the device.
But ST-LINK can erase the device, and ST-LINK says the device is not protected.
-Matt
;){kind=link}