Yes, i saw that the other 64Kb are in an different memory area.
Moreover, this area is directly coupled to the CPU (and CPU only) and is 0 wait state.
So it could be used by the stack as well as by variables that needs fast read/write and are only accessed by the CPU (no DMA).
Should make a performance improvment.
I haven't tried yet but I saw it could be like this :
/* put the stack at the top of the CCM memory */
_estack = 0x10010000;
MEMORY
{
ram (rwx) : ORIGIN = 0x20000C00, LENGTH = 125K
ccmram (rwx) : ORIGIN = 0x10000000, LENGTH = 64K
rom (rx) : ORIGIN = 0x08010000, LENGTH = 960K
}
...
.ccm (NOLOAD) :
{
.= ALING(4);
*(.ccm)
.= ALIGN(4);
} > ccmram
....
Like this the stack use the faster RAM and some variables could be declared like this :
int array[2048] __attribute__((section(".ccm")));
I'll give a look at your latest version, thanks.
Xavier