RKUSBDriver calls rk-usb-loader with invalid arguments

[rvdgracht]

The RKUSBDriver tries to load a usb-loader first by calling:
rk-usb-loader db /var/cache/labgrid/path/to/usbloader.bin
and later on
rk-usb-loader wl 0x40 /var/cache/labgrid/path/to/bootloader.img
which both fail because the rk-usb-loader af found in the latest testing release (2025-08-21) doesn't accept those arguments.

root@lxatac-00055:~# rk-usb-loader -h
Usage: rk-usb-loader [OPTIONS] <IMAGE>

Options:
  -d          Enable debugging output
  -h          This help

[Bastian-Krause]

There was some confusion about different tools there, see labgrid-project/labgrid#1542. I think meta-lxatac should probably ship rkdeveloptool.

[rvdgracht]

That would fix #289 as well (which is actually more of a Labgrid issue than meta-lxatac).

[hnez]

Hi @rvdgracht,

starting with commit f9497a8, which first made it into the 25.04 stable release we ship rkdeveloptool in our pre-built meta-lxatac images.

You should be able to use it by configuring the following in your labgrid environment on the client:

tools:
  rk-usb-loader: /usr/bin/rkdeveloptool

Since this piece of config goes into the labgrid environment there is not too much we can do on the LXA TAC in terms of pre-configuring it correctly, other than dirty hacks like symlinking /usr/bin/rkdeveloptool to /usr/bin/rk-usb-loader.

I hope the PR mentioned by @Bastian-Krause will gain some traction again, since fixing it in labgrid sounds like the best solution, especially because the fix needs to land on the client, not the LXA TAC.

[tretter]

other than dirty hacks like symlinking /usr/bin/rkdeveloptool to /usr/bin/rk-usb-loader

Please don't.

The rk-usb-loader is useful as a separate tool and has different arguments than the rkdeveloptool.

This should be fixed in labgrid.