Error sending system.img while flashing JetPack

Hi,

I’m trying to flash my new TK1 with the latest JetPack 2.3.1 and get error NvError:0x8 when trying to send the system.img. It sends some of the system.img bytes then exits. When I re-run it, it sends a few more but still crashes. It’s the same error and basically the same log as in this post: https://devtalk.nvidia.com/default/topic/899196/jetson-tk1/tk1-failed-to-flash-device-/. That user was able to get an older JetPack version working.

I’ve also tried earlier versions, 2.3, 2.0 and 1.2, as well as following the instructions in this post: https://devtalk.nvidia.com/default/topic/982779/jetson-tk1/how-to-perform-a-correct-fresh-ubuntu-install-on-jetson-tk1/ and get the same error.

I’m running Ubuntu 14.04 on my host computer and it has plenty of ext4 space left.

Any help is greatly appreciated! Let me know any further info I can provide.

Thanks!

Is this a VM? USB issues might cause problems, especially under a VM. Also, is this the original USB micro-B cable that came with the Jetson? Is there an intervening USB HUB?

It probably doesn’t help much, but here is the official error code:

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

I’m running Ubuntu natively and using the provided microUSB cable directly to the host. The only ports in use are the AC power jack, ethernet and microUSB.

Here’s the log output, truncated a bit:

copying bctfile(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/bootloader/ardbeg/BCT/PM375_Hynix_2GB_H5TC4G63AFR_H5TC4G63CFR_RDA_924MHz.cfg)... done.
copying bootloader(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/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/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/rootfs ... done.
	Sync'ing system.img ... done.
	Converting RAW image to Sparse image... 

---- Raw to Sparse Image Converter v1.0 ----------------------------
  0: RAW:     3698688(    903 blks) ==>          28:3698700
  1: SKP:       40960(     10 blks) ==>     3698728:40972
  2: RAW:       :24588
  [ ... ] 
1750: RAW:       98304(     24 blks) ==>  2329207332:98316
1751: SKP:        4096(      1 blks) ==>  2329305648:4108
1752: RAW:    43802624(  10694 blks) ==>  2329305660:43802636
1753: SKP:  1856131072( 453157 blks) ==>  2373108296:1856131084
-- Total: -----------------------------------------------------------
1754 CHUNK 15032385536(3670016 blks) ==>  2373108308(579367 blks)

done.
system.img built successfully. 
copying dtbfile(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/kernel/dtb/tegra124-jetson_tk1-pm375-000-c00-00.dtb)... done.
copying cfgfile(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/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     29454335   14336.0MiB system.img
[     DTB] UV     29454336     29462527       4.0MiB tegra124-jetson_tk1-pm375-000-c00-00.dtb
[     EFI] UV     29462528     29593599      64.0MiB 
[     USP] UV     29593600     29601791       4.0MiB 
[     TP1] UV     29601792     29609983       4.0MiB 
[     TP2] UV     29609984     29618175       4.0MiB 
[     TP3] UV     29618176     29626367       4.0MiB 
[     WB0] UV     29626368     29630463       2.0MiB 
[     UDA] UV     29630464     30773247     558.0MiB 
[     GPT] UH     30773248     30777343       2.0MiB gpt.img
copying flasher(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/bootloader/ardbeg/fastboot.bin)... done.
Existing flashapp(/home/sam/tk1_jetpack/TK1/Linux_for_Tegra_tk1/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: 0x34001001740dc1891400000004fc8500
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: 0x00000001740dc1891400000004fc8500
   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

- 1048576/2097152 bytes sent
\ 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

- 1048576/2373108308 bytes sent
\ 2097152/2373108308 bytes sent
| 3145728/2373108308 bytes sent
/ 4194304/2373108308 bytes sent
- 5242880/2373108308 bytes sent
\ 6291456/2373108308 bytes sent
| 7340032/2373108308 bytes sent
/ 8388608/2373108308 bytes sent
- 9437184/2373108308 bytes sent
\ 10485760/2373108308 bytes sent
| 11534336/2373108308 bytes sent
/ 12582912/2373108308 bytes sent
- 13631488/2373108308 bytes sent
\ 14680064/2373108308 bytes sent
| 15728640/2373108308 bytes sent
/ 16777216/2373108308 bytes sent
- 17825792/2373108308 bytes sent
\ 18874368/2373108308 bytes sent
| 19922944/2373108308 bytes sent
/ 20971520/2373108308 bytes sent
- 22020096/2373108308 bytes sent
\ 23068672/2373108308 bytes sent
| 24117248/2373108308 bytes sent
/ 25165824/2373108308 bytes sent
- 26214400/2373108308 bytes sent
\ 27262976/2373108308 bytes sent
| 28311552/2373108308 bytes sent
/ 29360128/2373108308 bytes sent
- 30408704/2373108308 bytes sent
\ 31457280/2373108308 bytes sent
| 32505856/2373108308 bytes sent
/ 33554432/2373108308 bytes sent
- 34603008/2373108308 bytes sent
\ 35651584/2373108308 bytes sent
| 36700160/2373108308 bytes sent
/ 37748736/2373108308 bytes sent
- 38797312/2373108308 bytes sent
\ 39845888/2373108308 bytes sent
| 40894464/2373108308 bytes sent
/ 41943040/2373108308 bytes sent
- 42991616/2373108308 bytes sent
\ 44040192/2373108308 bytes sent
| 45088768/2373108308 bytes sent
/ 46137344/2373108308 bytes sent
- 47185920/2373108308 bytes sent
\ 48234496/2373108308 bytes sent
| 49283072/2373108308 bytes sent
/ 50331648/2373108308 bytes sent
- 51380224/2373108308 bytes sent
\ 52428800/2373108308 bytes sent
| 53477376/2373108308 bytes sent
/ 54525952/2373108308 bytes sent
- 55574528/2373108308 bytes sent
\ 56623104/2373108308 bytes sent
| 57671680/2373108308 bytes sent
/ 58720256/2373108308 bytes sent
- 59768832/2373108308 bytes sent
\ 60817408/2373108308 bytes sent
| 61865984/2373108308 bytes sent
/ 62914560/2373108308 bytes sent
- 63963136/2373108308 bytes sent
\ 65011712/2373108308 bytes sent
| 66060288/2373108308 bytes sent
/ 67108864/2373108308 bytes sent
- 68157440/2373108308 bytes sent
\ 69206016/2373108308 bytes sent
| 70254592/2373108308 bytes sent
/ 71303168/2373108308 bytes sent
- 72351744/2373108308 bytes sent
\ 73400320/2373108308 bytes sent
| 74448896/2373108308 bytes sent
/ 75497472/2373108308 bytes sent
- 76546048/2373108308 bytes sent
\ 77594624/2373108308 bytes sent
| 78643200/2373108308 bytes sent
/ 79691776/2373108308 bytes sent
- 80740352/2373108308 bytes sent
\ 81788928/2373108308 bytes sent
| 82837504/2373108308 bytes sent
/ 83886080/2373108308 bytes sent
- 84934656/2373108308 bytes sent
\ 85983232/2373108308 bytes sent
| 87031808/2373108308 bytes sent
/ 88080384/2373108308 bytes sent
- 89128960/2373108308 bytes sent
\ 90177536/2373108308 bytes sent
| 91226112/2373108308 bytes sent
/ 92274688/2373108308 bytes sent
- 93323264/2373108308 bytes sent
\ 94371840/2373108308 bytes sent
| 95420416/2373108308 bytes sent
/ 96468992/2373108308 bytes sent
- 97517568/2373108308 bytes sent
\ 98566144/2373108308 bytes sent
| 99614720/2373108308 bytes sent
/ 100663296/2373108308 bytes sent
- 101711872/2373108308 bytes sent
\ 102760448/2373108308 bytes sent
| 103809024/2373108308 bytes sent
/ 104857600/2373108308 bytes sent
- 105906176/2373108308 bytes sent
\ 106954752/2373108308 bytes sent
| 108003328/2373108308 bytes sent
/ 109051904/2373108308 bytes sent
- 110100480/2373108308 bytes sent
\ 111149056/2373108308 bytes sent
| 112197632/2373108308 bytes sent
/ 113246208/2373108308 bytes sent
- 114294784/2373108308 bytes sent
\ 115343360/2373108308 bytes sent
| 116391936/2373108308 bytes sent
/ 117440512/2373108308 bytes sent
- 118489088/2373108308 bytes sent
\ 119537664/2373108308 bytes sent
| 120586240/2373108308 bytes sent
/ 121634816/2373108308 bytes sent
- 122683392/2373108308 bytes sent
\ 123731968/2373108308 bytes sent
| 124780544/2373108308 bytes sent
/ 125829120/2373108308 bytes sent
- 126877696/2373108308 bytes sent
\ 127926272/2373108308 bytes sent
| 128974848/2373108308 bytes sent
/ 130023424/2373108308 bytes sent
- 131072000/2373108308 bytes sent
\ 132120576/2373108308 bytes sent
| 133169152/2373108308 bytes sent
/ 134217728/2373108308 bytes sent
- 135266304/2373108308 bytes sent
\ 136314880/2373108308 bytes sent
| 137363456/2373108308 bytes sent
/ 138412032/2373108308 bytes sent
- 139460608/2373108308 bytes sent
\ 140509184/2373108308 bytes sent
| 141557760/2373108308 bytes sent
/ 142606336/2373108308 bytes sent
- 143654912/2373108308 bytes sent
\ 144703488/2373108308 bytes sent
| 145752064/2373108308 bytes sent
/ 146800640/2373108308 bytes sent
- 147849216/2373108308 bytes sent
\ 148897792/2373108308 bytes sent
| 149946368/2373108308 bytes sent
/ 150994944/2373108308 bytes sent
- 152043520/2373108308 bytes sent
\ 153092096/2373108308 bytes sent
| 154140672/2373108308 bytes sent
/ 155189248/2373108308 bytes sent
- 156237824/2373108308 bytes sent
\ 157286400/2373108308 bytes sent
| 158334976/2373108308 bytes sent
/ 159383552/2373108308 bytes sent
- 160432128/2373108308 bytes sent
\ 161480704/2373108308 bytes sent
| 162529280/2373108308 bytes sent
/ 163577856/2373108308 bytes sent
- 164626432/2373108308 bytes sent
\ 165675008/2373108308 bytes sent
| 166723584/2373108308 bytes sent
/ 167772160/2373108308 bytes sent
- 168820736/2373108308 bytes sent
\ 169869312/2373108308 bytes sent
| 170917888/2373108308 bytes sentdata send failed NvError 0x8
command failure/warning: create failed 
Failed flashing ardbeg.

Could this be a hardware issue? Is there some foolproof way to factory reset my board?

Thanks again for any help.

It could be hardware failure, though usually this would be something going on in the host. During actual hardware failure typically no image would send successfully…but here part is going through and only later is there a failure (several other partitions did go through successfully). Is there any kind of USB HUB in between? If so, try without the HUB.

So far as factory reset goes, flashing is how that would be done…it’s just a question of flashing with an older version versus a newer version of L4T. The flash itself is failing, so until flash works, you can’t reset…and once it does work, the newer version is better than the original factory version. If you can’t get it to work then you would go through RMA…the trouble is that under these circumstances I wonder if a new board would do exactly the same thing (my gut feeling is that this kind of error is host-side…RMA is ok, but you might end up back in this same situation again). The one case where this might be a true hardware failure is if it fails at the same eMMC address each time…it could be eMMC went bad at that location.

If you do choose to RMA, look for RMA at the top of this URL:
https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/

I was able to flash the board by switching to a different Linux host computer. They’re both running Ubuntu 14.04, but the first uses i3 and the second uses Unity. Not sure if that matters.

If I want to develop applications with the first computer I can just install the Jetpack tools without flashing, right? Or was there anything that happened that specifically paired the host computer to the Jetson?

Thanks!

JetPack is just a front end to packages and flash.sh. You don’t have to flash with it, so yes, you can do package management and deselect flash.

The only issue I can think of would be if JetPack on the new host set up that host as a router…perhaps the other host is also set up as a router. Somewhere, if Jetson runs DHCP, there must be one and only one router to respond to DHCP requests.