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] [November 2015 Threads] System halt after running for a long timePosted by joe_her on November 3, 2015 I got a PC freertos simulation that looks OK, but after running for a few hours, it freezes.
I set breakpoints in all tasks, and no BP is hit, the only running loop is the prvSimulatedPeripheralTimer (), infinite for(;;) loop.
Any ideas that will help debugging this will be appreciated.
Thanks.
Johanan
System halt after running for a long timePosted by rtel on November 3, 2015 Is this using the FreeRTOS Windows port, which is often referred to as the Windows simulator, or is it a simulation you have created yourself?
System halt after running for a long timePosted by joe_her on November 3, 2015 Using FreeRTOS windows port.
Thanks
System halt after running for a long timePosted by rtel on November 3, 2015 Are you using any Windows system calls, such as printf, or WinSocks?
Those are known to cause issues, although there are workarounds.
Also, we have noticed strange behaviour when calling rand(), so will
provide our own version if it is necessary.
Regards.
System halt after running for a long timePosted by joe_her on November 3, 2015 Using winsoc for UDP. Actually the simulation is used as development for the STM32F4 target. The same code is used (using compiler #ifdef whenever necessary) for the PC simulation and target. All I/O hardware done by functions calls. In the simulation, it sends and receives UDP packets to an Arduino that activates all I/O, while the target uses the same function calls for real I/O.
If the problem is with the UDP socket, then I don't mind too much, as this is just a simulation. How can I verify this?
My current strategy is to comment out functions, until the one that creates the problem will be found. Whoever this takes a very long time...
System halt after running for a long timePosted by rtel on November 3, 2015 If you download the FreeRTOS+TCP source code
(http://www.freertos.org/tcp) you will see how we get around this.
Some of the demos use FreeRTOS+TCP sockets to communicate with WinSock
sockets. To do that reliably all use of the WinSock API is done inside
standard Windows threads (as opposed to Windows threads that are under
the control of the FreeRTOS scheduler). The standard Windows threads
then use a stream buffer (thread safe circular buffer with no system
calls) to pass data to and from the FreeRTOS tasks. The key is not to
have Windows system calls in FreeRTOS tasks themselves.
System halt after running for a long timePosted by joe_her on November 3, 2015 Yep, commenting out the UDP removed the problem, now I'll do the workaround.
Thanks agian, many hours saved....
System halt after running for a long timePosted by joe_her on November 11, 2015 Just by running that UDP task from windows thread with _beginthread ( ) , and communicating to FreeRTOS via a buffer fixed all these issues.
Thanks again.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|