Bootburn Usage

Use the Bootburn utility to flash platform boards with the boot loader, kernel, and file system. The Bootburn utility is provided as part of the Foundation package.

Bootburn

Bootburn is a shell script that:
Boots the device in the recovery-mode with RAMDisk
Signs or generates the images on the host
Transfers the images to target using ADB
Flashes the boards
Bootburn automatically resizes the rootfs image on the target to optimize the available storage on the partition dedicated to it, either on eMMC or NOR.
Bootburn supports a host NFS share as the mount point for the target rootfs. This feature provides a convenient way for developers to copy files between the target and host for rapid development. In this case, the uncompressed target rootfs directory on the host is leveraged directly by the target.
Bootburn relies on the Foundation services to provide the flashing and boot loader functionality. You configure it with the CFG file rather than with Bootburn command-line parameters; Bootburn supports limited command line options.

Bootburn Command Usage

Run the bootburn.sh script from a shell on your host Linux system by executing the command:
./bootburn.sh <options>

Bootburn Options

The supported options are as follows.
Options
Description
-b <e3550a01-t186a | e3550a01-t186b | e3550a03-t186a | e3550a03-t186b>
(lower-case b)
Provides the board name and revision. Possible board names include:
e3550xxx-t194a : Xavier A
e3550xxx-t194b : Xavier B
e3550xxx-t194ia : IVI SKU Xavier A
p3479a01-t194 - Xavier-AD SKU
p3479a04-t194 - Xavier-AD SKU
p3479a04-t194ad125 - Xavier-AD 125 SKU
Where xxx is the board revision, which can be b01 or b03 based on the e3550 board revision. See Section 1.0 of the Release Notes for your release to confirm your board and revision information.
Not all boards are supported in Safety and Standard. For more information, see Supported Platforms/PCTs and SDK/PDK Packages.
--board_config <board_name>.json
Can be used with bootburn.sh, create_bsp_images.sh, and flash_bsp_images.sh.
-d <partition_name> <dtb_file>
(lower-case d)
Specifies the DTB file to flash and the target partition. The default file is defined in BoardSetFilePathsAndDefaultValues.
bpmp-fw-dtb and kernel-dtb may be specified simultaneously.
Note: This option is not intended to specify kernel-dtb in Hypervisor.
--encryption_key
Takes as parameter the full file path and name. Secure boot encryption key. Can be used with bootburn.sh and create_bsp_images.sh.
-f (lower case)
Failure analysis (FA) mode support.
--gpuvbios_fw
Specifies the firmware to flash to the dGPU.
-h
(lower-case h)
Provides guidance on the actions and options of bootburn.
-i (lower case i)
File path to platform configuration file. If not provided for hypervisor configurations, then the tool expects the platform configuration file to be present in the hypervisor output directory
-k <configuration file>
(lower-case k)
Specifies the configuration file for flashing.
-m (lower case)
Flashing Modular Diagnostic Software (MODS). This option enables mods-specific overrides.
-o
(lower-case o)
Skips flashing of recovery partitions. Used by minicom.
WARNING: If you are using minicom with -o option, minicom does not initialize the port and therefore does NOT check or acquire the lock files for the communication port. If minicom is running in the background and you run bootburn with the -x option, bootburn acquires the lock BEFORE accessing the communication port. So, when bootburn attempts to communicate with AURIX it fails.
-p <key_file_path>
(lower-case p)
Signs the boot loader, secure OS (TOS), kernel and BCT binary, then flashes the device. <key_file_path> must be the full pathname of the key_file.
-q
(lower-case q)
Flashes QNX images.
-s
(lower-case s)
Skips flashing the file system.
Use the -s flag only when the target file system is already flashed.
-t <output_directory>
(lower-case t)
Specifies the output directory where images to be flashed onto the target are to be stored. The default directory is named _temp_dump, and is present in the flashing directory.
-x
Specifies the communication port for AURIX to put the SoC in recovery mode automatically.
With this -x option, bootburn performs target validation for the user provided board name on the command line, with the -b option, before flashing the board.
Bootburn generates a unique ID from the target Inforom data. The allowed target ID list for the user provided board is generated from BOM data file included in the package. Bootburn aborts flashing if the target unique ID is not found in the list of generated unique IDs for the provided board name. This feature is supported on e3550b01 and e3550b03 boards with Inforom system object version 3 or above.
Note: On boards with inforom, the bct sku info is updated with the information in the inforom.
If the -x option is used during the AURIX setup, at the end during the AURIX reset of the flashing procedure there may be output messages of the form: "Killed sudo cat $l_Aurix > $p_FlashFiles/$l_AurixLogFile". These messages are not errors and can be safely ignored.
WARNING: If minicom is used with the -o option, minicom does not initialize the port and therefore does NOT check or acquire the lock files for the communication port.
If minicom is running in the background and you run bootburn with the -x option, bootburn acquires the lock BEFORE accessing the communication port. So when bootburn attempts to communicate with AURIX it fails.
If you quit minicom forcefully it may not fully stop the process and it will be lingering in the background.
When bootburn attempts to connect in this state it will acquire the port but the output will still be directed to the minicom running in the background.
Avoid using the -o option when using minicom.
-z <board_info>-
(lower-case z)
Notes: On boards with inforom, only the bct sku info is updated; inforom sku info is not updated.
Provides the board information options, which include:
--skunum: Specifies the board SKU_Info, such as: 699-62382-0010-100. The label on your board provides the value to use. SKU_Info is mandatory for the –z option.
--setskuversion: Specifies AB. The label on your board provides the value to use. AB is mandatory for the –z option.
--setprodinfo: For example, 600-62379-0100-100 AB. This option is equivalent to --skunum and --setskuversion.
--setboardserial: Specifies the five-digit serial number.
--setmacid mac0 <0xaabbccddeeff>: Specifies a 6‑byte hexadecimal serial number. Make sure when using the –-setmacid option to give every device a unique MAC ID.
The -z sub-options are enclosed in quotes, and must include --skunum and --setskuversion. The other sub-options are optional. If they are provided, they are stored on the target.
For example:
-z "--skunum 699-62382-0010-100 --setskuversion AB --setprodinfo 699-62382-0010-100 AB --setboardserial 00250 --setmacid mac0 0x00504b94df"
-B <boot_device>
(upper-case B)
Specifies the boot device, which must be either qspi or emmc. qspi is the default.
-C
(upper-case C)
Specifies use of debug binaries for the boot loader.
-D
(upper-case D)
Directs bootburn debug output to stdout along with the tool’s regular output. If -D is not specified, debug output goes to a temporary file.
-E
(upper-case E)
Enables DRAM ECC.
-I <bus_id> <device_id>
(upper-case I)
Flashes a specific device when multiple devices are in recovery.
To get the bus and device ID of each device in recovery, enter the lsusb command on the host. For example, if lsusb gives the following output:
Bus 003 Device 105: ID 0955:7018 NVidia Corp.
Bus 003 Device 104: ID 0955:7018 NVidia Corp.
Then flash the second device with the –I option as in this example:
-I 003 104
-L
(upper-case L)
Enables low power modes. This option requires that the spe-fw and WB0 firmware packages be included in the bootburn configuration because low-power modes require them.
-M
(upper-case M)
Specifies development version firmware.
-R
(upper-case R)
Specifies RCM boot support, where the device boots without being flashed. When the target is in recovery mode, this option causes the flashing script to download all binaries, other than BCT, from the host. The target then reads the BCT from storage and other binaries from RAM. It boots the kernel directly on RAM.
This option is much faster than when flashing also occurs. It is especially useful during debugging.
Use the -R flag to initiate RCMBOOT with any of the commands mentioned in this table.
-T
(upper-case T)
Enables tracing. Tracing logs are stored under the bootburn directory as log_trace*.txt.
--safety
Execute bootburn scripts in safety mode. Only a limited set of options are available for use in safety mode.
-U
Pass in the UFS provision configuration file.
-V
(upper case V)
Specifies read-back verification, where the binary images are read back (after writing) from the target’s storage and compared with the original binary images. The two sets of images are compared to detect discrepancies.
-X
(upper case X)
Enable Golden Register Address:Value Dump into GR memory carveout.

Kernel Parameter Combinations

Possible combinations of kernel parameters nfsdev, ip, and nfsroot are as follows. An error indicates that the initramfs shell is started.
nfsdev
ip
nfsroot
Result
(not set)
(not set)
(not set)
no network; root must be set in some other way
(not set)
(not set)
set
error; needs IP configuration
(not set)
set
(not set)
error; no root path to mount
(not set)
set
set
valid combination
set
(not set)
(not set)
valid combination; DHCP request is sent
set
(not set)
set
error; needs IP configuration
set
set
(not set)
error; no root path to mount
set
set
set
valid combination; no DHCP requests

Passing Additional Kernel Parameters

To pass additional kernel parameters, modify the os_args parameter of the kernel-dtb and kernel-dtb-r partitions in this file.
drive-t186ref-foundation/virtualization/pct/<platform>/linux/linux_storage_qspi.cfg
Where <platform> is:
e3550xxxb01-t194a for Xavier A (x1)
e3550xxx-t194b for Xavier B (x2)
e3550xxx-t194ia for IVI SKU Xavier A(x1)
xxx in the above platform name should be replaced with b01 or b03 based on the revision of e3550 board used.
To bind:
cd <top>/drive-t186ref-foundation
make -f Makefile.bind PCT=linux BOARD=<platform>
To flash all images for Linux:
cd <top>/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x
./bootburn.sh -b <platform> -B qspi
To flash kernel-dtb only:
cd <top>/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x
./bootburn.sh -b <platform> -B qspi

Updating the path for the targetfs

To update the path for the targetfs, modify the dirname parameter of the filesystem partition in:
drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/quickboot_qspi_linux_initramfs.cfg
This step applies to the configuration file used for qspi boot, that is, modify dirname in the file that does not have _initramfs in its filename.

Using the targetfs.img file for Linux guest rootfs

Note:
This feature is only supported under Linux AV PCT.
Invoke use_rootfs_img.sh to use the targetfs.img file as Linux AV guest rootfs instead of the rootfs directory contents under drive-t186ref-linux/targetfs:
cd <top>/drive-t186ref-foundation
./drive-t186ref-foundation/tools/host/use_rootfs_img.sh
Note:
use_rootfs_img.sh does not work when using custom targetfs folders as described in Updating the path for the targetfs.

Dialout Group

Add yourself to the dialout group since it is not possible to open the serial ports to the AURIX via sudo.
To add yourself to the dialout group:
sudo adduser <user name> dialout
You must log out and log back in for the command to take effect.

Bootburn Configuration File

The following is the list of keys that can be added to a JSON file and their meanings.
Name
Description
Default
Used By
Optional
f_NvQbDtbImage
Qb Dtb
 
Quick Boot
N
 
 
 
 
 
f_MB1Pad
Pad Voltage/DPD cfg file
None
Tegrabct_v2
N
f_MB1Pinmux
Pinmux configuration File
None
Tegrabct_v2
N
f_MB1Prod
File containing Prod setting for pinmux
None
Tegrabct_v2
N
f_MB1Pmic
File containing PMIC-Real MMIO/I2C
None
Tegrabct_v2
N
f_MB1Misc
Misc Parameter File
None
Tegrabct_v2
N
f_MB1Softfuses
Soft Fuse Configuration File
None
Tegrabct_v2
N
f_MB1GpioInt
Gpio Interrupt Routing Cfg File
None
Tegrabct_v2
N
f_MB1BootDevice
Device specific Platform Cfg File
None
Tegrabct_v2
N
f_MB1DramECCMisc
ECC Misc Parameter (rcm-flash)
None
Tegrabct_v2
N
f_MB1Scr_mods
SCR configuration file (Mods Version)
None
Tegrabct_v2
Y
f_MB1Scr
SCR configuration file
None
Tegrabct_v2
N
f_MB1FlashingScr
SCR configuration file (rcm-flash)
None
Tegrabct_v2
N
f_MB1MinRatchet
Minimum Ratched Cfg File
None
Tegrabct_v2
N
f_MB1DeviceProd
Device specific Prod cfg File
None
Tegrabct_v2
N
 
 
 
 
 
f_FlashingMB1SdRamParam
verified memory cfg from mem-qual (rcm-mode)
None
sw_memcfg_overlay.pl
N
f_MB1SdRamParam
verified memory cfg from mem-qual (Mission Mode)
 
None
sw_memcfg_overlay.pl
N
f_MB1SdRamParamEcc
Override for f_MB1SdramParam if ECC is enabled
None
sw_memcfg_overlay.pl
N
f_MB1wb0SdRamParam
verified memory cfg from mem-qual for SC7
None
sw_memcfg_overlay.pl
N
f_MB1wb0SdRamParamEcc
Override for f_MB1wb0sdramParam if ECC is enabled
None
sw_memcfg_overlay.pl
N
f_MB1SdRamSwOverride
SW cfg values to be overwritten 'BCT = 0xHEX_VALUE'
None
sw_memcfg_overlay.pl
N
 
 
 
 
 
s_Kernel_Dtb_Variant
Substitution string for Kernel Dtb
None
Dtb Manipulations
If used
f_FlashingDtbImg
RCM Flashing Dtb
None
Dtb Manipulations
N
f_BpmpFwDtb
Bpmp Fw Dtb
None
Dtb Manipulations
N
f_SafeBpmpFwDtb
Bpmp Fw Dtb (Safe Mode)
None
Dtb Manipulations
N
s_BPMP_Dtb_Variant
Substition string for bpmp Dtb
None
Dtb Manipulations
If used
f_FlashingBpmpFwDtb
Flashing Bpmp Fw Dtb
None
Dtb Manipulations
N
f_DtbImg
Guest Os Dtb
None
Dtb Manipulations
N
 
 
None
 
N
f_UFSPhyLaneFile
Uphy lane cfg file (to extract USB lan ID and ownership pair from)
None
Misc
N
s_FuseBypass
FuseByPass File Name
fuse_bypass_t186.bin
Misc
N
n_DramOverride
Does board support ECC
False
Bootburn scripts
Y
 
 
 
 
 
s_GrCsvString
 
None
Used in Golden Registers
Y
s_BoardId
 
None
Used in Golden Registers
Y
S_MediaCombination
 
None
Used in Golden Registers
Y

Example Board Configuration File

The following is an example of a JSON file. You can either use built-in path substitution or full paths names.
The built-in string substitutions are for PDK.
Name
Definition
Default
Value
p_PlatformBCT
 
None
<PdkTop>/platform-config/hardware/nvidia/platform/t19x/automotive/bct
s_VerStr
Tegra Version
a02-
a01- or a02-
l_BootDevice
Boot Device
qspi
Qspi, sdmmc, or ufs
s_DtbImgSuffix
Wrapper for Qnx
“”
For Qnx “-qnxwrap”
p_BCT
 
None
<PdkTop>/platform-config/bct/t19x
p_PlatformCommonBCT
 
None
<PdkTop>/platform-config/hardware/nvidia/platform/t19x/common/bct
e3550b01-t194a
{
"f_NvQbDtbImage":"t19x-refs.dtb",
"f_MB1Pad":"<p_PlatformBCT>/e3550/padvoltage/tegra194-mb1-padvoltage-e3550-0001-b01.cfg",
"f_MB1Pinmux":"<p_PlatformBCT>/e3550/pinmux/tegra194-mb1-bct-pinmux-gpio-e3550-0001-b01-ta.cfg",
"f_MB1Prod":"<p_PlatformBCT>/e3550/prod/tegra194-mb1-bct-prod-e3550-0001-b01-ta.cfg",
"f_MB1Pmic":"<p_PlatformBCT>/e3550/pmic/tegra194-mb1-bct-pmic-e3550-0001-b01.cfg",
"f_MB1Misc":"<p_BCT>/misc/tegra194-mb1-bct-misc-auto.cfg",
"f_MB1Softfuses":"<p_BCT>/softfuses/tegra194-mb1-soft-fuses-safety.cfg",
"f_MB1GpioInt":"<p_PlatformBCT>/common/gpioint/tegra194-mb1-bct-gpioint-e3550-0001-b01.cfg",
"f_MB1BootDevice":"<p_PlatformBCT>/e3550/device/tegra194-mb1-bct-device-<l_BootDevice>-e3550-0001-b01.cfg",
"f_FlashingMB1SdRamParam":"<p_PlatformBCT>/e3550/sdram/E3550_B01_XA_32GB_2x_refresh_Micron_32Gb_lpddr4x_204Mhz.cfg",
"f_MB1SdRamParam":"<p_PlatformBCT>/e3550/sdram/E3550_B01_XA_32GB_2x_refresh_Micron_32Gb_lpddr4x_EARLYBOOT_665.6Mhz.cfg",
"f_MB1SdRamParamEcc":"<p_PlatformBCT>/e3550/sdram/E3550_B01_XA_32GB_2x_refresh_Micron_32Gb_lpddr4x_EARLYBOOT_665.6Mhz_ECC.cfg",
"f_MB1wb0SdRamParam":"<p_PlatformBCT>/e3550/sdram/E3550_B01_XA_32GB_2x_refresh_Micron_32Gb_lpddr4x_204Mhz.cfg",
"f_MB1wb0SdRamParamEcc":"<p_PlatformBCT>/e3550/sdram/E3550_B01_XA_32GB_2x_refresh_Micron_32Gb_lpddr4x_204Mhz_ECC.cfg",
"f_MB1DramECCMisc":"<p_BCT>/misc/tegra194-mb1-bct-misc-dram-ecc.sub.cfg",
"f_MB1SdRamSwOverride":"<p_BCT>/misc/tegra194-memcfg-sw-override-auto.cfg",
"f_MB1Scr_mods":"<p_PlatformBCT>/../../common/bct/scr/tegra194-mb1-bct-scr-cbb-mods.cfg",
"f_MB1Scr":"<p_PlatformBCT>/../../common/bct/scr/tegra194-mb1-bct-scr-cbb-mini.cfg",
"f_MB1FlashingScr":"<p_PlatformBCT>/../../common/bct/scr/tegra194-mb1-bct-scr-cbb-mods.cfg",
"s_Kernel_Dtb_Variant":"e3550-0001-b01-A",
"f_DtbImg":"tegra194-e3550-0001-b01-A<s_DtbImgSuffix>.dtb",
"f_FlashingDtbImg":"tegra194-e3550-0001-b01-A-flashing-base.dtb",
"f_BpmpFwDtb":"tegra194-<s_VerStr>bpmp-e3550-0001-b01-A.dtb",
"f_SafeBpmpFwDtb":"tegra194-<s_VerStr>safe-bpmp-e3550-0001-b01-A.dtb",
"s_BPMP_Dtb_Variant":"<s_VerStr>bpmp-e3550-0001-b01-A",
"f_FlashingBpmpFwDtb":"tegra194-<s_VerStr>bpmp-e3550-0001-b01-A.dtb",
"f_UFSPhyLaneFile":"<p_PlatformCommonBCT>/uphy-lane/tegra194-mb1-bct-uphy-lane-ufs-x2.cfg",
"s_FuseBypass":"fuse_bypass_t194.bin",
"s_GrCsvString":"E3550-XA",
"s_BoardId":"b01",
"f_MB1MinRatchet":"<p_PlatformBCT>/common/ratchet/tegra194-mb1-bct-ratchet.cfg",
"f_MB1DeviceProd":"<p_PlatformBCT>/e3550/deviceprod/tegra194-mb1-bct-deviceprod-e3550-0001-b01.cfg"
}
}

Example of Successful Flash

Bootburn completed successfully!
 
Bootburn Time 505.16470408439636 seconds
 
returning to directory /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py
Cleaning up ...
Cleaning temp dir

Example of Unsuccessful Flash

 
------------ Stack Trace ------------
stack frame 0 : PrintStackTrace(234) in /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/flashtools_nverror.py
 
stack frame 1 : AbnormalTermination(250) in /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/flashtools_nverror.py
 
stack frame 2 : GenerateImage(1791) in /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/bootburn_lib.py
 
stack frame 3 : CreateFlashImages(1926) in /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/bootburn_lib.py
 
stack frame 4 : bootburn_active(94) in ./bootburn.py
 
stack frame 5 : run(93) in /usr/lib/python3.4/multiprocessing/process.py
 
stack frame 6 : _bootstrap(254) in /usr/lib/python3.4/multiprocessing/process.py
 
stack frame 7 : _launch(77) in /usr/lib/python3.4/multiprocessing/popen_fork.py
 
stack frame 8 : __init__(21) in /usr/lib/python3.4/multiprocessing/popen_fork.py
 
stack frame 9 : _Popen(267) in /usr/lib/python3.4/multiprocessing/context.py
 
stack frame 10 : _Popen(212) in /usr/lib/python3.4/multiprocessing/context.py
 
stack frame 11 : start(105) in /usr/lib/python3.4/multiprocessing/process.py
 
stack frame 12 : bootburn(280) in ./bootburn.py
 
stack frame 13 : bootburnCommandLine(355) in ./bootburn.py
 
stack frame 14 : <module>(359) in ./bootburn.py
 
-------------------------------------
 
s_ERROR_TOOL_NVIMAGEGEN
 
ERROR CODE = 53
s_ERROR_TOOL_NVIMAGEGEN
Exception raised in bootburn_active
Traceback (most recent call last):
File "./bootburn.py", line 94, in bootburn_active
bootburnLib.CreateFlashImages(targetConfig.f_FlashCfg)
File "/media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/bootburn_lib.py", line 1926, in CreateFlashImages
self.GenerateImage(configFiles, l_Operation, p_TempDumpPath)
File "/media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/bootburn_lib.py", line 1791, in GenerateImage
AbnormalTermination("s_ERROR_TOOL_NVIMAGEGEN", nverror.NvError_NvImagegen)
File "/media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py/flashtools_nverror.py", line 258, in AbnormalTermination
raise OSError(errorCode)
OSError: 53
 
returning to directory /media/home/t186-dev-main-1201/foundation/embedded/tools-t19x/scripts/t194_bootburn_py
Cleaning up ...
Cleaning temp dir

Decoding Errors

Additional information is needed to fully determine the cause of some errors. That information can be found in the log files. The command executed determines the name of the log file (bootburn.txt, bootburnTegra-A.txt, BootburnTegra-B.txt, create_bsp.txt, or flash_bsp.txt). in the _t194_bootburn_py folder.
Error Name
Numeric Value
Meaning
Most Likely Cause
NvError_NotSupported
2
Context Specific
Consult log for more details
NvError_NotInitialized
3
Incorrect setting of environmental variables
Consult log for more details
NvError_BadParameter
4
Either unknown parameter or incorrect use of options
Context Specific
NvError_Timeout
5
Timeout conditions waiting for a system event
Consult log for more details
NvError_InvalidSize
10
bad Parition Size
Missing file or invalid cfg
NvError_ResourceError
15
Can't connect to Aurix Port
Consult log for more details
NvError_BomDataBoardMapFileNotFound
37
Board Bom Data File not Found
Missing Data File
NvError_TargetValidationFail
38
Aurix Validation Failed
Consult log for more details
NvError_TegraBctError
49
Call to Nvtegrabct_v2 failed
Consult log for more details
NvError_TegraRcmError
50
tegrarcm_v2 failed
Consult log for more details
NvError_TegraSkuInfoError
51
Nvskuinfo return an error
Consult log for more details
NvError_TegraSignError
52
Tegrasign failed to sign
Bad key or missing file
NvError_ImageMismatch
53
Must use Debug if using Virtual Box
User error
NvError_NvImagegen
53
NvImagegen has failed
Consult log for more details
NvError_DeviceFailToBoot
54
Attempt to read Target uid failed
Consult log for more details
NvError_SystemCommand
55
Shell Command Failed
Consult log for more details
NvError_RatchetConfigNotFound
56
Ratchet Tool is not found
Invalid Configuration
NvError_AdbShell
59
Target side shell script failed
Consult log for more details
NvError_Adb
60
Adb Operation Failed
Consult log for more details
NvError_Bad_MD5
62
Md5 Checksum Failed
Device has corrupted data
NvError_FileOperationFailed
196,611
Various Failures of Linux File Operations
Consult log for more details
NvError_DirOperationFailed
196,612
Missing Directory need
Consult log for more details
NvError_ConfigVarNotFound
196,614
Missing file
Consult log for more details
NvError_InvalidConfigVar
196,615
Sku Info not set or Low Power cfg issue
Consult log for more details
NvError_DeviceNotFound
196,625
Requested Device can't be found
Device not found
NvError_FileNotFound
196,627
Missing File
Consult log for more details
NvError_InvalidArgument
196,628
Context Specific
Consult log for more details
NvError_FileNameNotExist
196,631
Missing file
Consult log for more details
NvError_SystemCommandFailed
196,634
System Command Failed
Consult log for more details