cancel
Showing results for 
Search instead for 
Did you mean: 

core locked up and read out fails

Arno1
Senior

Hi,

My STM32H735G-DK is having issues.

When I try to flash a known good firmware, I get the following:

command: STM32_Programmer_CLI -c port=SWD freq=4000 mode=UR --erase all -d build/stm32h735.bin 0x08000000 -v --start 0x08000000

-------------------------------------------------------------------
                  STM32CubeProgrammer v2.5.0
-------------------------------------------------------------------
 
ST-LINK SN  : ***
ST-LINK FW  : V3J7M2
Board       : STM32H735G-DK
Voltage     : 3.28V
SWD freq    : 8000 KHz
Connect mode: Under Reset
Reset mode  : Hardware reset
Device ID   : 0x483
Revision ID : Rev Z
Device name : STM32H72x/STM32H73x
Flash size  : 1 MBytes
Device type : MCU
Device CPU  : Cortex-M7
 
 
Mass erase ...
 
Mass erase successfully achieved
 
 
Memory Programming ...
Opening and parsing file: sbsfu_H735.elf
File          : sbsfu_H735.elf
Size          : 54008 Bytes
Address       : 0x08000000
 
 
Erasing memory corresponding to segment 0:
Erasing internal memory sector 0
Download in Progress:
[==================================================] 100%
 
File download complete
Time elapsed during download operation: 00:00:00.224
 
 
 
Verifying ...
 
 
Read progress:
 
 
Error: Failed to read memory at address 0x08000000 during verification
 
 
Error: Download verification failed
 
 
 
RUNNING Program ...
Address:      : 0x8000000
Warning: The core is locked up
Start operation achieved successfully

This could be due to perhaps writing a wrong sbsfu project in the past (for H753)

When in STM32CubeProgrammer I try to read the flash out I always get "Error: Data read failed". only when reading from address 0x600, 0x100 bytes I can read all zeroes. Any other address until 0x08080000 gives me the error.

When looking at the option bytes, RDP is set to AA (never set it to CC but tried using BB then AA to try and reset it) and WRP is all checked (not active).

SEC_AREA_END has a lower value than SEC_ARE_START so it should be disabled.

Any way I can resolve this? I really hope my device isn't bricked.

Thank you

1 ACCEPTED SOLUTION

Accepted Solutions
Arno1
Senior

Well, I fixed it.

Turns out PCROP start was set to 0x6 and end to 0x8. After some fiddling I managed to set it to 0xff and 0x00 while also flipping RDP to BB and back to AA.

View solution in original post

6 REPLIES 6
Arno1
Senior

Well, I fixed it.

Turns out PCROP start was set to 0x6 and end to 0x8. After some fiddling I managed to set it to 0xff and 0x00 while also flipping RDP to BB and back to AA.

Javier1
Principal

i have a similar problem

when trying to flash with stm32cubemx gui some bins

i get the same :0693W000007ExAkQAK.png

we dont need to firmware by ourselves, lets talk
MQi.1
Senior II

PCROP, where is it? I got the same problem:

0693W000008woWAQAY.png0693W000008woWFQAY.png0693W000008woWKQAY.png0693W000008woWZQAY.pngactually, I met this issue because when I run in STM32CubeIDE, it couldn't download code into the board:

0693W000008woWeQAI.png 0693W000008woWGQAY.png

I'm getting that same issue right now, were you ever able to fix it?

MQi.1
Senior II

My solution:

  1. plug out, wait a little time, plug in, then reprogramming.
  2. alternately programming by CubeIDE and CubeProg.
DPatr.2
Associate III

I had this issue after pulling the code from remote server.

In project structure, inside "Core"

There has to have "Startup" Folder with startup_stm32f429zitx.s file inside

I am using STM32F429ZIT6, yours might be different.

We thought this file was autogenerated by CubeMX but it looks not.