len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-04-20 21:41:59 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update comments in main-full.c of CM0 demo.

Browse source
This commit is contained in:
Richard Barry 2012-01-22 21:26:47 +00:00
parent ebc8ddd7da
commit f10b6ffdc5
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Demo/CORTEX_M0_LPC1114_LPCXpresso/RTOSDemo/Source/main-full.c
View file

@ -63,11 +63,12 @@
* required to configure the hardware, are defined in main.c.
******************************************************************************
*
* main_full() creates all the demo application tasks (including a set of tasks
* that test the interrupt nesting behaviour) and a timer, then starts the
* scheduler. The web documentation provides more details of the standard demo
* application tasks, which provide no particular functionality, but do provide
* a good example of how to use the FreeRTOS API.
* main_full() creates a set of standard demo tasks (including a set of tasks
* that test the interrupt nesting behaviour), some application specific tasks,
* and a timer. It then starts the scheduler. The web documentation provides
* more details of the standard demo application tasks, which provide no
* particular functionality, but do provide a good example of how to use the
* FreeRTOS API.
*
* The interrupt nesting test tasks require that two timers are configured to
* generate interrupts. The interrupt service routines are defined in
@ -92,7 +93,7 @@
* without reporting any errors. If the check timer callback discovers that a
* task has either stalled, or reported an error, then it changes the period of
* the check timer from the initial three seconds, to just 200ms. The callback
* function also toggles an LED each time it is called. This provides a visual
* function also toggles the LED each time it is called. This provides a visual
* indication of the system status: If the LED toggles every three seconds,
* then no issues have been discovered. If the LED toggles every 200ms, then
* an issue has been discovered with at least one task.