diff options
| author | hathach <[email protected]> | 2026-09-03 17:14:39 +0700 |
|---|---|---|
| committer | hathach <[email protected]> | 2026-09-04 04:21:57 +0700 |
| commit | 9e681141bc24ff71081dfce683ae4371e7520124 (patch) | |
| tree | 582dfcaad9b9f23be348143f12f1f9d0520e2052 /lib/FreeRTOS/Source/include/queue.h | |
| parent | dcb3fcfd30ac03b810d6de82674c008d5163400f (diff) | |
hil: sysview CI - rig capture subcommands and report generator
sysview_ci.py builds, flashes and captures the sysview-flagged boards
(stm32f407disco and raspberry_pi_pico in tinyusb.json) on the rig, taking
each board's flock via hil_lock and restoring park firmware afterwards.
Hard-won correctness baked in from the dogfood runs: firmware paths carry
the flasher's extension via FLASHER_SUFFIX (JLinkExe and OpenOCD infer the
image format from it, and the RTT control block still comes from the ELF,
which is not always the flashed image); WCH boards are detected by their
wch-riscv target config (is_wch_board(), the plain "openocd" flasher name
since #3804 folded openocd_wch/openocd_adi away); build and flash failures
are excerpted from BOTH ends (cmake prints the diagnosis first and the call
stack last, ninja the reverse) and flash failures include the flasher's own
output so rc=124 can distinguish a wedged probe from a dead target; a bad
ELF no longer aborts the whole multi-board run; the enumeration wait sits
after the capture session's own reset; each capture picks a free RTT server
port. session_resets()/sysview.attach_only skips the in-session reset for
boards that never come back from it (metro_m4_express: both campaign
captures died with 'No control block found' while attach-without-reset
streamed immediately) - the flasher's post-flash reset already supplied the
fresh boot.
The suites join the pre-commit hil-test hook and master's test/hil/test/
carve-out pin.
Diffstat (limited to 'lib/FreeRTOS/Source/include/queue.h')
0 files changed, 0 insertions, 0 deletions
