[问答]

如何将Type-C改为普通USB？

3745 RK3399

问答对人有帮助，内容完整，我也想知道答案 0 如何将Type-C改为普通USB？ 0
2022-3-7 07:18:01　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × liutiefu 该类别下有 26 个回答。邀请回答 tigerwang711 该类别下有 20 个回答。邀请回答 ze55me 该类别下有 20 个回答。邀请回答杀狼000 该类别下有 19 个回答。邀请回答 zhuzb0754 该类别下有 19 个回答。邀请回答冰箱洗衣机该类别下有 18 个回答。邀请回答 YYXIAO 该类别下有 18 个回答。邀请回答 jjll652 该类别下有 17 个回答。邀请回答河神大人该类别下有 17 个回答。邀请回答 mede1001 该类别下有 17 个回答。邀请回答安德森大该类别下有 17 个回答。邀请回答 CDCNKA 该类别下有 17 个回答。邀请回答世态薄凉该类别下有 16 个回答。邀请回答熊本熊该类别下有 16 个回答。邀请回答 YOYOOO 该类别下有 16 个回答。邀请回答麻酱该类别下有 16 个回答。邀请回答 vinww特烦恼该类别下有 15 个回答。邀请回答 723662364d 该类别下有 15 个回答。邀请回答 musicalboy 该类别下有 15 个回答。邀请回答万航渡路该类别下有 15 个回答。邀请回答举报刘英相关推荐 • 如何将Type-C修改为普通USB？ 8385 • USB Type-C设计细节 4838 • 什么是USB Type-C看完你就懂了 4250 • USB Type-C和Power Delivery的设计规格是什么 4313 • 基于USB Type-C方案的USB设计升级 4036 • USB Type-C插座的解决方案 5275 • 苹果推出USB Type-C接口macbook引爆USB Type-C，那到底哪些厂商有USB Type C芯片？ 24334 • Type-C接口它到底有哪些优势呢？ 2610 • 有关USB Type-C的知识点都总结在这里了 2428 • 如何安全地布设USB Type-C插座连接器？ 2241 1个回答

答案对人有帮助，有参考价值 0 CPU：RK3399 系统：Android 7.1.2 为了降低成本，主板将Type-C改为MicroUSB接口，节省了fu*302芯片参考Rockchip的官方文档第4部分：Micro USB2.0 OTG DTS配置 RKDocs/common/u/Rockchip-Developer-Guide-Linux4.4-RK3399-USB-DTS-CN.pdf &tcphy0 { ; }; &u2phy0 { ;/ Micro USB2 PHY删除了extcon属性/ otg-vbus-gpios = ;/ Vbus GPIO配置/ u2phy0_otg: otg-port {/文档中错误写成了u2phy1_otg / ; }; ...... }; &u*drd3_0 { extcon = ;/ Micro USB3控制器的extcon属性引用u2phy0 / ; }; &u*drd_dwc3_0 { ;/ Micro USB3控制器的dr_mode配置为otg / ;/ maximum-speed属性配置为high-speed / phys = ;/ phys属性只引用USB2 PHY节点/ ; ; }; 按照文档中说明，修改这部分就可以了，但是编译内核部分烧录后，不能进安卓系统，串口一直循环打印如下： [9.878630] init: Starting service'surfaceflinger'... [10.294620] init: Service'surfaceflinger'(pid532) killed by signal6 [10.294664] init: Service'surfaceflinger'(pid532) killing any childreninprocess group [10.294709] init: Service'zygote' ieing killed... [10.356365] init: Service'zygote'(pid254) killed by signal9 [10.356441] init: Service'zygote'(pid254) killing any childreninprocess group [10.356634] init: write_file: Unable to open'/sys/android_power/request_state': No such file or directory [10.356778] init: write_file: Unable to write to'/sys/power/state': Invalid argument [10.356805] init: Service'audioserver' ieing killed... [10.357239] init: Service'cameraserver' ieing killed... [10.357327] init: Service'media' ieing killed... [10.357454] init: Service'netd' ieing killed... [10.358943] init: Starting service'zygote'... [10.364342] init: Service'audioserver'(pid299) killed by signal9 [10.364427] init: Service'audioserver'(pid299) killing any childreninprocess group [10.365879] init: Starting service'audioserver'... [10.369573] init: Service'netd'(pid310) killed by signal9 [10.369677] init: Service'netd'(pid310) killing any childreninprocess group [10.370582] init: Untracked pid575killed by signal9 [10.374127] init: Service'media'(pid297) killed by signal9 [10.374192] init: Service'media'(pid297) killing any childreninprocess group [10.375119] init: Service'cameraserver'(pid300) killed by signal9 [10.375158] init: Service'cameraserver'(pid300) killing any childreninprocess group [10.376450] init: Starting service'media'... [10.378976] init: Starting service'cameraserver'... [10.382610] init: couldn't write 580 to /dev/cpuset/camera-daemon/tasks: No such file or directory [12.079202] init: Starting service'netd'... 开始怀疑是因为没有全部编译的问题，但是全部编译烧录后，还是不能开机，一直提示找不到drm device，串口一直循环打印如下： __bionic_open_tzdata: couldn't find any tzdata when looking for GMT! Starting recovery (pid185) on Fri Jan18 08:52:30 2013 bootmode = emmc recovery filesystem table ========================= 0/mnt/internal_sd vfat /dev/block/platform/fe330000.sdhci/by-name/user0 1/mnt/external_sd vfat /dev/block/mmcblk0p10 2/system ext4 /dev/block/platform/fe330000.sdhci/by-name/system0 3/cache ext4 /dev/block/platform/fe330000.sdhci/by-name/cache0 4/metadata ext4 /dev/block/platform/fe330000.sdhci/by-name/metadata0 5/data ext4 /dev/block/platform/fe330000.sdhci/by-name/userdata0 6/cust ext4 /dev/block/platform/fe330000.sdhci/by-name/cust0 7/custom ext4 /dev/block/platform/fe330000.sdhci/by-name/custom0 8/misc emmc /dev/block/platform/fe330000.sdhci/by-name/misc0 9/uboot emmc /dev/block/platform/fe330000.sdhci/by-name/uboot0 10/charge emmc /dev/block/platform/fe330000.sdhci/by-name/charge0 11/resource emmc /dev/block/platform/fe330000.sdhci/by-name/resource0 12/parameter emmc /dev/block/platform/fe330000.sdhci/by-name/parameter0 13/boot emmc /dev/block/platform/fe330000.sdhci/by-name/boot0 14/recovery emmc /dev/block/platform/fe330000.sdhci/by-name/recovery0 15/backup emmc /dev/block/platform/fe330000.sdhci/by-name/backup0 16/trust emmc /dev/block/platform/fe330000.sdhci/by-name/trust0 17/baseparameter emmc /dev/block/platform/fe330000.sdhci/by-name/baseparameter0 18/frp emmc /dev/block/platform/fe330000.sdhci/by-name/frp0 19/tmp ramdisk ramdisk0 emmc_pointis/dev/block/mmcblk1 sd_pointis(null) sd_point_2is(null) I:InternalSD_ROOT: /mnt/internal_sd I:ExternalSD_ROOT: /mnt/external_sd read cmdline [4.309235] fs_mgr: Warning: unknown flag resize I:Boot command: boot-recovery I:Got argumentsfromboot message [4.311229] fs_mgr: Warning: unknown flag resize === startvoiddumpCmdArgs(int,char):296=== argv[0] = recovery. argv[1] = --wipe_all. localeis[en_US] stageis[] reasonis[(null)] cannot find/open a drm device: No such file or directory cannot open fb0: No such file or directory [4.352842] init: Service'recovery'(pid185) killed by signal11 [4.352952] init: Service'recovery'(pid185) killing any childreninprocess group [9.358734] init: Starting service'recovery'... 查看dts文件，里面还有一个地方&cdn_dp使用了fu*0，屏蔽此处即可开机 &cdn_dp { ; extcon = ; phys = ; }; 最后建议把i2c中与fu302通讯的部分也disable掉，此处不改也没有问题，只是i2c不通，但可以正常开机。 fu0: fu*30x@22{ ; reg = <0x22>; ; pinctrl-0= ; int-n-gpios = ; vbus-5v-gpios = ; ; }; b1e03227fa9720da4fde362389b7768.png (3.38 MB, 下载次数: 0) 2021-2-17 10:57 上传

2022-3-7 13:44:56 评论举报彭小海