[HELP] Not a genuine ST Device

[Ahmad_k]

I have bunch of STM32F103 mcu that I thought they are originals, I can flash them normally and my project works 100%. Now I am trying to debug a new project but keil threw this error "Not a genuine ST Device"

I checked the ID (0x2BA01477) and yes it was not genuine, the correct ID must be 0x1BA01477

Does anyone know a way to debug those chip without using OpenOCD ?

[pickit2]

Just a thought can you change the ID in the software to match the fake ID.

[Ahmad_k]

Just a thought can you change the ID in the software to match the fake ID.

Keil and STM32CubeIDE are now checking vendor ID first , both software call a function named JEP106ID which must return 0x20 for genuine, I patched that. the remaining is the Chip ID which I don't know where they are hiding it.

[Manuel]

If it's not coded in software maybe you can 'patch' some descriptor file....

check here:
https://community.platformio.org/t/debugging-of-stm32f103-clone-bluepill-board-wrong-idcode/14635

have ho idea if it can help.

take care.
X!

[Ahmad_k]

After a lot of work, I was able to debug some of the clones but only with keil which is great. Some of the clones mcu still not able to work with them.

I have patched the vendor id. Debug is working with stlink and jlink

[Kombinator]

Hello
I have chips with both revisions  0x2BA01477 and 0x1BA01477
At revision 0x2BA01477.
Keil gives me the message both when recording and when debugging the controller. But after the message it overwrites the flash and debugs the controller normally.....
 

[Ahmad_k]

Are you using latest MDK version ? For me I cannot debug after that message pop up, anyway I have patch it and it is working now.

[Kombinator]

I use MDK 5.36. 0    and compiler version5  hard.  ST-Link FW  V2J45S7
I'm working on simple projects that don't require me to change compiler settings.
/////////////

I installed on the new version of the 5.39 compiler and had problems programming and debugging the controller with IDCODE  0x2BA01477
The problem is not in the compiler !!!
The problem is in the fake inscription on the controller housing!!!
Vendor: MindMotion , GigaDevice   ...   And more clones
32F103x8x
The problem is to understand what was written.
My controller was written MM32F103C8
After I loaded from Pack Installer  Device: MindMotion  -  MM32F103C8   and changed the device of the project, everything worked normally at first sight!!!

Something that worries me!!!
Keil uses algorithms for working with the flash of each controller that are loaded into RAM. Keil works with different algorithms for the different STM32F103 clones. Anyone interested in viewing KEIL files with a .FLM extension
Surprises are possible if the Keil code changes.