Layering of MCU Software

sfesdm

Layering of MCU Software [Copy link]

After working for many years, I have written programs that implement functions according to requirements, and I consider them completed after the tests are stable. However, looking at the various couplings between codes, I always feel "uncomfortable" and always have a desire to separate them. However, due to various factors, I have never learned the idea of layering, let alone separating the codes.

Recently, I finally made up my mind to take this first step. Please tell me whether you have the habit of layering your code in your work, or talk about your own layering ideas~~~

kiroking

For me, software layering is for easy porting, which makes it easier for me to develop the next similar project.

dcexpert

This is where the importance of system architecture comes in. Why do some programs look complicated? In fact, it is to better achieve modularization and separate the application from the underlying layer.

Software engineering is about solving these problems, not just creating a program.

qwqwqw2088

The MCU software is layered, which means it is easy to transplant and archive, so that future generations can read it.

There are some differences from modular programming

高进

MCU software is also divided into layers? This is overkill.

How can we layer things if there is no object-oriented programming, no design patterns, and no reflection mechanism?

Make some library functions yourself, and call the library functions when you use them. Then you can update only the library files when you update.