(I speak here with reference to the binutils patches in the mspgcc4
repository. Not sure which release you're using.)
Chip-specific constants like that are stored in ld/emulparams/msp430all.sh.
It appears ones for INFO and BOOT were added for some (but not all) chips,
but are never referenced. They probably should be used in ld/scripttempl/
elf32msp430.sc in place of the hard-coded constants. (And maybe
elf32msp430_3.sc; not sure why that family merits its own script).
Did you discover this by analysis, or can you provide a short shell sequence
that generates an elf32 with content in these sections so I can verify
before/after behavior on various chips?
Below are sections from the ld manual; I don't know specifically why one
would want to put data into a memory section but not write it to the chip.
``.bootloader''
Defines the bootloader portion of the ROM (if applicable). Any
code in this section will be uploaded to the MPU.
``.infomem''
Defines an information memory section (if applicable). Any code in
this section will be uploaded to the MPU.
``.infomemnobits''
This is the same as the `.infomem' section except that any code in
this section will not be uploaded to the MPU.
Peter
On Thu, May 27, 2010 at 5:33 AM, Hans Nieuwenhuis <[email protected]> wrote:
> Hi all,
>
> Just found out that binutils (2.20.1, but also older revs.) installs
> incorrect linker files for the msp430x54xx parts. These parts have
> their bootloader starting at 0x1000, but as shown in the snippet blow
> that's where the linker puts the infomem section. Infomem should be
> four blocks of 128 bytes starting at 0x1800.
>
> bootloader(rx) : ORIGIN = 0x0c00, LENGTH = 1K
> infomem(rx) : ORIGIN = 0x1000, LENGTH = 256
> infomemnobits(rx) : ORIGIN = 0x1000, LENGTH = 256
>
> What is the purpose of the sections infomem and infomemnobits as they
> both point the same start address? Can someone shed a light on this?
>
> Thanks,
>
> Hans
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
