-portBASE_TYPE xTimer;\r
-\r
- xBaseFrequency = xBaseFrequencyIn;\r
-\r
- for( xTimer = 0; xTimer < configTIMER_QUEUE_LENGTH; xTimer++ )\r
- {\r
- /* As the timer queue is not yet full, it should be possible to both create\r
- and start a timer. These timers are being started before the scheduler has\r
- been started, so their block times should get set to zero within the timer\r
- API itself. */\r
- xFreeRunningTimers[ xTimer ] = xTimerCreate( "FR Timer", /* Text name to facilitate debugging. The kernel does not use this itself. */\r
- ( ( xTimer + 1 ) * xBaseFrequency ),/* The period for the timer. The plus 1 ensures a period of zero is not specified. */\r
- pdTRUE, /* Autoreload is set to true. */\r
- ( void * ) xTimer, /* An identifier for the timer as all the free running timers use the same callback. */\r
- prvFreeRunningTimerCallback ); /* The callback to be called when the timer expires. */\r
-\r
- if( xFreeRunningTimers[ xTimer ] == NULL )\r
- {\r
- xTestStatus = pdFAIL;\r
- }\r
- else\r
- {\r
- /* The scheduler has not yet started, so the block period of \r
- portMAX_DELAY should just get set to zero in xTimerStart(). Also,\r
- the timer queue is not yet full so xTimerStart() should return\r
- pdPASS. */\r
- if( xTimerStart( xFreeRunningTimers[ xTimer ], portMAX_DELAY ) != pdPASS )\r
- {\r
- xTestStatus = pdFAIL;\r
- }\r
- }\r
- }\r