Trying to flash Jetson Xavier NX fails - bad module?

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
1

I have a new Jetson Xavier NX that I have been trying to flash. Followed the instructions from the manufacturer of the carrier board and tried autoflash. Error is always:

[   3.1620 ] MB2 Applet version 01.00.0000
Board ID(3668) version(302) sku(0001) revision(B.0)
lz4c installed at /usr/bin/lz4c
Compressing /home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/tegra194-a02-bpmp-p3668-a00.dtb ...
Copy /home/dayd/AD-board/Linux_for_Tegra/kernel/dtb/tegra194-p3668-0001-p3509-0000.dtb to /home/dayd/AD-board/Linux_for_Tegra/kernel/dtb/tegra194-p3668-0001-p3509-0000.dtb.rec
NVDISP+UEFI in bootloader/nvdisp-init.bin ..
copying bctfile(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-memcfg-p3668-0001-a00.cfg)... done.
copying bctfile1(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-memcfg-sw-override.cfg)... done.
copying minratchet_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-ratchet-p3668.cfg)... done.
copying device_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-bct-device-qspi-p3668.cfg)... done.
copying misc_cold_boot_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-l4t.cfg)... done.
copying misc_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-flash.cfg)... done.
copying pinmux_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-pinmux-p3668-a01.cfg)... done.
copying gpioint_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg)... done.
copying pmic_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-pmic-p3668-0001-a00.cfg)... done.
copying pmc_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-padvoltage-p3668-a01.cfg)... done.
copying prod_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-prod-p3668-0001-a00.cfg)... done.
copying scr_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying scr_cold_boot_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying bootrom_config(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-reset-p3668-0001-a00.cfg)... done.
copying dev_params(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-br-bct-qspi-l4t.cfg)... done.
copying dev_params_b(/home/dayd/AD-board/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-br-bct_b-qspi-l4t.cfg)... done.
Existing bootloader(/home/dayd/AD-board/Linux_for_Tegra/bootloader/nvtboot_cpu_t194.bin) reused.
copying initrd(/home/dayd/AD-board/Linux_for_Tegra/bootloader/l4t_initrd.img)... done.
bl is uefi
Making Boot image... done.
Not signing of boot.img
Making recovery ramdisk for recovery image...
Re-generating recovery ramdisk for recovery image...
/home/dayd/AD-board/Linux_for_Tegra/bootloader/ramdisk_tmp /home/dayd/AD-board/Linux_for_Tegra/bootloader /home/dayd/AD-board/Linux_for_Tegra
41966 blocks

gzip: /home/dayd/AD-board/Linux_for_Tegra/kernel/Image: not in gzip format
_BASE_KERNEL_VERSION=5.10.104-tegra
command is failed
*** ERROR: flashing failed.

Does this mean I have a bad module and need to contact the supplier? Purchased through arrow.

2

Actually the log you shared does not mean anything here.

Is this a custom board or devkit? Which jetpack version are you trying here? Could you share full flash log since the flash command is entering?

3

Since this is not an NVidia carrier board only the manufacturer of your carrier board can help you.

Of course your setup checks all the usual boxes, i.e. correct Ubuntu Linux version, no virtualisation (must be a real Ubuntu PC, no WSL or VMWare/VirtualBox/…) etc etc.

4

@WayneWWW unfortunately, that was all that was being spit out from the terminal. The console on the other USB port just said that it was in recovery mode with even less info… But

@fchkjwlsq - I was trying to run out of a docker. I have used Orin AGX / drive that way very successfully - in fact, I think that is recommended for that platform. That was my mistake. I had the bright idea to try a full blown Ubuntu VM and some USB redirects ( because I can’t stomach .Deb based distro on my daily driver ) - and it worked. My guess is since I compile my own kernel, I probably missed an option that comes with the stock Ubuntu kernel. Unfortunately - I can’t figure out what option I may have missed based on this output. I suppose I could dump kernel configs and compare, but doesn’t matter. I was just trying to make sure my SoM wasn’t busted - it isn’t - I get a session when I connect an HDMI monitor, etc.

5

This is definitely not true as I’ve been flashed Jetson for like years. I know what a full log on your host would be like.

What I was trying to say is there must be logs before these lines that you shard

[ 3.1620 ] MB2 Applet version 01.00.0000
Board ID(3668) version(302) sku(0001) revision(B.0

You should share the log before these lines too. If you don’t see anything, it means how you dumped the log has some problem that makes you unable to see early log.

6

Also, what @fchkjwlsq said is correct, if this is custom board, we don’t guarantee sdkmanager would work on it. You should check with board vendor.

7

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