On Nov 20, 2010, at 1:00 PM, Peter Bigot wrote: > I suspect assigning a specific address using asm, though, overrides this and > makes the section irrelevant. In any case, I believe there may need to be a > different linker script used for these devices when the USB is to be > enabled, to ensure program variables don't end up creeping in the area > reserved for USB. Yet another variation point....
Are you aware of any other MSP430 peripherals which steal memory blocks like the USB interface? If this is something that we'll see more of as TI creates more MSP430 variants, then it may be necessary to devise a clean, generalized way to deal with varying memory maps within a given part. Maybe just defining different part ID variants (e.g. -mmsp430f5529usb, -mmsp430f5529nousb, etc.) would be good enough, or maybe that would become too cumbersome if there's ever a part with a lot of memory map variability. -- Mark J. Blair, NF6X <n...@nf6x.net> Web page: http://www.nf6x.net/ GnuPG public key available from my web page. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users