cancel
Showing results for 
Search instead for 
Did you mean: 

STM32F103 bootloader issue

Tsugi.1
Associate II

Hi all.

I am using the STM32F103RBT6 microcontroller.

Some MCUs mounted on the board did not run the bootloader.

When I checked system memory ​address(0x1FFFF000 - 0x1FFFF800) with STM32CUBEIDE ,

The range of the address is filled with 0xff(attached file).

Is there any way to recover MCUs in this situation?

A picture of the faulty MCUs package is attached.

MCUs that can communicate with the bootloader have some binary written in the system memory.

Thank you

5 REPLIES 5
Tsugi.1
Associate II

The system memory of the MCU that can communicate with the bootloader is shown in the attached file.

Peter BENSCH
ST Employee

Welcome, @Tsugi.1​, to the community!

To exclude a fake as far as possible, please check the system memory (0x1FFFF000) and also the unique device ID (0x1FFFF7E8) with the STM32CubeProgrammer.

Regards

/Peter

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Tsugi.1
Associate II

Thank you for your reply.

the address of unique device ID(0x1FFFF7E8) is written some binary(attach file).

but address of system memory(0x1FFFF000) is filled with 0xff

Tsugi.1
Associate II

address of  system memory (0x1FFFF000) is filled with 0xff

TDK
Guru

Barring a weird STM32CubeProgrammer communication issue, your chip is likely counterfeit and is missing a bootloader. 0x1FFFF000 is in ROM which you can't write to. The UID looks bad as well.

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