2025-04-21 4:17 PM
Hi All,
I'm new to using the STM32 and honestly had great grief trying to connect to the chip.
I'm using STlink V3 and designed my own PCB.
Trying to flash a F/W to the PCB.
I ordered the PCB from JLCPCB.
I keep getting unable to get core ID as a message and I can't figure out why?
I seem to be able to connect for a few seconds but than i get a message, unable to get core ID and it disconnects.
When I compile a code and try to flash it, it also tells me flash successful but I don't think the code got flashed successfully as the chip doesn't work as expected and also I am still unable to connect to it and i get messages unable to get Core ID.
Any help or suggestions? I have the RST connected to GND with a resistor, schematics attached.
2025-04-21 4:42 PM
> When I compile a code and try to flash it, it also tells me flash successful but I don't think the code got flashed successfully as the chip doesn't work as expected
If it says successful, it was probably successful. "doesn't work as expected" is probably a code bug. What does your code do? Keep it simple, blink an LED as a first test.
Run it in debug mode, step through, etc.
Schematic seems okay.
> I have the RST connected to GND with a resistor
Guessing this is a typo. A 1 nF cap to GND is fine.
2025-04-21 5:12 PM
Thanks for your reply.
I was under the same impression as you.
But using STM32CubeProgrammer i can never fully connect to the STM32 in the new PCBs.
It keeps telling me unable to get core ID.
Any idea why?
2025-04-21 5:23 PM
Try removing R62 and see if it improves
2025-04-21 5:23 PM - edited 2025-04-21 5:24 PM
If you cannot connect, what is telling you the flash was successful?
Could be a board manufacturing issue. Bad solder joint. Wrong orientation. No or insufficient power. Rather than guess, be objective about it.
2025-04-21 5:32 PM
would this play any affect?
The Schematic design is created using STM best guidelines.
Also why am i able to flash a firmware at times and not be able to connect to the chip?
2025-04-21 5:34 PM
"If you cannot connect, what is telling you the flash was successful?" i'm wondering the same exact thing.
I got the PCB made at JLCPCB, the chip has sufficient power. If it's wrong orientation i would not be able to connect not even for a few seconds and i would not be able to flash any firmware successfully using STM32cubeIDE
2025-04-21 6:24 PM
I got the PCB made at JLCPCB, the chip has sufficient power.
What is sufficient power supposed to mean? Are you 100% sure that Vdd is supplied to the STM32? If the STM32 does not have Vdd, STM32CubeProgrammer will complain about not getting the core ID.
Copy and paste the exact errors you're getting as there has to be more than just than one message..
2025-04-21 10:13 PM
Is there a BOOT0 that i need to connect to ground?
Do you know which pin this is looking at my schematics?
2025-04-22 5:02 AM
21:47:35 : STM32CubeProgrammer API v2.19.0 | Windows-64Bits
21:50:58 : UR connection mode is defined with the HWrst reset mode
21:50:58 : ST-LINK SN : 0019003C3133510A36303739
21:50:58 : ST-LINK FW : V3J16M7B5S1
21:50:58 : Board : STLINK-V3SET
21:50:58 : Voltage : 3.26V
21:50:58 : SWD freq : 50 KHz
21:50:58 : Connect mode: Under Reset
21:50:58 : Reset mode : Hardware reset
21:50:58 : Device ID : 0x466
21:50:58 : Revision ID : Rev Y
21:50:58 : Debug in Low Power mode is not supported for this device.
21:50:58 : UPLOADING OPTION BYTES DATA ...
21:50:58 : Bank : 0x00
21:50:58 : Address : 0x40022020
21:50:58 : Size : 108 Bytes
21:50:58 : Bank : 0x01
21:50:58 : Address : 0x40022080
21:50:58 : Size : 4 Bytes
21:50:58 : UPLOADING ...
21:50:58 : Size : 1024 Bytes
21:50:58 : Address : 0x8000000
21:50:58 : Read progress:
21:50:58 : Data read successfully
21:50:58 : Time elapsed during the read operation is: 00:00:00.129
21:50:59 : Error: Unable to get core ID
21:50:59 : Error: Unable to get core ID
21:50:59 : Warning: Connection to device 0x466 is lost
21:51:00 : Disconnected from device.
Even if i change modes or frequency or even reset mode.. same error log.. any suggestions?
Target voltage measured 3.28V which is within range.