We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Joseph,
Thanks. I don't like the idea of skipping the faulty instruction, either.
In case that M3 is handling multiple tasks within a queue, and it gets stuck (bus fault by read access to system memory) within one task.
Is it possible for M3 to abort the remaining operations after limited retries for current task gracefully and move forward to handle next task in the queue? or M3 has to be stalled for a system reset.
Kevin
Hi Kevin,
You can possibly implement this in your bus fault handler.
For example, create a static variable to count the number of retry, and if it exceed the limit then signal to the embedded OS to kill the task. You might also able instruct the OS to restart the task, but it depends on the OS you use. Or potentially move the task into a suspended queue.
But whether the system can still function correctly after the task is killed and restarted is application dependent.
Regards,
Joseph
Sent from my iPad