Skip to main content
Visitor II
June 3, 2025
Solved

Onboard STLink-V2.1 on STM32MP157D-EV1 doesn't work

  • June 3, 2025
  • 2 replies
  • 553 views

Hi All,

We bought 3 STM32MP157D-EV1 boards (https://www.st.com/en/evaluation-tools/stm32mp157f-ev1.html)

While running in it as it is out of the box, we have found out that on-board STLink-V2.1 doesn't work at all when connected to Win11.

We've installed latest STM32CubeProgrammer and it actually installed latest STLink USB drivers (VCP and STLink) but despite all our efforts STLink doesn't work (LD06 doesn't glow) and Win11 Device Manager flags it as under error:

DubBartolec_0-1748919850585.png


Is there solution to this issue ?


 





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

    JP1 must be removed (otherwise it force the STLINK in reset in order to avoid conflict when using another debugger).

    Probably a manufacturing issue when they setup default jumpers.

    PatrickF_0-1748934434778.png

     

    Regards,

    2 replies

    Technical Moderator
    June 3, 2025

    Hi,

    I confirm board STLINK is running well on W11.

    Did you have JP1 removed ?

    Obvious, but please confirm you are using STM32MP157D-EV1 CN4 connector.

    Did you try another cable ? Type-A <-> Micro-B is recommended.

    Could you try an STLINK FW upgrade https://www.st.com/en/development-tools/stsw-link007.html 

     

    Regards.

    Visitor II
    June 3, 2025

    Hi @PatrickF 

    I've confirmed...

    • JP1 is inserted
    • We are using CN4
    • We tried several USB cables including one supplied with the board.
    • We tried upgrade as you recommended and it never detects ST-Link. It needs to do that in order to upgrade it:

      DubBartolec_0-1748932353831.png

      No matter what we do we end up with this (all three board on 4+ different Win11 laptops and computers).

      DubBartolec_1-1748932427047.png

      Here is photo of board. LD6 is not illuminating at all.

      DubBartolec_2-1748932490922.png

      What would be next thing to try ?

       

       

    PatrickFAnswer
    Technical Moderator
    June 3, 2025

    JP1 must be removed (otherwise it force the STLINK in reset in order to avoid conflict when using another debugger).

    Probably a manufacturing issue when they setup default jumpers.

    PatrickF_0-1748934434778.png

     

    Regards,

    Visitor II
    June 3, 2025

    Hi @PatrickF 
    Thanks STLink works now.