Coral USB Accelerator

[Magnetiser]

I can't get my 5B to recognise the Coral USB Accelerator.

 

lsusb doesn't show anything but does when I attach a USB storage device.

 

I've installed libedgetpu1-std with a validated gpg key but nothing happens - the led on the device doesn't even turn on.

 

Do I need to install a special USB driver or something into the kernel ?

 

 

 

[clockfort]

I have OPi 5 plus, not the 5B, but I'm not running into the issue you're describing, the Coral shows up fine.

 

I can think of two possible issues, though:

- Did you already know that the Google Coral doesn't show up under a sensible USB device ID until you perform an inference for the first time ( https://github.com/google-coral/edgetpu/issues/536 ) ? It presents as USB device ID "1a6e:089a Global Unichip Corp." until you touch it, and then transforms into "18d1:9302 Google Inc."

- The Google Coral takes a ton of power over USB, especially if you're using libedgetpu1-max instead of libedgetpu1-std. Maybe your 5V supply isn't beefy enough?

 

$ dmesg | tail -n 3
[ 7830.308924] usb 6-1.4: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[ 7830.326474] usb 6-1.4: New USB device found, idVendor=1a6e, idProduct=089a, bcdDevice= 1.00
[ 7830.326485] usb 6-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0

$ lsusb -s 006:003
Bus 006 Device 003: ID 1a6e:089a Global Unichip Corp.

$ sudo lsusb -vs 006:003
Bus 006 Device 003: ID 1a6e:089a Global Unichip Corp.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.10
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         9
  idVendor           0x1a6e Global Unichip Corp.
  idProduct          0x089a
  bcdDevice            1.00
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001b
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              896mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      1 Device Firmware Update
      bInterfaceProtocol      2
      iInterface              0
      Device Firmware Upgrade Interface Descriptor:
        bLength                             9
        bDescriptorType                    33
        bmAttributes                        7
          Will Not Detach
          Manifestation Tolerant
          Upload Supported
          Download Supported
        wDetachTimeout                   1000 milliseconds
        wTransferSize                     256 bytes
        bcdDFUVersion                   1.01
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000006
      BESL Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000c
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   2
      Lowest fully-functional device speed is High Speed (480Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
Device Status:     0x0000
  (Bus Powered)

 

I'm on this version of armbian if it matters

 

$ cat /etc/armbian-image-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepi5-plus
BOARD_NAME="Orange Pi 5 Plus"
BOARDFAMILY=rockchip-rk3588
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=bfc8271
VERSION=23.08.0-trunk
LINUXFAMILY=rk35xx
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=wip
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
FORCE_BOOTSCRIPT_UPDATE=
VENDOR=Armbian
REVISION=23.08.0-trunk
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
IMAGE_UUID=698fa7a2-04c2-4922-ba21-4832ce7d3c13

 

Edited August 18, 2023 by clockfort

[Magnetiser]

Thanks @clockfort

 

It's really good to know you can see the USB on Armbian.

 

I was aware that you have to run inference before seeing the proper device in lsusb but I can't even see Global Unichip Corp.

 

I hit bootloader issues when I flashed Armbian and my Orange Pi was dropping into initramfs. I since fixed the partitions and flashed Ubuntu XFCE (from the official Orange PI website) onto my orange Pi. And have been stuck ever since - I've even got frigate running in docker with mqtt and am back to the same old problem about tpu delegates.

 

After your reply, I'm going to flash the Armbian image onto a SD card and boot from that to see if I can see the USB.

 

Can I ask, did you install the edge tpu runtime (libedgetpu...) before being able to see the Coral USB device?

 

[TRS-80]

On 8/26/2023 at 11:59 AM, Magnetiser said:

I since fixed the partitions and flashed Ubuntu XFCE (from the official Orange PI website)

 

I think this might be the problem.  Although I am certainly no expert in desktop stuff, I think it involves some low level things, which may differ between their version and ours.  I am also assuming that's some legacy kernel (although I didn't bother to look).

 

On 8/26/2023 at 11:59 AM, Magnetiser said:

I'm going to flash the Armbian image onto a SD card and boot from that to see if I can see the USB

 

This sounds like a better way forward.  Let us know how it goes.