New Jetson TK1 - Power button didnt work, Jetpack install fails and shuts unit down.

When i first plugged in the power cord into my Jetson TK1 the unit fired up. I pressed the power button repeatedly to power on/off the device but it only stayed on.

I proceeded with installing JetPack per the instructions, with the board in Recovery mode.
The TK1 and my host Ubuntu 14.02 running on a Dell Latitute E6400 were individually connected thru ethernet to the same router. As instructed i connected the TK1 to the Host using the provided usb cable and confirmed thru lsusb the TK1 was seen.

I then get the following install error which also shuts down the TK1.

*** Flashing target device started. ***
./nvflash --bct PM375_Hynix_2GB_H5TC4G63AFR_RDA_924MHz.cfg --setbct --configfile flash.cfg --create --bl fastboot.bin --odmdata 0x6009C000 --go
usb read error (108): Cannot send after transport endpoint shutdown
Nvflash 4.13.0000 started
BR_CID: 0x34001001740de1001c00000013058280
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: 0x00000001740de1001c00000013058280
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 failed NvError 0x0
    command failure/warning: bootloader download failed
    Failed flashing ardbeg.

Read all the relevant board messages and I’m at a loss on how to proceed.

Any feedback would be awesomely appreciated.

When the TK1 first arrives, I would expect that connecting power causes it to start without requiring the power button. Sometimes after the device has powered up and then is powered down with power disconnected the power button could possibly be required when reconnecting power.

When powering the unit off by power button instead of software there is a time delay the button needs to be pressed for several seconds (this helps avoid accidental power off). Since this is a full computer forcing power off while the system runs can cause problems with file system corruption (journaling file systems keep the file system usable, but chunks of files may be lost). Power down should be done via either the GUI button or via command “sudo shutdown -h now” (incorrect shutdown should be harmless so far as hardware is concerned…only software is an issue when using the power button).

The USB read error refers to the micro-USB cable. The fact that the supplied cable worked to detect the TK1 via lsusb shows that basics were correctly in place. Other issues can occur because of virtual host installs, otherwise this would tend to be an issue in the Jetson. How is your Linux host installed? Is it a standalone install? Is this a vmware install?

The Linux host is standalone install on a Dell Latitude E6400.

I also tried following the How to Reinstall the Original File System on Jetson TK1 instructions at
http://charlab.github.io/jetson/2014/10/28/how-to-reinstall-original-file-system-on-jetson-tk1/

but for R21.4,ie Tegra124_Linux_R21.4.0_armhf.tbz2

Same error with the TK1 shutting off while in Recovery Mode.

Here’s the lsusb output

sabrisansoy@ubuntubot:~/Downloads/tk1_reflash$ lsusb
Bus 002 Device 012: ID 0955:7140 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 003: ID 046d:c077 Logitech, Inc.
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Now when i hit the power button the device starts then shuts off immediately.
If i’m holding the Recovery Button down first then the power switch the unit stays on.

This sounds like hardware failure. Since recovery mode does not shut off automatically, I’m not 100% certain that it is hardware failure…there is a tiny possibility that the boot loader software is the cause of the non-recovery-mode power off issue. If a flash corrupted the boot software, then it becomes possible it is a software problem. However, the USB read error tends to validate the hardware being at fault. Unfortunately, I’d say it’s time to start the RMA procedure.

If you look here, a few lines down is an RMA procedure note:
https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/

I have the same problem, please help if you had solved it .

fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed: nverror 0x0
command failure/warning: bootloader download failed
Failed flashing ardbeg.

Hey Suryamohan,
i had mine replaced. Here’s a link to get the process started

If you look here, a few lines down is an RMA procedure note:
https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/

ssansoy,

thanks man , I will also try to replace then