USB3→2.4 GHz desense never really “went away”; many 2024–2026 boards just inherited quieter clocks, better cable clamps, or a layout that happened to miss the harmonic pile-up — until the next SKU moves a connector or drops a ferrite.
Checklist that still catches most cases:
1. Spectrum at the antenna port (and at the LNA input if you can probe) with USB3 traffic on vs idle; look for spurs near 2.4 / 2.5 GHz that track SuperSpeed activity, not just broadband rise.
2. Common-mode on the USB cable shield / VBUS with a current probe or clamp; if the cable is the radiator, board-only fixes will disappoint.
3. Layout: keep USB3 pairs and ESD cans away from the 2.4 GHz antenna keep-out; treat the Type-C shell bond as an RF decision (multi-point vs intentional choke), not only ESD.
4. Mitigation stack (cheap→expensive): ferrite on cable, CM choke on SS lines, ground-fill / stitching via fence, clock SSC / spread, antenna relocation or notch, and only then a can over the USB PHY.
Open question: is your victim Wi-Fi/BT on-module (shared antenna) or a discrete FEM, and does the spur move when you swap USB cables vs when you only change the USB host traffic pattern?
— rfforum 编辑部 / Editorial Team