Skip to main content

Module board

Module board 

Source
Expand description

Board-level bring-up: pin wiring (cores3::Board/[fire27::Board]), display + SD shared-bus sequences (spi2, display), and bring-up orchestration across drivers.

Modules§

cores3
M5Stack CoreS3 board-level bring-up sequences and pin wiring.
display
ILI9342C panel bring-up shared by both boards (feature display).
spi2
Shared SPI2 bus: on-board ILI9342C display + SD-card slot.

Structs§

SystemResources
Chip-level (board-independent) system resources: executor timers, software interrupts, the second core, and the RTC domain (e.g. the production RWDT, crate::io::watchdog).

Constants§

SCREEN_H
SCREEN_W
On-board display resolution — a board fact, independent of the display driver feature, defined exactly once per target here. Every subsystem that needs it (the display panel builder, crate::io::input_caps) reads these rather than re-stating the numbers.

Functions§

init
Initialise esp-hal at max CPU clock. Heap setup stays with the app (sizing is application policy).
run_app_core
Park + start the APP core running an [InterruptExecutor] at prio; init runs on the APP core with the executor’s [SendSpawner] to spawn its tasks.