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] [August 2011 Threads] portYIELD_WITHIN_API hangPosted by Andrea Benoni on August 10, 2011 I am using RedSuite with last FreeRTOS on a LPC2387. I solved some problems related to force supervisor on startup.
Now I have a problem with portYIELD_WITHIN_API inside vTaskDelay. The run stops on the Yield, I search similar post and I checked: - tick is running vPreemptiveTick loops - process is moved correctly from running->blocked->running based on tick
It seems blocked to "SWI 0" instruction.
Thank for your support Andrea
RE: portYIELD_WITHIN_API hangPosted by Johan Christiansen on August 10, 2011 Check that your software interrupt / exception is running and caught correctly by the appropriate handler.
RE: portYIELD_WITHIN_API hangPosted by Andrea Benoni on August 10, 2011 I checked with debugger and vPreemptiveTick is called, but return always to Yield point of vTaskDelay. vApplicationTickHook is correctly called by interupt function.
RE: portYIELD_WITHIN_API hangPosted by Andrea Benoni on August 10, 2011 I tried to activate vApplicationIdleHook, it is also executed only one time. I tried to trace return from vPreemtiveTick to task moving the pc+4 and it restart to executes until next vTaskDelay.
I am reading Using the FreeRTOS...guide but I am not able to find informations abut Yield should work at low level. I am tracing portSAVE_CONTEXT portRESTORE_CONTEXT and seems all ok. I am trying to understand what should cause the execution of next instruction.
Andrea
RE: portYIELD_WITHIN_API hangPosted by Andrea Benoni on August 10, 2011 Probably I found the problem, I had a wrong SWI pointer, correct is _swi: .word vPortYieldProcessor
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|