Unnamed repository; edit this file 'description' to name the repository. http://cgit.235523.xyz/tinyusb.git/atom/docs/reference/hil_boards.md?h=hil-add-ea4088qs 2026-09-03T21:03:39Z 2026-09-03T21:03:39Z hathach thach@tinyusb.org 2026-09-03T11:19:17Z urn:sha1:ff9767e7e0297a94f26885d8a91f273707ec9507 The board's probe is an LPC-Link2 with no VCOM, so its console is RTT. Two host tests could not run that way: test_host_cdc_msc_hid and test_host_msc_file_explorer opened the flasher's VCOM directly instead of going through open_board_console(), and the config gate rejecting is_cdc/is_msc fixtures on "logger": "rtt" boards existed only to keep them from dying mid-run on a port that does not exist. Route both through the console abstraction and drop the gate. The reset ordering differs per console -- RTT owns the probe so the board must be reset before the console opens, a VCOM survives the reset so it opens first -- and that rule now lives in open_console_reset() instead of being spelled out at each call site. The roster entry runs device, host and dual: USB1's Type-A drives a hub with a CH340 (TX-RX shorted, for the cdc echo) and a thumbdrive, while USB2 keeps serving the device tests. BUFFER_SIZE_DOWN=128 because that echo writes up to 64 bytes at once and SEGGER's ring keeps one byte free, which the 16-byte default cannot hold; 64 measured unreliable, 128 reliable. Measured on the rig: 19 passed, 0 failed, 0 skipped. usbtest 30/30, host MSC reads 682 KB/s, device CDC/MSC ~510 kB/s (full speed behind the rig's hub). 2026-08-25T02:46:42Z Ha Thach thach@tinyusb.org 2026-08-25T02:46:42Z urn:sha1:da255b1d2db10b8f31332a779b2a526f579acee1 ci: an empty selection must build nothing, plus selector follow-ups A PR whose build axis legitimately selected nothing rebuilt everything. build.yml reads .build.families twice - as a |-joined regex, and implicitly as "is anything selected" - but tested only -z "$FAMILY_REGEX", which an empty list and a charset-rejected one both satisfy while meaning opposite things. ci_set_matrix had already returned the correct all-empty matrix; the fall-open branch discarded it. #3842 and #3840 each spent 74 cmake legs on it. Branch on the two cases instead, rename FAM_* to FAMILY_*, and cover the block with a test that extracts it from build.yml and executes it - it had no test at all, which is how this shipped through two merges. Follow-ups to the same machinery: glob.escape the repo root at five sites, so a checkout path containing [ or * stops failing closed; drop the ci-full label, read after the matrix was already computed and so never functional; delete 13 mcu:MKL25ZXX / mcu:SAME5X skip tokens matching no board; carry the rule table in the module docstring, guarded against drift; and pin six selection behaviours a mutation pass proved untested. Cut the selector's cost 1.8x (26.0s -> 14.6s) with 0 divergences over 260 paths, and stop scoping the membrowse upload by the PR example filter. 2026-08-20T17:47:27Z hathach thach@tinyusb.org 2026-08-20T07:30:59Z urn:sha1:872b4fbdc3c607b522211839a6b3b82e18310a1b Document the ci and hfp HIL rigs in enough detail to reproduce one: bill of materials with photos, BIOS/IOMMU and vfio-pci passthrough on the Proxmox host, the Renesas uPD720201 firmware install, the guest software and permissions, the one-hub-per-root-port USB topology rule and the per-box split of probe and DUT hubs, how CI drives the rigs, and the operational gotchas. The attached-board table is generated from test/hil/tinyusb.json and test/hil/hfp.json by tools/gen_doc.py into docs/reference/hil_boards.md, which the page includes. Sphinx excludes that partial so it is not also built as an orphan document. Also exclude docs/superpowers/ from the Sphinx build: it holds internal plans, specs and handoffs rather than published documentation, and since nothing references them from a toctree each emitted "document isn't included in any toctree" -- 26 warnings in total, so build_doc.py -W could never pass. It now does.