- Embedded Systems Architecture
- Daniele Lacamera
- 185字
- 2021-06-25 21:55:05
Source code organization
The code base should contain all the source code, third-party libraries, data, scripts, and automations needed to build the final image. It is a good idea to keep self-contained libraries in separate directories, so that they can be easily updated to newer versions by replacing the subdirectory itself. Makefiles and other scripts can be placed in the project's root directory. Application code should be short and synthetic, and access the modules abstracting the macro functionalities. Functional modules should describe a process while hiding the details of the underlying implementation, such as reading data from a sensor after it has been properly sampled and processed. Aiming for small, self-contained, and adequately abstracted modules also makes the components of the architecture easier to test. Keeping the majority of the logic for the application components separated from their hardware-specific implementation improves portability across different platforms, and allows us to change the peripherals and the interfaces used on the target even during the development phase. Abstracting too much, though, impacts costs, in terms of development effort and resources needed, so the right balance should be researched.
- Linux操作系統(tǒng)基礎
- Learning Android Intents
- Arch Linux Environment Setup How-to
- Linux網絡操作系統(tǒng)與實訓(第三版)
- 嵌入式操作系統(tǒng)(Linux篇)(微課版)
- 混沌工程:復雜系統(tǒng)韌性實現之道
- 數據中心系統(tǒng)工程及應用
- Java EE 8 Design Patterns and Best Practices
- macOS效率手冊
- 嵌入式系統(tǒng)原理及開發(fā)
- 竹林蹊徑:深入淺出windows驅動開發(fā)
- Linux內核設計的藝術:圖解Linux操作系統(tǒng)架構設計與實現原理
- Introduction to R for Quantitative Finance
- Learning BeagleBone
- Linux集群之美