Flashing Linux on a Colibri T20

Technical Support
, , ,
1

Hi I’m trying to flash Linux on a old Calibri board, which is currently running a WindowsCE.
I’ve downloaded Colibri-T20_LXDE-Image_2.8.7 from your website and have troubles to send the image to the device:

 Colibri T20 V1.2A
 Carrier Board Colibiri Evaluation V3.2B

If I reboot the board I get the info I’m running

  Toradex Bootloader 1.4 BETA for Tegra Build Feb 17 2015

So I did following on my linux host (Open SuSE):

Colibri-T20_LXDE-Image_2.8.7 # mount /dev/sdb1 /mnt
Colibri-T20_LXDE-Image_2.8.7 # mount | grep /mnt
/dev/sdb1 on /mnt type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

Colibri-T20_LXDE-Image_2.8.7 # ./update.sh  -o /mnt
Colibri T20 rootfs detected
Image file colibri_t20-256-v11-nand.img has been successfully generated!
Image file colibri_t20-256-v12-nand.img has been successfully generated!
Image file colibri_t20-512-v11-nand.img has been successfully generated!
Image file colibri_t20-512-v12-nand.img has been successfully generated!
mkfs.ubifs
        root:         rootfs/
        min_io_size:  4096
        leb_size:     253952
        max_leb_cnt:  4084
        output:       colibri-t20_bin/ubifs_248KiB.img
        jrn_size:     8388608
        reserved:     0
        compr:        lzo
        keyhash:      r5
        fanout:       8
        orph_lebs:    1
        space_fixup:  1
        super lebs:   1
        master lebs:  2
        log_lebs:     4
        lpt_lebs:     2
        orph_lebs:    1
        main_lebs:    738
        gc lebs:      1
        index lebs:   13
        leb_cnt:      748
        UUID:         7FE7A7A8-C44F-4D71-BC6F-5C1EFB4BE16C
Success!
mkfs.ubifs
        root:         rootfs/
        min_io_size:  4096
        leb_size:     516096
        max_leb_cnt:  4084
        output:       colibri-t20_bin/ubifs_504KiB.img
        jrn_size:     8388608
        reserved:     0
            compr:        lzo
        keyhash:      r5
        fanout:       8
        orph_lebs:    1
        space_fixup:  1
        super lebs:   1
        master lebs:  2
        log_lebs:     4
        lpt_lebs:     2
        orph_lebs:    1
        main_lebs:    363
        gc lebs:      1
        index lebs:   7
        leb_cnt:      373
        UUID:         07464C83-405B-40E0-BF10-46A01E076D6D
Success!

UBI image of root file system generated, copying data to target folder...
Successfully copied data to target folder.

To flash the Apalis/Colibri T20/T30/TK1 module a running U-Boot is required. Boot
the module to the U-Boot prompt and

insert the SD card, USB flash drive or when using TFTP connect Ethernet only
and enter:
'run setupdate'

then to update all components enter:
'run update'

Alternatively, to update U-Boot enter:
'run update_uboot'
to update a component stored in UBI enter:
'run prepare_ubi' (for Colibri T20)
followed by one of:
'run update_kernel'
'run update_fdt' (for device tree enabled kernels)
'run update_rootfs'


If you don't have a working U-Boot anymore, connect your PC to the module's USB
client port, bring the module into the recovery mode and start the update.sh
script with the -d option. This will copy U-Boot into the module's RAM and
execute it.

Now I plug the sdcard into the carrier board, and boot the device into recovery mode. I can see the USB device now on the host linux:

Colibri-T20_LXDE-Image_2.8.7 # lsusb | grep NV
Bus 003 Device 033: ID 0955:7820 NVIDIA Corp. T20 [Tegra 2] recovery mode

Now I try to send the u-boot command to the board:

Colibri-T20_LXDE-Image_2.8.7 # ./update.sh -d -r256  -vV1_2 
Colibri T20 rootfs detected

bct file: ../colibri-t20_bin/colibri_t20-256-v12-nand.bct
bootloader file: ../colibri-t20_bin/u-boot-dtb-tegra.bin
load addr 0x80108000
entry addr 0x80108000
./tegrarcm: could not open USB device: No such device

That’s it. The USB device disappeard on linux host and nothing happens anymore. If I reboot the board, WindowsCE starts again. What I’m doing wrong?

Thanks for your help!
colibri linux colibri-t20 t20 boot install

2

Actually I wanted to post this topic in public discussion, but I couldn’t send the post without a tag. As you can see: it has tags. So you can turn this into a public post.

1 Like
3

Hello @moberza,

Just to confirm, are you using the 256 MB version of the Colibri T20?

It is possible that your current user lacks the required permissions to communicate to the device.
Can you try again with sudo?

I have tested it with a Debian 12 host and the bootloader was loaded correctly without the need for sudo.
In this system, the user is member of the dialout and plugdev groups.

Best Regards,
Bruno

7

Yes it’s the 256 MB version. Anyway since it turned out the the device has not enough RAM for our application, we discarded this topic and working now with an Colibri IMX6 board (where torizon installer is working).

thx for testing it.

8

Hello @moberza,

Thanks for the update.

Best Regards,
Bruno