Embedded Linux Workflow Notes

Embedded work is mostly about respecting boundaries. Kernel changes, board descriptions, drivers, and user space all move together, but each layer needs its own debugging discipline.

The most useful habit I keep is documenting every hardware assumption next to the code that depends on it. That makes regression work much easier when the build is passing but the board behavior is not.

1. Verify the RT kernel config before chasing driver-level issues.
2. Check the device tree first when peripherals do not enumerate.
3. Confirm DMA, MMIO, and clock assumptions against the board documentation.
4. Keep a clean regression path for every low-level change.

This is the kind of note I expect to keep expanding as the embedded work grows. Short, practical, and close to the implementation details.