Unlock the Gateway: Join the Embed Threads
Unlock the Possibilities: Dive In with Login Access
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As a firmware developer, I’m interested in learning about best practices for firmware development in embedded systems. What are some recommended coding practices, modular design approaches, and software testing strategies for developing reliable and maintainable firmware?
Few of best practices I think are :-
1)Use of static qualifier for global variables which are only used in that .c files
2)Divide long codes in multiple functions
3)Create separate .c file & .h file for every pheripheral like do,adc etc
4)use of volatile qualifier for variables used in ISR
5)And most importantly naming of variables should be proper
https://betterprogramming.pub/the-power-of-10-nasas-rules-for-coding-43ae1764f73d?gi=ca3059da6748
These rules are Stated by NASA
These tend to match how I follow my coding standards
Folks do take a look;)