Hello everyone,
I have a Colibri T20 target supporting 2.3 BSP.
I used to update the target, set in recovery mode, by means of its USB slave port.
Now I am trying to update the target from 2.3 BSP to 2.8 BSP by means of an USB stick.
The problem is that U-boot provided in 2.3 BSP does not support the setupdate command.
U-Boot 2011.06-svn58-svn26 (Nov 23 2015 - 17:13:54)
TEGRA2
DRAM: 512 MiB
NAND: 1024 MiB
MMC: Tegra2 SD/MMC: 0
Board: Toradex Colibri T20
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
Colibri T20 # run setupdate
Error: “setupdate” not defined
Colibri T20 #
I cannot find setupdate support in the U-Boot sources.
Then, as suggested by Txx Recovery Mode | Toradex Developer Center
I set target RCM in order to transfer and execute 2.8 BSP U-Boot directly on target RAM
Colibri T20 # enterrcm
Entering RCM…
Then in the Linux Host (Fedora 27 KDE) I issued the 2.8 BSP update.sh script with the -d option:
[venturi@localhost Colibri-T20_LXDE-Image_2.8.1]$ ./update.sh -d -m 3 -r 512 -v V1_2
Colibri T20 rootfs specified
bct file: …/colibri-t20_bin/colibri_t20-512-v12-nand.bct
bootloader file: …/colibri-t20_bin/u-boot-dtb-tegra.bin
load addr 0x80108000
entry addr 0x80108000
device id: 0x7820
uid: 0x0428008744411317
RCM version: 2.1
downloading miniloader to target at address 0x40008000 (132976 bytes)…
miniloader downloaded successfully
Chip UID: 0x00000000000000000428008744411317
Chip ID: 0x20
Chip ID Major Version: 0x1
Chip ID Minor Version: 0x3
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-v12-nand.bct
- 4080/4080 bytes sent
…/colibri-t20_bin/colibri_t20-512-v12-nand.bct sent successfully
sending file: …/colibri-t20_bin/u-boot-dtb-tegra.bin
/ 725808/725808 bytes sent
…/colibri-t20_bin/u-boot-dtb-tegra.bin sent successfully
[venturi@localhost Colibri-T20_LXDE-Image_2.8.1]$
The problem is that the target simply remains frozen in recovery mode, and U-boot is not run at all.
How to solve such problem ?
Thank you for your attention.