Re: Interrupt Syntax

Peter Bigot <[email protected]>
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.user
Message-ID <CAPOJ94Po1pi9jnCq2j=S6=vzfWU=OWHYczzmMCuGNh9d=parXg@mail.gmail.com>
It's valid in the ones it works in.  The pragma approach probably isn't
good before 20120406; the attribute approach should work in any mspgcc
version.  The syntactic sugar that used to be recommended just makes it
hard to see what's going on.  There is an isr_compat.h or some such header
that's supposed to work on all the toolchains which you could try too.

Peter

On Tue, Mar 19, 2013 at 8:32 AM, Dean Chester <[email protected]>wrote:

> For which version is this valid syntax? Just tried to use it for a simple
> test with my version which is:
>
> Deans-MacBook-Pro:src dean$ msp430-gcc -v
> Using built-in specs.
> Reading specs from
> /usr/local/msp430-uniarch-20110716/lib/gcc/msp430/4.5.3/../../../../msp430/lib/msp430mcu.spec
> COLLECT_GCC=msp430-gcc
>
> COLLECT_LTO_WRAPPER=/usr/local/msp430-uniarch-20110716/libexec/gcc/msp430/4.5.3/lto-wrapper
> Target: msp430
> Configured with: ../../gcc-4.5.3/configure --target=msp430
> --enable-languages=c,c++ --prefix=/usr/local/msp430-uniarch-20110716
> Thread model: single
> gcc version 4.5.3 (GCC)
>
> And I got a compiler error.
>
> D.
>
>
> On Tue, Mar 19, 2013 at 1:18 PM, Peter Bigot <[email protected]> wrote:
>
>> Ahem.  Let's try that again without pressing "send" prematurely:
>>
>> That page suggests including <signal.h> and using the interrupt macro.
>> <signal.h> is deprecated; its content is in <legacymsp430.h> and you need
>> to include that file to use it without getting a warning at compile time.
>> If you tried it, you should have seen that warning.
>>
>> I personally use the CCS syntax since that's now supported by mspgcc and
>> makes portability easier.
>>
>> #pragma vector=TIMER0_A0_VECTOR
>> __interrupt void
>> ta0cc0_isr (void)
>>
>> Under the covers this and the legacy method both use the native gcc syntax
>> which involves the interrupt attribute.
>>
>> static void
>> __attribute__((__interrupt__(TIMER0_A0_VECTOR)))
>> isr_cc0_TA0 (void)
>>
>> Hopefully this message will show up in the archive so others can find it.
>>
>> Peter
>>
>> On Tue, Mar 19, 2013 at 7:56 AM, Wayne Uroda <[email protected]> wrote:
>>
>> > Hi,
>> >
>> > I just want to double check, is the interrupt syntax described here:
>> >
>> > http://mspgcc.sourceforge.net/manual/x918.html
>> >
>> > still modern and current? I know many parts of MSPGCC have changed, and
>> > I may be getting confused with IAR or code composer because somewhere I
>> > recall the ISR syntax changed from one version to another.
>> >
>> > Thanks,
>> >
>> > - Wayne
>> >
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Everyone hates slow websites. So do we.
>> > Make your web apps faster with AppDynamics
>> > Download AppDynamics Lite for free today:
>> > http://p.sf.net/sfu/appdyn_d2d_mar
>> > _______________________________________________
>> > Mspgcc-users mailing list
>> > [email protected]
>> > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_d2d_mar
>> _______________________________________________
>> Mspgcc-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>>
>>
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar

_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.