Unable to boot in Jetson TK1 after flashing with version R21.5

Dear Sir

I have problems with Jetson Tk1.

When I first booting, they need upgrade and i do sudo apt-get upgrade, after rebooting it show nothing but i can still press ctrl+alt+F1 to login and enter the jetson. after that i tried to flash the firmware to R21.5 from R19.2 with UBuntu 14.04 LTS, the the result is blank, and network, usb didn’t work

The flash process like this

mkdir reflash
cd reflash
wget https://developer.nvidia.com/embedded/dlc/l4t-Jetson-TK1-Driver-Package-R21-5

wget https://developer.nvidia.com/embedded/dlc/l4t-Jetson-TK1-Sample-Root-Filesystem-R21-5

#Then I extract the Driver Package tarball:
sudo tar xpf l4t-Jetson-TK1-Driver-Package-R21-5
#Then I extract the File System tarball into a specific sub-directory:
cd Linux_for_Tegra/rootfs
sudo tar xpf …/…/l4t-Jetson-TK1-Sample-Root-Filesystem-R21-5
#Then I apply binaries
cd …/
sudo ./apply_binaries.sh

#Then I plug in the USB cable and put the TK1 into recovery mode.
#Verify the board is connected with:
lsusb

#Finally, I’ve tried each of the following
sudo ./flash.sh jetson-tk1 mmcblk0p1 with the result success

after all of that i restart the board (press reset button) and the screen, usb, and lan didn’t work

if i push the recovery button and type lsusb in host computer,it still detect the NVIDIA (NVIDIA Corp)

The Question
how to solve it, so i can have the newest firmware in jetson-tk1 and the system can work normally ?

Thx

Note that the driver system should not be unpacked sudo (it can be if you always use root for everything you do with the driver package, but generally speaking it isn’t necessary…anything to do with rootfs needs root as well as flash.sh which deals with loopback).

Your flash procedure was correct, but you can flash with full eMMC use via (flashing again with full eMMC use would be a good test anyway):

sudo ./flash.sh <b>-S 14580MiB</b> jetson-tk1 mmcblk0p1

(if the hard drive fills up there will be odd login errors, although failing video would not be one of them)

If you just did “apt update” and “apt-get upgrade” there shouldn’t be an issue on any of the R21.x releases. If you used apt to upgrade from the original L4T R19.2/Ubuntu 14.04 to Ubuntu 16.04 this would guarantee failure (Ubuntu’s method of migrating the major version to a newer version completely erases all of the hardware access files). Long ago there were also some issues with some of NVIDIA’s GUI-related files being overwritten if the mesa package updated, but I believe this was fixed quite some time back…updating on the original R19.2 or R19.3 might still cause this to occur.

It sounds like recovery mode still works when intended, but let me verify that recovery mode does go away (no lsusb response for it on host) when you reboot the Jetson and don’t use the recovery button? This would be correct behavior, I ask because if recovery mode remains after reboot without trying to be in recovery mode, then you have a hardware failure.

Flash installs firmware too. Do you have serial console? If so, then you can check if the update overwrote the libGL.so file (this would cause GUI failure, though not other failures). You’d run “sha1sum -c /etc/nv_tegra_release” to see if the hardware-specific files are in place. That 9-pin D-sub connector uses 115200 8N1 settings to work as a console.

Dear Sir

I already tried “sudo ./flash.sh -S 14580MiB jetson-tk1 mmcblk0p1” but the result is the same (Nothing happened and still blank).

I tried to “lsusb” without going into recovery mode (just reboot without pressing the recovery button) and the result is, it didn’t detect the Nvidia (Nvidia Corp)

I don’t have serial console

What should i do to restore the the jetson tk1 back normally ?

thx

The R21.5 is actually “normal”. The original R19.2 is not available, R19.3 is the lowest version available. If this is an issue under R21.5, then it is unlikely R19.3 would be any different.

When you say the LAN does not work, are you able to see your router logs and verify if a DHCP request went out?

FYI, a serial console cable would be very very helpful right now. All kinds of things can go wrong and you’d still have serial console working.

If nothing else, perhaps you could save a log of the flash (or if using JetPack I think it preserves a log) and post it here.

Dear Sir

What I mean with the LAN does not work is, there are green led when the router and Jetson-TK1 are both connected, but the led still orange/red (the device not connected). I already tried JetPack3.0 several times, but it failed to download, even if connect or not to device)

Thx

Here is the flash result***********

user@user-Lenovo-G50-80:~/reflash/Linux_for_Tegra$ sudo ./flash.sh -S 14580MiB jetson-tk1 mmcblk0p1
copying bctfile(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/BCT/PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg)… done.
copying bootloader(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/u-boot.bin)… done.
populating kernel to rootfs… done.
populating jetson-tk1_extlinux.conf.emmc to rootfs… done.
done.
Making system.img…
populating rootfs from /home/user/reflash/Linux_for_Tegra/rootfs … done.
Sync’ing system.img … done.
Converting RAW image to Sparse image…

---- Raw to Sparse Image Converter v1.0 ----------------------------
0: RAW: 3747840( 915 blks) ==> 28:3747852
1: SKP: 57344( 14 blks) ==> 3747880:57356
2: RAW: 4096( 1 blks) ==> 3747892:4108
3: SKP: 61440( 15 blks) ==> 3752000:61452
4: RAW: 4096( 1 blks) ==> 3752012:4108
5: SKP: 33550336( 8191 blks) ==> 3756120:33550348
6: RAW: 24576( 6 blks) ==> 3756132:24588
7: SKP: 96768000( 23625 blks) ==> 3780720:96768012
8: RAW: 8192( 2 blks) ==> 3780732:8204
9: SKP: 3731456( 911 blks) ==> 3788936:3731468
10: RAW: 4096( 1 blks) ==> 3788948:4108
11: SKP: 264691712( 64622 blks) ==> 3793056:264691724
12: RAW: 8192( 2 blks) ==> 3793068:8204
13: SKP: 268427264( 65534 blks) ==> 3801272:268427276
14: RAW: 8192( 2 blks) ==> 3801284:8204
15: SKP: 268427264( 65534 blks) ==> 3809488:268427276
16: RAW: 8192( 2 blks) ==> 3809500:8204
17: SKP: 268427264( 65534 blks) ==> 3817704:268427276
18: RAW: 8192( 2 blks) ==> 3817716:8204
19: SKP: 939515904( 229374 blks) ==> 3825920:939515916
20: RAW: 4096( 1 blks) ==> 3825932:4108
21: SKP: 1207955456( 294911 blks) ==> 3830040:1207955468
22: RAW: 8192( 2 blks) ==> 3830052:8204
23: SKP: 268427264( 65534 blks) ==> 3838256:268427276
24: RAW: 8192( 2 blks) ==> 3838268:8204
25: SKP: 671080448( 163838 blks) ==> 3846472:671080460
26: RAW: 4096( 1 blks) ==> 3846484:4108
27: SKP: 2147479552( 524287 blks) ==> 3850592:2147479564
28: RAW: 12288( 3 blks) ==> 3850604:12300
29: SKP: 134205440( 32765 blks) ==> 3862904:134205452
30: RAW: 8192( 2 blks) ==> 3862916:8204
31: SKP: 3731456( 911 blks) ==> 3871120:3731468
32: RAW: 81920( 20 blks) ==> 3871132:81932
33: SKP: 2009444352( 490587 blks) ==> 3953064:2009444364
34: RAW: 4096( 1 blks) ==> 3953076:4108
35: SKP: 2147479552( 524287 blks) ==> 3957184:2147479564
36: RAW: 4096( 1 blks) ==> 3957196:4108
37: SKP: 134213632( 32767 blks) ==> 3961304:134213644
38: RAW: 8192( 2 blks) ==> 3961316:8204
39: SKP: 2013257728( 491518 blks) ==> 3969520:2013257740
40: RAW: 8192( 2 blks) ==> 3969532:8204
41: SKP: 57344( 14 blks) ==> 3977736:57356
42: RAW: 4096( 1 blks) ==> 3977748:4108
43: SKP: 61440( 15 blks) ==> 3981856:61452
44: RAW: 4096( 1 blks) ==> 3981868:4108
45: SKP: 33550336( 8191 blks) ==> 3985976:33550348
46: RAW: 12288( 3 blks) ==> 3985988:12300
47: SKP: 100519936( 24541 blks) ==> 3998288:100519948
48: RAW: 6356992( 1552 blks) ==> 3998300:6357004
49: SKP: 2006908928( 489968 blks) ==> 10355304:2006908940
50: RAW: 8192( 2 blks) ==> 10355316:8204
51: SKP: 255844352( 62462 blks) ==> 10363520:255844364
– Total: -----------------------------------------------------------
52 CHUNK 15288238080(3732480 blks) ==> 10363532(2530 blks)

done.
system.img built successfully.
copying dtbfile(/home/user/reflash/Linux_for_Tegra/kernel/dtb/tegra124-jetson_tk1-pm375-000-c00-00.dtb)… done.
copying cfgfile(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/cfg/gnu_linux_fastboot_emmc_full.cfg) to flash.cfg… done.
creating gpt(ppt.img)…

*** GPT Parameters ***
Device Sector Size ------- 512
device size -------------- 15766388736
bootpart size ------------ 8388608
userpart size ------------ 15758000128
Erase Block Size --------- 2097152
FS Buffer size ----------- 4096
Partition Config file ---- flash.cfg
Visible partition flag — GP1
Primary GPT output ------- PPT->ppt.img
Secondary GPT output ----- GPT->gpt.img
Target device name ------- none

*** PARTITION LAYOUT(20 partitions) ***
[ BCT] BH 0 16383 8.0MiB
[ PPT] UH 0 4095 2.0MiB ppt.img
[ PT] UH 4096 8191 2.0MiB
[ EBT] UH 8192 16383 4.0MiB u-boot.bin
[ LNX] UH 16384 49151 16.0MiB
[ SOS] UH 49152 61439 6.0MiB
[ NVC] UH 61440 65535 2.0MiB
[ MPB] UH 65536 77823 6.0MiB
[ MBP] UH 77824 90111 6.0MiB
[ GP1] UH 90112 94207 2.0MiB
[ APP] UV 94208 29954047 14580.0MiB system.img
[ DTB] UV 29954048 29962239 4.0MiB tegra124-jetson_tk1-pm375-000-c00-00.dtb
[ EFI] UV 29962240 30093311 64.0MiB
[ USP] UV 30093312 30101503 4.0MiB
[ TP1] UV 30101504 30109695 4.0MiB
[ TP2] UV 30109696 30117887 4.0MiB
[ TP3] UV 30117888 30126079 4.0MiB
[ WB0] UV 30126080 30130175 2.0MiB
[ UDA] UV 30130176 30773247 314.0MiB
[ GPT] UH 30773248 30777343 2.0MiB gpt.img
copying flasher(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/fastboot.bin)… done.
Existing flashapp(/home/user/reflash/Linux_for_Tegra/bootloader/nvflash) reused.
*** Flashing target device started. ***
./nvflash --bct PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg --setbct --configfile flash.cfg --create --bl fastboot.bin --odmdata 0x6009C000 --go
Nvflash 4.13.0000 started
BR_CID: 0x34001001740de0c90000000008048080
rcm version 0X400001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x40 major: 1 minor: 1
chip sku: 0x0
chip uid: 0x00000001740de0c90000000008048080
macrovision: disabled
hdcp: disabled
jtag: disabled
sbk burned: false
board id: 0
warranty fuse: 0
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0

RCM communication completed
BCT sent successfully
sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb

  • 59661/59661 bytes sent
    tegra124-jetson_tk1-pm375-000-c00-00.dtb sent successfully
    odm data: 0x6009c000
    downloading bootloader – load address: 0x83d88000 entry point: 0x83d88000
    sending file: fastboot.bin
  • 594363/594363 bytes sent
    fastboot.bin sent successfully
    waiting for bootloader to initialize
    bootloader downloaded successfully
    ML execution and Cpu Handover took 1 Secs
    Partition backup took 0 Secs
    setting device: 2 3
    deleting device partitions
    creating partition: BCT
    creating partition: PPT
    creating partition: PT
    creating partition: EBT
    creating partition: LNX
    creating partition: SOS
    creating partition: NVC
    creating partition: MPB
    creating partition: MBP
    creating partition: GP1
    creating partition: APP
    creating partition: DTB
    creating partition: EFI
    creating partition: USP
    creating partition: TP1
    creating partition: TP2
    creating partition: TP3
    creating partition: WB0
    creating partition: UDA
    creating partition: GPT
    sending file: ppt.img
    \ 2097152/2097152 bytes sent
    ppt.img sent successfully
    padded 4 bytes to bootloader
    sending file: u-boot.bin
  • 439120/439120 bytes sent
    u-boot.bin sent successfully
    sending file: system.img
    \ 10363532/10363532 bytes sent
    system.img sent successfully
    sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb
  • 59661/59661 bytes sent
    tegra124-jetson_tk1-pm375-000-c00-00.dtb sent successfully
    sending file: gpt.img
    \ 2097152/2097152 bytes sent
    gpt.img sent successfully
    Create, format and download took 10 Secs
    Time taken for flashing 13 Secs
    *** The target ardbeg has been flashed successfully. ***
    Reset the board to boot from internal eMMC.

The conversion of raw to sparse is extremely small in terms of number of conversions. This same command for me required 3200 “chunks”. Yours used 52 chunks (about 30:1 ratio). After the flash, what is the exact byte size of “bootloader/system.img.raw” and “bootloader/system.img”?

In that bootloader subdirectory, what is the output of:

df -H -T .

Basically the flash succeeded, but the image sent is very suspicious in size or content.

********* output df -H -T ************

user@user-Lenovo-G50-80:~/reflash/Linux_for_Tegra/bootloader$ df -H -T
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 4,2G 4,1k 4,2G 1% /dev
tmpfs tmpfs 829M 1,3M 828M 1% /run
/dev/sda6 ext4 7,5G 5,4G 1,7G 76% /
none tmpfs 4,1k 0 4,1k 0% /sys/fs/cgroup
none tmpfs 5,3M 0 5,3M 0% /run/lock
none tmpfs 4,2G 78k 4,2G 1% /run/shm
none tmpfs 105M 37k 105M 1% /run/user

******* File Size *******
-rwxr-xr-x 1 root root 9,9M Jul 26 04:34 system.img
-rw-r–r-- 1 root root 15G Jul 26 04:34 system.img.raw

According to this your root file system has only 1.7GB of free space…the system has filled up and is truncating the image file.

The size of the uncompressed raw image for “-S 14580MiB” would be 1458010241024 bytes (the image file produced should be 15288238080 bytes). You only gave a “human readable” size of the system.img.raw so I can’t tell if it was valid…have to use “ls -l”. The compressed image is normally in the rough size of 2GB. The 9.9MB size says your system ran out of space long before the compressed image was created…it is truncated. This is the problem…the image was not transferred to the Jetson in whole. This is also why so few “chunks” were created during compression.

You probably need about 3.5GB more space before you can safely flash. If you are willing to let it take a long time (several hours perhaps), then you can use the uncompressed image for the data to send over the USB2 wire. Originally there was no compressed image in the scheme of how flash proceeded…the software still allows using non-compressed images…the system.img.raw file can be renamed as “system.img”, then flash with “sudo ./flash.sh -r -S 14580MiB jetson-tk1 mmcblk0p1” and the flash should proceed. Then you don’t need the compressed version of the file.

Here is my detail about system.img****

-rwxr-xr-x 1 root root 10363532 Jul 26 04:34 system.img
-rw-r–r-- 1 root root 15288238080 Jul 26 04:34 system.img.raw

i copied system.img.raw to system.img

After I Flash the result is the same :

Flashing Process****

user@user-Lenovo-G50-80:~/reflash/Linux_for_Tegra$ sudo ./flash.sh -r -S 14580MiB jetson-tk1 mmcblk0p1
copying bctfile(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/BCT/PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg)… done.
copying bootloader(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/u-boot.bin)… done.
populating kernel to rootfs… done.
populating jetson-tk1_extlinux.conf.emmc to rootfs… done.
done.
Reusing existing system.img…
done.
copying dtbfile(/home/user/reflash/Linux_for_Tegra/kernel/dtb/tegra124-jetson_tk1-pm375-000-c00-00.dtb)… done.
copying cfgfile(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/cfg/gnu_linux_fastboot_emmc_full.cfg) to flash.cfg… done.
creating gpt(ppt.img)…

*** GPT Parameters ***
Device Sector Size ------- 512
device size -------------- 15766388736
bootpart size ------------ 8388608
userpart size ------------ 15758000128
Erase Block Size --------- 2097152
FS Buffer size ----------- 4096
Partition Config file ---- flash.cfg
Visible partition flag — GP1
Primary GPT output ------- PPT->ppt.img
Secondary GPT output ----- GPT->gpt.img
Target device name ------- none

*** PARTITION LAYOUT(20 partitions) ***
[ BCT] BH 0 16383 8.0MiB
[ PPT] UH 0 4095 2.0MiB ppt.img
[ PT] UH 4096 8191 2.0MiB
[ EBT] UH 8192 16383 4.0MiB u-boot.bin
[ LNX] UH 16384 49151 16.0MiB
[ SOS] UH 49152 61439 6.0MiB
[ NVC] UH 61440 65535 2.0MiB
[ MPB] UH 65536 77823 6.0MiB
[ MBP] UH 77824 90111 6.0MiB
[ GP1] UH 90112 94207 2.0MiB
[ APP] UV 94208 29954047 14580.0MiB system.img
[ DTB] UV 29954048 29962239 4.0MiB tegra124-jetson_tk1-pm375-000-c00-00.dtb
[ EFI] UV 29962240 30093311 64.0MiB
[ USP] UV 30093312 30101503 4.0MiB
[ TP1] UV 30101504 30109695 4.0MiB
[ TP2] UV 30109696 30117887 4.0MiB
[ TP3] UV 30117888 30126079 4.0MiB
[ WB0] UV 30126080 30130175 2.0MiB
[ UDA] UV 30130176 30773247 314.0MiB
[ GPT] UH 30773248 30777343 2.0MiB gpt.img
copying flasher(/home/user/reflash/Linux_for_Tegra/bootloader/ardbeg/fastboot.bin)… done.
Existing flashapp(/home/user/reflash/Linux_for_Tegra/bootloader/nvflash) reused.
*** Flashing target device started. ***
./nvflash --bct PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg --setbct --configfile flash.cfg --create --bl fastboot.bin --odmdata 0x6009C000 --go
Nvflash 4.13.0000 started
BR_CID: 0x34001001740de0c90000000008048080
rcm version 0X400001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x40 major: 1 minor: 1
chip sku: 0x0
chip uid: 0x00000001740de0c90000000008048080
macrovision: disabled
hdcp: disabled
jtag: disabled
sbk burned: false
board id: 0
warranty fuse: 0
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0

RCM communication completed
BCT sent successfully
sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb

  • 59661/59661 bytes sent
    tegra124-jetson_tk1-pm375-000-c00-00.dtb sent successfully
    odm data: 0x6009c000
    downloading bootloader – load address: 0x83d88000 entry point: 0x83d88000
    sending file: fastboot.bin
  • 594363/594363 bytes sent
    fastboot.bin sent successfully
    waiting for bootloader to initialize
    bootloader downloaded successfully
    ML execution and Cpu Handover took 1 Secs
    Partition backup took 0 Secs
    setting device: 2 3
    deleting device partitions
    creating partition: BCT
    creating partition: PPT
    creating partition: PT
    creating partition: EBT
    creating partition: LNX
    creating partition: SOS
    creating partition: NVC
    creating partition: MPB
    creating partition: MBP
    creating partition: GP1
    creating partition: APP
    creating partition: DTB
    creating partition: EFI
    creating partition: USP
    creating partition: TP1
    creating partition: TP2
    creating partition: TP3
    creating partition: WB0
    creating partition: UDA
    creating partition: GPT
    sending file: ppt.img
    \ 2097152/2097152 bytes sent
    ppt.img sent successfully
    padded 4 bytes to bootloader
    sending file: u-boot.bin
  • 439120/439120 bytes sent
    u-boot.bin sent successfully
    sending file: system.img
    / 15288238080/15288238080 bytes sent
    system.img sent successfully
    sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb
  • 59661/59661 bytes sent
    tegra124-jetson_tk1-pm375-000-c00-00.dtb sent successfully
    sending file: gpt.img
    \ 2097152/2097152 bytes sent
    gpt.img sent successfully
    Create, format and download took 857 Secs
    Time taken for flashing 860 Secs
    *** The target ardbeg has been flashed successfully. ***
    Reset the board to boot from internal eMMC.

after df -H -T**

user@user-Lenovo-G50-80:~/reflash/Linux_for_Tegra$ df -H -T
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 4,2G 4,1k 4,2G 1% /dev
tmpfs tmpfs 829M 1,3M 828M 1% /run
/dev/sda6 ext4 7,5G 5,5G 1,6G 78% /
none tmpfs 4,1k 0 4,1k 0% /sys/fs/cgroup
none tmpfs 5,3M 0 5,3M 0% /run/lock
none tmpfs 4,2G 82k 4,2G 1% /run/shm
none tmpfs 105M 50k 105M 1% /run/user

******after ls -l ******
user@user-Lenovo-G50-80:~/reflash/Linux_for_Tegra/bootloader$ ls -l
total 291372
drwxr-xr-x 4 1001 1001 4096 Jun 8 2016 ardbeg
-rwxr-xr-x 1 root root 594363 Jul 26 16:34 fastboot.bin
-rw-r–r-- 1 root root 4173 Jul 26 16:34 flash.cfg
-rw-r–r-- 1 root root 2097152 Jul 26 16:34 gpt.img
-rw-r–r-- 1 root root 5867 Jun 8 2016 LICENSE
-rw-r–r-- 1 root root 5867 Jun 8 2016 LICENSE.mkbctpart
-rw-r–r-- 1 root root 13123 Jun 8 2016 LICENSE.mkbootimg_and_mkubootscript
-rw-r–r-- 1 root root 5867 Jun 8 2016 LICENSE.mkgpt
-rw-r–r-- 1 root root 5867 Jun 8 2016 LICENSE.mksparse
-rw-r–r-- 1 1001 1001 21752 Jun 8 2016 LICENSE.u-boot_and_mkimage
-rwxr-xr-x 1 root root 486872 Jun 8 2016 mkbctpart
-rwxr-xr-x 1 root root 441007 Jun 8 2016 mkbootimg
-rwxr-xr-x 1 root root 485979 Jun 8 2016 mkgpt
-rwxr-xr-x 1 root root 121996 Jun 8 2016 mkimage
-rwxr-xr-x 1 root root 475945 Jun 8 2016 mksparse
-rwxr-xr-x 1 root root 466091 Jun 8 2016 mkubootscript
-rwxr-xr-x 1 root root 1307069 Jun 8 2016 nvflash
-rw-r–r-- 1 root root 42545 Jul 26 16:34 PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg
-rw-r–r-- 1 root root 2097152 Jul 26 16:34 ppt.img
-rw-r–r-- 1 root root 15288238080 Jul 26 16:32 system.img
-rw-r–r-- 1 root root 15288238080 Jul 26 04:34 system.img.raw
-rw-r–r-- 1 root root 1998 Jul 25 20:46 table
-rw-r–r-- 1 root root 59661 Jul 26 16:34 tegra124-jetson_tk1-pm375-000-c00-00.dtb
-rw-r–r-- 1 root root 439120 Jul 26 16:34 u-boot.bin

Your available space did drop from 1.7GB to 1.6GB. There are actually several other files generated during flash (but none nearly as large), and I’m wondering if somewhere in the process of running out of space one of those smaller files failed. The flash operation itself appears to have succeeded, so it must be the content of one of those earlier files failing. Is there any way you can mount a larger partition and start with a clean set of flash software with enough disk space?

I’m using “/dev/sdc1” as an example partition, you’d have to adjust for your system. Basically what you would do is format a partition with “sudo mkfs.ext4 /dev/sdc1”, then “sudo mount /dev/sdc1 /home/user/reflash/Linux_for_Tegra”. After this the parent directories would still be visible, but anything in Linux_for_Tegra would show as a brand new partition with nothing in it…the original would still be there untouched, and would show up again after “sudo umount /dev/sdc1”. From the “/home/user/reflash/” directory you could once again unpack the driver package and go through the sample rootfs and apply_binaries.sh step. If you delete the entire content of the original Linux_for_Tegra directory before you mount the extra disk partition, then you’d have plenty of space.

I can tell you for certain that the original issue was running out of disk space. Although the “-r” option had a chance to work, there are a number of other smaller operations going on and one of those may have been altered by having run out of space. For example, with 1.7GB extra it should not have been possible to use “cp” on system.img.raw to create system.img…it should have run out of space. Something else had to be deleted before you could do that. If you did delete enough other items on disk to achieve that, then some of the earlier steps for file unpacking may have still been truncated and not fixed by just the system.img.raw copy…some of those earlier operations for example determine what is in system.img.raw.

Dear Sir

Thank you very much, it worked

Hi,
I am dealing with the same problem and after trying the solution you´ve got, my TK1 still not booting. I am flashing with R216 and i did the “dev/sdc1” partition in a external USB and mounted to the Linux_for_Tegra directory.
All went fine with the flashing according to the results displayed but screen is not working yet.

Dear fabian

I didn’t usb swap, but i provide space about 70 GB. It worked also for R21.6. I already tried it. you have at least 50 GB free space to install it, if the problem same with me

Thx

If your USB stick is not formatted correctly boot will fail. The default of a USB stick is usually type VFAT which is incompatible with preserving file permissions. Did you use “mkfs.ext4 /dev/<whichever_it_is>”?

Also, U-Boot does not understand 64-bit filesystem extensions. Most hosts do not enable these, but some newer Linux hosts do. Verify that you don’t see either of these in the host “/etc/mke2fs.conf” ext4 section: “64bit”, “metadata_csum”.

Yes, i literally did “mkfs.ext4 /dev/sdc1” (´cause was the USB). But before that, i got a message that i needed to format and mount a new partition on that USB disk. So i typed “umount /dev/sdc1” and then the step already known.

On your Linux host PC which you flashed from, look at file “/etc/mke2fs.conf”. There will be a secton on ext4. Within that do you see either “64bit” or “metadata_csum”? Some of the newer systems use these which are intended for larger hard drives (they are the 64-bit extensions). Linux works great with these, but U-Boot does not…if these are the default on your host then this would cause a failure even if everything seemed correct.

i got this:
ext4 = {
features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
inode_size = 256

Either of the “64bit” or “metadata_csum” will cause U-Boot to fail to see this as ext4 (this U-Boot predates those ext4 64-bit options). The mkfs option (I’m going by memory, not where I can check) should be “mkfs.ext4 -o ^64bit,^metadata_csum /dev/whichever/it/is”. Any “^” option is negated and not used if otherwise present as default environment.