Not able to flash stm32g030c8t6 with st link v2

adityasatyaji · ‎2024-05-10

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

STM32CubeProgrammer v2.16.0

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

Log output file: C:\Users\adity\AppData\Local\Temp\STM32CubeProgrammer_a09404.log

ST-LINK SN : 37FF6C064243393022292357

ST-LINK FW : V2J43S0

Board : --

Voltage : 2.93V

SWD freq : 4000 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x466

Revision ID : Rev 1.1

Device name : STM32G03x/STM32G04x

Flash size : 64 KBytes

Start Address : 8000000

Device type : MCU

Device CPU : Cortex-M0+

BL Version : 0x53

Memory Programming ...

Opening and parsing file: ST-LINK_GDB_server_a09404.srec

File : ST-LINK_GDB_server_a09404.srec

Size : 37.62 KB

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 18]

Error: failed to erase memory

Encountered Error when opening C:\ST\STM32CubeIDE_1.15.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.200.202311302303\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Shutting down...

Exit.

EXUE.2 · ‎2024-05-11

it looks like you use STM32CubeIDE_1.15.0 to call STM32_Programmer_CLI.exe download the FW to STM32G03x/STM32G04x?

I have tried use independent STM32CubeProgrammer.exe (both v2.14.0 and v2.17.0) to download FW to STM32G0B1RE, it are worked, can you use independent STM32CubeProgrammer.exe to try it?

log as below:

14:44:24 : STM32CubeProgrammer API v2.14.0 | Windows-64Bits
14:44:57 : UR connection mode is defined with the HWrst reset mode
14:44:57 : ST-LINK SN : 066BFF383034434757243008
14:44:57 : ST-LINK FW : V2J45M30
14:44:57 : Board : NUCLEO-C092RC
14:44:57 : Voltage : 3.26V
14:44:57 : SWD freq : 4000 KHz
14:44:57 : Connect mode: Normal
14:44:57 : Reset mode : Software reset
14:44:57 : Device ID : 0x467
14:44:57 : Revision ID : Rev Z
14:44:57 : Debug in Low Power mode is not supported for this device.
14:44:57 : UPLOADING OPTION BYTES DATA ...
14:44:57 : Bank : 0x00
14:44:57 : Address : 0x40022020
14:44:57 : Size : 64 Bytes
14:44:57 : Bank : 0x01
14:44:57 : Address : 0x40022080
14:44:57 : Size : 16 Bytes
14:44:57 : UPLOADING ...
14:44:57 : Size : 1024 Bytes
14:44:57 : Address : 0x8000000
14:44:57 : Read progress:
14:44:57 : Data read successfully
14:44:57 : Time elapsed during the read operation is: 00:00:00.007
14:45:01 : Read File: C:\GitHub\NUCLEO-C092RC_G0B1RE\project_NUCLEO-C092RC_G0B1RE\EWARM\NUCLEO-C092RC_G0B1\Exe\NUCLEO-C092RC_G0B1RE.srec
14:45:01 : Number of segments: 1
14:45:01 : segment[0]: address= 0x8000000, size= 0x92A7
14:45:03 : Memory Programming ...
14:45:03 : Opening and parsing file: NUCLEO-C092RC_G0B1RE.srec
14:45:03 : File : NUCLEO-C092RC_G0B1RE.srec
14:45:03 : Size : 36.66 KB
14:45:03 : Address : 0x08000000
14:45:03 : Erasing memory corresponding to segment 0:
14:45:03 : Erasing internal memory sectors [0 18]
14:45:04 : Download in Progress:
14:45:05 : File download complete
14:45:05 : Time elapsed during download operation: 00:00:01.181

adityasatyaji · ‎2024-05-11

Hi EXUE.2, thank you for the reply. I am new to the stm32, But I have already tried to using the STM32CubeProgrammer but still it is not working, and the programming is crashing

adityasatyaji · ‎2024-05-11

10:08:08 : STM32CubeProgrammer API v2.16.0 | Windows-64Bits
10:08:37 : UR connection mode is defined with the HWrst reset mode
10:08:38 : ST-LINK SN : 37FF6C064243393022292357
10:08:38 : ST-LINK FW : V2J43S0
10:08:38 : Board : --
10:08:38 : Voltage : 2.94V
10:08:38 : SWD freq : 4000 KHz
10:08:38 : Connect mode: Under Reset
10:08:38 : Reset mode : Hardware reset
10:08:38 : Device ID : 0x466
10:08:38 : Revision ID : Rev 1.1
10:08:38 : Debug in Low Power mode is not supported for this device.
10:08:39 : UPLOADING OPTION BYTES DATA ...
10:08:39 : Bank : 0x00
10:08:39 : Address : 0x40022020
10:08:39 : Size : 108 Bytes
10:08:39 : Bank : 0x01
10:08:39 : Address : 0x40022080
10:08:39 : Size : 4 Bytes
10:08:39 : UPLOADING ...
10:08:39 : Size : 1024 Bytes
10:08:39 : Address : 0x8000000
10:08:39 : Read progress:
10:08:39 : Data read successfully
10:08:39 : Time elapsed during the read operation is: 00:00:00.010
10:08:49 : Memory Programming ...
10:08:49 : Opening and parsing file: SESNSOR_FRONT1.hex
10:08:49 : File : SESNSOR_FRONT1.hex
10:08:49 : Size : 37.74 KB
10:08:49 : Address : 0x08000000
10:08:49 : Erasing memory corresponding to segment 0:
10:08:49 : Erasing internal memory sectors [0 18]
10:08:50 : Download in Progress:
10:08:51 : File download complete
10:08:51 : Time elapsed during download operation: 00:00:01.330
10:08:51 : Verifying ...
10:08:51 : Read progress:
10:08:51 : Download verified successfully
10:08:51 : RUNNING Program ...
10:08:51 : Address: : 0x08000000
10:08:51 : Application is running, Please Hold on...
10:08:51 : Start operation achieved successfully
10:09:11:068 : fail @0x00000001
10:09:12:099 : fail @0x00000001
10:09:13:129 : fail @0x00000001
10:09:14:160 : fail @0x00000001
10:09:15:184 : fail @0x00000001
10:09:16:210 : fail @0x00000001
10:09:17:241 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:17:242 : fail @0x00000001
10:09:18:263 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:18:264 : fail @0x00000001
10:09:19:289 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:19:291 : fail @0x00000001
10:09:20:320 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:20:321 : fail @0x00000001
10:09:21:350 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:21:351 : fail @0x00000001
10:09:22:381 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:22:382 : fail @0x00000001
10:09:23:426 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:23:428 : fail @0x00000001
10:09:24:451 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:24:452 : fail @0x00000001
10:09:25:478 : r ap 0 @0x1FFF1FFE 0x00000004 bytes Data 0x00000053
10:09:25:479 : fail @0x00000001

program still not running

EXUE.2 · ‎2024-05-12

Hi @adityasatyaji , it looks like your FW downloading is success, but FW running is fail, I have some questions:

1. what kind of board are you using? development board of ST or design by yourself?

2. if you have checked your memory address allocation in .icf? maybe you can try a demo code of ST to debugging it by IAR or MDK-Keil.

3. 0x1FFF1FFE if the System memory of MCU, it is boot as below capture, if your boot pin configuration is right?

adityasatyaji · ‎2024-05-12

I am using my own design board and I have not checked the memory allocation as I am using the cube ide .

I will check the boot mode and reassign bits as per datasheet if they are changed. but I have not changed them in code or manually before anywhere so I need to find where they have changed.