Unnamed repository; edit this file 'description' to name the repository. http://cgit.235523.xyz/tinyusb.git/atom/?h=hil-openocd-recover-flasher 2026-08-28T19:47:20Z 2026-08-28T19:47:20Z hathach thach@tinyusb.org 2026-08-19T06:10:33Z urn:sha1:76313ba7723355fc8a3fe6a3da90916074d7f9fa 2026-08-28T19:47:20Z hathach thach@tinyusb.org 2026-08-19T06:00:22Z urn:sha1:340a1d7d1a72b2e1381f60fbcc54e08a034b389b 2026-08-28T19:47:20Z hathach thach@tinyusb.org 2026-08-19T05:39:49Z urn:sha1:7c2c09c63c08c980c02e188d2f814f5e9eb55fe3 2026-08-28T19:47:20Z hathach thach@tinyusb.org 2026-08-19T05:23:06Z urn:sha1:ba7c32fbae9529ea9db7ec25c4011d7021720f73 2026-08-28T19:41:13Z Ha Thach thach@tinyusb.org 2026-08-28T19:41:13Z urn:sha1:84dcec43c709643f8a1b1ebbab6d08fbbc605a6d rp2350: ETM trace board pico2_etm_trace 2026-08-28T18:08:40Z hathach thach@tinyusb.org 2026-08-28T09:40:25Z urn:sha1:f7eb812679598aecc1d7702264ba48e6c178d5da 2026-08-28T18:08:40Z hathach thach@tinyusb.org 2026-08-28T09:40:07Z urn:sha1:839c324458f6900a58182d9aa23d846e8ec55c94 Closes the sys-clock question. rp2350: the dynamic 156 MHz switch is removed - 150 MHz soak-tested clean (and a runtime switch truncates ETM capture on the trace carrier). rp2040 keeps its existing 120 MHz: soak sweeps show 120 = 8/8, stock 125 = 0/3 (bulk-OUT collapses, device NAKs ~600:1 with zero CRC errors on the wire), and 132 = 2/10 flaky despite an exact 12n/375k divider - no divider criterion predicts rp2040 PIO-USB health (the RX state machine samples at raw sysclk), so only soak-validated clocks ship. 2026-08-28T18:08:31Z hathach thach@tinyusb.org 2026-08-28T09:39:58Z urn:sha1:6e8e2caf7fc2dc5575f5e0c71e69c1b19b3f5699 Board files for the trace carrier (console GP12/13, LED GP10, I2C GP8/9, PIO-USB host on GP20, all retargeted in board.cmake so the SDK defaults cannot mux a trace pin), compile-time trace pin-conflict checks, the measured DBGPAUSE rationale, Ozone project, and skill/docs updates. Trace validated at the stock 150 MHz (75 MHz TRACECLK, +1 ns sampling): zero overflow through a 15 s throughput soak; V2 probe ceiling 120 MHz. 2026-08-28T09:09:22Z Ha Thach thach@tinyusb.org 2026-08-28T09:09:22Z urn:sha1:64d952c027df194ea8b107b3d5d0b6c4cb9a994b hil: drop the sysfs blindness subsystem and derive the recovery reserve 2026-08-28T07:18:41Z hathach thach@tinyusb.org 2026-08-27T08:26:43Z urn:sha1:20bb94fcf9ad7fca7fb685e53307f4d03b1340fd The modules were 21% comment, much of it review-cycle argument rather than guidance -- _kill_kids stated 'descendant by construction, no argv check needed' twice, eight lines apart. Deleting such comments outright makes maintenance worse: the next reader simplifies the thing the comment was defending. So the history moves to the 2026-07-30 fleet-wedge design doc, which gains a trim addendum recording what was removed, what was deliberately kept, and the rule that decided each -- the CI ceiling bounds how long a run burns, and does nothing about state that outlives it. One comment was not merely long but WRONG: the report wipe carried 'The unlink is DEFERRED to inside the pool try/except below', which is the opposite of what the code does -- it sits before Manager() with its own comment explaining why. That is the failure mode this pass is about, so it is deleted rather than reworded. Kept everywhere: citations that refute a plausible wrong reading. That usb_lock_device_interruptible is why the readers are killable, that usblp_mutex is driver-global, that rawmidi honours O_NONBLOCK where usblp does not. Two follow-ups are retired with them: pr3803-hil-blindness-reporting.md (there is no blindness to report any more) and pr3803-usbtest-recovery-reserve.md (the reserve is derived now). Kept: pr3803-flasher-recover.md, which PR #3832 implements, plus pr3803-pci-rebind-stranding.md and pr3803-hil-iar-rerun-spec.md, both independent of this work.