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] [March 2010 Threads] Tick time incorrect in CodeWarrior DEMOPosted by Shirley Chen on March 11, 2010 I found the tick time is incorrect in both CodeWarrior DEMO project. Compare value need to be added to TC0 before enable TFLG1 in file port.c, in function void interrupt vPortTickInterrupt( void ). The value that is added on TC0 is based on the system bus frequency. In my case is 2500 @ 20MHz bus clock. Anybody has the same experience?
RE: Tick time incorrect in CodeWarrior DEMOPosted by Dave on March 12, 2010 I just looked at the code but don't understand your comments because I cannot see anything being added to TC0. Can you explain further?
RE: Tick time incorrect in CodeWarrior DEMOPosted by Shirley Chen on March 12, 2010 From the code generated by the Processor Expert TickTimer.c, interrupt service routine as below
ISR(TickTimer_Interrupt) { TC0 += CmpVal; /* Add value corresponding with periode */ TFLG1 = 1; /* Reset interrupt request flag */ TickTimer_OnInterrupt(); /* Invoke user event */ }
CmpVal(in this case = 2500) is added on to TC0 to generate the 1kHz interrupt. When the vector for TC0 is redirected to vPortTickInterrupt( void ) in port.c file as below, void interrupt vPortTickInterrupt( void ) { #if configUSE_PREEMPTION == 1 { /* A context switch might happen so save the context. */ portSAVE_CONTEXT();
/* Increment the tick ... */ vTaskIncrementTick();
/* ... then see if the new tick value has necessitated a context switch. */ vTaskSwitchContext(); TC0 += 2500; // I added the code here TFLG1 = 1;
/* Restore the context of a task - which may be a different task to that interrupted. */ portRESTORE_CONTEXT(); } #else { vTaskIncrementTick(); TC0 += 2500; // I added code here TFLG1 = 1; } } #endif Without the the code I added, the TC0 interrupt will be enabled with TC0 = 0, that is the next ISR will come in when the TC0 counts 0xFFFF cycle, which exceed 1ms period, that was why the tick time appeared longer than it suppose to be.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|