Skip to main content
Visitor II
October 28, 2025
Solved

STM32N6 Flash Memory Protection

  • October 28, 2025
  • 2 replies
  • 297 views

I'm trying to flash an an NUCLEO-N657X0-Q board with the STM32N6 using STM32CubeProgrammer v2.20.0. I have two NUCLEO-N657X0-Q boards here: One of them flashes just fine, the other one refuses to work. Both boards are in development mode (BOOT jumpers set accordingly as described here https://github.com/STMicroelectronics/STM32N6-GettingStarted-ImageClassification?tab=readme-ov-file#boot-modes). In STM32CubeProgrammer, I have selected the appropriate External loader to be able to write to the external flash memory.

As a simple experiment, I am trying to erase a sector of the external flash memory. I am using the exact same STM32CubeProgrammer settings for both boards. Erasing the flash works just fine on one of the boards, but on the other board, I get the following error:

Jeija_0-1761678820914.png

Did I accidentally enable some kind of flash memory protection? How do I disable it? Or is my board broken? The board still boots the old code in the flash memory when in flash boot mode, so I don't think the flash chip is completely broken. Also, downloading code to RAM and debugging works fine with both boards, so the STM32N6 also seems to be working just fine.

Any ideas on how to proceed from here?

 

Best answer by Aziz BRIGUI

Hello @Jeija,

Issue fixed in STM32CubeProgrammer v2.21 available under this link.

Aziz

2 replies

KDJEM.1
Technical Moderator
November 3, 2025

Hello @Jeija and welcome to the community;

 

Similar issue is reported here.

This issue is already reported internally through Ticket number: 216448.

(PS: Ticket number: 216448, is only for reference and not available outside of ST).

 

Thank you.

Kaouthar

 

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.
Aziz BRIGUI
Aziz BRIGUIBest answer
Technical Moderator
November 18, 2025

Hello @Jeija,

Issue fixed in STM32CubeProgrammer v2.21 available under this link.

Aziz

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.