Flashing the Board

Note:

For convenience during flashing, the information in this chapter has been duplicated from the OS-agnostic chapter in Foundation 5.0 SDK Development Guide.

Options	Description
-a	Flashes Android images.
-b <p3407-t186\|p2379c01-t186a\|p2379c01-t186b>	Provides the board name and revision. Flashes QNX IFS. See Section 1.0 of the Release Notes for your release to confirm your board and revision information.
-d <partition_name> <dtb_file>	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.
-e <emulation_target>	Specifies the target board for emulation. Valid emulation targets are: reilly, ohara-gfx, ohara-compute, drew-gfx, and drew-compute.
-h	Provides guidance on the actions and options of bootburn.
-l	Flashes Linux images.
-o	Skips flashing of recovery partitions.
-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	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>	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.
-u <partition_name1> <partition_name2> … (lower-case u)	Updates the partition name(s) and does not write anything else. Partitions bct, mb1-bootloader (-r), and pt cannot be updated using this option. A guest partition’s partition name includes a prefix that indicates the guest ID, e.g. the kernel DTB partition of guest 1 is 1_kernel-dtb. To update a rebuilt kernel, use this option instead of the default bootburn command, which updates all the partitions of the boot medium (NOR): 1. Back up the original kernel binaries’ Image and zImage files. 2. Copy the updated Image and zImage files to the directory: <top>/drive-t186ref-linux/kernel-rt_patches 3. Enter this command to update the partition: ./bootburn.sh -b <p3407-t186\|p2379c01-t186a\|p2379c01-t186b> -u kernel 4. To identify the partition name, consult the configuration file used for flashing.
-x <aurix_port>	Specify the AURIX port for putting the Tegra devices in recovery and booting them after successfully flashing them. Valid only for NVIDIA DRIVE PX 2 systems. For example: -x /dev/ttyUSB1
-z <board_info>-	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 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>	Specifies the boot device, which must be either qspi (the default) or emmc.
-C (upper-case C)	Specifies use of debug binaries for the boot loader.
-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	Enables DRAM ECC.
-G	Flashes Integrity images.
-H	Flashes the Hypervisor image (the default).
-I <bus_id> <device_id>	Flashes a specific Tegra device when multiple devices are in recovery. To get the bus and device ID of each Tegra 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 Tegra device with the -I option as in this example: -I 003 104
-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	Specifies development version firmware.
-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.
-S (upper case S)	Skips confirmation prompts from bootburn, as if “y” is selected for each prompt.
-T	Enables tracing. Tracing logs are stored under the bootburn directory as log_trace*.txt.
-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.

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

Note:

Prior to executing bootburn.sh first move to its location with the following command:

cd drive-t186ref-foundation/tools/host/flashtools/bootburn

Note:

When Ubuntu 14.04 or 16.04 LTS is used for the host PC for flashing, when DRIVE PX 2 is placed in recovery mode and flashed messages similar to the following appear:

Unable to mount FunctionFS gadget (adb)
Unable to open MTP device '[usb:001,050]'

This is due to gvfs-mtp-volume-monitor server trying to mount the ADB device using the MTP protocol. Since MTP is not used for flashing, this message can be ignored.

Issue the following command to kill the server to prevent the popup from occuring again:

sudo killall gvfs-mtp-volume-monitor

Note:

Prior ADB configurations (e.g., ADB server running, ADB aliases with paths) may interfere with the Bootburn shell and cause it to fail with USB errors. Running bootburn.sh with bash -x reveals these issues.

Note:

A keyfile is also created during the first boot with 32-byte random vector from /dev/urandom, accessible only by kernel.

Suppose the TZ call to get passphrase is not supported on some platform, it uses the passphrase in the keyfile as a secondary/backup option for the initial passphrase. The keyfile is stored in the usr partition of the root-file system.