Error flashing Jetson Xavier NX from Host Machine

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Training to fix this problem, i’m running sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1 form a host machine.

But this is the output:
sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1

###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.3
###############################################################################
# Target Board Information:
# Name: jetson-xavier-nx-devkit-emmc, Board Family: t186ref, SoC: Tegra 194,
# OpMode: production, Boot Authentication: NS,
###############################################################################
copying soft_fuses(/home/ubuntu/Downloads/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
./tegraflash.py --chip 0x19 --applet "/home/ubuntu/Downloads/Linux_for_Tegra/bootloader/mb1_t194_prod.bin" --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins "mb2_applet nvtboot_applet_t194.bin" --cmd "dump eeprom boardinfo cvm.bin;reboot recovery"
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 
[   0.0015 ] Generating RCM messages
[   0.0021 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /home/ubuntu/Downloads/Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[   0.0027 ] Header already present for /home/ubuntu/Downloads/Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[   0.0054 ]
[   0.0060 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0066 ] Assuming zero filled SBK key
[   0.0067 ] File mode.txt write failed
[   0.0067 ]
Error: Return value 10
Command tegrasign_v2 --key None --getmode mode.txt
Reading board information failed.

The host machine is a ubuntu 18.04 running from a pendrive.

Anyone knows how to solve this problem.

Thanks!

2

I don’t know the meaning of “Return value 10”, but I’m wondering if your host Ubuntu install is read-only, or lacking enough disk space. A lot of live installer distributions lack loopback ability, but you didn’t go far enough into this to need loopback, nor large disk spaces (though read-only would be fatal even here).

This matches read-only as a probably cause:

What do you see from “df -H -T”? What do you see from “cat /etc/mtab”?

3

@linuxdev After installing Ubuntu in other Machine start working find.

Thanks!