• Locked Locked
  • Replies 2 replies
  • Subscribers 119 subscribers
  • Views 2400 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What to do upon detection of Error

Muhammad Ahsan
Note: This was originally posted on 29th July 2011 at http://forums.arm.com

Hi,
I have implemented a couple of tests for Cortex-M3. These tests include calculation of CRC checksum over selected flash area, verification of Clock using Clock Supervisor and verification of occurance of Interrupts. the tests are working perfectly but I am not sure what to do, in case CRC checksum is wrong, or any of the other mentioned tests do not meet the desired results.
One option is to implement endless loop, waiting for watchdog to hit, is it meaningful? any other ideas would be highly appreciated.
All these tests are part of self test library that has to be integrated with the end user application. Is it make sense to leave it to the user to define whatever he thinks suitable in case of failure of component?
Looking for some quick response!
Regards,
  • Arm Employee Badge
    Note: This was originally posted on 24th August 2011 at http://forums.arm.com

    I concur with ttfn , dependent on the type of verification test you could decide to either proceed with the next step or revalidate that test. Its entirely a system level decision. Perhaps if you had more specifics then we could provide better definitions for what your tests are really checking for?
  • Arm Employee Badge
    Note: This was originally posted on 2nd August 2011 at http://forums.arm.com

    There isn't really a set answer.  The question you should ask yourself is what would a failure mean, and what would be must useful/safest to do.

    For example, a CRC check might imply memory corruption.  Memory corruption would mean you could not rely on code executing correctly.  Therefore it might be best not to even attempt running it.  What would be helpful?  Error code?  Error light?  Error buzz?