Hi all,

I have almost 1200 vars in my project, for STM32.
I want to have them ordered, so that I will be able to read them through a MODBUS protocol (via CAN, UART, etc).
Example, as done in my previous lives :
global.c
#pragma segment memory=zzzz
volatile u8 var1;
volatile u8 var2;
volatile u8 var3;

so that i would find in .map file, something like that :
0x20000000 var1
0x20000001 var2
0x20000002 var3
In that way, I can sort my vars, make sections, add some without distroying all the mapping, etc

The only way I found with RIDE/GCC is to declare a segment in a .ld file :
----------file.ld------------------------------
...
.ram_data :
{
_bb_ram_data = . ;
. = ALIGN(0x100);
_b_ram_data = . ;
_e_ram_data = _bb_ram_data + SIZEOF (.ram_data); /* pirouette inélégante, mais que ca qui compile ok */
} >RAM
...
----end file.ld----------------------------

I define some vars in a global.c

volatile u8 BYTE_AD_25 __attribute__ ((section (".ram_data")));
volatile u8 BYTE_AD_26 __attribute__ ((section (".ram_data")));
volatile u8 BYTE_AD_27 __attribute__ ((section (".ram_data")));

declared in a global.h file

Then, i need to erase vars at start (because Gcc will not) :

----erase fct----------------------------
extern u32 _b_ram_data; //declaration des extern definis dans le fichier .ld
extern u32 _e_ram_data;

u8p_RAM = (u8 *)((u32)(&_b_ram_data));
for (u16_j=0;u16_j<(((u32)&_e_ram_data) - ((u32)&_b_ram_data));u16_j++)
{
*u8p_RAM++ = 0;
}
----end erase fct----------------------------

And i found that in .map file :
.ram_data 0x20000c00 0x50 C:\...\global.o
0x20000c03 BYTE_AD_27
0x20000c01 BYTE_AD_25
0x20000c02 BYTE_AD_26
That's OK, but I want to be sure that's the only way before adding "__attribute__ ((section (".ram_data")));" to my thousand of variables ! ! ! !
I spent many hours on that issue, and this is not 'elegant' at all. Please help if anybody knows...

Hoping I am clear enough !