Hello all: I'm trying to get and up to date toolchain for MSP430. I came across some binary packages, but those were for gcc 3.x and binutils 2.14 or previous (can't remember the exact versions right now sorry).
Also I wanted to be able to build the toolchain myself so I could package it for Debian. Since binutils natively supports msp430 this is not a big deal for this package. Regarding binutils, I've seen that msp430Fx2x1x(eZ430 model) is not explicitly listed anywhere I could see there but having taken a look into the binutils code it would be relatively simple to add it if I have understood the code correctly. This is, the exact chip model is only used for marking a field in the elf object and there are no other instruction or optimisation code involved. So it would be needed to add a new line for static const bfd_arch_info_type arch_info_struct[] in bfd/cpu-msp430.c like this: N (16, bfd_mach_msp20, "msp:20", FALSE, & arch_info_struct[y]) and defining bfd_mach_msp20 accordingly. Is this right? After having binutils I started to build gcc-4.1 and I got an internal gcc error that prevented the build to finish correctly, but someone at #gcc advised me to use the configure option --without-bootstrap and then build started to go fine. I've still been unable to finish it for some collateral problems not related to either gcc or msp430 patches. What are the advised configure options for building gcc? I chose gcc4.1 since theirs was the newest patches on the CVS repo and hence it would contain a wider range of MSP430 models, like the MSP430F2013 which is the one that the eZ430 uses. This mail is to ask for opinions regarding this process. Am I using the right versions? Is this chip model totally supported? Are msp430 binutils and gcc mature/functional enough? I also welcome whoever interested in packaging this stuff for Debian/Ubuntu so we could work together towards this aim. Best regards, -- Raúl Sánchez Siles
