DCD Table error - Windows

[mazegreg]

Hi,
When trying to load a .imx, I got the following error :

C:\workdir\imx_usb_loader\msvc\imx_usb\Debug>imx_usb.exe burner.imx config file <C:\workdir\imx_usb_loader\msvc\imx_usb\Debug\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
config file <C:\workdir\imx_usb_loader\msvc\imx_usb\Debug\mx6_usb_work.conf>
parse C:\workdir\imx_usb_loader\msvc\imx_usb\Debug\mx6_usb_work.conf
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename burner.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
loading DCD table @0x910000
out err=-2, last_trans=0 cnt=0x1e8 max=0x400 transferSize=0x0 retry=0
out err=-2, last_trans=0 cnt=0x1e8 max=0x200 transferSize=0x0 retry=1
out err=-2, last_trans=0 cnt=0x1e8 max=0x100 transferSize=0x0 retry=2
out err=-2, last_trans=0 cnt=0x1e8 max=0x80 transferSize=0x0 retry=3
out err=-2, last_trans=0 cnt=0x1e8 max=0x40 transferSize=0x0 retry=4
out err=-2, last_trans=0 cnt=0x1e8 max=0x20 transferSize=0x0 retry=5
out err=-2, last_trans=0 cnt=0x1e8 max=0x10 transferSize=0x0 retry=6
out err=-2, last_trans=0 cnt=0x1e8 max=0x8 transferSize=0x0 retry=7
out err=-2, last_trans=0 cnt=0x1e8 max=0x10 transferSize=0x0 retry=8
out err=-2, last_trans=0 cnt=0x1e8 max=0x8 transferSize=0x0 retry=9
out err=-2, last_trans=0 cnt=0x1e8 max=0x10 transferSize=0x0 retry=10
Giving up
!!perform_dcd returned -2
DoIRomDownload failed, err=-2
HAB security state: development mode (0x56787856)

It was compiled successfully but still no idea how to get rid of this...

Thank you very much for helping :)
Regards,
Grégoire

[nicolas-s]

We have the same issue.

Any news ?

[mazegreg]

Hi!
Still no news on my side.
Grégoire

[gibsson]

Hi,

We unfortunately do not have a Windows machine to try this on and therefore rely on the community for its support.

Lately the Windows improvements were brought by @falstaff84:
#48

Maybe he can help you.

Regards,
Gary

[agners]

Hm, might be related to libusb/libusb#222

Can you try a libusb version which comes with that fix?

(there were two issues, one should be addressed by a change in imx_usb 561f037).

[rolfisch]

edited: Sorry, I just saw my error message is different: "No dcd table"

filename u-boot.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
No dcd table, barker=402000d1

loading binary file(u-boot.imx) to 177ff400, skip=0, fsize=56c00 type=aa
out err=-7, last_trans=0 cnt=0x4000 max=0x400 transferSize=0x0 retry=0
out err=-7, last_trans=0 cnt=0x4000 max=0x200 transferSize=0x0 retry=1

Original Comment:
I have the same issue (using Ubuntu 17.10), but only with a certain u-boot.imx
OK with u-boot.imx generated with yocto
NOT OK with u-boot.imx generated with buildroot
So I thing the header is different... maybe wrong, maybe different than expected by imx_usb_loader

Regards, rolfisch

[agners]

@rolfisch this seems not related to this issue.

[ghost]

Just wanted to throw my 2 cents in and say that i had a successful run on windows with the libusb from this pre-release: https://github.com/libusb/libusb/releases/tag/v1.0.22-rc2

[sdygert-impinj]

Using libusb v1.0.22-rc3 I was able to solve this issue too. I didn't try earlier RC versions.

[gibsson]

Thank you all for tracking this down. @mazegreg , can you check if upgrading the libusb version fixes your issue. If so, please close the bug. Thanks!

[mazegreg]

Thank you so much all for your suggestions. I will give a try soon and give feedback!
Regards