Check with -v if there is some successfull communication with the device? I
suspect not, perhaps the device is in deep sleep or openocd refuses to attach,
as I have seen often with openocd.
Otherwise some header file tells 0x09 = STLINK_JTAG_IDCODE_ERROR.
---
** [tickets:#149] ST-Link Unsupported status code 0x09**
**Status:** new
**Milestone:** 0.9.0
**Created:** Fri Mar 31, 2017 11:44 AM UTC by steve
**Last Updated:** Fri Mar 31, 2017 11:44 AM UTC
**Owner:** nobody
Using STM32L031 Nucleo for detailed investigation, although suspect similar
problem on STM32L050 Nucleo. Running ST-Link software 2J28M18 (latest as of
now). OpenOCD release 0.10 final
Fails to connect to target.
Relevant debug output:
~~~
Debug: 256 47 stlink_usb.c:817 stlink_usb_init_mode(): MODE: 0x01
Debug: 257 47 stlink_usb.c:442 stlink_usb_error_check(): unknown/unexpected
STLINK status code 0x9
Error: 258 47 stlink_usb.c:1779 stlink_usb_open(): init mode failed (unable to
connect to the target)
~~~
Looking in the source, this status code does not appear to be recognised at all
- presumably recent addition.
I tried reducing clock speed from 300kHz to 100kHz without any difference.
Note: I can connect to the target using ST-Link.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
