Thanks for your answer,

I effectively did not use the TI headers.

It works fine now.

Fred

2010/8/21 Peter Bigot <[email protected]>:
> That problem should be fixed in the 20100815 release of mspgcc4 and
> msp430-libc (again the ti version).   Also with that version you
> should be able to include the correct header for the chip rather than
> the legacy one.  You'll still have to lie about the mcu.
>
> Peter
>
> 2010/8/20 Frédéric Sureau <[email protected]>:
>> Hi all,
>>
>> I tried to compile a "flash the led" example for the msp430f5529 using
>> your method :
>> include legacy header : msp430x552x.h
>> using mmcu : msp430x5418
>>
>> I encountered this error (on many lines) :
>>
>> /opt/msp430-gcc-4.4.4/lib/gcc/msp430/4.4.4/../../../../msp430/include/msp430x552x.h:1448:
>> erreur: expected ‘)’ before numeric constant
>>
>> The problem seems to be on lines using the macro function "const_sfrb"
>> or "const_sfrw".
>> When I search for these macro in iomacros.h there is no definition.
>>
>> For the moment I tried using "sfrb" instead, and the compilation is OK
>> (I did not tried on target yet).
>>
>> Fred
>>
>> Le 19 août 2010 15:35, Frédéric Sureau <[email protected]> a écrit :
>>> ---------- Forwarded message ----------
>>> From: Peter Bigot <[email protected]>
>>> Date: 2010/8/11
>>> Subject: Re: [Mspgcc-users] mspgcc or mspgcc4 for a msp430f5529
>>> To: "GCC for MSP430 - http://mspgcc.sf.net"; 
>>> <[email protected]>
>>>
>>>
>>> I believe some people are having some success using mspgcc4 and compiling
>>> with the TI headers version of msp430-libc.  There's a bug in the headers
>>> right now that means you should include the legacy header msp430x552x.h
>>> instead of the chip-specific one, and the compiler isn't aware of the 5529
>>> so you'll have to provide it an option for a different 5xx family chip, such
>>> as -mmcu=msp430x5418.  Patches for both these problems are in the works.
>>>
>>> msp430-libc as available on the mspgcc4 project should also work with mspgcc
>>> if you need to use the MSP430X support that's in that CVS branch.
>>>
>>> Peter
>>>
>>> On Wed, Aug 11, 2010 at 8:10 AM, Aurélien Gauducheau <
>>> [email protected]> wrote:
>>>
>>>> Hi, I try to load the OS on a Contiki msp430f5529 I would like to know if
>>>> mspgcc or mspgcc4 support msp430f5529. If not, is there a procedure or a
>>>> patch for that mspgcc or mspgcc4 support the msp430f5529? thanks you Best
>>>> regards Aurélien
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by
>>>>
>>>> Make an app they can't live without
>>>> Enter the BlackBerry Developer Challenge
>>>> http://p.sf.net/sfu/RIM-dev2dev
>>>> _______________________________________________
>>>> Mspgcc-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Mspgcc-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Mspgcc-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>

Reply via email to