Repository navigation
Home
Buildroot external tree for STM32MP135D, targeting the MyIR MYD-YF135-256N-256D SOM.
This external tree supports projects shipping on the STM32MP13, specifically the MYD-YF135 SOM, that want to stay close to upstream Buildroot, Linux, and firmware, so that security fixes land quickly and version bumps remain practical instead of waiting on vendor updates.
Highlights of this project:
- Upstream tags for Buildroot, Linux, TF-A, OP-TEE, and U-Boot.
- Board changes isolated in
board/andconfigs/. - Small drift, easier release-to-release incremental upgrades.
- A/B firmware and root filesystem updates with factory fallback, via RAUC and a TF-A BL2 fallback walk, with no out-of-tree patches.
- Nix and flakes for reproducible host tooling, plus hermetic full-image and SDK builds.
Hardware and driver functionality is limited to what is supported in upstream Linux, U-Boot, TF-A, and OP-TEE. If this matches your priorities, start with the Setup page.
The primary target is USB gadget devices: OTG in peripheral mode, a USB host port, SD, and UART console. Ethernet, audio, display, and camera are not enabled at this time, but dbl-buildroot may be a good starting point for applications that need them.
- Setup: Prerequisites, Nix environment, build commands, incremental targets, and hermetic builds.
- Hardware: SoC, RAM, flash, console, memory map, and SPI-NAND partition layout.
- Boot Chain: Boot sequence, device tree, and NAND parameters with OTP fuse details.
- Flashing: DFU flashing via STM32CubeProgrammer and BOOT pin settings.
- Build Variants: Release and debug build variants, external toolchain SDK, and configuration fragments.
- CI: GitHub Actions workflows, running locally with act, and caching.
- Parent Integration: Submodule usage, mkProject parameters, parent device tree, Nix-built rootfs overlays, updating, and drift detection.
- Differences: Comparison with vendor and community configurations.
See the CONTRIBUTING file for patch guidelines, pre-commit setup, and commit style.
See the SECURITY file for vulnerability reporting.