Skip to main content
ask6483
Associate
September 1, 2026
Solved

STM32C011 ROM bootloader has a version bug

  • September 1, 2026
  • 6 replies
  • 64 views

Hello,

I’m recently working on utilizing ROM I2C bootloader on STM32C0116F6U6, Device ID: 0x443, Rev Z.
It seems that bootloader is reporting wrong version 0x11 instead of 0x12, while I got reply to GET command (0x00) from protocol v1.2 instead of v1.1 - there is clearly a byte 21 (0xA1) in reply (which is protocol v1.2 according to AN4221). Get as well as get version command are both returning 0x11.

Because of this bug utilities like stm32flash are failing by not reading all bytes after issuing get command. stm32flash will try to resync by writing bad command (0xFF) and waiting for NACK but bootloader can keep clock line low for up to 6.2s if all bytes from previous transaction were not read.

LA outputs, Get version:
 

 

Get command is returning 0xA1 byte which should not be there:
 

 

stm32flash too short get command read (it was expecting protocol v1.1), clock line will be hold low for 6.23s after writing resync byte (0xFF):
 

 

Best answer by mƎALLEm

The team confirmed the bootloader is OK but the issue resides in the documentation  i.e. in the AN4221 page 10:

Byte 21 is missing in this list and the bootloader V1.1 has 0xA1 in Byte 21. The document will be updated accordingly.

6 replies

mƎALLEm
ST Technical Moderator
September 1, 2026

Hello ​@ask6483 and welcome to the ST community,

Could you please confirm my understanding?

So by sending Get Version command, you are receiving bootloader version V1.1 according to the value 0x11 shown by the logic analyzer:

While by sending Get command, you are receiving this pattern:

which corresponds to bootloader version 1.2 according to what was described in the AN4221 Rev 14/ page 11: 

Could you please confirm my understanding so I can escalate it internally afterward?

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
ask6483
ask6483Author
Associate
September 1, 2026

Exactly this, version seems wrong. Command set is returned for version v1.2. Note that I didn't tried if 0xA1 is actually working or not.

mƎALLEm
ST Technical Moderator
September 2, 2026

Hello,

Ok thank you for the confirmation, I’ll escalate the case over the internal ticket CDM0065488 (not accessible by the community users).

I’ll get back to you as soon as I have a feedback.

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
mƎALLEm
mƎALLEmBest answer
ST Technical Moderator
September 2, 2026

The team confirmed the bootloader is OK but the issue resides in the documentation  i.e. in the AN4221 page 10:

Byte 21 is missing in this list and the bootloader V1.1 has 0xA1 in Byte 21. The document will be updated accordingly.

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.
ask6483
ask6483Author
Associate
September 3, 2026

Ok, thank you.