RKUSBDriver doesn't support the rockchip SOCs accepted by RKUSBLoader

[rvdgracht]

RKUSBDriver uses rk-usb-loader which doen't support all Rockchip SOCs.

I.e. I have a RK3562 connected.
Note: It is detected by Labgrid. The RKUSBLoader resource class does pick it up.

root@lxatac-00055:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 005: ID 2207:350d Fuzhou Rockchip Electronics Company 

root@lxatac-00055:~# labgrid-client -p mytac show
...
Acquired resource 'RKUSBLoader' (lxatac-00055/lxatac-usb-ports-p3/NetworkRKUSBLoader/RKUSBLoader):
  {'acquired': 'mytac',
   'avail': True,
   'cls': 'NetworkRKUSBLoader',
   'params': {'busnum': 1,
              'devnum': 5,
              'extra': {'proxy': 'lxatac-00055', 'proxy_required': False},
              'host': 'root@lxatac-00055',
              'model_id': 13581,
              'path': '1-1.3',
              'vendor_id': 8711}}
...

root@lxatac-00055:~# rk-usb-loader barebox.img
[+] scanning for USB device matching 2207/ffff:350a/fffe...

But the rk-usb-loader can't work with/detect it.
We've been using the xrock tool successfully for a while now to flash Rockchip boards.
Would be great if Labgrit could work with xrock as well.

[hnez]

Hi @rvdgracht,

But the rk-usb-loader can't work with/detect it.

starting with commit f9497a8, which first made it into the 25.04 stable release we also ship rkdeveloptool in our pre-built meta-lxatac images. Could you check if that works with the SoCs you use?

---

We've been using the xrock tool successfully for a while now to flash Rockchip boards. Would be great if Labgrit could work with xrock as well.

If rkdeveloptool does not work for your usecase I would be open to adding xrock to meta-lxatac. Adding new tools does however always come with additional maintenance burden in the future, so if rkdeveloptool is sufficient, I would prefer to just use that instead.

Regarding xrock support in labgrid feel free to leave an issue on their GitHub page or even open a PR. Changes there always make it into meta-lxatac sooner or later.