4 ms·
MISRA is there as a standard for safety-critical code. Some contracts, some customers, some regulatory regimes will require compliance with MISRA, or perhaps an
by ribs 3y ago
MISRA is there as a standard for safety-critical code. Some contracts, some customers, some regulatory regimes will require compliance with MISRA, or perhaps another embedded coding standard, like AUTOSAR.
Generally, your customer/regulator will allow you to deviate from the standard; you just need to document and explain the deviations.
A static analysis tool like Helix QAC or Klocwork (bias: my company Perforce sells them) will capture your compilation and scan your code in detail to find deviations from the standard. You can then fix those deviations, or use the tool to document and explain them.
- phkahler 3y ago>> or perhaps another embedded coding standard, like AUTOSAR. I can deal with MISRA, it's just a safer subset of C. Most people demanding AUTOSAR compliance don't even know what AUTOSAR was created for, or the fact that those use cases never actually happen in practice. It's so fucked up I won't even work for a company producing AUTOSAR code any more. It's just a hard NO from me because it's an absolute waste of time and money.
- rcxdude 3y agoSee this (now somewhat legendary on the subreddit) comment on r/embedded regarding autosar: https://www.reddit.com/r/embedded/comments/leq366/comment/gmiq6d0/ https://www.reddit.com/r/embedded/comments/leq366/comment/gm... . You're not alone.