hw_validated Directory Reference

Apps confirmed working on a stock EK-RA8D2 board: smoke (no-UART), uart (print over SCI), manual (jumper/button steps), and hil (hardware-in-the-loop, driven by the bench rig).

More...

Directory dependency graph for hw_validated:

Directories
	c6
	hil
	manual

Detailed Description

Apps confirmed working on a stock EK-RA8D2 board: smoke (no-UART), uart (print over SCI), manual (jumper/button steps), and hil (hardware-in-the-loop, driven by the bench rig).

Apps confirmed working on a stock EK-RA8D2, filed by which harness can verify them, not by how mature they are.

	Verified by
hil/	The app's own hil.conf: UART scrape, J-Link memprobe, RTT, USB class binding or a wire-side TCP probe. just hil::suite on the bench, and the same manifests again in the emulator via just apps::emulator::eil.
c6/	The same, on the ESP32-C6 bench configuration. just hil::c6.
manual/	Build only – acceptance is a human observation, a picture on the LCD or a file copied from a PC.

just apps::build <appname> from the repo root builds any of them; the name works whichever subdir the app lives in.

Promoting an app is a git mv here plus a root-level hil.conf for its examples/ek_ra8d2/hw_validated/<lane>/<app>/src/main.c. hil/ is the default and carries an obligation: check_hil_eil_parity.py requires every app in it to be exercised by ra8_emulator too, in a mode the EIL suite can assert, with no skips – which is what stops a new HIL app from quietly escaping emulator coverage, and why an app whose peripheral the emulator does not model cannot simply be dropped in.

c6/ is separate for a bench reason, not a maturity one: C6 apps need SW4-4 OFF, which takes the Arduino and mikroBUS connectors off the board for every app in the default pass, so one run cannot serve both – and ra8_emulator models no C6 (#494), so the parity obligation above cannot be met yet.