Dark_iaji

sudo dmesg | grep "typec" [ 0.845532] typec_fusb302 4-0022: error -EINVAL: cannot register tcpm port [ 0.846545] typec_fusb302: probe of 4-0022 failed with error -22 Doesn't seem to be working, I was hoping to use the OTG mode of the USB-C port. I made some modifications to rk3399-nanopc-t4-type-c-modeling.patch. 32 lines + data-role = "otg"; 129 lines + dr_mode = "otg";

Is it feasible to make fusb302 work in OTG mode at this stage?

Basically this was caused by my tragic experience with nanopc-t3 where I deployed BitTorrent client with OS installed in emmc and after running for several weeks it seems that due to my negligence, the BitTorrent client A large number of cache writes on the side led to the exhaustion of emmc's rewritable times, and then nanopc-t3 was damaged due to my wrong operation of replacing emmc. Later, I no longer trust the reliability of emmc, especially with a large number of write operations under the scene. nvme ssd is much better than emmc in terms of performance and reliability, which is why I bought nanopc-t4 later. Sounds like uboot works perfectly fine on your device? Or are you not an nvme device?

https://github.com/sigmaris/u-boot First I tried the mainline uboot v2022.04 version and the sigmaris uboot, in the uboot command line I executed the nvme info command and found no nvme devices available. https://github.com/radxa/u-boot Since the radxa version does not have the relevant configuration files for nanopc-t4, the compilation and testing of the radxa version is abandoned. Is the patch in this thread for the mainline v2020.04 release? @piter75 @Hover