On 2007-11-14, Peter Jansen <[email protected]> wrote:
>>> For the Nth time, I'm once again stuck because mspgcc and/or
>>> binutils doesn't know about the device type I'm using (this
>>> time it happens to be the MSP430F2330).
>>
>> The MSP430F2274 has almost the same peripheral set (the same
>> for the ones I'm using). The memory map isn't quite the same,
>> so I had to modify a linker script. But, it's working (so far).
>>
>> Is there some way to de-couple the cpu type from the toolchain
>> a little? Maybe by provide a "generic" CPU type and a linker
>> script and msp430xXXXX.h template file?
>
> I did a patch for this quite some time ago (2007-01-27),
> asking for comment and quite some water has gone under the
> bridge for work on the compiler since then.
>
> Its quite possiable to use the MSP-A and MSP-B (and now MSP-C
> for the X) CPU definitions. This makes the compiler devoiced
> from the CPU type number and then binutils to select a
> 'generic' linker script and then just change your linker
> script for the application. Sould I re-work the patches and
> put them in now?
It seems like a good idea to me. I think this will be the
third time in about 9 months that I'll have to patch and
rebuild my toolchain because of an unknown CPU type. The work
required to constantly add CPU types to the toolchain could be
put to better use as well.
>> I know... quit whining and do it...
>
> A few hints above, whining might prompt someone to do
> something about it :-)
--
Grant Edwards grante Yow! I'm in ATLANTIC CITY
at riding in a comfortable
visi.com ROLLING CHAIR...
