2024-07-06 05:08 AM
Solved! Go to Solution.
2024-07-06 09:03 AM - edited 2024-07-06 11:18 AM
Dear @Glowing_Brick ,
Indeed this is not our STLink and not produced by ST , this is a clone most probably. So issue is coming from there .
Similar Discussion here :
STOne-32
2024-07-06 05:20 AM
Dear @Glowing_Brick ,
Welcome in STCommunity , is that possible to have a picture of the top marking of your device ? To check is the MCU is a genuine one . We have seen similar posts and behavior and at the end the MCU was not from ST and ST-link detect it .
Hope it helps ,
STOne-32
2024-07-06 07:44 AM
Of course. Thank you for your kindness
The SWD id of it is 0x2ba01477,Seems consistent with the manual
2024-07-06 08:06 AM
Hi @Glowing_Brick ,
Thank you .
No particular visible issue but I still have some doubts - how you flashed a code ? Is that possible to Program via ST-Link and STM32CubeProgrammer and read the UniqueID etc ? Or may be also ST-Link issue if possible to have a picture as well .
Ciao
STOne-32
2024-07-06 08:53 AM
Thank you for your help :)
I directly flashes the code at 2.3V.... The UniqueID read from 0x1FFF 7A10 is:
0x540057 0x31385113 0x31363930
I’ve previously used this ST-Link for debugging an STM32F103 without any problems. here's a picture of the ST-Link after removing its case.
Could this issue potentially be related to the circuit design? Since this core board is homemade and this is its first test, I don't know if there might be a critical design flaw ...
2024-07-06 09:03 AM - edited 2024-07-06 11:18 AM
Dear @Glowing_Brick ,
Indeed this is not our STLink and not produced by ST , this is a clone most probably. So issue is coming from there .
Similar Discussion here :
STOne-32