AFAIK (but I might be wrong, misinterpreting the TI datasheets), one should not have any problems compiling programs for the MSP430X processors using the normal compiler build. The 430X cores handle all the old binary code jus as if there were not 430X. Only that you cannot access the flash above 64K this way.
There is an assembler function that handles usage of data stored in the additional flash (by using handcoded ASM instructions for fetching the data). The normal Linker has no problems putting the data into this upper memory too. The main problem is flashing the devices. The 5x series has a different flash controller, so the standard toolchain will fail to write anything into their flash. (you could use the built-in but also incompatible serial bootstrap loader) and the flash tools do not know about more than 64KB address area in the binary files. I'd be happy if I could just use the new hardware in the new 5xxx processors even without the additional flash and without any 430X code. An mspgcc build with updated flash tool and proper headers would be fine for me for the next year or more, as I rather need the I/O pins and USCI modules than the additional flash. JMGross ----- Ursprüngliche Nachricht ----- Von: Hans Nieuwenhuis An: [email protected] Gesendet am: 24 Jul 2009 16:53:59 Betreff: Re: [Mspgcc-users] using JTAG debugger - several issues Hi Frank, According to the ms430x2xx user guide the only devices that have the MSP430X core implemented are the ones with over 64kb address area. Since your device only has 60kb I think you don't need to recompile, just check if you include directory contains a msp430x24x.h file. I am using the msp430f2252 and msp430f2272 with the normal version (without MSP430X support) for over a year now. Kind regards, Hans
