[Meta] Radxa Rock Pi 4C Plus and TeslaUSB #776

KrzysztofHajdamowicz · 2023-09-17T18:14:16Z

Describe the problem

I have an idea to compile issues mentioned in multiple issues example into single thread, allowing for faster searching.

Device

Rock Pi 4C plus

OS Image

Armbian

Car Model

Model Y

USB connection

Glove box

Logs

No response

Additional information

No response

KrzysztofHajdamowicz · 2023-09-17T18:15:03Z

So far, my progress is:

Get image https://github.com/radxa-build/rock-4c-plus/releases/download/20230312-1521/Armbian_23.05.0-trunk_Rockpi-4cplus_jammy_current_5.15.101_minimal.img.xz
Flash microSD card using that image
Plug ethernet cable to Rock Pi 4C+
Boot it
SSH into, using root/1234 credentials
Run through initial configuration
use nano to create file thermals.dts

/dts-v1/;
/plugin/;

/ {
        compatible = "radxa,rockpi4c-plus", "radxa,rockpi4", "rockchip,rk3399";

        fragment@0 {
                target=<&tsadc>;
                __overlay__ {
                        status = "okay";
                        /* tshut mode 0:CRU 1:GPIO */
                        rockchip,hw-tshut-mode = <1>;
                        /* tshut polarity 0:LOW 1:HIGH */
                        rockchip,hw-tshut-polarity = <1>;
                };
        };

};

run armbian-add-overlay thermals.dts
reboot
Run TeslaUSB installer: curl https://raw.githubusercontent.com/marcone/teslausb/main-dev/setup/generic/install.sh | bash
Use /boot/teslausb_setup_variables.conf from TeslaUSB that was running in glovebox on Raspberry Pi 4B (so, 1:1 configuration migration)
Plug USB drive that was used by Raspberry Pi 4B from step 10.
12a. Iterate for a few times, fixing each error one by one:
12b. mkdir /mnt/{cam,music,boombox}
12c.

systemctl disable --now systemd-resolved
systemctl mask systemd-resolved
systemctl enable --now dnsmasq

12d. mv /mutable/varlib/misc{,.old}
12e. copy /etc/wpa_supplicant/wpa_supplicant.conf from Raspberry Pi 4B to Rock Pi 4C Plus
12f. Installer finally passes
13. Reboot
14. /backingfiles and /mutable are mounted
15. unfortunately, USB OTG in upper USB3 port is not working.
https://www.youtube.com/watch?v=ngMiCgQzwkI
dmesg:

[   46.419618] overlayfs: "xino" feature enabled using 2 upper inode bits.
[   46.803441] loop0: detected capacity change from 0 to 419428352
[   46.870567] exFAT-fs (loop0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   47.067020] ------------[ cut here ]------------
[   47.067040] WARNING: CPU: 1 PID: 1528 at drivers/usb/dwc3/gadget.c:3649 dwc3_stop_active_transfer.part.0.constprop.0+0xb4/0xcc
[   47.067064] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs usb_f_mass_storage libcomposite exfat lz4hc lz4 zram binfmt_misc xfs sg btsdio snd_soc_hdmi_codec bluetooth snd_soc_simple_card snd_soc_rk817 snd_soc_simple_card_utils snd_soc_core brcmfmac snd_pcm_dmaengine hantro_vpu(C) rockchip_vdec(C) snd_pcm brcmutil rockchip_iep rockchip_rga v4l2_h264 snd_timer videobuf2_dma_contig dw_hdmi_i2s_audio dw_hdmi_cec v4l2_mem2mem videobuf2_dma_sg snd videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 soundcore rfkill videobuf2_common videodev mc cpufreq_dt sch_fq_codel ramoops reed_solomon pstore_blk pstore_zone ip_tables x_tables autofs4 uas realtek dwmac_rk stmmac_platform stmmac pcs_xpcs
[   47.067247] CPU: 1 PID: 1528 Comm: disable_gadget. Tainted: G         C        5.15.101-rockchip64 #1
[   47.067256] Hardware name: Radxa ROCK Pi 4C+ (DT)
[   47.067261] pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   47.067269] pc : dwc3_stop_active_transfer.part.0.constprop.0+0xb4/0xcc
[   47.067277] lr : dwc3_stop_active_transfer.part.0.constprop.0+0x78/0xcc
[   47.067285] sp : ffff80000d1abb20
[   47.067289] x29: ffff80000d1abb20 x28: ffff00000511ac40 x27: 0000000000000000
[   47.067300] x26: 0000000000000000 x25: 0000000000000000 x24: ffff000005237900
[   47.067312] x23: ffff0000052229b0 x22: 0000000000000000 x21: ffff000005222a78
[   47.067323] x20: 0000000000000000 x19: ffff0000053ad900 x18: ffffffffffffffff
[   47.067334] x17: 0000000000000000 x16: 0000000000000000 x15: 3d454d414e5f4344
[   47.067345] x14: ffff800009dcc4e0 x13: 0000000000000040 x12: 0000000000000000
[   47.067356] x11: ffffffffffff3f08 x10: ffff8000edff5000 x9 : ffffffffffff3f04
[   47.067368] x8 : 00004161a8e29e9d x7 : ffffffffffff3f00 x6 : ffffffffffff3f0c
[   47.067379] x5 : ffff800009aa9000 x4 : ffffffffffff3f0c x3 : 0000000000000000
[   47.067389] x2 : 0000000000000c08 x1 : ffff80000b90c900 x0 : 00000000ffffff92
[   47.067401] Call trace:
[   47.067405]  dwc3_stop_active_transfer.part.0.constprop.0+0xb4/0xcc
[   47.067413]  dwc3_remove_requests.constprop.0+0x2c/0xf0
[   47.067421]  __dwc3_gadget_ep_disable+0x5c/0x1a0
[   47.067428]  dwc3_gadget_pullup+0xc8/0x240
[   47.067435]  usb_gadget_disconnect+0x38/0x10c
[   47.067444]  usb_gadget_remove_driver+0x30/0xec
[   47.067451]  usb_gadget_unregister_driver+0x70/0xe4
[   47.067458]  gadget_dev_desc_UDC_store+0xb8/0x13c [libcomposite]
[   47.067490]  configfs_write_iter+0xc4/0x124
[   47.067501]  new_sync_write+0xe8/0x184
[   47.067510]  vfs_write+0x238/0x29c
[   47.067516]  ksys_write+0x68/0xf4
[   47.067523]  __arm64_sys_write+0x1c/0x2c
[   47.067529]  invoke_syscall+0x48/0x114
[   47.067539]  el0_svc_common.constprop.0+0x44/0xfc
[   47.067547]  do_el0_svc+0x28/0xa0
[   47.067554]  el0_svc+0x28/0x80
[   47.067564]  el0t_64_sync_handler+0xa4/0x130
[   47.067571]  el0t_64_sync+0x1a0/0x1a4
[   47.067579] ---[ end trace dfca4f5855ded11e ]---
[   47.186435] loop1: detected capacity change from 0 to 419430400
[   47.186735]  loop1: p1
[   47.263967] loop2: detected capacity change from 0 to 209715200
[   47.264289]  loop2: p1
[   47.481811] loop1: detected capacity change from 0 to 419428352
[   48.530664] Mass Storage Function, version: 2009/09/11
[   48.530689] LUN: removable file: (no medium)
[   48.542549] LUN: removable file: (no medium)
[   48.554082] LUN: removable file: (no medium)
[  107.841583] loop1: detected capacity change from 0 to 419428352
[  107.858035] exFAT-fs (loop1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 3588.566311] loop0: detected capacity change from 0 to 419430400
[ 3588.567791]  loop0: p1
[ 3588.771289] loop0: detected capacity change from 0 to 419428352

Wireless access point is not created

Diagnostics:
diagnostics.txt

marcone · 2023-09-17T18:56:35Z

I haven't had time to try your steps yet, but I would suggest using a recent Armbian build with a newer kernel, e.g. Armbian_23.8.1_Rockpi-4cplus_jammy_current_6.1.50.img.xz from https://redirect.armbian.com/rockpi-4cplus/archive/

KrzysztofHajdamowicz · 2023-09-17T19:08:41Z

I have tried it first. It does not see USB SSD (Samsung T7) and USB-NVME adapter with Samsung 980 Pro connected to USB 3.0 ports, only 2.0 ports see connected drive.

What's better, when I use image from first comment and do apt upgrade, newer system can't see those drives. Looks, like 23.8.1 is buggy somehow.

miles267 · 2023-09-17T19:13:07Z

I’ve just used apt-get update and apt-get upgrade as well as unfreezing kernel updates. That way it’ll ensure the kernel stays current regardless of the installed image. Also there is now a new beta coding UI you can install that’s a convenient option.

KrzysztofHajdamowicz · 2023-09-17T19:26:26Z

Also there is now a new beta coding UI you can install that’s a convenient option.

What do You mean? I'm new in Armbian world so discovering something new is fun :)

miles267 · 2023-09-17T19:29:35Z

Sorry. Please try this:

sudo apt update && sudo apt install armbian-config. You should then be able to run armbian-config to u freeze kernel installs and configure WLAN, etc. it’s the same as running nmtui.

KrzysztofHajdamowicz · 2023-09-17T22:14:59Z

Armbian_23.8.1_Rockpi-4cplus_jammy_current_6.1.50.img.xz from https://redirect.armbian.com/rockpi-4cplus/archive/

Flash image to microSD card
Boot
Do initial config
apt update && apt install armbian-config
use armbian-config to enable dwc3-0-host hardware overlay. SSD is now visible on lower USB3 port.
Also enable overlay rockpi4cplus-usb-host. After reboot, there is an error in dmesg

[    3.224357] dwc3 fe800000.usb: error -ETIMEDOUT: failed to initialize core
[    3.224499] dwc3: probe of fe800000.usb failed with error -110

Install TeslaUSB: curl https://raw.githubusercontent.com/marcone/teslausb/main-dev/setup/generic/install.sh | bash
Use /boot/teslausb_setup_variables.conf from TeslaUSB that was running in glovebox on Raspberry Pi 4B (so, 1:1 configuration migration)
Mon Sep 18 12:11:09 AM CEST 2023 : STOP: this device (Radxa ROCK Pi 4C+) does not have a UDC driver appeared in /boot/teslausb-headless-setup.log

Looks like #769 is present in current Armbian images.

EDIT

Created dwc3-peripherial.dts

/dts-v1/;
/plugin/;

/ {
    compatible = "rockchip,rk3399";
    fragment@0 {
      target = <&usbdrd_dwc3_0>;
      __overlay__ {
        dr_mode = "peripheral";
      };
    };
};

armbian-add-overlay dwc3-peripherial.dts
11. Lost USB SSD visibility.
12. dmesg.txt

marcone · 2023-09-17T23:07:01Z

6. Also enable overlay rockpi4cplus-usb-host. After reboot, there is an error in dmesg

The rockpi4cplus-usb-host overlay switches the top USB3 port to host mode (as described in /boot/dtb/rockchip/overlay/README.rockchip-overlays), thereby disabling the required OTG mode, which then leads to the error you see when trying to install TeslaUSB:

9. Mon Sep 18 12:11:09 AM CEST 2023 : STOP: this device (Radxa ROCK Pi 4C+) does not have a UDC driver appeared in /boot/teslausb-headless-setup.log

KrzysztofHajdamowicz · 2023-09-18T08:04:18Z

Also enable overlay rockpi4cplus-usb-host. After reboot, there is an error in dmesg

The rockpi4cplus-usb-host overlay switches the top USB3 port to host mode (as described in /boot/dtb/rockchip/overlay/README.rockchip-overlays), thereby disabling the required OTG mode, which then leads to the error you see when trying to install TeslaUSB:

Mon Sep 18 12:11:09 AM CEST 2023 : STOP: this device (Radxa ROCK Pi 4C+) does not have a UDC driver appeared in /boot/teslausb-headless-setup.log

overlay and SSD visibility:
no-overlay.txt
dwc3-0-host rockpi4cplus-usb-host.txt
dwc3-0-host.txt

dwc3-0-host overlay is the only overlay that gives SSD visibility in any of USB3 port (lower port, being specific).
Even with dwc3-0-host overlay, there is no UDC driver.

KrzysztofHajdamowicz · 2023-09-20T21:14:41Z

https://imola.armbian.com/dl/rockpi-4cplus/archive/Armbian_23.8.1_Rockpi-4cplus_bookworm_current_6.1.50_minimal.img.xz

spiced with:

apt install vim nano htop ncdu mc curl wget
wget https://github.com/radxa/overlays/raw/main/arch/arm64/boot/dts/rockchip/overlays/rk3399-dwc3-0-peripheral.dts -O rk3399-dwc3-0-peripheral.dts
armbian-add-overlay rk3399-dwc3-0-peripheral.dts
reboot
after reboot:

# dmesg | grep -i dwc
[    2.730303] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
[    2.730408] dwc3: probe of fe900000.usb failed with error -110

No SSD visibility in lower USB3 port, had to use USB2 port to make drive visible.
For testing purporses, teslausb installed using microSD card as backing storage to simplify device.

Unfortunately, whole rig is not visible in PC.
diagnostics.txt

KrzysztofHajdamowicz · 2023-09-22T19:05:38Z

OK, I have managed to get something working:

Use image Armbian_23.8.1_Rockpi-4cplus_jammy_current_6.1.50.img.xz
apt update && apt upgrade
Run TeslaUSB installer: curl https://raw.githubusercontent.com/marcone/teslausb/main-dev/setup/generic/install.sh | bash
In teslausb_setup_variables.conf comment out SSID, WIFIPASS, AP_SSID, AP_PASS, AP_IP,
teslausb_setup_variables.conf.txt
Perform configuration: /etc/rc.local

TeslaUSB works on Rock Pi.
Caveats:

After booting Rock Pi, devices appear and after few seconds disappear and re-appear after a second or two.
Lower USB3.0 port is not working, thus no USB3.0 for backing storage.

mjpcomp · 2024-03-08T08:25:02Z

For anyone coming through here and noticing there's a Wiki now on how to install and get the 4C+ working:

Under the https://github.com/marcone/teslausb/wiki/Rock-Pi-4C--Installation#software-requirements Software Requirements section, the link to the image no longer works as that listed version has been archived. You can find that particular version here: https://imola.armbian.com/dl/rockpi-4cplus/archive/

marcone · 2024-03-08T16:20:51Z

@mjpcomp the linked image was already archived, the problem is that that particular archive was deleted, as I'm sure the one you linked to will be deleted at some point too. This is because Armbian is switching to community images for the Rock Pi 4C+ due to lack of an official maintainer. The problem is that the community image does not have working OTG.

mjpcomp · 2024-03-13T19:29:25Z

@mjpcomp the linked image was already archived, the problem is that that particular archive was deleted, as I'm sure the one you linked to will be deleted at some point too. This is because Armbian is switching to community images for the Rock Pi 4C+ due to lack of an official maintainer. The problem is that the community image does not have working OTG.

Ah, thanks for the heads up - that's definitely good to know... I'm going to make sure I keep an extra copy of this image around.. Wonder if it may need to be hosted on archive.org or something just in case it does go the way of the Dodo...

Crosenhain · 2024-03-13T22:25:41Z

I found that the USB-OTG was unreliable, so I took a stab in the dark and removed the usbstoragequirks line from /boot/armbianEnv.txt and ran update_initramfs -u, rebooted, and it seems to be much more reliable from my initial testing. I don't use an external USB drive for storage, so ymmv.

I still see the drives appear for a little bit, then go away, and then come back again. I suspect this might be due to the sync script running on startup but I haven't confirmed this yet.

stauffenberg2020 · 2024-04-24T13:06:02Z

After booting Rock Pi, devices appear and after few seconds disappear and re-appear after a second or two.

@KrzysztofHajdamowicz, @marcone, Can you please let me know if a workaround has been been found for this. Does Tesla complain about it in the alerts section for this?

ZhongDev · 2024-04-25T06:06:14Z

For anyone coming through here and noticing there's a Wiki now on how to install and get the 4C+ working:

Under the https://github.com/marcone/teslausb/wiki/Rock-Pi-4C--Installation#software-requirements Software Requirements section, the link to the image no longer works as that listed version has been archived. You can find that particular version here: https://imola.armbian.com/dl/rockpi-4cplus/archive/

The archive link path got changed.
The current link to the archive is now https://imola.armbian.com/archive/rockpi-4cplus/archive/
I wanted to leave it here in case someone else is looking for the version specified in the wiki.

stauffenberg2020 · 2024-04-25T06:53:45Z

I still see the drives appear for a little bit, then go away, and then come back again.

@Crosenhain , Does Tesla complain about this and show an alert/active alert?

miles267 · 2024-04-26T14:58:01Z

@ZhongDev how has this behaved for you? I've been successfully and reliably running 2x RPi 4's.

Though I've attempted to test the RPi 4C, I found that it both did not reliably remain connected to multiple cars I tested with, but also the wifi connectivity was abysmal; even with an antenna attached. Since I wasn't sure whether there was truly anything to be gained by using the 4C, I've reverted to the RPi 4.

ZhongDev · 2024-04-28T03:11:14Z

@miles267 So far it seems to be mostly smooth for the past 3 days. (20 Drives, Sentry on, Disabled at home). There was one drive where the 4c+ failed to mount at the start of the drive, But I just replugged the USB in the glovebox and it has worked. I may try disabling "usbstoragequirks" like @Crosenhain so that hopefully it is more stable, and fewer failed mounts happen.

ZhongDev · 2024-04-28T03:12:34Z

Also, Wifi signal has been okay, however I'm not sure if that is due to the 4c+ or my overbuilt Unifi wifi network.

gerculanum · 2024-04-28T03:18:45Z

Older Rock 4C+ Armbian builds, including the one in the installation instructions, have a boot stability issue. This issue renders the board unusable in cars as it often fails to boot and register as USB storage. This has been fixed by armbian/build#6414. Newer Armbian builds should perform better. However, they require this overlay to enable peripheral mode on the OTG port, which can be added using the armbian-add-overlay command.

TeslaUSB on a Rock 4C+ works well in my car, with no WiFi issues.

ZhongDev · 2024-04-28T05:24:14Z

@gerculanum Thank you for that! I will try again soon using a new community build. I used an archived build because teslausb refused to install properly a community build. I think probably because i did not use the overlay.

Crosenhain · 2024-05-08T21:43:16Z

I still see the drives appear for a little bit, then go away, and then come back again.

@Crosenhain , Does Tesla complain about this and show an alert/active alert?

I need to check this again, my car recently updated to 2024.14.3, which apparently did contain some fixes for USB drive problems according to a local Tesla service rep.

Crosenhain · 2024-05-11T22:00:46Z

I do not have an alert - I think I did in the previous software version.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Meta] Radxa Rock Pi 4C Plus and TeslaUSB #776

[Meta] Radxa Rock Pi 4C Plus and TeslaUSB #776

KrzysztofHajdamowicz commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023

marcone commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023 •

edited

miles267 commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023

miles267 commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023 •

edited

marcone commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 18, 2023

KrzysztofHajdamowicz commented Sep 20, 2023

KrzysztofHajdamowicz commented Sep 22, 2023

mjpcomp commented Mar 8, 2024

marcone commented Mar 8, 2024

mjpcomp commented Mar 13, 2024

Crosenhain commented Mar 13, 2024

stauffenberg2020 commented Apr 24, 2024 •

edited

ZhongDev commented Apr 25, 2024 •

edited

stauffenberg2020 commented Apr 25, 2024

miles267 commented Apr 26, 2024

ZhongDev commented Apr 28, 2024

ZhongDev commented Apr 28, 2024

gerculanum commented Apr 28, 2024

ZhongDev commented Apr 28, 2024

Crosenhain commented May 8, 2024

Crosenhain commented May 11, 2024

[Meta] Radxa Rock Pi 4C Plus and TeslaUSB #776

[Meta] Radxa Rock Pi 4C Plus and TeslaUSB #776

Comments

KrzysztofHajdamowicz commented Sep 17, 2023

Describe the problem

Device

OS Image

Car Model

USB connection

Logs

Additional information

KrzysztofHajdamowicz commented Sep 17, 2023

marcone commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023 • edited

miles267 commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023

miles267 commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 17, 2023 • edited

marcone commented Sep 17, 2023

KrzysztofHajdamowicz commented Sep 18, 2023

KrzysztofHajdamowicz commented Sep 20, 2023

KrzysztofHajdamowicz commented Sep 22, 2023

mjpcomp commented Mar 8, 2024

marcone commented Mar 8, 2024

mjpcomp commented Mar 13, 2024

Crosenhain commented Mar 13, 2024

stauffenberg2020 commented Apr 24, 2024 • edited

ZhongDev commented Apr 25, 2024 • edited

stauffenberg2020 commented Apr 25, 2024

miles267 commented Apr 26, 2024

ZhongDev commented Apr 28, 2024

ZhongDev commented Apr 28, 2024

gerculanum commented Apr 28, 2024

ZhongDev commented Apr 28, 2024

Crosenhain commented May 8, 2024

Crosenhain commented May 11, 2024

KrzysztofHajdamowicz commented Sep 17, 2023 •

edited

KrzysztofHajdamowicz commented Sep 17, 2023 •

edited

stauffenberg2020 commented Apr 24, 2024 •

edited

ZhongDev commented Apr 25, 2024 •

edited