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 2009 Threads] Hook function to initialize tick timer?Posted by jdabbs003 on June 22, 2009 We are porting to the Epson S1C33 architecture. One thing that would be nice (for us) is to define a port-specific hook/callback to actually setup the FreeRTOS tick timer. The reason is that there are so many timers with so many options, it's cumbersome to use #if/#elif/#elif to cover all possibilities in the port.c code.
However, it seems like this is not done with other ports. Is using a port-specific hook function to initialize the tick timer a problem with FreeRTOS? If so, is there a better way to deal with this situation?
Thanks.
RE: Hook function to initialize tick timer?Posted by Richard on June 22, 2009 There is no reason why not to use a callback or hook function - there is at least one port that does this by default already (I think its one of the ColdFire V2 ports where the vector table changes depending on the exact part being used).
Another common technique is to #define prvSetupTimerInterrupt to another function in FreeRTOSConfig.h, then you can define the 'other' function to setup whichever time you want, although some ports also require an asm file modification if the handler has an asm wrapper.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|