[META] probe-rs + LPC deploy audit: reconcile follow-ups after #1000 #1002

Context

This is a new roll-up created after concern that the previous focused meta, #1000, may have been closed too aggressively.

#1000 was opened and closed on 2026-07-07 after PR #1001 merged. The closeout says the probe-rs / LPC-Link2 path is complete, but this issue exists as the guardrail: do not rely on the #1000 closeout alone. Reconcile every strong related probe-rs / LPC issue and either prove it is resolved on current main or file a concrete follow-up.

Search scope used to seed this issue: FastLED/fbuild issues matching probe-rs, probe_rs, LPC, LPC845, LPC8xx, LPC-Link2, CMSIS-DAP, lpc21isp, and nxplpc. Weak keyword-only matches were excluded unless they overlap the LPC deploy path.

Primary probe-rs / LPC-Link2 cluster

• probe-rs on LPC-Link2 CMSIS-DAP v1.0.7: series of upstream quirks to patch through #930 - original probe-rs on LPC-Link2 CMSIS-DAP v1.0.7 umbrella; verify its split-out children fully cover the original blocker list.
• probe-rs on LPC-Link2 v1.0.7: blocker #4 — SerialNumber + remaining DAP_Info fallbacks (#930 follow-up) #931 - DAP_Info fallback work; confirm the close is backed by current probe-rs behavior and proof links, not just the later meta close.
• probe-rs on LPC-Link2 v1.0.7: SWD-attach layer quirks (#930 follow-up) #932 - SWD attach quirks; confirm the close is backed by FastLED/probe-rs changes and hardware evidence.
• cross-compile + host FastLED/probe-rs fork (#930 follow-up) #933 - probe-rs artifact channel; verify fbuild consumes a specific usable FastLED probe-rs release with all six host artifacts, provenance, and SHA256 verification.
• wire fbuild LpcDeployer to prefer probe-rs when CMSIS-DAP probe enumerates (#930 follow-up) #934 - fbuild LpcDeployer integration; verify probe-rs dispatch, lpc21isp fallback, and --no-probe-rs coverage.
• probe-rs LPC-Link2 v1.0.7: push through all blockers end-to-end, single-shot #935 - single-shot hardware validation umbrella; preserve its hardware evidence and identify any remaining unverified blocker from the original sequence.
• probe-rs (fork): replace hidapi with nusb for CMSIS-DAP v1 HID transport — the actual fix for touchless LPC-Link2 deploy #936 - nusb/HID transport issue; confirm whether the current winning path is nusb, hidapi fallback, or both, and document the driver-state implication for Windows.
• [META] probe-rs + LPC-Link2 LPC deploy roll-up #1000 - prior closed meta; audit its closeout against current main and link this replacement issue from there if needed.
• PR Install FastLED probe-rs for LPC SWD deploy #1001 - implementation PR; audit tests, fallback behavior, release pinning, and post-merge hardware validation.

Parent LPC deploy/build context

• [META] LPC845-BRK on-hand burn-down: cover the open LPC8xx work end-to-end #586 - broader LPC845-BRK burn-down remains open; update it so this new probe-rs/LPC audit is the active focused tracker.
• fbuild deploy: own nxplpc/LPC8xx flash end-to-end (FastLED is removing its direct pyocd path) #921 - fbuild-owned nxplpc/LPC8xx flash path; confirm it is truly superseded by the current deploy path.
• nxplpc: LpcDeployer feeds -hex to a .bin firmware and passes CMSIS-DAP speed=1000 as the lpc21isp baud #927 - immediate lpc21isp .bin / baud issues; confirm no regression when probe-rs is unavailable or disabled.
• LPC845-BRK: deploy must always unwedge the shared VCOM (pyocd/SWD flash leaves CDC in Windows error 31) #565 - VCOM unwedge; confirm probe-rs-as-default does not reintroduce the shared VCOM/Windows error 31 failure mode.
• LPC8xx Stage 7: deploy support (lpc21isp / pyocd / cmsis-dap / jlink) #551 - original LPC8xx deploy support; verify the current deployer closes the actual Stage 7 requirement, not only one happy path.
• LPC8xx Stage 6: FastLED canary — Blink/DemoReel100/FxEngine compile for lpc845/lpc804 #550, [META] LPC8xx end-to-end support: orchestrator + Arduino framework + real FastLED sketches #487, Native support for NXP LPC8xx (LPC845-BRK, LPCXpresso804, LPCXpresso845-MAX) #513, Stage 2: implement NXP LPC8xx build orchestrator (replace stub, unstub LPC804/LPC845 CI) #477, lpc8xx: convert 5 stub workflows to real builds (Stage 8 of #487) — orchestrator + upstream proof are in #528 - older LPC8xx build/framework/CI support context; keep as background unless the audit finds a direct deploy regression.
• [META] FastLED #3339 LPC bring-up lessons — fbuild structural follow-up across 4 axes #699 - structural LPC bring-up follow-ups; keep as background unless a regression points back to serial/deploy architecture.

Adjacent open issues surfaced by search

These matched the search terms but are not automatically blockers for this focused deploy audit. Reclassify only if the investigation proves overlap:

• fbuild: design unified namespaced routing for platform/framework/library artifacts driven by platformio.ini [env:*] #574 - namespaced platform/framework/library routing.
• Proposal: first-class fbuild cache save / restore for toolchains + platforms + framework + zccache sidecar #527 - cache save/restore.
• feat(online-data): ingest per-board VID:PID tables from upstream vendor manifests #722 - VID/PID data ingestion.
• tracking: ignored-test inventory (driven by #839) #880 - ignored-test inventory.
• Multi-checkout daemon collision: two repos share port 8765, wrong-version daemon serves both (stale flags, dead-endpoint deploys) #940 - multi-checkout daemon collision / wrong-version daemon.

Acceptance criteria

• Every primary cluster issue above has a comment or linked PR proving the resolved state on current main, or a new follow-up issue exists for the gap.
• fbuild deploy tests/platform/lpc845brk -e lpc845brk --port COM10 --verbose is validated on current main and shows probe-rs SWD flashing through the LPC-Link2 CMSIS-DAP path with COM10 reopening afterward.
• fbuild deploy ... --no-probe-rs is validated or covered by tests to prove the lpc21isp fallback path still works.
• The probe-rs artifact source is current, reproducible, and checksum-verified for all supported hosts, or there is a follow-up that names the missing artifact/provenance work.
• [META] LPC845-BRK on-hand burn-down: cover the open LPC8xx work end-to-end #586 links here as the focused probe-rs/LPC deploy audit and no longer treats [META] probe-rs + LPC-Link2 LPC deploy roll-up #1000 as the only source of truth.
• This issue is closed only after the audit is complete, not merely because Install FastLED probe-rs for LPC SWD deploy #1001 is merged.

Related

• Previous focused meta: [META] probe-rs + LPC-Link2 LPC deploy roll-up #1000
• Implementation PR: Install FastLED probe-rs for LPC SWD deploy #1001
• Broader LPC tracker: [META] LPC845-BRK on-hand burn-down: cover the open LPC8xx work end-to-end #586