[OpenOCD-devel] [openocd:tickets] #149 ST-Link Unsupported status code 0x09

[steve <ra...@us...>]

Uwe,
I think the error code you've found is right, and should be added - I've been doing some more debugging, and am getting an ID code of zero returned.
Will pursue your suggestion of 'deep sleep' - that could have happened in the course of messing around.
I tried Paul's suggestion on reset, and that enabled me to connect sufficiently to get back the ID code, although it did give an error message! `Error: BUG: can't assert SRST`
Will investigate further.


---

** [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 01:56 PM 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 ope...@li... 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.