Questions related to U-boot of V2.8.1 BSP for Colibri T20 in recovery mode

Technical Support
, , ,
1

I have a Colibri T20 EVM V3.1A provided with SODIMM Col T20 512M V1.2A

I tried to update EVM from V2.3 to V2.8.1 BSP by means of USB stick

according to Flashing Embedded Linux to Tegra Modules

USB stick was FAT16 formatted on a Fedora 27 KDE, single partition and brand new partition table.

I decompressed Colibri-T20_LXDE-Image_2.8.1.tar.bz2

From #Colibri-T20_LXDE-Image_2.8.1 issued ./update.sh -o /run/media/venturi/0944-F91D safely.

Then I set EVM in recovery mode, inserted the USB stick and USB cable and issued safely:

./update.sh -d -r 512 -m 3 -v V1_2

Apparently EVM U-Boot refuses to deal with USB stick:

Colibri T20 # ver

U-Boot 2016.11-2.8.1+g30a1208727 (Mar 12 2018 - 14:11:45 +0100)

arm-angstrom-linux-gnueabi-gcc (GCC) 7.2.0

GNU ld (GNU Binutils) 2.29.0.20170912

Colibri T20 # run setupdate

MMC: no card present

MMC: no card present

** Bad device mmc 0 **

** Invalid partition 1 **

Waiting for Ethernet connection… unable to connect.

However if I issue:

Colibri T20 # usb reset

resetting 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:00:00:00

2 USB Device(s) found

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

GNU ld (GNU Binutils) 2.29.0.20170912
If I issue:

Colibri T20 # fatls usb 0:1

** Invalid partition 1 **

If I issue:

Colibri T20 # fatls usb 0:0

        colibri_t20/

  710   flash_blk.img 

  444   flash_eth.img 

  307   flash_mmc.img

3 file(s), 1 dir(s)

If I issue:

Colibri T20 # usb info

…

3: Mass Storage, USB Revision 2.0

  • CBM USB2.0 201351001DFE8702

  • Class: (from Interface) Mass Storage

  • PacketSize: 64 Configurations: 1

  • Vendor: 0x0204 Product 0x6025 Version 1.0

    Configuration: 1

    • Interfaces: 1 Bus Powered 100mA

      Interface: 0

      • Alternate Setting 0, Endpoints: 2

      • Class Mass Storage, Transp. SCSI, Bulk only

      • Endpoint 1 Out Bulk MaxPacket 512

      • Endpoint 1 In Bulk MaxPacket 512

Colibri T20 # usb tree

USB device tree:

1 Hub (480 Mb/s, 0mA)
u-boot EHCI Host Controller

1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
|±2 Vendor specific (480 Mb/s, 4mA)
ASIX Elec. Corp. AX88772B 000001

1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
|±2 Hub (480 Mb/s, 2mA)
|
|±3 Mass Storage (480 Mb/s, 100mA)
CBM USB2.0 201351001DFE8702

1)How could I solve such problem ?

N.B. differently from the guide:

2)I did not issue the nand.erase chip command: is this strictly necessary ?

Infact at present I would like to save and test the V2.3 U-boot with V2.81 kernel and Root File system.

3)I did not issue the cfgblock create command: is this strictly necessary ? What IT version mean ? Is y

actually the right answer ? (else where I found N).

4)Moreover, what is the meaning and solution for the ETH problem ?

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:00:00:00

Thanks in advance for your attention.

2

1)How could I solve such problem ?

N.B. differently from the guide:

I guess you missed the bold note under step 2 of the preparation section:

Note: U-Boot expects a partition table (MBR) on the SD card or USB flash drive and the FAT partition to be the first partition!

2)I did not issue the nand.erase chip command: is this strictly necessary ?

At least the UBI part of the raw NAND flash would need erasing before flashing or you will face the following issue.

Infact at present I would like to save and test the V2.3 U-boot with V2.81 kernel and Root File system.

Unfortunately the U-Boot from V2.3 won’t be able to cope with 2.8.1 kernel and root file system. So you won’t be able to mix and match. I am afraid you will either need to use all from V2.3 or update to all from 2.8.1.

Please also note that BSP V2.3 is still considered stable while 2.8.1 is just a first beta version.

3)I did not issue the cfgblock create command: is this strictly necessary ?

No, but without it you may not have a valid serial number and therefore Ethernet MAC address.

What IT version mean ? Is y

That means the industrial temperature SKUs Colibri T20 512MB IT V1.2A PN 00221200 and Colibri T20 256MB IT V1.2A PN 00241200.

actually the right answer ? (else where I found N).

4)Moreover, what is the meaning and solution for the ETH problem ?

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:00:00:00

That is just a warning informing you about the Ethernet MAC address in the SROM being different from the one in the U-Boot environment. If U-Boot finds a valid Toradex factory configuration block in flash it will automatically set the ethaddr environment variable unless the user did override that one with a custom Ethernet MAC address.

Thanks in advance for your attention.

You are very welcome.

3

First of all I greatly appreciate your accurate and prompt support.

This time I Gparted the USB stick and

Colibri T20 # fatls usb 0:0

** Unrecognized filesystem type **

Colibri T20 # fatls usb 0:1

        colibri_t20/

  710   flash_blk.img

  444   flash_eth.img

  307   flash_mmc.img

3 file(s), 1 dir(s)

and run setupdate works perfectly.

Other issues were covered exactly

About V2.8 U-boot I will try to insert the “old” V2.3 TFTP/NFS boot features which did not require a

DHCP server to access EVM and specify input files…

Best Regards.

4

You are very welcome.