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] [June 2012 Threads] Dealing with MPU faultsPosted by Tamir Michael on June 25, 2012 Hello,
I am using a LPC1788 with FreeRTOS MPU. In case of a memory protection fault, is there a valid and solid way to resume program operation? I intend to develop the system with the MPU enabled, but if a fielded system encounters a memory issue I do not necessarily with the have it watchdog reset and report a failure - some violations are survivable, or maybe this is compromises the entire purpose of an MPU...? I would appreciate any opinion.
RE: Dealing with MPU faultsPosted by Richard on June 25, 2012 MPU faults allow you to detect access violations before they occur. That means the system state is know because nothing bad has actually happened yet, so you can then take evasive action as is appropriate to your application. This is different to detecting something like a stack overflow after it has happened, because after it has happened all you know is it has happened, and that is it, so there is nothing you can do to correct the situation with confidence that you have corrected everything.
Only the application itself can know what to do when a fault occurs. The application knows the software components, which are critical, which not, which can be restarted, which it would not be safe to restart, etc.
Regards.
RE: Dealing with MPU faultsPosted by Tamir Michael on June 26, 2012 Thank you.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|