I was wondering if anyone is successfully using tegra-uboot-flasher-scripts, or, more specifically the tegrarcm flasher with the TK1?
I’m trying to use it instead of nvflash to flash a Jetson-TK1 and although no errors are reported, it looks like the bootloader isn’t actually flashed. Instead the Jetson boots as usual (with the previous u-boot flashed with nvflash).
During the supposed flashing with tegrarcm, nothing is sent to the serial console of TK1 - as opposed to flashing it with nvflash, which reports being in recovery mode and flash progress.
Output from tegra-uboot-flasher:
sudo ./tegra-uboot-flasher flash jetson-tk1
+ cp /home/user/dev/tegra-uboot-flasher/_out/jetson-tk1/u-boot.dtb /tmp/tmpTHUA2e/u-boot-runflash.dtb
+ cd /tmp/tmpTHUA2e
+ fdtput -p -t x /tmp/tmpTHUA2e/u-boot-runflash.dtb /config bootdelay 0xfffffffe
bootcmd: echo >>> Verifying image in RAM... ; crc32 0x801be000 0x0007d200 0x80000000 ; if itest.l *0x80000000 != 0xf2eaf26a; then echo CRC MISMATCH of initial image; exit; fi ; echo >>> Selecting MMC device... ; mmc dev 0 1 ; echo >>> Writing image to MMC... ; mmc write 0x801be000 0 0x3e9 ; echo >>> Reading image back from MMC... ; mmc read 0x8023b200 0 0x3e9 ; echo >>> Verifying image from flash... ; crc32 0x8023b200 0x0007d200 0x80000000 ; if itest.l *0x80000000 != 0xf2eaf26a; then echo CRC MISMATCH of readback image; exit; fi ; echo >>> Setting up environment... ; env default -f -a ; saveenv ; echo >>> Flashing OK, rebooting... ; reset
+ cd /tmp/tmpTHUA2e
+ fdtput -p -t s /tmp/tmpTHUA2e/u-boot-runflash.dtb /config bootcmd echo >>> Verifying image in RAM... ; crc32 0x801be000 0x0007d200 0x80000000 ; if itest.l *0x80000000 != 0xf2eaf26a; then echo CRC MISMATCH of initial image; exit; fi ; echo >>> Selecting MMC device... ; mmc dev 0 1 ; echo >>> Writing image to MMC... ; mmc write 0x801be000 0 0x3e9 ; echo >>> Reading image back from MMC... ; mmc read 0x8023b200 0 0x3e9 ; echo >>> Verifying image from flash... ; crc32 0x8023b200 0x0007d200 0x80000000 ; if itest.l *0x80000000 != 0xf2eaf26a; then echo CRC MISMATCH of readback image; exit; fi ; echo >>> Setting up environment... ; env default -f -a ; saveenv ; echo >>> Flashing OK, rebooting... ; reset
+ cd /tmp/tmpTHUA2e
+ /tmp/tmpTHUA2e/flasher.sh
bct file: /home/user/dev/tegra-uboot-flasher/_out/jetson-tk1/PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.bct
booloader file: /tmp/tmpTHUA2e/u-boot-flasher.bin
load addr 0x80108000
entry addr 0x80108000
device id: 0x7140
uid: 0x34001001740de102240000000bff8040
RCM version: 64.1
downloading miniloader to target at address 0x4000e000 (136920 bytes)...
miniloader downloaded successfully
Chip UID: 0x00000001740de102240000000bff8040
Chip ID: 0x40
Chip ID Major Version: 0x1
Chip ID Minor Version: 0x1
Chip SKU: 0x81 (t124)
Boot ROM Version: 0x1
Boot Device: 0x2 (EMMC)
Operating Mode: 0x3 (developer mode)
Device Config Strap: 0x0
Device Config Fuse: 0x0
SDRAM Config Strap: 0x3
sending file: /home/user/dev/tegra-uboot-flasher/_out/jetson-tk1/PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.bct
- 8192/8192 bytes sent
/home/user/dev/tegra-uboot-flasher/_out/jetson-tk1/PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.bct sent successfully
sending file: /tmp/tmpTHUA2e/u-boot-flasher.bin
/ 1257984/1257984 bytes sent
/tmp/tmpTHUA2e/u-boot-flasher.bin sent successfully
Has anyone encountered this behaviour?