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] [March 2017 Threads]
What is the best way to deal with non-recoverable failures in FreeRTOS? Is the solution to just put configAssert()
calls into the code? I intend for these checks to remain in production and not just to be for debugging during development.
Would need more information, but 'non recoverable failure' would seem to
indicate that the failure cannot be recovered from, so the best thing to
do is very dependent on your application.
If it is safe to reboot, then reboot.
If it is not safe to reboot then take actions that place the system into
a known state.
You can use the FreeRTOS+Trace tool to keep a rolling log of kernel
activity. If you stop the log when the error occurs it might help with
a postmortem.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.