Hi Alice.
Thanks for your the interest.
I kept the standard memory sections config.
I tried changing the in the Build Options settings panel:
the Heap amount from 0x0400 to upper values (0x0C00 or 0x1000) with no compiling and linking errors, but I have run time exceptions on isatty() call.
Following suggestions like described in Memory Areas and Using malloc() , I tried to configure linker with -WI switch but I think that symbol definition is different from the one I used. I found other suggestions like reported in compiler construction - use no heap in gnu gcc - Stack Overflow and others without achieving more heap.
I'm testing the available memory amount with this simple function
uint32_t GetAvailableMemory(void)
{
char *p;
uint32_t siz = 1;
p = calloc(1,siz);
while (p)
{
siz++;
p = realloc(p,siz);
}
free(p);
return siz;
}
At least I could follow tweaks like Allocation of Variables at Absolute Address in RAM - Cypress using static or global pre-allocation
but I would like not to change malloc()-like calls because I'm generating C-code from a Matlab algorithm.
The .ld Linker file obviously reflects the PE config for I ask to generate linker code.
