feat(rp2040): warn on failed USB devices - #1090
Conversation
Detect present Windows USB devnodes with non-zero problem codes, report their topology during port scans, and recommend direct motherboard connections for external hubs. Closes #1087
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Detect present Windows USB devnodes with non-zero problem codes, report problem code and USB topology during fbuild port scan, and recommend direct motherboard USB connections when an external hub is detected. The diagnostic is non-fatal and never associates unidentified nodes with a target board. Closes #1087. Validation: focused warning tests, 150 fbuild-serial unit tests, all-target compile check, and live Windows scan with two Code 43 nodes detected.