Skip to main content
ChrisH
ChrisH
Associate III
February 23, 2016
Question

Bug in STLink - OSX

  • February 23, 2016
  • 2 replies
  • 627 views
Posted on February 23, 2016 at 06:32

Unfortunately new STLink update bricked 3 of my boards (in terms of usability under OS X) again the issue is with libusb. Now I can't downgrade this firmware cause you cant find any older versions on the website. Apparently release notes mentioned sth about fixing problems with OS X well turns out there are new ones (old ones). I'm on fresh 4

Verbose output from terminal: 

libusb_handle_events() timeout
[!] send_recv
2016-02-23T05:31:00 DEBUG src/stlink-common.c: stlink mode: unknown!
libusb_handle_events() timeout
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: stlink mode: unknown!
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** stlink_enter_swd_mode ***
libusb_submit_transfer(-6)
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** looking up stlink version
libusb_submit_transfer(-6)
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: st vid = 0x0000 (expect 0x0483)
2016-02-23T05:31:03 DEBUG src/stlink-common.c: stlink pid = 0x0000
2016-02-23T05:31:03 DEBUG src/stlink-common.c: stlink version = 0x0
2016-02-23T05:31:03 DEBUG src/stlink-common.c: jtag version = 0x0
2016-02-23T05:31:03 DEBUG src/stlink-common.c: swim version = 0x0
2016-02-23T05:31:03 DEBUG src/stlink-common.c: notice: the firmware doesn't support a jtag/swd interface
2016-02-23T05:31:03 DEBUG src/stlink-common.c: notice: the firmware doesn't support a swim interface
2016-02-23T05:31:03 INFO src/stlink-common.c: Loading device parameters....
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** stlink_core_id ***
libusb_submit_transfer(-6)
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: core_id = 0x00000000
libusb_submit_transfer(-6)
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** stlink_read_debug32 0 is 0xe0042000
libusb_submit_transfer(-6)
[!] send_recv
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** stlink_read_debug32 0 is 0x40015800
2016-02-23T05:31:03 WARN src/stlink-common.c: unknown chip id! 0
2016-02-23T05:31:03 DEBUG src/stlink-common.c: *** stlink_close ***
Segmentation fault: 11

    This topic has been closed for replies.

    2 replies

    Amel NASRI
    Amel NASRI
    ST Technical Moderator
    February 23, 2016
    Posted on February 23, 2016 at 16:42

    Hi hockuba.krzyszto.002,

    Some STLink upgrade related issues are discussed [DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Discovery/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/STM32Discovery/ST%20Link%20upgraded%20to%20V2.J26.S0%20stopped%20working%20and%20cannot%20be%20downgraded&FolderCTID&currentviews=64]here. Please refer to SC's answer, it may bring you some help.

    If you still face issues even with SC's recommendations, please let me know in order to review your case.

    -Mayla-

    To give better visibility on the answered topics, please click on "Best Answer" on the reply which solved your issue or answered your question.
    ChrisH
    ChrisHAuthor
    Associate III
    February 23, 2016
    Posted on February 23, 2016 at 16:57

    Thank you for your reply, yes I'm facing same issues as the one mentioned in the discussion link. The only way to make stlink work again is downgrade, current version doesn't work under OS X and throws libusb errors basically stlink debugger is invisible completely under OS X.

    Terms & ConditionsAccessibility statement