Shulou(Shulou.com)06/01 Report--

How to change RK3399 Type-C to MicroUSB? for this question, this article introduces the corresponding analysis and answer in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

CPU:RK3399

System: Android 7.1.2

In order to reduce the cost, the motherboard changes Type-C to MicroUSB interface, which saves the fusb302 chip.

Refer to the official documentation of Rockchip part 4: Micro USB2.0 OTG DTS configuration

RKDocs/common/usb/Rockchip-Developer-Guide-Linux4.4-RK3399-USB-DTS-CN.pdf

& tcphy0 {

Status = "disabled"

}

& u2phy0 {

Status = "okay"; / * Micro USB2 PHY deleted the extcon attribute * /

Otg-vbus-gpios =; / * Vbus GPIO configuration * /

U2phy0_otg: otg-port {/ * document was mistakenly written as u2phy1_otg * /

Status = "okay"

}

.

}

& usbdrd3_0 {

Extcon =; / * the extcon attribute of the Micro USB3 controller refers to u2phy0 * /

Status = "okay"

}

& usbdrd_dwc3_0 {

Dr_mode = "otg"; / * dr_mode of the Micro USB3 controller is configured as otg * /

Maximum-speed = "high-speed"; / * the maximum-speed attribute is configured as high-speed * /

Phys =; / * the phys attribute references only the USB2 PHY node * /

Phy-names = "usb2-phy"

Status = "okay"

}

According to the instructions in the document, you can modify this part, but after burning the compiled kernel, you cannot enter Android. The serial port has been printed in a loop as follows:

[9.878630] init: Starting service 'surfaceflinger'...

[10.294620] init: Service 'surfaceflinger' (pid 532) killed by signal 6

[10.294664] init: Service 'surfaceflinger' (pid 532) killing any children in process group

[10.294709] init: Service 'zygote' is being killed...

[10.356365] init: Service 'zygote' (pid 254) killed by signal 9

[10.356441] init: Service 'zygote' (pid 254) killing any children in process 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' is being killed...

[10.357239] init: Service 'cameraserver' is being killed...

[10.357327] init: Service 'media' is being killed...

[10.357454] init: Service 'netd' is being killed...

[10.358943] init: Starting service 'zygote'...

[10.364342] init: Service 'audioserver' (pid 299) killed by signal 9

[10.364427] init: Service 'audioserver' (pid 299) killing any children in process group

[10.365879] init: Starting service 'audioserver'...

[10.369573] init: Service 'netd' (pid 310) killed by signal 9

[10.369677] init: Service 'netd' (pid 310) killing any children in process group

[10.370582] init: Untracked pid 575 killed by signal 9

[10.374127] init: Service 'media' (pid 297) killed by signal 9

[10.374192] init: Service 'media' (pid 297) killing any children in process group

[10.375119] init: Service 'cameraserver' (pid 300) killed by signal 9

[10.375158] init: Service 'cameraserver' (pid 300) killing any children in process 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'...

At first, it was suspected that it was due to the lack of full compilation, but after all the compilation and burning, it still could not be turned on, and the drm device could not be found all the time, and the serial port kept printing as follows:

_ _ bionic_open_tzdata: couldn't find any tzdata when looking for GMT!

Starting recovery (pid 185) on Fri Jan 18 08:52:30 2013

Bootmode = emmc

Recovery filesystem table

=

0 / mnt/internal_sd vfat / dev/block/platform/fe330000.sdhci/by-name/user 0

1 / mnt/external_sd vfat / dev/block/mmcblk0p1 0

2 / system ext4 / dev/block/platform/fe330000.sdhci/by-name/system 0

3 / cache ext4 / dev/block/platform/fe330000.sdhci/by-name/cache 0

4 / metadata ext4 / dev/block/platform/fe330000.sdhci/by-name/metadata 0

5 / data ext4 / dev/block/platform/fe330000.sdhci/by-name/userdata 0

6 / cust ext4 / dev/block/platform/fe330000.sdhci/by-name/cust 0

7 / custom ext4 / dev/block/platform/fe330000.sdhci/by-name/custom 0

8 / misc emmc / dev/block/platform/fe330000.sdhci/by-name/misc 0

9 / uboot emmc / dev/block/platform/fe330000.sdhci/by-name/uboot 0

10 / charge emmc / dev/block/platform/fe330000.sdhci/by-name/charge 0

11 / resource emmc / dev/block/platform/fe330000.sdhci/by-name/resource 0

12 / parameter emmc / dev/block/platform/fe330000.sdhci/by-name/parameter 0

13 / boot emmc / dev/block/platform/fe330000.sdhci/by-name/boot 0

14 / recovery emmc / dev/block/platform/fe330000.sdhci/by-name/recovery 0

15 / backup emmc / dev/block/platform/fe330000.sdhci/by-name/backup 0

16 / trust emmc / dev/block/platform/fe330000.sdhci/by-name/trust 0

17 / baseparameter emmc / dev/block/platform/fe330000.sdhci/by-name/baseparameter 0

18 / frp emmc / dev/block/platform/fe330000.sdhci/by-name/frp 0

19 / tmp ramdisk ramdisk 0

Emmc_point is / dev/block/mmcblk1

Sd_point is (null)

Sd_point_2 is (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 arguments from boot message

[4.311229] fs_mgr: Warning: unknown flag resize

= start void dumpCmdArgs (int, char * *): 296 =

Argv [0] = recovery.

Argv [1] =-- wipe_all.

Locale is [en_US]

Stage is []

Reason is [(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' (pid 185) killed by signal 11

[4.352952] init: Service 'recovery' (pid 185) killing any children in process group

[9.358734] init: Starting service 'recovery'...

Check the dts file and there is another place & cdn_dp uses fusb0. You can turn it on by blocking it.

& cdn_dp {

Status = "disabled"

Extcon =

Phys =

}

Finally, it is recommended to disable the part of i2C that communicates with fusb302. There is no problem here, but i2C is not connected, but it can be turned on normally.

Fusb0: fusb30x@22 {

Compatible = "fairchild,fusb302"

Reg =

Pinctrl-names = "default"

Pinctrl-0 =

Int-n-gpios =

Vbus-5v-gpios =

Status = "disabled"

}

This is the answer to the question about how to change RK3399 Type-C to MicroUSB. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.