2023-05-05 01:03 AM - edited 2023-11-20 06:24 AM
When using STM32CubeProgrammer to program STM32F103VET6, it is found that using the "page erase" function will erase the first page error by mistake (erase pages 1, 3, 5).
Upon inspection, it is found that the page erase data sent by STM32CubeProgrammer v2.13 is 0x03 0x01 0x03 0x05 0x00 0x04, while the data sent by STM32CubeProgrammer v2.7.0 is 0x02 0x01 0x03 0x05 0x05.
By consulting the AN3155 manual, it is found that the data sent by v2.7.0 is correct and the data stream sent by v2.13 is wrong.
2023-05-10 04:07 AM
I also found this error.
Here are 2 examples for STM32F103 (STM32_Programmer_CLI.exe with "-vb 3")
Erasing Segment <0> Address <0x08002000> Size <16>Bytes
Erasing internal memory sector 8
data sent successfully to target: 0x000808 - STM32CubeProgrammer v2.7 (correct)
data sent successfully to target: 0x01080009 - STM32CubeProgrammer v2.13 (incorrect erasing of sector 0x00)
Erasing Segment <1> Address <0x08002200> Size <17280>Bytes
Erasing internal memory sectors [8 25]
1108090a0b0c0d0e0f1011121314151617181910 - STM32CubeProgrammer v2.7 (correct)
1208090a0b0c0d0e0f101112131415161718193320 - STM32CubeProgrammer v2.13 (uncorrect erasing of sector 0x33)
2023-05-10 10:58 AM
Another message about this error. And no response from ST staff. https://community.st.com/s/question/0D53W00002A2S50SAF/erase-sectors-problem-frame-data-send-uart-connection-mode
2023-05-11 01:59 AM
Yes, I think it's a bug.