On Tue, Jun 26, 2012 at 3:39 AM, Simeon Felis <simeon.fe...@hs-regensburg.de> wrote: > According to [1] page 12 the f1612 has 55k rom. But the > msp430/lib/ldscripts/msp430f1612/memory.x > indicates that it has about 54k rom: > rom (rx) : ORIGIN = 0x2500, LENGTH = 0xdae0 /* END=0xffe0, size > 56032 */ > > What is correct now?
The linker script appears consistent with the device datasheet at http://www.ti.com/product/msp430f1612; see page 15. The device does not have 55 kiB ROM; that's been rounded up by 256 bytes. > I crated a msp430f1612 device with the openMSP from opencores with > exactly 55k to imitate the msp430f1612, however when I try to download > the .elf, I get an error because of different available sizes. > > How can I manipulate the linker script to fit the .elf into the device? Don't. Correct your device description to match the linker script. > I tried: > > MEMORY { > sfr : ORIGIN = 0x0000, LENGTH = 0x0010 /* END=0x0010, > size 16 */ > peripheral_8bit : ORIGIN = 0x0010, LENGTH = 0x00f0 /* END=0x0100, > size 240 */ > peripheral_16bit : ORIGIN = 0x0100, LENGTH = 0x0100 /* END=0x0200, > size 256 */ > ram_mirror (wx) : ORIGIN = 0x0200, LENGTH = 0x0800 /* END=0x0a00, > size 2K */ > infomem : ORIGIN = 0x0a00, LENGTH = 0x0100 /* END=0x0b00, > size 256 as 2 128-byte segments */ > infob : ORIGIN = 0x0b00, LENGTH = 0x0080 /* END=0x0b80, > size 128 */ > infoa : ORIGIN = 0x0b80, LENGTH = 0x0080 /* END=0x0c00, > size 128 */ > ram (wx) : ORIGIN = 0x0c00, LENGTH = 0x1400 /* END=0x2000, > size 5K */ > rom (rx) : ORIGIN = 0x2000, LENGTH = 0xdc00 /* END=0xf800, > size 56320 */ > vectors : ORIGIN = 0xffe0, LENGTH = 0x0020 /* END=0x10000, > size 32 as 16 2-byte segments */ > /* Remaining banks are absent */ > bsl : ORIGIN = 0x0000, LENGTH = 0x0000 > infoc : ORIGIN = 0x0000, LENGTH = 0x0000 > infod : ORIGIN = 0x0000, LENGTH = 0x0000 > ram2 (wx) : ORIGIN = 0x0000, LENGTH = 0x0000 > usbram (wx) : ORIGIN = 0x0000, LENGTH = 0x0000 > far_rom : ORIGIN = 0x00000000, LENGTH = 0x00000000 > } > REGION_ALIAS("REGION_TEXT", rom); > REGION_ALIAS("REGION_DATA", ram); > REGION_ALIAS("REGION_FAR_ROM", far_rom); > PROVIDE (__info_segment_size = 0x80); > PROVIDE (__infob = 0x0b00); > PROVIDE (__infoa = 0x0b80); > > But here I also receive an error about different rom sizes. How come? I don't know offhand, but what you have does not reflect the memory layout of the F1612. Peter > [1] http://www.ti.com/lit/sg/slab034v/slab034v.pdf > > -- > M.Eng. Simeon Felis > Fakultät Elektro- und Informationstechnik > Laboratory for Safe and Secure Systems, LaS3 - a software engineering > discipline (www.las3.de) > Seybothstrasse 2 > P.O. 12 03 27 > 93025 Regensburg > Germany > FON: +49 (0)941 / 943 9823 > MOB: +49 (0)176 / 2323 8962 > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
