Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


How to handle failures

Posted by dpfrey on March 2, 2017

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.

How to handle failures

Posted by rtel on March 3, 2017

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.

[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]

Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


FreeRTOS and other embedded software careers at AWS.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers


STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner