TX2 module differences in R32.4.4

Hello~
I have two TX2, P/N 135-0807-001 R2 and 135-0807-002 R1, and use L4T R32.4.4.
But when I use “fdisk -l”, I get different partition size.

P/N 135-0807-002 R1

    Disk /dev/mmcblk0boot1: 8 MiB, 8388608 bytes, 16384 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk /dev/mmcblk0boot0: 8 MiB, 8388608 bytes, 16384 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

P/N 135-0807-001 R2

    Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

I need to use new partition “UBENV” to save the uboot environment, so I want to know what’s the difference between these two TX2.
Thanks in advance.

hello yihsi0909,

there’re three different TX2 modules. please check Jetson Modules and please also refer to technical specifications for details.
you may also check Jetson TX2 Developer Kit User Guide for different developer kit carrier boards (i.e. revision B02, B04, and C02)
thanks

@JerryChang
I can’t find relevant information.
Both of these modules are TX2, but has changed DRAM & eMMC.

hello yihsi0909,

please dump the eeprom information of your TX2 platform.
for example, $ sudo i2cdump -f -y 7 0x50 b
according to the information, 699-83310-1000-B02 as shown below, it’s revision B02.

nvidia@tegra-ubuntu:~$ sudo i2cdump -f -y 7 0x50 b
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 0d 00 ee 0c e8 03 42 41 00 00 00 00 00 00    ?.?.????BA......
10: 00 00 00 00 36 39 39 2d 38 33 33 31 30 2d 31 30    ....699-83310-10
20: 30 30 2d 42 30 32 20 41 2e 30 00 00 00 00 00 00    00-B02 A.0......
...

Hello @JerryChang

P/N 135-0807-002 R1 is 699-83310-1000-D02 D.0
P/N 135-0807-001 R2 is 699-83310-1000-D00 E.0

Hi,

Please also search the “PCN” in our download center. It will record the hardware change on each module.

Hi @WayneWWW

I can’t find the reason for the partition difference from Jetson_TX2_PCN_206440_DRAMeMMC_Public.pdf.

Are you sure both devices are TX2 modules with rel-32.4.4?

Hi @WayneWWW

Yes, I’m sure.

Hi @JerryChang @WayneWWW
Is there any solution for this problem?
Thank in advance!

We are still checking this internally.

Looks like this issue is due to different emmc EXT_CSD (Extended Card-Specific Data). The software driver has nothing to do with this. I mean different emmc may have different card data and cause different boot partition size.

I have a similar problem. With the replacement to 135-0807-002 R1, our build system based on the very old JetPack stopped working.
We’re stuck in the R28 and wouldn’t want to change anything. We have made many changes to the base image and do not find the strength to repeat it on the new JetPack.

flash log: full.txt (168.9 KB)

Jetson_TX2_PCN_206440_DRAMeMMC_Public.pdf

I read PCN. But I thinking how we can integrate changes into our build system (backports)

The PCN also provides rel-28.4 version for new modules. Please try them to confirm your module can be flashed or not.

As for the original issue, the bootloader will change the CONFIG_ENV_OFFSET according to the EXT_CSD from emmc.
Solution will be ready in next release.

Tegra186_Linux_R28.4.0_aarch64.tbz2

I download R28.4 and replaced my old ‘bootloader’ directory, files ‘flash.sh’ and *.conf files from the root of the archive. And it is works!

1 Like