RK3588的usb调试记录小结

usb3.0的接口无法识别部分3.0U盘:

这是前阵子出现的情况,当时usb3.0接口是可以识别鼠标键盘的2.0设备的,这就说明usb的2.0功能是没问题的,但是对于usb3.0的设备就出现了部分设备可以识别,一些不可以识别的情况。当然如果说usb2.0没问题的话,那么2.0U盘应该也是可以识别的吧,事实证明确实如此。

不管是直接使用2.0的U盘还是将3.0的U盘只插入到3/4的位置都是可以识别的,只是U盘会被识别成2.0设备,这就说明usb2.0接口应该是没问题的;
而且部分无法识别的U盘插入电脑或者其他设备中也可以识别,排除了U盘自身3.0接口坏掉的问题。

接着就是排查usb3.0的问题了,一开始以为是内核配置或者是一些版本不兼容问题导致,查了很多资料,文末会贴一些出来,有可能会有些帮助。后面发现不管怎么试好像都不能识别,后面发现是硬件问题,电路上有两个电容没加上,我人直接开麻 - _ -

usb问题排查资料

RK一般会有一些自带文档可以协助问题排查,usb相关的在platform/docs/common/USB/的目录里

在这里插入图片描述

Linux USB3.0 接移动硬盘频繁卡死问题解决方法 https://www.imiku.com/archives/376.html
usb的硬件技术浅析 https://www.cnblogs.com/Linux-tech/p/13352562.html
韦东山的usb开发指南 https://zhuanlan.zhihu.com/p/609754745
Linux kernel U盘识别流程 https://blog.csdn.net/encourage2011/article/details/76407232

### RK3588 USB Configuration and Issues For the RK3588 platform, configuring and troubleshooting USB involves several key aspects including driver setup, device recognition, and potential common issues encountered during usage. #### Driver Setup The Buildroot environment provided with the RK3568 SDK includes necessary libraries but requires specific configurations to support various peripherals like USB devices. For USB functionality on RK3588, ensuring that the correct drivers are included in the kernel is crucial[^1]. This typically means enabling options related to USB host controllers such as DWC2 or XHCI within the Linux kernel configuration menu (`make menuconfig`). #### Device Recognition Once appropriate drivers have been configured into the system image built by Buildroot, connecting a USB device should result in it being recognized automatically upon insertion. The dmesg command can be used to check logs for any messages indicating successful detection of new hardware: ```bash dmesg | grep usb ``` If no errors appear here when plugging in your USB gadget, chances are good that basic connectivity has succeeded. #### Common Problems and Solutions However, some typical problems may arise while working with USB ports on this chipset: - **Insufficient Power Supply**: Some high-power external drives might require more power than what an onboard port provides. - **Incompatible Kernel Modules**: Missing modules could prevent certain types of USB equipment from functioning properly even though they physically connect fine. To address these concerns, one approach would involve verifying whether all required firmware files exist under `/lib/firmware/`. Additionally, loading missing module(s) via `modprobe` commands at runtime or adding them permanently through editing `/etc/modules`. Another issue noted specifically around building environments similar to those mentioned earlier pertains to dependency resolution failures due to missing headers during compilation processes involving graphical interfaces over SSH connections[^3]. --related questions-- 1. How does one verify if the proper USB drivers are loaded after booting up? 2. What steps must be taken to ensure sufficient power delivery to connected USB peripherals? 3. Can you provide guidance on resolving dependency issues arising from absent header files during cross-compilation tasks? 4. Is there documentation available detailing how to add custom USB functionalities using Buildroot for RK3588 boards? 5. Are there known limitations regarding speed or performance when utilizing multiple USB devices simultaneously on RK3588 systems? : Mentioned about needing additional setups beyond just having pre-integrated libaries. : Highlighted challenges faced during development which indirectly points towards possible complications in setting up USB-related features requiring specific include paths.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值