FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [September 2005 Threads] vTaskDelay()Posted by Nobody/Anonymous on September 29, 2005 Are there any restrictions in using vTaskDelay nested im oder functions?
Ex. function2() { vTaskDelay(1); } function1() { vTaskDelay(1); function2(); } MyTask() { for(;;) { function1(); } }
vTaskDelay in function1() works fine, but in function2() it results in data_abort_handler. I'm using Philips LPC2138 with FreeRTOS V3.2.0.
Does anyone have an idea? Thank for help. Kind regards Stefan
RE: vTaskDelay()Posted by Nobody/Anonymous on September 29, 2005 There is no problem with using the function in this way. If there is a problem with the call at the higher nesting depth then the most likely problem would be a stack shortage - as the function depth will be using more stack before the call toe vTaskDelay. Try increasing the stack allocated to the task when the task is created.
RE: vTaskDelay()Posted by Nobody/Anonymous on September 30, 2005 You're absolutly right. It was a Problem wit to less stack. Thanks a lot!
Kind regards Stefan
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|