You're reading from Mastering Embedded Linux Programming - Third Edition

Product type Book

Published in May 2021

Publisher Packt

ISBN-13 9781789530384

Pages 758 pages

Edition 3rd Edition

Languages

Concepts

Embedded Systems

Authors (2):

Frank Vasquez

Chris Simmonds

View More author details

Table of Contents (27) Chapters

Preface

1. Section 1: Elements of Embedded Linux

2. Chapter 1: Starting Out

3. Chapter 2: Learning about Toolchains

4. Chapter 3: All about Bootloaders

5. Chapter 4: Configuring and Building the Kernel

6. Chapter 5: Building a Root Filesystem

7. Chapter 6: Selecting a Build System

8. Chapter 7: Developing with Yocto

9. Chapter 8: Yocto Under the Hood

10. Section 2: System Architecture and Design Decisions

11. Chapter 9: Creating a Storage Strategy

12. Chapter 10: Updating Software in the Field

13. Chapter 11: Interfacing with Device Drivers

14. Chapter 12: Prototyping with Breakout Boards

15. Chapter 13: Starting Up – The init Program

16. Chapter 14: Starting with BusyBox runit

17. Chapter 15: Managing Power

18. Section 3: Writing Embedded Applications

19. Chapter 16: Packaging Python

20. Chapter 17: Learning about Processes and Threads

21. Chapter 18: Managing Memory

22. Section 4: Debugging and Optimizing Performance

23. Chapter 19: Debugging with GDB

24. Chapter 20: Profiling and Tracing

25. Chapter 21: Real-Time Programming

26. Other Books You May Enjoy

Porting Linux to a new board

Porting Linux to a new board can be easy or difficult, depending on how similar your board is to an existing development board. In Chapter 3, All About Bootloaders, we
ported U-Boot to a new board, named Nova, which is based on the BeagleBone Black. Very few changes need to be made to the kernel code, so it is very easy. If you are porting to completely new and innovative hardware, there will be more to do. We will delve
deeper into the topic of additional hardware peripherals in Chapter 12, Prototyping with Breakout Boards.

The organization of architecture-specific code in arch/$ARCH differs from one system to another. The x86 architecture is pretty clean because most hardware details are detected at runtime. The PowerPC architecture puts SoC and board-specific files into subdirectory platforms. The ARM architecture, on the other hand, is quite messy, in part because there is a lot of variability between the many ARM-based SoCs. Platform-dependent code...