Skip to main content
Associate II
Oct 29, 2026 5:10 AM UTC
Question

S25FS512SDSBHV213 Flash erase failed STM32N657

Hello Team, 

We are currently facing a same issue as STM32N6570-DK: Cannot erase external Flash. and 

but i think they were facing this issue on the EVK ( STM32N657-DK ), here we are facing the issue in our custom design. 

what happened till now :
1.  We received boards and tried to flash, got a success tested multiple binaries also able to erase the flash using the cube programmer. 
2.  suddenly we are unable to flash any new binary and not able to erase the external flash :(.
3. tried the suggested methods to erase the flash from the community but failed. 

  1.  tried with both the external loaders  MX25YM51245G and MX66UW1G45G.

seeking for the help from you guys if any one can it would be really appreciated. 

Attaching the OTP dump here 
Thanks and regards 
Harsh

2 replies

Kouthair
ST Technical Moderator
Oct 30, 2026 9:14 AM UTC

Hello ​@Harsh_Bhavsar & welcome to the community,
Is the N6 in DEV BOOT configuration (BOOT0 LOW, BOOT1 HIGH) when you are trying to program the flash?
What are the steps that you are using to perform the erase operation? Please provide any additional information that could be helpful.
I’d also suggest looking into :
 

 

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Associate II
Nov 2, 2026 9:44 AM UTC

Hello ​@Kouthair, 

Thank you for the response, Yes the MCU is in DEV BOOT condition when we are programming the flash. 
The external Loader selected in the cube programmer is MX25UM51245G_STM32N6570-NUCLEO. 
I am using the Erase external memory in the Erase & Programming tab.

Here what is happening is this issue, we initially noticed in one board which we were using previously for testing and we flashed multiple binaries in it. then after 2nd and now today the 3rd board today. 

in one board we replaced the flash chip and flashed a binary which is flashed in the other working board whose flash is not locked after that image. but the board in which the FLASH chip is replaced locked again….. 

We are not  getting the root whether the MCU is the problem OR binary is the problem OR the FLASH itself is the problem. 

Because of the binary’s limitation we are not able to read the content of the flash, we wanted to read protection registers of it. 

we are stuck  here :( 
​@Pratik Savle is my colleague working on the same board but he is not facing issue like i am. 

If any information is required please do let me know.

Regards
Harsh Bhavsar