platform directory

• binary crates for stages bt0 + main
• default declarative image layout and boot flow (currently DTFS in board.dts)
  • see also Documentation: draft boot flow storage/memory design #783
• final image (tbd: oreboot-$platform-$features.bin)

binary crate

• manifest: Cargo.toml; name must be unique; convention tbd
• target config: .cargo/config.toml; linker script and optimizations
  • see also document how to keep binary size low #797
• build.rs for generating linker script (tbd via build system)

building, flashing and running images

• done in oreboot build system (currently xtask/)
• instrument building binary crates with configured features
  • objcopy to target/$arch/release/$elfname.bin
• stitch together stage binaries
  • depending on layout declaration (DTFS) and storage (SPI flash, SD card, ...)
  • offer passing custom declaration
  • needs solid validation, error handling and feedback
  • must not leak build system internals to the end user
• commonly, add vendor specific header(s), possibly signatures for secure boot
• per-platform functions/libraries to
  • flash an image
  • provision fuses (secure boot)
  • run bt0 (and possibly more) directly
  • debug (gdb, OpenOCD, ...)