System clocks form the basis of how VxWorks tracks time and timeouts.
Most OS objects that support timeouts (semaphores, message queues, events), as well as the taskDelay call, are in units of clock pulses that are based on the system clock.
Generally speaking, the system clock speed is chosen by the board designer for any reason.
Reducing the clock frequency slightly increases the system load, since during each clock signal of the system, the operating system must serve various timeout elements, time interval counters, and other internal elements.
If you need to complete a task at high speed (2000 - 8000 Hz), you can use the auxiliary clock. AuxClock API is a simplified interface to the interrupt service routine. Whenever the clock expires, the routine defined by sysAckClockConnect is called from the ISR aux clock.
There is no system overhead associated with Aux Clock during ISR maintenance.
Of course, to use auxClock, you need 2 hardware hours. In addition, some vxWorks components, such as spyware, use auxClock. If you have such a component, you cannot use it, because there is a conflict.
Note that if more than two timers are installed on your hardware platform, you can write your own routines to essentially do the same thing as the Aux Clock API.
source share