New Jetson TX2 module

Hello
We have a two jetson TX2 modules newly purchased, when we connect it with the Nvidia carrier board with HDMI and Display nothing is showing on the display after power up. it on has one red LED in the centre that powers up. nothing else, even though we press the power button. we have tried flashing the OS using Jetpack 3.3 using USB recovery and reset but at the last we get a message telling failed to flash the device

Since individual modules arrive with no software the original pre-flash boot failure is expected. The most common reason for a flash failing if use of a VM (which doesn’t not correctly handle USB).

Can you give more details about the flash failure? Is the host a VM? If not, then other details, e.g., log messages would help. The attempt to flash would have set up flash content, and so you could do a manual flash with logging on command line. Locate the flash software’s “Linux_for_Tegra/” subdirectory within the JetPack directory, and try this with the Jetson in recovery mode:
sudo ./flash.sh jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt

HI. Thanks for Reply. My host is not a VM. I have installed Ubuntu 16.04 on a physical machine(HP Z600). In my carrier board only cr5 led is on, pressing power button does not help anything. However i followed your instruction with Jetson recovery mode( i am not sure whether it went to recovery mode or not as none of the button works, also typing lsusb in terminal does not show anything). This is the log i got after flashing through terminal
###############################################################################

L4T BSP Information:

R28 (release), REVISION: 2.1, GCID: 11272647, BOARD: t186ref, EABI: aarch64,

DATE: Thu May 17 07:29:06 UTC 2018

###############################################################################
Error: Invalid target rootdev(mmcb1k0p1).

Usage: sudo ./flash.sh [options] t186ref
Where,
rootdev for t186ref:
mmcblk0p12 ------------ internal eMMC.
sda1 ----------------- external USB devices. (USB memory stick, HDD)
eth0 ----------------- nfsroot via RJ45 Ethernet port.
eth1 ----------------- nfsroot via USB Ethernet interface.
options:
-b --------- nvflash boot control table config file.
-c --------- nvflash partition table config file.
-d --------- device tree file.
-e ------- Target device’s eMMC size.
-f -------- Path to flash application: nvflash or tegra-rcm.
-h ------------------- print this message.
-i ------------------- pass user kernel commandline as-is to kernel.
-k ---- partition name or number specified in flash.cfg.
-m ----- MTS preboot such as mts_preboot_si.
-n -------- Static nfs network assignments
:::
-o --------- ODM data.
-p --------- Total eMMC HW boot partition size.
-r ------------------- skip building and reuse existing system.img.
-s ----- PKC key used for signing and building bl_update_payload.
-t ------- tegraboot binary such as nvtboot.bin
-u -------- PKC server in @ format.
-w --------- warm boot binary such as nvtbootwb0.bin
-x --------- Tegra CHIPID. default = 0x18(jetson-tx2)
0x21(jetson-tx1), 0x40(jetson-tk1).
-y -------- PKC for secureboot, NS for non-secureboot.
-z -------------- Serial Number of target board.
-B --------- BoardId.
-C --------- Kernel commandline arguments.
WARNING:
Each option in this kernel commandline gets
higher preference over the same option from
fastboot. In case of NFS booting, this script
adds NFS booting related arguments, if -i option
is omitted.
-F --------- Flash server such as fastboot.bin.
-G ------- Read partition and save image to file.
-I ---------- initrd file. Null initrd is default.
-K ---------- Kernel image file such as zImage or Image.
-L ------ Bootloader such as cboot.bin or u-boot-dtb.bin.
-M -------- MTS boot file such as mts_si.
-N --------- i.e. :/my/exported/nfs/rootfs.
-P <end of PPT + 1> – Primary GPT start address + size of PPT + 1.
-R ------ Sample rootfs directory.
-S ------------ Rootfs size in bytes. Valid only for internal
rootdev. KiB, MiB, GiB short hands are allowed,
for example, 1GiB means 1024 * 1024 * 1024 bytes.
-T -------- ITS file name. Valid only for u-boot.
–no-flash ----------- perform all steps except physically flashing the board.
This will create a system.img.
–bup ---------------- Generate bootloader update payload(BUP).
–multi-spec---------- Enable support for building multi-spec BUP.
–clean-up------------ Clean up BUP buffer when multi-spec is enabled.
–usb-instance – Specify the USB instance to connect to; integer
ID (e.g. 0, 1), bus/dev (e.g. 003/091), or USB
port path (e.g. 3-14). The latter is best.

If you are using a more recent release of L4T/JetPack/SDK Manager, then you’ll probably need to use an Ubuntu 18.04 LTS host. Is it possible to upgrade the host to 18.04? Perhaps not the most convenient thing to do, but if you can, then this may save you some frustration.

The red LED is to show main power is delivered to the module. Other LEDs (green) should light if the system is booted (or in the process of booting). Similarly, if in recovery mode, then the green LEDs should show up. Some revisions have a power LED associated with the PCIe slot as well.

Even if no software is installed recovery mode should work with the pair of green LEDs near the power button. Recovery mode does not depend on any software being flashed. Any time you hold down the recovery button, followed by either power on or cycle of power, then it should be in recovery mode.

If you are in recovery mode, then the green LEDs near the power button should be on. If you also have the micro-B USB connected between Linux host PC and Jetson, then output from this would occur for a TX2 (TX2i will require a different ID):
lsusb -d 0955:7c18

If this fails, then you may need an RMA.

The flash command, without the correct arguments, will print the help options instead of flashing. What you posted is what the flash.sh script will show if the flash command is not valid. You would need to be in the directory with the flash.sh script, and specifically:
sudo ./flash.sh jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt
(this logs)

If you were to flash without a log:
sudo ./flash.sh jetson-tx2 mmcblk0p1

Are you able to enter recovery mode with the green lights on? If this does not occur, then you may have a hardware issue in the carrier board.

Hi…Thanks for help. As you said i found out that, the carrier board was not proper. I replaced the carrier board with working one and as you said everything is working fine. I also flashed with new OS.