Say you (or a customer) want assurances of better quality embedded code. What can be done other than "be careful" and "lots of unit testing"?
Follow most of the MISRA standard? Do something like this to measure code coverage during testing?
https://mcuoneclipse.com/2014/12/26/code-coverage-for-embedded-target-with-eclipse-gcc-and-gcov/
The above modifies the code produced - I can imagine alternatives involving the automated use of a debugger.
Much of quality is "I know it when I see it", but that doesn't satisfy a customer looking for something more specific.
Follow most of the MISRA standard? Do something like this to measure code coverage during testing?
https://mcuoneclipse.com/2014/12/26/code-coverage-for-embedded-target-with-eclipse-gcc-and-gcov/
The above modifies the code produced - I can imagine alternatives involving the automated use of a debugger.
Much of quality is "I know it when I see it", but that doesn't satisfy a customer looking for something more specific.