Bootburn Usage

-b <board_name>

(lowercase b)

Provides the board name. Possible board names include:

• p3710-10-a01
• p3710-10-a01-f1
• p4024-a00-a
• p4024-a00-a-f1
• p4024-a00-b
• p4024-a00-b-f1
• p3898-b00

See Section 1.0 of the Release Notes for your release to confirm your board and revision information.

For more information, see Supported Platforms/PCTs and SDK/PDK Packages under API Modules.

Can be used with bootburn.py, create_bsp_images.py, and flash_bsp_images.py board_name must include absolute path.

-d <partition_name> <dtb_file>

(lowercase 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.

This option does not need the encryption key to be passed.

Either the -encrypt or --encryption_key option can be used with bootburn.py and create_bsp_images.py.

Additionally, edit drive-foundation/tools/flashtools/flash/tegrasign_v3_oemkey.yaml or drive-foundation-safety/tools/flashtools/flash/tegrasign_v3_oemkey.yaml.

"AES" : {
"SBK" :
{
"IV" : OEM_FUSE_IV,
"Manifest" : "10860000",
"Offset" : "0d01",
#"Plain" : "63979cd900154cfaedc539cd17572387296058fe988013c055be99bfd8db41f9",
"Plain" : "753aafbeab213322ef0f8cecc805d1b086e252953dfb3cac215a778f68cb5a72",
#"Plain" : "0000000000000000000000000000000000000000000000000000000000000000",

(#) denotes a comment in yaml files.

Add the key that is needed in the yaml file as follows:

"Plain" : "<key>"

Where <key> is the hexidecimal value of the key. There are some standard SBK (Secure Boot Keys), so you may be able to uncomment the key. Make sure that all SBK entries are commented out (#) except for the one in use.

--encryption_key (obsolete)

Takes as parameter the full file path and name. Secure boot encryption key.

See the description of the -encrypt option.

-h

(lowercase h)

-k <configuration file>

(lowercase k)

-o

(lowercase 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>

(lowercase p)

Can be used with bootburn.py and create_bsp_images.py. Tells Bootburn what keys will be used in HSM mode. Key String is Key + Encrypt Keys. Key is rsa|eddsa. Encrypt Keys are sbk or kek0. Examples:

--hsm rsa

--hsm rsa+sbk

--hsm eddsa

--hsm eddsa+sbk

-q

(lowercase q)

-s

(lowercase s)

Skips flashing the file system.

Use the -s flag only when the target file system is already flashed.

-t <output_directory>

(lowercase t)

-u <partition_name ...>

(lowercase u)

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 p3710 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.

-B <boot_device>

(upper-case B)

-C

(upper-case C)

-D

(upper-case D)

-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)

-M

(upper-case M)

-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)

-V

(upper case V)

Specified customer data such as skuinfo and others to be updated during flashing

See flashing_customer_data.docx for information on how to use it.

verified memory cfg from mem-qual (Mission Mode)