Degraded performance on new Xavier NX 8GB 900-83668-0000-000 affected by PCN206980

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
, ,
24

The logs we discussed.
48B02D7A8D56-flash-uart.zip (9.9 KB)
48B02D7A8D56-mass-flash-uart.zip (10.0 KB)

RAM code doesn’t seem to be different (0x1 in each case) but the EMC device tree doesn’t seem to be loaded properly.

image
image1866×377 48.7 KB

25

Ok. Can I double confirm now if you can see the performance drop right on this mass flash module?

26

I can confirm that I see it.

27

Could you share your steps to do massflash?

28

First I generate the nvmflash.sh script with this command

sudo BOARDID=3668 BOARDSKU=0001 FAB=100 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

I decompress the generated mfi_jetson-xavier-nx-devkit-emmc.tbz2 file

I am putting the board to recovery mode.

Then I run sudo ./nvmflash.sh to flash.

29

Hi dimitris_akridas,

We’re using below steps to flash image, the result looks good without issue.

$ sudo BOARDID=3668 BOARDSKU=0001 FAB=301 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
$ tar xpvf mfi_jetson-xavier-nx-devkit-emmc.tbz2 
$ cd mfi_jetson-xavier-nx-devkit-emmc/
$ sudo ./nvmflash.sh --showlogs

You can use flash.sh command to get your board info like below:
Board ID(3668) version(301) sku(0001) revision(A.0)
Then use the correct board info to the nvmassflashgen.sh flash command.

30

Can you please give more specific guidance on how to get the board info using flash.sh command ?

31

Hi,

Our point is your FAB given in massflash is wrong.

32

So using the flash.sh, I am getting this info

for the non working module

Board ID(3668) version(301) sku(0001) revision(G.0)

For the working module

Board ID(3668) version(300) sku(0001) revision(B.0)

Does that mean that FAB should be 301 and 300 for each board accordingly ?

33

You can try and validate that first.

34

Generating mass flash script with the following command and FAB → 301, for the non working module fixes the problem

sudo BOARDID=3668 BOARDSKU=0001 FAB=301 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

SOC family:tegra194 Machine:NVIDIA Jetson Xavier NX Developer Kit
Online CPUs: 0-5
cpu0: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
cpu1: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
cpu2: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
cpu3: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
cpu4: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
cpu5: Online=1 Governor=schedutil MinFreq=1420800 MaxFreq=1420800 CurrentFreq=1420800 IdleStates: C1=0 c6=0
GPU MinFreq=1109250000 MaxFreq=1109250000 CurrentFreq=1109250000
EMC MinFreq=204000000 MaxFreq=1600000000 CurrentFreq=1600000000 FreqOverride=1
Fan: PWM=160
NV Power Mode: MODE_15W_6CORE

Thanks for the help.

May I ask, is there any official documentation to compare the different board versions ? 100 vs 300 vs 301 ?

35

Hi,
There is some information in
Jetson EEPROM Layout — Jetson Linux Developer Guide documentation

It is to identify minor deviation between the modules. Please read the information from eeprom of the modules. And set it correctly in the commands. To ensure correct DRAM setting is used for the modules.

37

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.