Unable to flash Colibri_T20_LinuxImageV2.6 on my Colibri T20 based my Embedded Device

Hi all,

We are using a Colibri T20 board embedded into a custom Key’ Touch Device.
Currently, it is working under WinCE and we expect to migrate it under a linux system with Yocto.
First at all, we’re trying to flash the Toradex example linux images.

  1. I have downloaded the Colibri_T20_LinuxImageV2.3 image.
    I set the board into RecoveryMode and I simply executed:

./update.sh -r 512 -v V1_2

It took few minutes to upload everything. I set the board in nbormal mode. Reboot. Everything works, I got the Linux Angstrom loaded.

  1. I’ve then downloaded the Colibri_T20_LinuxImageV2.6 (beta) image.
    At first glance, I noted that the flashing tool were different. t20_nvflash for the image 2.3 and tegrarcm for the latter.
    I had to execute this command:

update.sh -r 512 -v V1_2 -d

I got the following output:

Colibri T20 rootfs detected

bct file: ../colibri-t20_bin/colibri_t20-512-v11-nand.bct
booloader file: ../colibri-t20_bin/u-boot-dtb-tegra.bin
load addr 0x80108000
entry addr 0x80108000
device id: 0x7820
uid:  0x0a7c814842e165d7
RCM version: 2.1
downloading miniloader to target at address 0x40008000 (132976 bytes)...
miniloader downloaded successfully
Chip UID:                0x00000000000000000a7c814842e165d7
Chip ID:                 0x20
Chip ID Major Version:   0x1
Chip ID Minor Version:   0x4
Chip SKU:                0x8 (t20)
Boot ROM Version:        0x1
Boot Device:             0x1 (NAND)
Operating Mode:          0x3 (developer mode)
Device Config Strap:     0x0
Device Config Fuse:      0x20
SDRAM Config Strap:      0x0
sending file: ../colibri-t20_bin/colibri_t20-512-v11-nand.bct
- 4080/4080 bytes sent
../colibri-t20_bin/colibri_t20-512-v11-nand.bct sent successfully
sending file: ../colibri-t20_bin/u-boot-dtb-tegra.bin
\ 636532/636532 bytes sent
../colibri-t20_bin/u-boot-dtb-tegra.bin sent successfully

It took 3 or 4 seconds max.
So, I assume that the roofts was not flashed at all.
I reboot the device, and it is still the Linux Image 2.3 that is loaded.

As far as I know, the update.sh script does not have the same behavior at all ?
Have I done something wrong ?

Any idea to flash the linux image correctly ?



Please proceed as per this flashing article on our developer website.

Hi Marcel,

Thanks for the link.
I’m a newbie in Toradex, and after hours, I finally understood the difference between Toradex linux image 2.3 and 2.6. The flashing procedure is indeed different.

I also followed the installation procedure of a TFTP in order to flash the system over the Ethernet netwrok.
Indeed, our Embedded Device SD card slot is not accessible for the end-user.
Thus, for our production env, flashing over the Ethernet is the most reliable solution.