I'll get the basic patch for this into the queue for mspgcc4. Jens-Michael, would you say that for chips that have INFOA through INFOD, the sections should be named infoa (etc) and that infomem should be dropped on those chips? Do we need infoanobits (etc) for each of those as well?
If the elf32msp430.sc template script is updated to make the bootloader, individual info, and combined infomem sections all optional driven by presence of the corresponding variable in the msp430all.sh script, just like the fartext section is, is there any motivation to keep the forked elf32msp430_3 script? Peter On Thu, May 27, 2010 at 10:50 AM, JMGross <msp...@grossibaer.de> wrote: > > Indeed. When I started messing with the linker files for my bootloader > project, I noticed it too, but forgot to report it. I use the 12/08 windows > build of mspgcc3 (non-X) > > The differece between infomem and infomemnobits is that infomemnobits is > dumped after relocating. Its contents are not put into the output file and > not written to the MSP. > So you can define variables placed there and won't cause an infomem write > when flashing the chip. > > In addition, since the 54xx have the INFOA segment handled differently than > the others, there should be separate sections. On CCE and IAR, all 4 INFO > sections are separate rather than one huge section. And on some > MSPs, INFOA contains unique calibration data and should be only usable on > purpose and not by jsut placing something in infomem. > > JMGross > > ----- Ursprüngliche Nachricht ----- > Von: Hans Nieuwenhuis > An: mspgcc-users@lists.sourceforge.net > Gesendet am: 27 Mai 2010 12:33:04 > Betreff: [Mspgcc-users] Linker script for msp430x54xx > > 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? > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
