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] [June 2015 Threads]
Hello,
I'am doing a project about the CAN bus using the FreeRTOS in PIC18F, but I face with a problem in the interrupt;
The PIC18 does allow two priorities of interrupt. The project is set up to use compatibility mode, so I make my own routine of interrupt for receiving the message in bus CAN, just after the routine of prvTickISR, and the problem is that if I switch the context in the routine, PIC18 will not receive the message, the program will entrer the block of vListRemove() and vListInsert() (in fonction of vTaskIncrementTick() -> prvCheckDelayedTasks();), and I see that the number of the list is so big, about 0x69, but I just have three tasks;
I don't understand why in the routine prvTickISR, it works to switch the context, but in my own routine, il doesn't work at all.
Thanks in advance four your attention and work.
static void prvTickISR( void )
{
/* Interrupts must have been enabled for the ISR to fire, so we have to
save the context with interrupts enabled. */
portSAVECONTEXT( portGLOBALINTERRUPT_FLAG );
PIR3bits.CCP1IF = 0;
/* Maintain the tick count. */
vTaskIncrementTick();
#if configUSE_PREEMPTION == 1
{
/* Switch to the highest priority task that is ready to run. */
vTaskSwitchContext();
}
#endif
portRESTORE_CONTEXT();
}
the routine like that doesn't work:
static void vCANRxISR (void)
{
portSAVECONTEXT(portGLOBALINTERRUPT_FLAG);
PIR5bits.RXB0IF = 0;
xSemaphoreGiveFromISR(xBinarySemaphoreCANRecv,&xHigherPriorityTaskWoken);
vTaskSwitchContext();
portRESTORE_CONTEXT();
}
static void vCANRxISR (void)
{
PIR5bits.RXB0IF = 0;
xSemaphoreGiveFromISR(xBinarySemaphoreCANRecv,&xHigherPriorityTaskWoken);
taskYield();
}
the routine like that work fine:
static void vCANRxISR (void)
{
PIR5bits.RXB0IF = 0;
xSemaphoreGiveFromISR(xBinarySemaphoreCANRecv,&xHigherPriorityTaskWoken);
}
The PIC18 is really not a good architecture for a pre-emptive OS.
There is an example ISR provided, which is called vSerialRxISR(), and is found in the FreeRTOSDemoPIC18_MPLABserial directory. I don't think your code is following the same scheme.
Regards.
Thanks for your reply.
Yes, I have refered the exemple ISR vSerialRxISR(), and follow the same scheme, it works.
But I want to know why the ISR prvTickISR() can switch the context, but in my own routine, if I use the context swtich, it doesn't work ? and I have confirmed that is not the reason of stack overflow
Besides the banking memory of the PIC18, there are other reasons that the pic18 is not good for a pre-emptive OS ?
Regards
Sorry - from a quick look at the code, I'm not sure either. I would suggest stepping through the interrupt from entry to exit to see if that highlights any clues.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.