Skip to main content
Explorer II
October 29, 2020
Solved

STLink not working on new MacBook Pro

  • October 29, 2020
  • 3 replies
  • 2312 views

I am trying to program a STM32F411E-DISCO with a new MacBook Pro. I installed STLink and then I installed the IDE. When I try to debug, the IDE says no STLink is detected.

Here is a screenshot of my debug config.

0693W0000059juqQAA.png 

Here is a screenshot of the STLink Upgrade window

0693W0000059juvQAA.pngAll the jumpers are on the board.

Thanks for your help!

    This topic has been closed for replies.
    Best answer by TDK

    The board has two USB ports. Make sure you're using the correct one (CN1), which is a USB-mini, not a micro. Make sure you're not using a charging cable.

    3 replies

    TDKAnswer
    Super User
    October 29, 2020

    The board has two USB ports. Make sure you're using the correct one (CN1), which is a USB-mini, not a micro. Make sure you're not using a charging cable.

    Explorer II
    October 29, 2020

    Thank you for your quick reply!

    I am sure I am connected to the correct port.

    How can I determine if I am using a charging cable rather than a data cable?

    ST Employee
    October 29, 2020

    Hi,

    You must install the Ide with the 1.4.0 installer (not from an update of a previous version), it should then install STLinkServer and if STlinkServer is installed correctly, it should work.

    Did you have an error installing STLinkServer application ?

    Rgds,

    Laurent

    Graduate
    November 11, 2024

    Hello. The following is machine-translated so it might seem a bit strange. I'd like to ask if I can use my only computer, the "MacBook Pro with M1 version", to connect to ST-LINK V2 to program the STM32 on a C8T6 chip's PCB board. I've tried using V1 before but without success. STM32CubeIDE couldn't recognize ST-LINK, and thus it wasn't able to program. I hope you can help me solve this problem. Thank you very much.

    Explorer II
    October 29, 2020

    Well as it turns out, @TDK​ was correct. I had a charging cable...or maybe a bad cable. When I changed it, everything started working. Thank you both for helping me!