Arm Community
Site
Search
User
Site
Search
User
Groups
Research Collaboration and Enablement
DesignStart
Education Hub
Innovation
Open Source Software and Platforms
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello Forum
Operating Systems forum
SoC Design and Simulation forum
中文社区论区
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Innovation blog
Internet of Things (IoT) blog
Operating Systems blog
Research Articles
SoC Design and Simulation blog
Tools, Software and IDEs blog
中文社区博客
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Arm Development Studio forum
What to do upon detection of Error
Jump...
Cancel
Locked
Locked
Replies
2 replies
Subscribers
121 subscribers
Views
2076 views
Users
0 members are here
Options
Share
More actions
Cancel
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
Offline
Muhammad Ahsan
over 9 years ago
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,
Offline
Mahesh
over 9 years ago
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?
Cancel
Up
0
Down
Cancel
Offline
Martin Weidmann
over 9 years ago
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?
Cancel
Up
0
Down
Cancel