Jetson TX2 Module Error

Jetpack3.3.1_log_1.txt (262.0 KB) SDK_Jetpack3.3.1_log.txt (811.4 KB) SDK_Jetpack3.3.3_log.txt (1013.5 KB)

I just got TX2 Module but i think this is something different as old one.

It does not work when fusing with Jetpack 3.3.1 version,

Attached the log of fusing.

NTC_Jetpack3.3.1_log is the log when fusing the image we are using, and in the case of this image, there is a phenomenon of freezing at a certain part.

SDK_Jetpack3.3.1_log and SDK_Jetpack3.3.3_log are logs when fusing using the SDK tool,

When using the SDK tool, similarly, when the Jetpack 3.3.1 version was used, there was a problem where it freezes at certain parts.

In the case of Jetpack 3.3.3, fusing succeeded, although some errors appeared.

We uploaded the image we are using, but the image is not uploaded to all modules.

(stops at the same specific part in the flash process)

So, by any chance, I uploaded the image on the Jetson TX2 module that I was using.

The image was uploaded normally to the existing module.

I am wondering if there is any difference between the Jetson TX2 module that I purchased this time and the module that was used previously.

Some notes to start: JetPack is actually a front end to the flash software. The actual flash is from what is called the “driver package”, which JetPack installs for you. If you’ve flashed, then the content in the “Linux_for_Tegra/” directory is the driver package. Within this is the “Linux_for_Tegra/rootfs/” directory, and that is from the “sample rootfs” package (which JetPack also installs). The “rootfs/” content is purely Ubuntu until the “” script is executed with sudo, and this adds some drivers to the “rootfs/”. This is what actually gets installed: An image designed from “rootfs/”, and is then known as “Linux for Tegra” (“L4T”). You can find the installed L4T release version via:
head -n 1 /etc/nv_tegra_release

This URL lists all of the JetPack/SDKM releases, and on the right you will see the L4T release bound to that JetPack:

When you mention version 3.3.1 this corresponds to L4T R28.3.1. when you mention 3.3.3, this corresponds to L4T R28.4. When working with clones this becomes important because surrounding boot content must match by version.

Those earlier releases under JetPack3.x were a bit more lenient on boot environment (partitions were not enforcing signing), but when you flash using a cloned image you must be sure that all of the surrounding boot content (the non-rootfs partitions) are from the matching JetPack release. If the flash which created your working content was created originally with JetPack3.3.1, then you must use the same release (L4T of the software flashing your clone onto the new module must be R28.3.1). If the clone came from R28.3.1, but is being flashed with R28.4, then there is a very strong chance boot will fail.

Which release is your clone from? You could either run “head -n 1 /etc/nv_tegra_release” on the original module to find this, or you could loopback mount your clone on the host PC and find out there.

Once you’ve verified versions are correct, then you could copy your clone into “Linux_for_Tegra/bootloader/system.img” (be careful with your original copy) and then flash on command line to reduce complications. With the TX2 in recovery mode and in the “Linux_for_Tegra/” directory (this adds logging):
sudo ./ -r jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt

If there is still a failure, then you could attach log_flash.txt to the forum.

Beware that all of those non-rootfs partitions (other than the bootloader itself) are mostly equivalent to a PC’s CMOS BIOS. There is no BIOS in embedded systems, and if you mix those other partitions incorrectly, then boot will fail.

Many thanks for the reply.
I am trying with your guide.
I am searching about TX2 Module but i couldn’t find any information.
Is there any difference between recent one and old one?

log_flash.txt (23.8 KB)

as following the version of L4T release as below.
head -n 1 nv_tegra_release

R28 (release), REVISION: 2.1, GCID: 11272647, BOARD: t186ref, EABI: aarch64, DATE: Thu May 17 07:29:06 UTC 2018

sudo ./ -r jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt

i tried and it still didn’t work.
is there any other way i could do?

You have L4T R28.2.1, which is rather old, but was a reasonably high quality release. Are the reused image and software tool used to flash the clone image all R28.2.1? If they are different releases some boot files will be incompatible. However, this still would not explain the flash log.

The log shows the flash started normally and ran without error, then just stops like it locked up. The release version of the flash software would not matter for this, so something other than the release version is at issue. However, one of the first things anyone will ask is if you can try a more current version? Whatever is going on might work with a newer release. Are you forced to stick with R28.2.1?

FYI, here are URLs for listings of JetPack versions and L4T versions (L4T is what JetPack installs):

Please compare the info (e.g. sticker) on the module and see what is the # of recent TX2 module.

There are some PCN update on the download center. Maybe you can check that info too.