Disable external flash programming

[Vahid Ajallooeian]

Hello dear engineers,

How can I instruct the STM32cubeIDE to neglect programming of the exteranl flash parts?

This parts have been placed in an external ram memory which is to be read and programmed in runtime.

In Keil ide, it simply says since no flashing algorithm for the specified parts is available, I will not take these sections into account for programming.

The _flash.ld file has been changed as follows.

/* Memories definition */
MEMORY
{
 CCMRAM  (xrw)  : ORIGIN = 0x10000000,  LENGTH = 64K
 RAM  (xrw)  : ORIGIN = 0x20000000,  LENGTH = 192K
 FLASH  (rx)  : ORIGIN = 0x8000000,  LENGTH = 1024K
 ExtFlashSection (xrw)  : ORIGIN = 0xC00F0000,  LENGTH = 0x1f10000  
}

Any help would be appreciated.

[Vahid Ajallooeian]

@Rados?aw​ It is not unusual, Systems either have QSPI, NAND flash, SDCARD or other storage media for saving large data. Then as image data are really large for embeded systems, I choosed to use NAND flash as my storage. For not making runtime app to be slow, image data are going to be loaded into external ram at startup time. Usual or unusual?

[Radosław]

This is usual i agree, but unusual is to creating 2 programing files splited this way that you describe with preserwing degug informations. Or i miss something.

This is tricky, and also for my personal knowlage i will find some solution. Give me some time please. If you can mail to me directly.

[Radosław]

Still i can't understand why external flash must be programmed differently... This will be SD card or another removable memory?

[Vahid Ajallooeian]

Image file is copied to SD card directly so no need to be programmed via UC, NAND Flash is programed via UC with the information stored in the SD CARD.

[Radosław]

It seems to be much more problematic ;).

messing with section flags is very risky, i get strange effects, Remove this section after creating bin file can be solution, but debuging probably will be difficult.