FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [December 2010 Threads] PIC32 interrupt declarationPosted by pya on December 24, 2010 I don't understand interrupt declaration in FreeRtos. In the Pic32 demo for example : interupt prototype handler is declare with ipl set to 1 : void __attribute__( (interrupt(ipl1), vector(_UART2_VECTOR))) vU2InterruptWrapper( void ); But Uart2 interrupt priority is set to 2 (as configKERNEL_INTERRUPT_PRIORITY is set to 1) : ConfigIntUART2( ( configKERNEL_INTERRUPT_PRIORITY + 1 ) | UART_INT_SUB_PR0 | UART_TX_INT_EN | UART_RX_INT_EN );
So, what is the good setting ?
Thanks for your help.
RE: PIC32 interrupt declarationPosted by Richard on December 24, 2010 I think this is really a question for Microchip as they provide both the compiler and the library - and both seem to provide a way of setting the priority. I asked the question when writing the port too.
I think the __attribute__ set priority level must only be used when you are not making library calls.
In this case, as far as I know/recall, the priority passed to the ConfigIntUART2() library function will be the one used at run time.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|