Re: MSP430F5659, msp430mcu-20130321, Windows

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 <[email protected]>

> 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 damaging FRAM chips if it was used
> for them.
>
> Peter
>
>
>
> On Tue, Jul 2, 2013 at 8:08 AM, Thierry Varidel <
> [email protected]> wrote:
>
>> 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-msp430mcu with
>> previous builds. So is it supposed to work with this non FRAM chip?
>>
>> Best regards,
>>
>> TV
>>
>>
>> 2013/7/2 Peter Bigot <[email protected]>
>>
>>> > 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/[email protected]/msg11556.html
>>>
>>> In short, the new FRAM chip headers require a compiler patch and are
>>> unsupported in released mspgcc at this time.  An entity that may pay for
>>> mspgcc maintenance is caught up on an internal matter that must be resolved
>>> before they can fund a new release that includes the fix for this.  I have
>>> no ability to influence that process, and at this time do not plan to
>>> donate the necessary release packaging/testing effort myself (especially
>>> since I have no boards using these new chips).
>>>
>>> Peter
>>>
>>> On Tue, Jul 2, 2013 at 7:23 AM, Thierry Varidel <
>>> [email protected]> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I want to use mspgcc with the MSP430F5659 and I've seen that the header
>>>> files for this microcontroller have been made available in
>>>> msp430-mcu-20130321.zip.
>>>>
>>>> I'm working with Windows 8 and I was secretely hoping that it was as
>>>> simple
>>>> as copying the .x and .h files of the MCU in the mingw32 prebuilt
>>>> package
>>>> include and bin folders but if I do that, I have the following error
>>>> when
>>>> linking :
>>>>
>>>> memory.x(20): error : nonconstant expression for length
>>>>
>>>> I've spent a lot of time altavisting for this and it seems that I'm the
>>>> only guy in the world using this MCU with MSPGCC. I couldn't find any
>>>> clue
>>>> on how to put the mcu-20130321 in my mspgcc distribution.
>>>>
>>>> I'm using mspgcc 4.6.3 for now but I plan to update to 4.7.0 for large
>>>> memory support.
>>>>
>>>> Can anybody give me some information on how to achieve that?
>>>>
>>>> Thanks in advance!
>>>>
>>>> TV
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by Windows:
>>>>
>>>> Build for Windows Store.
>>>>
>>>> http://p.sf.net/sfu/windows-dev2dev
>>>> _______________________________________________
>>>> Mspgcc-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>>>
>>>>
>>>
>>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users