I have a U3ISPM20000KPA camera which is having USB cable for connection. But its a USB3 device and in axon for usb3 devices, its giving c type port. can you help me to connect them together?
You need some USB Type-C Male To USB-A Female Adapter.
I have connected it using this cable. But when i check i’m getting vicharak@vicharak:~$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M
/: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
it’s taking the camera as usb2 instead of usb 3
Even I do have one USB Hub that claims that one port is supported USB 3.0 But, in reality it does not.
Kindly, Check another device like USB 3.0 Pen drive first with axon using that Cable and Kindly verify cable while connecting with Any other system with USB 3.0 Pendrive so you can get an idea.
we have tried with usb3 pendrive, usb3 powerhub to connect to axon. and even changed the connetcor cables. But still axon is dtecting the pendrive, camera as usb2 only isntead of usb3. checked with 3 axon boards. Can you schedule a video call and check our connections and axon’s detection issue for usb3 devices
Which Axon image are you using !?
Give us output of /etc/os-release
Could you flash Latest image V2.0.1 !?
https://docs.vicharak.in/vicharak_sbcs/axon/axon-linux/linux-usage-guide/windows-rkdevtool/#flash-raw-image-in-emmc-to-axon-board
And, Could you confirm that when you connect USB 3.0 pendrive directly to Type C USB 3.0 port in Axon, it works !?
when I tried as per the raw image flashing guide video, I’m getting this error. Failed to switch storage and download boot fail.
sudo dmesg > usb.log
journalctl --no-pager > whole_system_log.txt
please try going to maskrom mode again maybe it will fix the issue, i faced similar issue earlier.
Yes, majority of time entering into maskrom can be the issue.