T20 image update methods

I have a T20 EVM V3.2A supporting Colibri T20 512 MB V1.2A

I believe it is not clear from Toradex documentation which are the supported methods for Colibri T20 Linux image update, and if some special constraints (apart U-Boot expects a partition table (MBR) on the SD card or USB flash drive and the FAT partition to be the first partition!).

In fact even from the latest:

https://developer.toradex.com/knowledge-base/flashing-linux-on-tegra-modules

it seems that the only “official” update method for T20 EVM V3.2A is by means of SD card.
I never tested this method.

At its beginnings, the document hints at using an USB disk as well.

But I find difficulties with such method:

With a first USB disk:

Colibri T20 # run setupdate

MMC: no card present

MMC: no card present

** Bad device mmc 0 **

starting USB...

USB0:   USB EHCI 1.00

USB1:   USB EHCI 1.00

USB2:   USB EHCI 1.00

scanning bus 0 for devices... 1 USB Device(s) found

scanning bus 1 for devices...

Warning: asix_eth MAC addresses don't match:

Address in SROM is         00:0e:c6:87:72:01

Address in environment is  00:14:2d:4a:43:cf

2 USB Device(s) found

scanning bus 2 for devices... EHCI timed out on TD - token=0x80008c80

unable to get device descriptor (error=-1)

2 USB Device(s) found

** Bad device usb 0 **

Waiting for Ethernet connection... unable to connect.

Colibri T20 #

With a second USB disk:

Colibri T20 # run setupdate

MMC: no card present

MMC: no card present

** Bad device mmc 0 **

starting USB...

USB0:   USB EHCI 1.00

USB1:   USB EHCI 1.00

USB2:   USB EHCI 1.00

scanning bus 0 for devices... 1 USB Device(s) found

scanning bus 1 for devices...

Warning: asix_eth MAC addresses don't match:

Address in SROM is         00:0e:c6:87:72:01

Address in environment is  00:14:2d:4a:43:cf

2 USB Device(s) found

scanning bus 2 for devices... 3 USB Device(s) found

reading flash_blk.img

Error: FAT sector size mismatch (fs=2048, dev=512)

** Unable to read file flash_blk.img **

Waiting for Ethernet connection... unable to connect.

At last, with my wonder I see that the TFTP method is not mentioned in the documents:
only ./update help hints to a TFTP server directory.

However, this method works fine!

I hope this helps.

I have a T20 EVM V3.2A supporting Colibri T20 512 MB V1.2A

And what exact software versions of things?

I believe it is not clear from Toradex documentation which are the supported methods for Colibri T20 Linux image update, and if some special constraints (apart U-Boot expects a partition table (MBR) on the SD card or USB flash drive and the FAT partition to be the first partition!).

In fact even from the latest:

https://developer.toradex.com/knowledge-base/flashing-linux-on-tegra-modules

it seems that the only “official” update method for T20 EVM V3.2A is by means of SD card.

I unsure as to why you would come to any such conclusion.

I never tested this method.

At its beginnings, the document hints at using an USB disk as well.

Yes, both is supported.

But I find difficulties with such method:

With a first USB disk:

With a second USB disk:

Looks like U-Boot has trouble detecting your USB memory sticks. Unfortunately, U-Boot’s USB stack is not quite as resilient to certain types of USB memory sticks as full-blown Embedded Linux. However, given a somewhat sane USB memory stick it really should be working fine.

At last, with my wonder I see that the TFTP method is not mentioned in the documents:
only ./update help hints to a TFTP server directory.

That would actually be mentioned here.

However, this method works fine!

Yes, we hope so!

I hope this helps.

Yes, thanks for your feedback. We are aware that the documentation at times is not quite that clear. However, in general, we do still support all those legacy update methods on older products while transitioning any of our later products exclusively to the new Toradex Easy Installer.