# Using Asserts in Embedded Systems | Interrupt

**URL:** <https://community.memfault.com/t/using-asserts-in-embedded-systems-interrupt/98>\
**Category:** Blog\
**Created:** [November 6, 2019, 6:22am UTC](https://community.memfault.com/t/using-asserts-in-embedded-systems-interrupt/98 "2019-11-06T06:22:26Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![t.piotrowicz](https://avatars.discourse-cdn.com/v4/letter/t/b4bc9f/32.png) [@t.piotrowicz](https://community.memfault.com/u/t.piotrowicz)\
**Post date:** [January 2, 2020, 9:30pm UTC](https://community.memfault.com/t/using-asserts-in-embedded-systems-interrupt/98/11 "2020-01-02T21:30:49Z")

</div>

Great article!  
I don’t understand fully the section When Not to Assert for example why not using assert in these cases:

- Don’t assert on operations that depend on the hardware behaving appropriately. If a sensor says it will return a value between 0-100, it’s probably best not assert when it’s above 100, because you can never trust today’s cheap hardware.
- Don’t assert on the contents of data read from persistent storage, unless it’s guaranteed to be valid. The data read from flash or a filesystem could be corrupted.

can you describe a little more here?

---

_[View the full topic](https://community.memfault.com/t/using-asserts-in-embedded-systems-interrupt/98)._