STM32N6570-DK: cannot program via CubeProgrammer

[youngpe]

I’m using CubeProgrammer v2.23.0 with the SDMMC_STM32N6570-DK external loader (no additional loaders). I have the boot switches in the boot0=L, boot1=H positions. I have looked at all the posts similar to this one, however none of the suggested fixes have helped.

When I try to program the eval board I get the following error message ... 

NOTE: I am able to download a new GUI directly from TouchGFX to external flash and it is fine. So, this is obviously an issue with CubeProgrammer/settings within?

 

[youngpe]

this is the log file below... 

 

12:44:39 : STM32CubeProgrammer API v2.23.0 | Windows-64Bits 
12:44:50 : UR connection mode is defined with the SWrst reset mode
12:44:50 : Warning: Device changed, refreshing...
12:44:50 : UR connection mode is defined with the SWrst reset mode
12:44:50 : ST-LINK SN  : 002700193235510E38363730
12:44:50 : ST-LINK FW  : V3J15M6
12:44:50 : Board       : STM32N6570-DK
12:44:50 : Voltage     : 3.29V
12:44:50 : SWD freq    : 8000 KHz
12:44:50 : Connect mode: Hot Plug
12:44:50 : Reset mode  : Software reset
12:44:50 : Device ID   : 0x486
12:44:50 : Revision ID : Rev B
12:44:51 : UPLOADING ...
12:44:51 :   Size          : 1024 Bytes
12:44:51 :   Address       : 0x8000000
12:44:51 : Read progress:
12:44:51 : Data read successfully
12:44:51 : Time elapsed during the read operation is: 00:00:00.004
12:46:28 : Opening and parsing file: STM32N6570-DK_OoB.hex
12:46:28 : Memory Programming ...
12:46:28 :   File          : STM32N6570-DK_OoB.hex
12:46:29 :   Size          : 59.02 MB 
12:46:29 :   Address       : 0x70000000
12:46:29 : Erasing memory corresponding to segment 0:
12:46:29 : Erasing external memory sector 256
12:46:29 : Error: failed to erase memory
12:46:29 : Error: failed to erase memory
12:46:29 : RUNNING Program ... 
12:46:29 :   Address:      : 0x70000000
12:46:29 : Application is running, Please Hold on...
12:46:29 : Start operation achieved successfully
 

[youngpe]

some progress - I can program the external flash now after changing the external loader from SDMMC_STM32N6570-DK to MX66UW1G45G_STM32N6570-DK.

 

[Maxime_BELAVAL]

Hello ​@youngpe, your boot configuration was indeed correct.

 

You couldn’t use an SDMMC external loader (SDMMC_STM32N6570-DK) because the STM32N6570-DK does not boot directly from the microSD card slot, hence the error returned by STM32CubeProgrammer.

 

On the STM32N6570-DK Discovery kit, the system expects the executable code (including the First Stage Bootloader (FSBL)) to be written into the high-speed external Octo-SPI NOR Flash starting at address 0x70000000.

 

If you map the SDMMC loader, STM32CubeProgrammer attempts to initialize the SD card interface instead of the XSPI peripheral to write your application code.

 

Max