Question

For embedded applications, it is often necessary to access fixed memory locations for peripheral registers. The standard way I have found to do this is something like the following:

// access register 'foo_reg', which is located at address 0x100 #define foo_reg *(int *)0x100  foo_reg = 1;      // write to foo_reg int x = foo_reg;  // read from foo_reg 

I understand how that works, but what I don’t understand is how the space for foo_reg is allocated (i.e. what keeps the linker from putting another variable at 0x100?). Can the space be reserved at the C level, or does there have to be a linker option that specifies that nothing should be located at 0x100. I’m using the GNU tools (gcc, ld, etc.), so am mostly interested in the specifics of that toolset at the moment.

Some additional information about my architecture to clarify the question:

My processor interfaces to an FPGA via a set of registers mapped into the regular data space (where variables live) of the processor. So I need to point to those registers and block off the associated address space. In the past, I have used a compiler that had an extension for locating variables from C code. I would group the registers into a struct, then place the struct at the appropriate location:

typedef struct {     BYTE reg1;    BYTE reg2;    ... } Registers;  Registers regs _at_ 0x100;  regs.reg1 = 0; 

Actually creating a ‘Registers’ struct reserves the space in the compiler/linker’s eyes.

Now, using the GNU tools, I obviously don’t have the at extension. Using the pointer method:

#define reg1 *(BYTE*)0x100; #define reg2 *(BYTE*)0x101; reg1 = 0  // or #define regs *(Registers*)0x100 regs->reg1 = 0; 

This is a simple application with no OS and no advanced memory management. Essentially:

void main() {     while(1){         do_stuff();     } } 

Answer 1

Your linker and compiler don’t know about that (without you telling it anything, of course). It’s up to the designer of the ABI of your platform to specify they don’t allocate objects at those addresses.

So, there is sometimes (the platform i worked on had that) a range in the virtual address space that is mapped directly to physical addresses and another range that can be used by user space processes to grow the stack or to allocate heap memory.

You can use the defsym option with GNU ld to allocate some symbol at a fixed address:

--defsym symbol=expression 

Or if the expression is more complicated than simple arithmetic, use a custom linker script. That is the place where you can define regions of memory and tell the linker what regions should be given to what sections/objects. See here for an explanation. Though that is usually exactly the job of the writer of the tool-chain you use. They take the spec of the ABI and then write linker scripts and assembler/compiler back-ends that fulfill the requirements of your platform.

Incidentally, GCC has an attribute section that you can use to place your struct into a specific section. You could then tell the linker to place that section into the region where your registers live.

Registers regs __attribute__((section('REGS')));