Hi,

Tested that Syntax and it does work without legacymsp430.h.

Is that the officially supported ISR syntax for mspgcc?


Thanks
Justin

On , Matthias Ringwald <matth...@ringwald.ch> wrote:


The syntax for declaring an interrupt with gcc is (as far as I learnt so far)



__attribute__((interrupt(VECTOR_NAME)))

void irq_handler_for_vector(void);



with VECOR_NAME the name of the IRQ vector. example:



__attribute__((interrupt(USCI_A2_VECTOR)))

void usbRxISR(void){



Best

Matthias



On 04.07.2011, at 09:22, justinsolar...@gmail.com wrote:



> Hi

> I am trying to find the correct syntax for interrupts using uniarch mspgcc.

>

> With mspgcc4 I know to include signal.h and for the ISR itself

> Interrupt(VECTOR) vector_name(void) { }

>

> And I know in the uniarch branch you have to change your signal.h to include leagacymsp430.h

> and the ISR (stays the same)

> Interrupt(VECTOR) vector_name(void) { }

>

>

> What is the correct syntax for uniarch mspgcc interrupts? with out using legacymsp430.h.

> ------------------------------------------------------------------------------

> All of the data generated in your IT infrastructure is seriously valuable.

> Why? It contains a definitive record of application performance, security

> threats, fraudulent activity, and more. Splunk takes this data and makes

> sense of it. IT sense. And common sense.

> http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________

> Mspgcc-users mailing list

> Mspgcc-users@lists.sourceforge.net

> https://lists.sourceforge.net/lists/listinfo/mspgcc-users



------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to