20231223解决使用4线的公公线缆链接PC（WIN10）和Firefly的AIO-3399(RK3399)开发板出现ADB链接不上的问题

2023/12/23 20:47

开发板：Firefly的AIO-3399J【RK3399】

SDK：rk3399-android-11-r20211216.tar.xz【Android11】

Android11.0.tar.bz2.aa【ToyBrick】

Android11.0.tar.bz2.ab

Android11.0.tar.bz2.ac

https://wiki.t-firefly.com/AIO-3399J/prepare_compile_android.html

AIO-3399J产品规格书立即购买

AIO-3399J 采用 RK3399 六核(A72x2+A53x4) 64 位处理器，主频高达1.8GHz，集成了四核 Mali-T860 GPU，性能优异。

1、简略步骤：

rootroot@rootroot-X99-Turbo:~/3TB$ cat Android11.0.tar.bz2.a* > Android11.0.tar.bz2

rootroot@rootroot-X99-Turbo:~/3TB$ tar jxvf Android11.0.tar.bz2

rootroot@rootroot-X99-Turbo:~/3TB$ mv Android11.0 61Android11.0

rootroot@rootroot-X99-Turbo:~/3TB$ cd 61Android11.0

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ cd u-boot

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/u-boot$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/u-boot$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/u-boot$ ./make.sh rk3399

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/u-boot$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/u-boot$ cd ..

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ cd kernel/

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ make ARCH=arm64 rockchip_defconfig android-11.config -j36

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ make ARCH=arm64 BOOT_IMG=../rockdev/Image-rk3399_Android11/boot.img rk3399-sapphire-excavator-edp-avb.img -j36

scripts/kconfig/conf --syncconfig Kconfig

WRAP arch/arm64/include/generated/uapi/asm/errno.h

WRAP arch/arm64/include/generated/uapi/asm/ioctls.h

WRAP arch/arm64/include/generated/uapi/asm/ioctl.h

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0/kernel$ cd ..

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ source build/envsetup.sh

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ lunch

rk3399_Android11-userdebug

Which would you like? [aosp_arm-eng] 42

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ ll

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ make -j36

rootroot@rootroot-X99-Turbo:~/3TB/61Android11.0$ ./build.sh -u

2、修改步骤：

Z:\3TB\61Android11.0\kernel\arch\arm64\boot\dts\rockchip\rk3399-sapphire.dtsi

&i2c4 {

status = "okay";

i2c-scl-rising-time-ns = <475>;

i2c-scl-falling-time-ns = <26>;

fusb0: fusb30x@22 {

compatible = "fairchild,fusb302";

reg = <0x22>;

pinctrl-names = "default";

pinctrl-0 = <&fusb0_int>;

int-n-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
vbus-5v-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
status = "disabled";

};

Z:\3TB\61Android11.0\kernel\arch\arm64\boot\dts\rockchip\rk3399-sapphire.dtsi

&tcphy0 {

extcon = <&fusb0>;
status = "disabled";

};

&tcphy1 {

status = "okay";

};

&tsadc {

/* tshut mode 0:CRU 1:GPIO */

rockchip,hw-tshut-mode = <1>;

/* tshut polarity 0:LOW 1:HIGH */

rockchip,hw-tshut-polarity = <1>;

status = "okay";

};

&u2phy0 {

status = "okay";
//extcon = <&fusb0>;
otg-vbus-gpios = <&gpio3 RK_PC6 GPIO_ACTIVE_HIGH>; /* Vbus GPIO???? */

u2phy0_otg: otg-port {

status = "okay";

};

u2phy0_host: host-port {

phy-supply = <&vcc5v0_host>;

status = "okay";

};

Z:\3TB\61Android11.0\kernel\arch\arm64\boot\dts\rockchip\rk3399-sapphire.dtsi

&usb_host1_ohci {

status = "okay";

};

&usbdrd3_0 {

status = "okay";

};

&usbdrd_dwc3_0 {

status = "okay";

dr_mode = "otg";
//extcon = <&fusb0>;
extcon = <&u2phy0>;
maximum-speed = "high-speed"; /* maximum-speed ¨o?D??????ahigh-speed */
phys = <&u2phy0_otg>; /* phys ¨o?D???¨°y¨??USB2 PHY?¨2|ì? */
phy-names = "usb2-phy";

};

&usbdrd3_1 {

status = "okay";

};

&usbdrd_dwc3_1 {

status = "okay";

dr_mode = "host";

};

Z:\3TB\61Android11.0\kernel\arch\arm64\boot\dts\rockchip\rk3399-sapphire-excavator-edp.dtsi

&rt5651 {

status = "okay";

};

&cdn_dp {
status = "disabled";

extcon = <&fusb0>;

phys = <&tcphy0_dp>;

};

&hdmi_dp_sound {

status = "okay";

};

参考资料：

http://www.thanksview.com/index.php/thread/19.html\&wd=\&eqid=9dcbd0e40000160f00000003647964fe

RK3399使用正常手机数据线无法连接adb的问题，显示fusb302 4-0022:

2020-06-23 10:14:57

ThanksView
RK3399刷入android系统时，开机后会一直显示fusb302 4-0022:connection has disconnected，这是因为RK3399开发板type-c口默认使用的OTG控制器，OTG线与常用的type-c数据线并不相同，普通的type-c充电线CC管脚通过56K电阻上拉到vbus，而OTG数据线通常是通过5.1K电阻下拉到地，因此主板电路，在插入OTG线时，将CC管脚的电平通过MOS管和三极管到ID管脚检测为0V，而插入普通充电线时，ID管脚检测大于1.8V即可，因此，若想用普通充电线做USB-adb使用，可采取将type-c控制器转为普通usb2.0 OTG方式。修改dts：

使用某些【劣质/老版本的】TYPE-C的数据线链接PC（WIN10）和NanoPC-T4(RK3399)开发板，出现LOG：

[ 1416.454553] fusb302 4-0022: connection has disconnected

https://blog.csdn.net/wb4916/article/details/135162438

20231222解决使用TYPE-C的数据线链接PC（WIN10）和NanoPC-T4(RK3399)开发板出现fusb302 4-0022: connection has disconnected的

http://www.friendlyelec.com.cn/agent.asp

http://www.friendlyelec.com.cn/

https://download.friendlyelec.com/NanoPC-T4

https://wiki.friendlyelec.com/wiki/index.php/NanoPC-T4/zh#.E4.B8.8B.E8.BD.BDAndroid10.E6.BA.90.E4.BB.A3.E7.A0.81

https://item.taobao.com/item.htm?spm=a1z09.2.0.0.37562e8dcotDm6\&id=570312633249\&_u=7ju3ku004a

友善NanoPC-T4瑞芯微RK3399开发板ROS双摄4K播放开源AI智能安卓10

WiKi维基教程（固件介绍，使用说明，操作步骤等）

http://wiki.friendlyelec.com/wiki/index.php/NanoPC-T4