Skip to main content
EHeo.1
Associate
November 27, 2020
Solved

How to write FW to stm32g070 by CubeProgrammer via UART

  • November 27, 2020
  • 1 reply
  • 794 views

I want to program the FW via UART.

Read and erase function are working fine, but write function is not working with below error message.

Anybody has a knowhow about this problem?

 14:35:12 : Port configuration: parity = even, baudrate = 115200, data-bit = 8,           stop-bit = 1.0, flow-control = off

 14:35:12 : Activating device: OK

 14:35:12 : Chip ID: 0x460 

 14:35:12 : BootLoader protocol version: 3.1

 14:35:14 : UPLOADING OPTION BYTES DATA ...

 14:35:14 :  Bank     : 0x00

 14:35:14 :  Address    : 0x1fff7800

 14:35:14 :  Size     : 52 Bytes

 14:35:14 :  Bank     : 0x01

 14:35:14 :  Address    : 0x1fff7870

 14:35:14 :  Size     : 4 Bytes

 14:35:15 : UPLOADING ...

 14:35:15 :  Size     : 131072 Bytes

 14:35:15 :  Address    : 0x8000000

 14:35:15 : Read progress:

 14:35:30 : Data read successfully

 14:35:30 : Time elapsed during the read operation is: 00:00:15.095

 14:35:42 : Memory Programming ...

 14:35:42 : Opening and parsing file: **

 14:35:42 :  File     : **

 14:35:42 :  Size     : 126 KBytes

 14:35:42 :  Address    : 0x08000000 

 14:35:42 : Erasing memory corresponding to segment 0:

 14:35:42 : Erasing internal memory sectors [0 62]

 14:35:43 : Download in Progress:

 14:36:13 : Timeout error occured while waiting for acknowledgement.

 14:36:13 : Error: Write Operation fails at address 0x8000000

 14:36:13 : Error: failed to download Segment[0]

 14:36:13 : Error: failed to download the File

 14:36:13 : RUNNING Program ... 

 14:36:13 :  Address:   : 0x08000000

 14:36:43 : Timeout error occured while waiting for acknowledgement.

 14:36:43 : Error: START command not acknowledged!

 14:36:43 : Error: Start operation failed

 14:36:45 : Timeout error occured while waiting for acknowledgement.

 14:36:45 : Error: GETID command not acknowledged!

This topic has been closed for replies.
Best answer by EHeo.1

For people in the same situation as me, I leave the way I solved.

I tried using the UART built in STLINK-V3, but the above phenomenon occurred.

After that, I tried again using the TTL cable, and it was written correctly.

1 reply

EHeo.1
EHeo.1AuthorBest answer
Associate
December 3, 2020

For people in the same situation as me, I leave the way I solved.

I tried using the UART built in STLINK-V3, but the above phenomenon occurred.

After that, I tried again using the TTL cable, and it was written correctly.