TK1 Failed to Flash Device

Trying to re-flash my tk1 and everything goes along for a while then I get this error:

Failed to flash device. please check /home/james/_installer/logs/flash_os_tk1.log for more details. then press Enter key when ready and try again.

here is the last line in the log that shows the error…

\ 77594624/2372277420 bytes sent
| 78643200/2372277420 bytes sentdata send failed NvError 0x8
command failure/warning: create failed
Failed flashing ardbeg.

Any Ideas anyone

The Host machine is an older laptop with a completely new install of Ubuntu 14.04.03

thanks you

Sorry I should have mentioned I’m trying to Flash Jetpack 2.0


I can’t use JetPack since my host is not Ubuntu, but I’m wondering if the log shows the flash command which JetPack used? Should be a line with “nvflash” in it.

Here’s the last part of the log that shows its flashing

copying flasher(/home/james/Linux_for_Tegra_tk1/bootloader/ardbeg/fastboot.bin)… done.
Existing flashapp(/home/james/Linux_for_Tegra_tk1/bootloader/nvflash) reused.
*** Flashing target device started. ***
./nvflash --bct PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.cfg --setbct --configfile flash.cfg --create --bl fastboot.bin --odmdata 0x6009C000 --go
Nvflash 4.13.0000 started
BR_CID: 0x340010017410b1000000000003010600
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: 0x000000017410b1000000000003010600
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

  • 59637/59637 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

  • 1048576/2097152 bytes sent
    \ 2097152/2097152 bytes sent
    ppt.img sent successfully
    padded 12 bytes to bootloader
    sending file: u-boot.bin

  • 440016/440016 bytes sent
    u-boot.bin sent successfully
    sending file: system.img

  • 1048576/2372277420 bytes sent
    \ 2097152/2372277420 bytes sent
    | 3145728/2372277420 bytes sent
    / 4194304/2372277420 bytes sent

  • 5242880/2372277420 bytes sent
    \ 6291456/2372277420 bytes sent
    | 7340032/2372277420 bytes sent
    / 8388608/2372277420 bytes sent

  • 9437184/2372277420 bytes sent
    \ 10485760/2372277420 bytes sent
    | 11534336/2372277420 bytes sent
    / 12582912/2372277420 bytes sent

  • 13631488/2372277420 bytes sent
    \ 14680064/2372277420 bytes sent
    | 15728640/2372277420 bytes sent
    / 16777216/2372277420 bytes sent

  • 17825792/2372277420 bytes sent
    \ 18874368/2372277420 bytes sent
    | 19922944/2372277420 bytes sent
    / 20971520/2372277420 bytes sent

  • 22020096/2372277420 bytes sent
    \ 23068672/2372277420 bytes sent
    | 24117248/2372277420 bytes sent
    / 25165824/2372277420 bytes sent

  • 26214400/2372277420 bytes sent
    \ 27262976/2372277420 bytes sent
    | 28311552/2372277420 bytes sent
    / 29360128/2372277420 bytes sent

  • 30408704/2372277420 bytes sent
    \ 31457280/2372277420 bytes sent
    | 32505856/2372277420 bytes sent
    / 33554432/2372277420 bytes sent

  • 34603008/2372277420 bytes sent
    \ 35651584/2372277420 bytes sent
    | 36700160/2372277420 bytes sent
    / 37748736/2372277420 bytes sent

  • 38797312/2372277420 bytes sent
    \ 39845888/2372277420 bytes sent
    | 40894464/2372277420 bytes sent
    / 41943040/2372277420 bytes sent

  • 42991616/2372277420 bytes sent
    \ 44040192/2372277420 bytes sent
    | 45088768/2372277420 bytes sent
    / 46137344/2372277420 bytes sent

  • 47185920/2372277420 bytes sent
    \ 48234496/2372277420 bytes sent
    | 49283072/2372277420 bytes sent
    / 50331648/2372277420 bytes sent

  • 51380224/2372277420 bytes sent
    \ 52428800/2372277420 bytes sent
    | 53477376/2372277420 bytes sent
    / 54525952/2372277420 bytes sent

  • 55574528/2372277420 bytes sent
    \ 56623104/2372277420 bytes sent
    | 57671680/2372277420 bytes sent
    / 58720256/2372277420 bytes sent

  • 59768832/2372277420 bytes sent
    \ 60817408/2372277420 bytes sent
    | 61865984/2372277420 bytes sent
    / 62914560/2372277420 bytes sent

  • 63963136/2372277420 bytes sent
    \ 65011712/2372277420 bytes sent
    | 66060288/2372277420 bytes sent
    / 67108864/2372277420 bytes sent

  • 68157440/2372277420 bytes sent
    \ 69206016/2372277420 bytes sent
    | 70254592/2372277420 bytes sent
    / 71303168/2372277420 bytes sent

  • 72351744/2372277420 bytes sent
    \ 73400320/2372277420 bytes sent
    | 74448896/2372277420 bytes sent
    / 75497472/2372277420 bytes sent

  • 76546048/2372277420 bytes sent
    \ 77594624/2372277420 bytes sent
    | 78643200/2372277420 bytes sentdata send failed NvError 0x8
    command failure/warning: create failed
    Failed flashing ardbeg.

Up until the last bytes sent it looks normal. The NvError 0x8 is this:

0x00000008, "module is in invalid state to perform the requested operation"

What should have happened is this:

system.img sent successfully

In particular, system.img is the root file system. I assume the JetPack version acts like a normal manual flash in that it updates the sample rootfs boot directory, creates a loopback mountable image as system.img, moves this to system.img.raw,and then creates a sparse image as system.img. Hardware could cause a failure of invalid state, but a simpler explanation would be that the system.img is invalid by reason of exceeding eMMC capacity.

There will be a subdirectory “bootloader” somewhere (I’m not sure how JetPack arranges directories) in the installation on the host. Within that, what is the exact size of any file starting with name “system.img”? E.g., “ls -l system.img*”?

Also, if a system.img is a raw image, it is loopback mountable…if it is a sparse image, then loopback mount will fail. Does this command (via sudo) run from the system.img file directory location succeed?

mkdir /mnt/tmp
mount -o loop -t ext4 system.img /mnt/tmp

…if that command works, you can umount via:

umount /mnt/tmp

If there is a system.img.raw, try the same thing using “system.img.raw” instead of “system.img”.

Hi Sorry too late, I deleted all the folders in the Host system…

I found this line
Existing flashapp(/home/james/Linux_for_Tegra_tk1/bootloader/nvflash) reused.

and I thought if there was a problem with this and its re-using it that could explain why it keeps failing, so I deleted everything and downloaded JetPack TK1-1.2 which installs 21.4 I assume that is the same 21.4 that JetPack 2.0 installs and It flashed just fine

so I’m back up and running now I have another dilemma, if its not the same do I want to re-try JetPack 2.0?

I’m not a Linux Guru so everything I do is learn as I go, I may try upgrading again but I will probably wait a couple weeks.

Release 21.4 is the most current L4T which can go on a TK1. This is the operating system for the TK1, and this will not care if you added it from the JetPack 1.2 or JetPack 2.0.

So far as I know the main difference between JetPack 1.2 and 2.0 is that 2.0 also understands the newer TX1, not just the TK1. In the case of a TK1 I think JetPack 2.0 will simply install the same things as JetPack 1.2…the difference is only when working with a TX1.

Since I’m unable to actually use JetPack without an Ubuntu host (I use Fedora) I’m not 100% certain that the secondary packages are the same between 1.2 and 2.0…by this I mean things like eclipse version going onto the host…it’s possible one of the host side packages had a minor upgrade.

Well I think I’ll just stay where I am for a while until I have a better understanding of whats going on… I do appreciate your help!!!

Thank you and Have a Great Holiday