Skip to main content
Visitor II
January 20, 2021
Question

ST-Link firmware verification - No ST-LINK detected found a strange way to fix

  • January 20, 2021
  • 9 replies
  • 9786 views

I have been struggled for several days. I have to plug in the board very quick and open the firmware update page on stm32 cubeIDE and update. After update, I can debug and can only last for 5 to 10 seconds. After that, I have to unplug and replug again and update the firmware again to be able to debug. Otherwise, keep showing: ST-Link firmware verification - No ST-LINK detected

    This topic has been closed for replies.

    9 replies

    Technical Moderator
    January 20, 2021

    Hello,

    To put you post in the right forum topics, could you please give more information on the product you are using (STM32 part number, nucleo/disco/etc.. board reference, ST-Link standalone, version, etc...).

    Regards.

    yunia.3Author
    Visitor II
    January 20, 2021
    Hi
    I am using nucleo board g474re. And I am using cubeIDE
    ST Employee
    January 20, 2021

    Hi,

    For STLink firmware upgrade, you can use directly the menu Help => STLink upgrade.

    You only need to do it once normally.

    Did you install STM32CubeIde or update the version ?

    You must install STM32CubeIde (v1.5.1 is the latest) with the installer to have STLink server installed.

    Rgds,

    Laurent

    yunia.3Author
    Visitor II
    January 20, 2021
    I am using the STM32CubeIde v1.5.1 now. Which I tried a lot of ways before like updating, uninstall, reinstall old and new versions several times since it used to works for 1.3 version( now even I changed back to 1.3, is not work)
    The strange thing is that if I do not do Help => STLink upgrade every time. It shows no stlink detected. And each firmware update only valid for 5 to 10s for me to debug(which can find the stlink and run on nucleo board). After that, I have to start the whole process again like, unplug usb, plug in, quickly open firmware update page either on cubeIDE or cube programer or utilities. I think it is my laptop issue since I have tried changed cables, new nucleo board etc. but I checked all my computer usb driver is up to date and the st debug server is all up to date.
    ST Employee
    January 20, 2021

    Try to use the installer to install the STM32CubeIde (v1.5.1).

    It will install the STLink usb driver (though you have them already with v1.3.0 install) and the latest STLink server tool and then you should be able to debug.

    Check the usb cable and also the usb connector, maybe there is an issue on the USB connector of nucleo board ?

    In Windows Device Manager, If you can see the STLink debug in USB devices, it should be ok.

    What you could do also is to install STM32CubeProgrammer and mass erase the device to be sure you don't have an application code messing with the board.

    Rgds,

    Laurent

    yunia.3Author
    Visitor II
    January 20, 2021

    0693W000007By0QQAS.png0693W000007By0LQAS.png0693W000007BxzcQAC.png

    yunia.3Author
    Visitor II
    January 20, 2021

    Hi,

    I did used the installer to install the STM32CubeIde (v1.5.1). And I have to used the above process to debug otherwise it always shows No ST-LINK detected.

    I checked and I know it has latest STLink server tool but I think on my laptop is not working. I changed several usb cables and I just bought a new nucleo board and still not work.

    In Windows Device Manager, I can see the STLink debug in USB devices, but still not work.

    I tried to manually search for the driver in ST folder and it cannot be changed.

    In STM programmer, I have to do the same thing to be able to find the board: quickly install the usb and click "firmware update" and it can be detected for just several seconds. Btw, How do I mass erase the device?

    ST Employee
    January 20, 2021

    Mass erasing the device can be done with the eraser (bottom left button).

    I suggest you to connect with hardware reset and connect under reset.

    But you must solve your stlink issue first I suppose.

    yunia.3Author
    Visitor II
    January 20, 2021
    How to do I solve the st link issue. I have been struggling for several days. I think the main issue is the laptop does not know to start st link and they consider as a usb and I am not sure what st link server I can try. I try to download from st website or reinstall it from cubeIDE folder. When I try the st link server exe, it seems not start installing.
    ST Employee
    January 20, 2021

    stlink server is installed when you install STM32CubeIde with installer.

    No need to reinstall it.

    I don't understand your issue "laptop does not know to start stlink" ?

    If you have connected the usb of stlink, usb enumerates and you see it in device manager, so it is started and should work.

    Maybe you played with jumpers on Nucleo board ?

    The two jumpers for STLink debug should be on if you see it in device manager.

    I don't know how to help, try the board and usb cable on another computer to check that the hardware is ok.

    And mass erase the device on this computer.

    Then try again on this laptop.

    Rgds,

    Laurent

    yunia.3Author
    Visitor II
    January 24, 2021

    Hi

    I tried a lot of times, only first several seconds can detect the st-link on Cube Programmer. And every time if I want to fix this, I have to plug in the usb and quickly open the firmware upgrades in CubeIDE or Cube programmer, and do the upgrade. After upgrade, I have to debug within several seconds to be able to find the st link. After several seconds, when I try to debug again, it losts st-link and shows the message again:No ST-LINK detected. I changed a laptop but still using thinkpad and does not work. All the usb driver is updated and the st0link debug can show in the "device manager". Where to find the two jumpers for STLink debug should be on in device manager and what are the names for the two jumpers

    ST Employee
    January 25, 2021

    Hi,

    I was talking about the 2 jumpers on the Nucleo to debug the mcu but it is not on all nucleo boards.

    And if you can debug, they are ok.

    If you can see the stlink for a few seconds, maybe it is the overcurrent limitation (PC shuts down the usb port).

    Try to boot in bootloader mode to erase the device with CubeProgrammer.

    To do that, you should set the Boot0 pin to VDD with a wire when you supply the board.

    Boot0 pin is available on the headers.

    After mass erase, you can remove the wire and reboot the board.

    Rgds,

    Laurent

    Visitor II
    January 20, 2021

    Possibly the Laptop USB Port damaged and can't supply enough power?

    Is STLink directly connected to Laptop, or through a USB Hub?

    • If STLink directly connected to Laptop: try putting a powered USB hub between so laptop doesn't have to power STLink
    • If Hub between: Try removing it and directly plugging ST Link into Laptop USB Port.
    • What kind of USB ports does laptop have (USB1, USB2, USB3, USBC...)

    Paul

    yunia.3Author
    Visitor II
    January 25, 2021

    The STLink directly connected to Laptop and I tried use a usb hub and use usb type c on laptop and still not work.

    I always use regular usb A in the past.

    Visitor II
    January 25, 2021
    1. Exit TouchGFX before running CubeIDE, Don't run IDE and TouchGFX at same time (till that issue is fixed)
    2. Is board powered by STLink during Programming? If yes then check Power consumption of your board. Consider powering board directly during programming. Try a different board.
    Graduate II
    January 25, 2021

    Is this a corporate laptop with a preclusion to allowing external memory drives, or AV software with similar functionality?​

    Graduate II
    January 25, 2021

    I'd perhaps also look at the Upper/Lower Filters attached to the USB MSC driver stack.

    Watch for performance tools looking to benchmark the external storage, there was an Intel Profiler that did something like that, perhaps a Microsoft one, and there was also a DELL Remote Diagnostic Agent tools that also interfered with normal system operation.

    If you have competent IT staff have them review the situation.