delay.h File Reference

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Functions
void	delay1s (void)
	Delays for one second. This routine is hard-timed and does not rely on interrupts. More...
void	delay50ms (void)
	Delays for 50ms. This routine is hard-timed and does not rely on interrupts. More...
void	delay50us (void)
	Delays for 50us. This routine is hard-timed and does not rely on interrupts. More...
void	delay5ms (void)
	Delays for 5ms. This routine is hard-timed and does not rely on interrupts. More...

Detailed Description

Note

The routines here are hard-timed and only depend on the CPU clock. They don't rely on interrupts being enabled or timers running but the delay time can be extended if interrupts consume CPU time while they are active since interrupts are not disabled.
They just eat up the CPU power for the time they are running.
If the CPU clock changes you'll have to adopt the delay50us-function since all of them rely on this.

Function Documentation

delay1s()

void delay1s

(

void

)

Delays for one second. This routine is hard-timed and does not rely on interrupts.

Referenced by DefaultConfig(), FTest(), and FTestSWUnreg().

Here is the caller graph for this function:

delay50ms()

void delay50ms

(

void

)

Delays for 50ms. This routine is hard-timed and does not rely on interrupts.

Referenced by Delay1s(), DoKFlags(), FTestToggleSignal(), and InitLCD().

Here is the caller graph for this function:

delay50us()

void delay50us

(

void

)

Delays for 50us. This routine is hard-timed and does not rely on interrupts.

Referenced by FTest485GetConnects(), FTestWalkingOne(), FTestWalkingZero(), and InitLCD().

Here is the caller graph for this function:

delay5ms()

void delay5ms

(

void

)

Delays for 5ms. This routine is hard-timed and does not rely on interrupts.

Referenced by InitLCD().

Here is the caller graph for this function: