STM32N5670-DK + stm32cubeide1.19.0 + stm32cubeprogrammer2.20.0 ERROR：Device debug script

yipeng · ‎2025-08-18

i DEBUG STM32N5670-DK Template_XIP_FSBL with stm32cubeide1.19.0 and ERROR comes：Device debug script

the detail is：

STMicroelectronics ST-LINK GDB server. Version 7.11.0

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61922

Status Refresh Delay : 15s

Verbose Mode : Disabled

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

Debugger connected

Waiting for debugger connection...

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

STM32CubeProgrammer v2.20.0

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

Log output file: C:\Users\supcon\AppData\Local\Temp\STM32CubeProgrammer_a04640.log

ST-LINK SN : 0038002E3333511*********

ST-LINK FW : V3J16M9

Board : STM32N6570-DK

Voltage : 3.27V

JTAG freq : 21333 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x486

Revision ID : Rev B

Device name : ST32N657

Device type : MCU

Device CPU : Cortex-M55

BL Version : --

Error: Erase command for internal Flash memory is not available for N6 devices.

Encountered Error when opening E:\ST\STM32CubeIDE_1.19.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.200.202503041107\tools\bin\STM32_Programmer_CLI.exe

Shutting down...

Exit.

i noticed that N6 has no internal FLASH？maybe？from：Nucleo N6 won't flash - STMicroelectronics Community

so，this is the reason why i cant debug N6？HOW can i fix it.

NesrynELMK · ‎2025-08-18

Hello @yipeng

The STM32N6 does not have internal Flash memory; instead, it features 128 KB of Boot ROM and 4.5 MB of RAM, with the option to expand memory externally.

The device boots from the Boot ROM and then either jumps to execute code directly from external Flash or copies the code into RAM for execution.

Regarding STM32CubeProgrammer, please try performing an ST-LINK firmware update.

You can refer to Application Note AN6265 , which explains how to debug an example using STM32CubeIDE.

Additionally, you can consult the Readme file of the project https://github.com/STMicroelectronics/STM32Cube

Kind regards,

yipeng · ‎2025-08-20

thanks for your comment.

i conformed that the FSBL of tamplete Template_XIP_FSBL should be bebuged through RAM ONLY.

To simplify debug process，i turned it to TAMPLATE ，which is the most simplest template.

i open stm32n657xx_axisram2_fsbl.sct file which is for KEIL and noticed that LR_IROM1 is 0x34180400 and RW_IRAM1 is 0x341C0000 which verify that TAMPLATE should be bebuged through RAM.i change some settings in KEIL for debug - through-RAM and it works！i can debug ， the LEDs flashing.

But，i failed to debug - through-RAM by STM32CUBEIDE，i changed lots of settings in “debug configuration” - “debuger” and “debug configuration” - “startup”，it didnt works.i view AN6265 and UM2609，but they do not mention debug - through-RAM configurations.is there more settings to setup a debug - through-RAM configuration？

thanks again！