That's almost certainly not the right correction, but as long as you don't
use the ram_mirror section it won't matter.
Thanks for following up; I'll add a ticket so if there's another release it
gets fixed.
Peter
On Tue, Jul 2, 2013 at 8:57 AM, Thierry Varidel wrote:
> I found the problem!
>
I found the problem!
There was a typo in the memory.x file at this line :
ram_mirror (wx) : ORIGIN = 0xfc000, LENGTH = 0x-f5c00
instead of :
ram_mirror (wx) : ORIGIN = 0xfc000, LENGTH = 0xf5c00
Now it compiles with mspgcc 4.7.0!
TV
2013/7/2 Peter Bigot
> Sorry; I misread that as the
Sorry; I misread that as the FR5969.
In short, the only combinations that are supposed to work are the ones that
are in mspgcc releases. The 20120406 mspgcc release you're using will
probably not work with 20130321 msp430mcu, but the 20120911 mspgcc release
probably would except for the risk of d
Hello Peter,
Thank you for answering.
I have seen the mailing list entry you mentioned before.
In it, you said that the release 20130321 of msp430mcu is not working with
FRAM chips but the F5659 is not using FRAM this is why I was thinking that
it was feasible to use its headers from 20130321-ms
> Can anybody give me some information on how to achieve that?
Not really. In some cases you can mix versions of the component packages
of mspgcc and they'll probably work; in this case you can't. See:
http://www.mail-archive.com/mspgcc-users@lists.sourceforge.net/msg11556.html
In short, the ne
