Originally published in the November 1988 Embedded Systems Programming magazine. Correction is the final step of any debugging exercise. Sometimes bug eradication is straightforward; sometimes a bug ...

In the world of embedded systems, the language debate is alive and well. For years, C has dominated this space, its minimalistic design and low-level control giving embedded engineers the tools to ...

Ask most embedded developers why they're still writing firmware in C, and you'll hear the same answer: "C++ is too heavy for embedded." That concern has merit. It's also more than 20 years out of date ...

Share on Facebook (opens in a new window) Share on X (opens in a new window) Share on Reddit (opens in a new window) Share on Hacker News (opens in a new window) Share on Flipboard (opens in a new ...

BARR-C:2018 is fully harmonized with MISRA C:2012. Many firmware developers choose to combine bug-killing stylistic rules from the BARR-C standard with safety guidelines from MISRA C. BARR-C:2018 is ...

C remains the darling of embedded programmers, but C++ garners a sizable chunk. Using C++ features judiciously can result in code that’s as efficient or more efficient than a comparable C application.

One of the key benefits of the C language, which is the reason it is so popular for embedded applications, is that it is a high-level, structured programming language, but has low-level capabilities.

Unit testing is a technique of breaking the code in small units of the entire code. These units can be verified to check the behaviour of a specific aspect of the software. One of the major challenges ...