''No ST-LINK detected'' when connecting with stm32f401RE board

Kristian Nielsen · ‎2017-06-21

Posted on June 21, 2017 at 13:50

I have a nucleo stm32f401RE board and it has been working fine for the most part.

Here recently, I followed a tutorial in the book ''mastering stm32'', where it said to install openocd. I had been following along

before this as well, and I had been able to connect to my board and flashing it with no problem. After attempting to get openocd to work though, this is no longer possible. Every time i try to connect to my board, I simply get the following error message:

I have not been able to find a solution for this anywhere, so I hope you guys can help! If there is anymore relevant information needed, just let me know.

Thank you very much.

o gaste · ‎2017-06-21

Posted on June 21, 2017 at 16:14

what probe are you using ?? what system are you working on ?

best bet are probe driver screwed up by openocd's one ... try reinstall it (

http://www.st.com/content/st_com/en/products/embedded-software/development-tool-software/stsw-link009.html

if using STlinkV2)

if on windows check in device control panel stlink v2 is recognise

Kristian Nielsen · ‎2017-06-21

Posted on June 21, 2017 at 16:30

Hey o gaste,

I?m working on windows 10. I unfortunately don?t know what you mean when referring to witch probe I am using?

I have already tried to update the drivers multiple times without any luck. Here is a picture of my device manager, which does not seem to contain the ''STMicroelectronics STLink dongle'':

Also, here is an image of my board, if that can give any clearance:

Thanks

o gaste · ‎2017-06-21

Posted on June 21, 2017 at 23:21

ok kristian

the board you are using is including a STLink dongle the small part where you usb plug is (witch I call also probe sorry it's a direct translation of french word and may be not accurate) you can use it also for flash other boards but here it looks binded to the nucelo as describe here

http://www.st.com/content/ccc/resource/technical/document/technical_note/group0/30/c8/1d/0f/15/62/46/ef/DM00290229/files/DM00290229.pdf/jcr:content/translations/en.DM00290229.pdf

anyway i think it's well known by windows under 'st link debug'

I sugest you to upgrade your probe (I checked it's the right word ) firmware by using this

http://www.st.com/content/st_com/en/products/embedded-software/development-tool-software/stsw-link007.html

(requiring a power off/on of your probe)

and check your board documentation about the 2 jumpers on the right side of usb plug

remember me why you have installed openocd ?? what EDI are you using ??

o gaste · ‎2017-06-22

Posted on June 22, 2017 at 14:42

I'm sorry I start to get stuck on your problem

OpenOCD is good when trying to debugunder gnu gdb or equivalent

I suppose you already tried to remove OpenOCD

if not I suggest you to try it and simply use Keil Microvision 5 free to debug

Kristian Nielsen · ‎2017-06-22

Posted on June 22, 2017 at 13:40

Thank you for your answer!

I am still having problems with the connection, and I still get the error message ''no st-link detected'' when i try to connect. I tried to upgrade my probe using the software that you linked, but that unfortunately had no effect. I tried both versions included, but got the following:

And with the other one, I simply get no device that I can choose, as seen here:

And there are no options in the dropdown menu.

I installed openocd since I am following along with a tutorial provided in the book I listed in my original post - ''Mastering STM32''. I was supposed to use it to debug my board, but as you can imagine, I haven't had much luck yet.

As for your other question, can you inform me what an EDI is? I have never heard this term before, so i don't really know the answer to it (Sorry about my lack of knowledge, I am very new to this haha).

- Kristian

Kristian Nielsen · ‎2017-06-22

Posted on June 22, 2017 at 14:56

I can understand that - it has been really frustrating, but thank you for your help so far.

I have removed OpenOCD but with no luck.

I donâ€™t really know where to go from here? Is there any other information that I could give you that might help? I can send images of the tutorial I followed, or I can send you the book as a pdf if that could resolve anything?

I would have no problem with using the Keil Microvision 5 for debugging, but I would still have to be able to connect to my device first correct?

Again, thank you very much for your help, I really appreciate it.

mike louaillier · ‎2017-06-23

Posted on June 23, 2017 at 20:38

Hello Kristian,

from your photo above it's clear that the jumpers on ur nucleo are correct, so it's very strange that the 'probe' could be bricked like that. (i call it a 'loader' since it is more often used just to load your program into the microController chip). the reason the nucleo board has slots in it is so that the loader part of the board can optionally be broken off once the uC has been programmed. But whether you separate it or not, it can be used independently of the main part of the board (by changing the jumpers) as a 'dongle' to program other stm devices or boards.

i've had the 'no st-link detected' when using the ST-Link Upgrade utility to upgrade my ST-Link dongle and usually got it working just by unpluging and repluging the device. But not always. i've had frequent problems with faulty usb cables.

maybe if you post the document you're using we can find what's wrong.

Akio Nakamura · ‎2017-06-24

Posted on June 24, 2017 at 13:37

Hello Kristian,

This may not really help you, but one reference information.

I hit the same problem a couple of months ago. I am also learning STMF32 on Eclipse, using the mastering stm32 book (Good book!). I tried several attempts to restore the connection, but all failed. At that time, I had Nucleo 32F303RE and 446RE.

Eventually, I utilized Windows 8.1 restoring function to put it back to the state of several days ago.

After that everything came back to normal.

I take a look at my current Windows hardware configuraiton and confirmed identical to what you showed on June 21, for the STM relevant items.

I suspect some of the related driver may have touched windows registry key (?). I am still not familiar with debugging feature on STM, due to lack of knowledge. I am using UART + TeraTerm to check the parameter, when needed.

Kristian Nielsen · ‎2017-06-24

Posted on June 24, 2017 at 22:35

Hello Akio,

Thank you very much for your answer!

I did in fact want to attempt to revert windows back to an earlier point, but I realized that currently do not have such a point, so that is unfortunately not possible. Good thinking though!