Hello All,
Debian 13 Trixie
Intro:
Up front . This is very much a hack. Trying to interface with a 5G gateway device that uses the MediaTek T750 SoC The device runs on android
This is the device with some very good background.Arcadyan KVD21 5G Gateway
https://github.com/chainofexecution/Arcadyan-KVD21
Am interfacing with the undocumented , debugging , usb-c port . This has an usb-c port for power supply and a second usb-c port that is never mentioned in the Arcadyan documentation Goal, Would like to be able to do a full rom dump to hack around on to build an custom android image for the device.
Info:
When the device is plugged in with the second usb-c port the following shows up in character devices :My wild wild guess is somehow the Linux kernel is trying to mux/demux the four picie interfaces that this SoC provides.
But, nothing show up in either lsusb or lsusb -t
There are no /dev/ttyACM* devices either at this point
If I run a command of 'mtk prntgpt' from this mtkclient scripts https://github.com/bkerler/mtkclient
Now this shows up in lsusb & lsusb -t / the mobile phone and also the cdc driver is up
Also after doing the script if the gateway is left alone and the pc is rebooted the characters devices goes from :to this:Here i can connect to the /dev/ttyACM0 with picocom but cannot input anything
A similar modem to this FG360-N, the FM350-GL works fine in pcie interface modem on Debian Trixie. This SoC is just a slightly newer version and should be able to use the native mtk_t7xx driver but the gateway is just crippled. I think if i could figure out what the /dev/android# are and do some udev rules may be able to get the device to be recognized correctly .
TIA
Debian 13 Trixie
Intro:
Up front . This is very much a hack. Trying to interface with a 5G gateway device that uses the MediaTek T750 SoC The device runs on android
This is the device with some very good background.Arcadyan KVD21 5G Gateway
https://github.com/chainofexecution/Arcadyan-KVD21
Am interfacing with the undocumented , debugging , usb-c port . This has an usb-c port for power supply and a second usb-c port that is never mentioned in the Arcadyan documentation Goal, Would like to be able to do a full rom dump to hack around on to build an custom android image for the device.
Info:
When the device is plugged in with the second usb-c port the following shows up in character devices :
Code:
lrwxrwxrwx 1 root root 15 Dec 25 22:22 /dev/android1 -> bus/usb/003/005lrwxrwxrwx 1 root root 15 Dec 25 22:22 /dev/android11 -> bus/usb/003/004lrwxrwxrwx 1 root root 15 Dec 25 22:22 /dev/android14 -> bus/usb/003/006lrwxrwxrwx 1 root root 15 Dec 25 22:22 /dev/android4 -> bus/usb/003/002But, nothing show up in either lsusb or lsusb -t
There are no /dev/ttyACM* devices either at this point
If I run a command of 'mtk prntgpt' from this mtkclient scripts https://github.com/bkerler/mtkclient
Now this shows up in lsusb & lsusb -t / the mobile phone and also the cdc driver is up
Code:
$ lsusbBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 001 Device 002: ID 8087:800a Intel Corp. HubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hubBus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 003 Device 004: ID 413c:1004 Dell Computer Corp. Dell USB Keyboard HubBus 003 Device 005: ID 046d:c016 Logitech, Inc. Optical Wheel MouseBus 003 Device 006: ID 413c:2006 Dell Computer Corp. Dell USB Keyboard HubBus 003 Device 007: ID 0781:5530 SanDisk Corp. CruzerBus 003 Device 008: ID 8087:0032 Intel Corp. AX210 BluetoothBus 003 Device 014: ID 0e8d:0003 MediaTek Inc. MT6227 phoneBus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hublsusb --tree/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/6p, 480M/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/8p, 480M/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 003: Dev 014, If 0, Class=Communications, Driver=[none], 480M |__ Port 003: Dev 014, If 1, Class=CDC Data, Driver=[none], 480M |__ Port 004: Dev 008, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 004: Dev 008, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 008: Dev 004, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 001: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 001: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 011: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 014: Dev 007, If 0, Class=Mass Storage, Driver=usb-storage, 480M/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000MCode:
ls -l /dev/ttyACM*ls: cannot access '/dev/ttyACM*': No such file or directoryCode:
$ ls -l /dev/ttyACM*crw-rw----+ 1 root dialout 166, 0 Dec 25 09:35 /dev/ttyACM0A similar modem to this FG360-N, the FM350-GL works fine in pcie interface modem on Debian Trixie. This SoC is just a slightly newer version and should be able to use the native mtk_t7xx driver but the gateway is just crippled. I think if i could figure out what the /dev/android# are and do some udev rules may be able to get the device to be recognized correctly .
TIA
Statistics: Posted by brcisna — 2024-12-26 16:19 — Replies 1 — Views 53