* application. It is provided as a convenient development and demonstration\r
* test bed only. This was tested using Windows XP on a dual core laptop.\r
*\r
- * In this example, one simulated millisecond will take approximately 40ms to\r
- * execute, and Windows will not be running the FreeRTOS simulator threads\r
- * continuously, so the timing information in the FreeRTOS+Trace logs have no\r
- * meaningful units. See the documentation page for the Windows simulator for\r
- * an explanation of the slow timing:\r
+ * Windows will not be running the FreeRTOS simulator threads continuously, so \r
+ * the timing information in the FreeRTOS+Trace logs have no meaningful units. \r
+ * See the documentation page for the Windows simulator for an explanation of \r
+ * the slow timing:\r
* http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html\r
* - READ THE WEB DOCUMENTATION FOR THIS PORT FOR MORE INFORMATION ON USING IT -\r
*******************************************************************************\r
The simply blinky demo is implemented and described in main_blinky.c. The more \r
comprehensive test and demo application is implemented and described in \r
main_full.c. */\r
-#define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1\r
+#define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0\r
\r
/*\r
* main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.\r
* application. It is provided as a convenient development and demonstration\r
* test bed only. This was tested using Windows XP on a dual core laptop.\r
*\r
- * In this example, one simulated millisecond will take approximately 40ms to\r
- * execute, and Windows will not be running the FreeRTOS simulator threads\r
- * continuously, so the timing information in the FreeRTOS+Trace logs have no\r
- * meaningful units. See the documentation page for the Windows simulator for\r
- * an explanation of the slow timing:\r
+ * Windows will not be running the FreeRTOS simulator threads continuously, so \r
+ * the timing information in the FreeRTOS+Trace logs have no meaningful units. \r
+ * See the documentation page for the Windows simulator for an explanation of \r
+ * the slow timing:\r
* http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html\r
* - READ THE WEB DOCUMENTATION FOR THIS PORT FOR MORE INFORMATION ON USING IT -\r
*\r
* application. It is provided as a convenient development and demonstration\r
* test bed only. This was tested using Windows XP on a dual core laptop.\r
*\r
- * In this example, one simulated millisecond will take approximately 40ms to\r
- * execute, and Windows will not be running the FreeRTOS simulator threads\r
- * continuously, so the timing information in the FreeRTOS+Trace logs have no\r
- * meaningful units. See the documentation page for the Windows simulator for\r
- * an explanation of the slow timing:\r
+ * Windows will not be running the FreeRTOS simulator threads continuously, so \r
+ * the timing information in the FreeRTOS+Trace logs have no meaningful units. \r
+ * See the documentation page for the Windows simulator for an explanation of \r
+ * the slow timing:\r
* http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html\r
* - READ THE WEB DOCUMENTATION FOR THIS PORT FOR MORE INFORMATION ON USING IT -\r
*\r
static void prvCheckTask( void *pvParameters )\r
{\r
portTickType xNextWakeTime;\r
-const portTickType xCycleFrequency = 1000 / portTICK_RATE_MS;\r
+const portTickType xCycleFrequency = 2500 / portTICK_RATE_MS;\r
\r
/* Just to remove compiler warning. */\r
( void ) pvParameters;\r