cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to get Core ID, No STM Target Errors

RAdam.1
Associate III

Hey there 

I have seen a few posts on this and tried a number of things:

1 I went through the process in the user manual and get the error shown

2. I tried to reboot board with the jumper moved to boot mode. I put it into UART mode but then got similar errors (Error Activating Device : KO. ...."

I get the same error on the programmer and the Cube IDE. USB cable is good (it works with other ST eval kits)

I'm running Windows 11, programmer is the latest v2.21.0, Cube is v2.0.0. I installed the cube expansion and built the beacon code. 

As a note, I can see the device using the ST BLE Toolbox and it shows as an Apple iBeacon and a peer to peer server and is unconnectable.

When I put the boot mode jumper on then power goes down to 0.26V when I connect over STLink.  And device does get hot but not sure if thats normal

 

 

 

 

 

Screenshot 2025-11-25 121648.png

2 REPLIES 2
TDK
Super User

> When I put the boot mode jumper on then power goes down to 0.26V when I connect over STLink.  And device does get hot but not sure if thats normal

No, not normal at all. Suggests you are shorting VDD to GND. It connects even though voltage is reported as 0.26 V? Anything connected to the board aside from the USB cable? Is it on a non-conductive surface?

If you feel a post has answered your question, please click "Accept as Solution".
RAdam.1
Associate III

Thanks TDK and I agree. Only goes to that voltage when the jumper is on the Boot Loader side. Jumper off it is fine at 3.3V, jumper on the Boot Loader side and I rescan the stlink and it drops to 0.26V and the regulator on the bottom heats up.. as you say, must be a short. when in that mode only..  

Nothing else connected and is on my wooden desk, very safe. 

 

Board functions when not in boot loader. but doesnt see the MCU via STLink

I ordered a new board from Arrow - so will see