Flashing Image via Colibri Loader: Error Message "Timeout waiting for EDBG_CMD_JUMPING ACK"

I am trying to revive a Col T30 1GB V1.1f module. During the previous flashing with the UpdateTool.exe something went wrong and the OS no longer boots:

Toradex Bootloader 2.0 for Tegra Built Mar  6 2017

Press [SPACE] to enter Bootloader Menu

Colibri T30 1GB V1.1F  SerialNo: 3009829
RAM: 1024 MB, CarveOut: 2 MB
Locating kernel image in flash...Done(603)
Decompressing IMAGE(25895437, 50612212) from FLASH(0) to RAM(80016000)...Done(141ms)
Error while decompressing, expected 50612212 bytes, but got 13702592 (IMAGE will probably not run)!
Jumping to image at 0x80016000...

The bootloader is still reachable and I am able to connect with Rs232 and USB. I set up the ip and usb configuration according to the description here. RNDIS seems to be working, the firewall is off, BOOT messages are sent.

Enter your selection: f
Colibri T30 1GB V1.1F  SerialNo: 3009829
RAM: 1024 MB, CarveOut: 2 MB

EbootUSBPreDownload: called!
Sent BOOTME to
Sent BOOTME to
Packet has the following data:
TFTP packet could have 2 name/value pairs
Locked Down Link 1
Src IP Port Dest IP Port Default TFTP block size set to: 512 bytes
This TFTP packet contains 1 options.
We currently only look at the first and expect it to be BLKSIZE.
The packet's option name is blksize.
The option's value is 1024
with a value that is in range.
BLKSIZE will be adjusted to 1024.
An OACK packet is the proper acknowledgement


+OEMMultiBinNotify(0x884FC0A8 -> 0)
Download file information:
-OEMIsFlashAddr(Rc = 1)

After a few minutes the colibri loader reports an error: “Timeout waiting for EDBG_CMD_JUMPING ACK” (The progress bar has shown “Finalizing Download (please wait)” during this.)
The image does still not boot.

Did I something obviously wrong here or missed a crucial step?

P.S.: I am trying to flash the 2.0 version of the Windows CE7 Image, but other versions failed as well.

alt text

Dear @Johannes

Actually we never meant to use the Colibri loader for flashing Tegra modules - it was written for the PXA modules. However, it would probably even work, but it requires a different input file format (*.bin instead of *.nb0).

In order to flash the module back to factory defauls, we recommend to use the Recovery Mode.

Please get back to me if you need more information.

Regards, Andy