Xavier NX with JetPack4.5.1 Fuse issue

We use Xavier NX develop our product.
When production we will write some data into fuse, such as below
Device ID: X0D000NX
secure key: “0x54888a15 0x1acba63b 0x3c5819aa 0xb14745b9 0xd4b97d77”
pkc file: fake-pkc-nx.pem
and also download secureboot_R32.4.3_aarch64 related file to Linux_for_Tegra.

When we use JetPack4.5.1 and burn fuse will cause device restart no any screen output. but use JetPack 4.4.1, 4.4 and 4.3 and burn flash will work properly after restart. Burn fuse operation as below. Is there any one can help to check?

  1. Run fuse patch
    /NX/L4T32.4.3/Linux_for_Tegra$ patch -p1 < …/0001-Fix-issue-burn-odm-reserved-l4t-bsp-secureboot-r32.3.1.patch.log
    patching file odmfuse.sh
    Hunk #1 succeeded at 635 with fuzz 2 (offset 5 lines).
    Hunk #2 succeeded at 1360 (offset 106 lines).
    Hunk #3 succeeded at 1399 (offset 106 lines).
    Hunk #4 succeeded at 1453 with fuzz 2 (offset 106 lines).
    /NX/L4T32.4.3/Linux_for_Tegra$ cd pkc/
    /NX/L4T32.4.3/Linux_for_Tegra/pkc$ patch -p0 < …/…/0002-diplay-tegra-fuses-via-tegrafuse-script.patch.log
    patching file tegrafuse.sh
    NX/L4T32.4.3/Linux_for_Tegra/pkc$

  2. Execute odmfuse.sh and successful
    /NX/L4T32.4.3/Linux_for_Tegra$ sudo BOARDID=2888 FAB=400 BOARDSKU=0001 BOARDREV=H.0 fuselevel=fuselevel_production /NX/L4T32.4.3/Linux_for_Tegra/odmfuse.sh --noburn -j -i 0x19 -c PKC -k /NX/L4T32.4.3/Linux_for_Tegra/fake-pkc-nx.pem -o ‘0xX0D000NX 0x54888a15 0x1acba63b 0x3c5819aa 0xb14745b9 0xd4b97d77 0x208bc913 0x00000000’ -p jetson-xavier-nx-devkit-emmc
    *** Generating fuse configuration … done.
    done.
    *** Start preparing fuse configuration …
    *** done.

  3. Content of burnfuse.sh
    Content of burnfuse.sh
    /NX/L4T32.4.3/Linux_for_Tegra$ cat burnfuses.sh
    #!/bin/bash
    set -e
    CWD=$PWD
    if [ -d /tmp/fuses_tests ]; then
    rm -fr /tmp/fuses_tests
    fi
    mkdir /tmp/fuses_tests
    tar xf fuseblob.tbz2 -C /tmp/fuses_tests
    cd /tmp/fuses_tests/bootloader
    sudo ./fusecmd.sh
    cd $CWD
    rm -fr /tmp/fuses_tests

  4. Execute burnfuse.sh
    /NX/L4T32.4.3/Linux_for_Tegra$ sudo ./burnfuses.sh
    [ 8.2038 ] tegradevflash_v2 --oem burnfuses blow_fuse_data.bin
    [ 8.2057 ] Bootloader version 01.00.0000
    [ 8.3426 ] Fusing burning successful
    [ 8.6365 ]
    [ 8.6385 ] tegradevflash_v2 --reboot recovery
    [ 8.6404 ] Bootloader version 01.00.0000
    [ 8.7592 ]

  5. Image Flash
    /NX/L4T32.4.3/Linux_for_Tegra$ sudo ./flash.sh -u fake-pkc-nx.pem -r jetson-xavier-nx-devkit-emmc mmcblk0p1

  6. Burn fuse with JetPack 4.5.1 will cause no screen output after power on.
    Burn fuse with JetPack 4.4.1, 4.4, 4.3 work properly after power on.
    No burn fuse with etPack 4.5.1 work properly after power on.

hello seanl1,

please check L4T | NVIDIA Developer and download the latest SecureBoot package,
for example, secureboot_R32.5.0_aarch64.tbz2.
thanks

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