i.MX USB SDP broken on imx6q-sabresd

[Fabio Estevam]

Hi,

I am trying to load SPL and u-boot-dtb.img via USB using the
imx_usb_loader tool.

Running the latest mainline U-Boot on a imx6q-sabresd I get:

$ sudo ./imx_usb SPL

On the console:

U-Boot SPL 2021.01-rc2-00005-g832bfad7451e (Nov 11 2020 - 23:00:05 -0300)
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...

Then I try to load u-boot-dtb.img and the following is seen on the host PC:

$ sudo ./imx_usb  u-boot-dtb.img
config file </usr/etc/imx-loader.d//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
config file </usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf>
parse /usr/etc/imx-loader.d//mx6_usb_sdp_spl.conf
Trying to open device vid=0x0525 pid=0xb4a4
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot-dtb.img
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item
header not found 8400:2e77d044, 4000
do_download failed, err=-22
HAB security state: development mode (0x56787856)

And nothing else appears in the console.

I tried to bisect, but the latest version I got this to run was
v2019.01, which was not using the driver model and prevents bisection.

Does anyone have any suggestions?

Thanks,

Fabio Estevam