AnsweredAssumed Answered

STM32F103 - Bootloader Init Problem

Question asked by sauer.michael.002 on Jul 10, 2015
Latest reply on Jul 14, 2015 by Clive One
Hi,

now i run into an other problem with the bootloader on the Nucleo Boards STM32F103 chip.
Im building an Android Library to update the STM32 Firmware over Bluetooth (RS232) and add from time to time each processor.
I successfully implemented F401 and F429 already and their bootloader react as expected
But if i try to init the F103 the same way like the F401 or the F429 i got no responses like described in application note.
Is this a bug in the bootloader or is this an issue of my .. whatever? ;)

Here i do a simple overview of the commands or bytes i send:

Nucleo Board STM32F103RB Bootloader
Bootloader ID: 0x22
Usually, as described in AN:

Send: 0x7f (Init Command)
Recv: 0x79 (ACK)

Send: 0x00 0xFF (GET Command)
Recv: 0x79 (ACK) + Answer from GET Command + 0x79 (ACK)

But it only works like this:
Send: 0x7f (Init Command)
Recv: 0x79 (ACK)

Send: 0x7f (Init)
Recv: 0x1f (NACK, means connection closed unsuccessfully last time)

Send: 0x00 0xFF (GET Command)
Recv: 0x79 (ACK) + Answer from GET Command + 0x79 (ACK)

--------------------------------------------------------------------

Nucleo Board STM32F401RE Bootloader works as expected
Bootloader ID: 0x31

Send: 0x7f (Init)
Recv: 0x79 (ACK)

Send: 0x00 0xFF (GET Command)
Recv: 0x79 (ACK) + Answer from GET Command + 0x79 (ACK)

--------------------------------------------------------------------

STM32F4 Discovery Board STM32F429ZI Bootloader works as expected
Bootloader ID: 0x31 (No Option Bytes in GVRP)

Send: 0x7f (Init)
Recv: 0x79 (ACK)

Send: 0x00 0xFF (GET Command)
Recv: 0x79 (ACK) + Answer from GET Command + 0x79 (ACK)

Outcomes