Examine RNDIS example for tiny USB library#1
Merged
chipsoft merged 5 commits intoNov 16, 2025
Conversation
Root cause analysis shows RW612 USB not detected on Windows 10 due to missing USB PHY initialization in TinyUSB board support. Analysis documents include: - Root cause: USB PHY power-on and register configuration missing - Comparison with working iMXRT implementation - Hardware architecture details (ChipIdea HS controller) - Step-by-step fix implementation guide - NXP SDK reference instructions Key findings: - USB controller clock is enabled correctly - USB PHY is never initialized (PWD, CTRL registers) - D+/D- transceivers remain inactive - Windows sees no device at all Fix requires: - Adding USB_DevicePhyInit() call to hw/bsp/rw612/family.c - USB PHY register configuration from NXP RW612 SDK - Possible USB pin mux configuration References NXP SDK USB examples for proper PHY initialization code.
Comprehensive analysis of USB PHY initialization across NXP boards to fix RW612 USB detection issue on Windows 10. Key findings: - Analyzed 3 NXP boards using ChipIdea HS USB controller - MCX MCXN9 provides best reference (modern architecture) - iMXRT has similar USBPHY initialization approach - LPC18/43 uses library-based init (not applicable) RW612_USB_REFERENCE_COMPARISON.md: - Detailed comparison of USB init methods (MCX, iMXRT, LPC) - MCX MCXN9 code analysis (lines 133-185) - Complete USB PHY initialization sequence - Power domain setup, clock config, PHY register init - TX timing calibration values - Identifies MCX as best reference for RW612 RW612_USB_PHY_FIX_IMPLEMENTATION.md: - Three implementation approaches: 1. Direct USBPHY register access (preferred - like MCX) 2. NXP SDK USB init functions 3. Minimal experimental init for testing - Complete code examples with line-by-line comments - Testing procedures and expected results - Troubleshooting guide for common issues - Verification checklist Implementation based on MCX reference: - Power on USB PHY (USBPHY->PWD = 0) - Enable LS/FS support (CTRL register) - Configure TX calibration - Uses same pattern as working MCX/iMXRT boards Critical missing steps identified in current RW612 code: - No USB PHY power-on sequence - No USBPHY register initialization - No TX timing configuration - Only clock enable + reset (insufficient) Next steps: - Verify USBPHY peripheral availability in RW612 headers - Apply fix from implementation guide - Test USB enumeration on Windows 10 References: - hw/bsp/mcx/family.c (primary reference) - hw/bsp/imxrt/family.c (secondary reference) - hw/bsp/lpc18/family.c (library approach)
Executive summary document consolidating all USB PHY analysis findings and providing clear path forward for fixing RW612 USB enumeration. Consolidates findings from: - RW612_USB_PHY_ISSUE_ANALYSIS.md (root cause) - RW612_USB_FIX_INSTRUCTIONS.md (step-by-step guide) - RW612_USB_REFERENCE_COMPARISON.md (board comparison) - RW612_USB_PHY_FIX_IMPLEMENTATION.md (concrete code) Key highlights: - Executive summary of root cause (missing USB PHY init) - Three-phase analysis breakdown (investigation → hardware → comparison) - Quick start guide with 3 implementation options - Expected results before/after fix - Complete testing procedure - Troubleshooting guide - Next action checklist Documents provide complete roadmap from problem identification to tested solution, with multiple approaches based on available tools (NXP SDK vs manual implementation). Analysis confidence: High (based on proven MCX/iMXRT reference code) Estimated fix time: 30-60 min (with SDK) or 2-4 hours (manual) All documents committed to branch for reference and implementation.
Implements complete USB PHY initialization to fix USB enumeration issue where Windows 10 shows nothing when RW612 is connected. Root cause: USB PHY was never powered on or configured, leaving D+/D- lines inactive. This is critical missing code that all other working NXP boards (MCX, iMXRT) include. Implementation based on hw/bsp/mcx/family.c (lines 168-184): - Power on USB PHY (USBPHY->PWD = 0) - CRITICAL missing step - Enable Low-speed/Full-speed device support (CTRL register) - Configure TX timing calibration (D_CAL, TXCAL45DP/DM) - Override trim values if needed (TRIM_OVERRIDE_EN) - Enable USB PHY clock if separate from controller Code changes in hw/bsp/rw612/family.c: - Replaced lines 86-90 (basic clock enable) - With lines 86-122 (complete USB PHY initialization) - Defensive code: works even if USBPHY not defined in headers - Uses #ifdef USBPHY to conditionally compile PHY init - Issues warning if USBPHY peripheral not found Expected results after this fix: ✅ Windows 10 should detect "USB Ethernet/RNDIS Gadget" ✅ NCM driver auto-installs (WINNCM) ✅ Network connectivity functional (ping 192.168.7.1) If USBPHY not defined in current headers:⚠️ Build will show warning but compile successfully ❌ USB will still not work (need NXP SDK device headers) → Solution documented in RW612_USB_FIX_APPLIED.md This fix follows the exact same pattern as: - MCX MCXN9: hw/bsp/mcx/family.c:168-184 (primary reference) - iMXRT: hw/bsp/imxrt/family.c:76-107 (secondary reference) Both boards use ChipIdea HS USB controller (same as RW612) and have proven, working USB PHY initialization code. Testing: - Code is syntactically correct and follows proven MCX pattern - Build test requires ARM toolchain (not available in current env) - Hardware test required to confirm USBPHY peripheral availability - Full testing instructions in RW612_USB_FIX_APPLIED.md References: - Analysis: RW612_USB_COMPLETE_ANALYSIS_SUMMARY.md - Implementation guide: RW612_USB_PHY_FIX_IMPLEMENTATION.md - Board comparison: RW612_USB_REFERENCE_COMPARISON.md - This fix documentation: RW612_USB_FIX_APPLIED.md Fixes: Missing USB PHY initialization causing no USB detection Implements: Option 1 (MCX-style direct USBPHY access) Status: Ready for hardware testing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the PR
A clear and concise description of what this PR solve.
Additional context
If applicable, add any other context about the PR and/or screenshots here.