NVIDIA DRIVE 5.0 Foundation SDK

Development Guide Release

Flashing Preprocessed Binaries (Tegra Parker)
Directory Structure of Preprocessed Binaries
Flashing the Prebuilt Binaries
Flashing SKUInfo
Flashing Flow
Applies to: This topic applies to platforms with NVIDIA® Tegra® code-name Parker.
This section describes how to flash prebuilt binaries that create_bsp_images.sh generated. Such binaries are generated offline, when the target is disconnected from the host.
The Flash BSP Tool (flash_bsp_image.sh) calls the following scripts:
Flash BSP flashes binaries that are generated offline by create_bsp_tool.sh. For more information, see Offline Generation of Flashing Binaries in the Appendix.
Flash BSP uses the following tools:
For information on the individual flashing tools, see Bootburn: Advanced Concepts in the Appendix.
flash_bsp_images.sh is at:
The following table lists the options flash_bsp_images.sh supports.
Enables debug messages from the Flashing script.
-P <path>
Specifies a directory from which flash_bsp_images.sh picks prebuild binaries. The script does not generate the binaries.
Specifies RCM support. Boots without Flashing Software(BCT is used from Media). Default flash-boot
-V <path>
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.
-b <board_and_rev>
Specifies the board name. The default value is p2382 t186.
Provides guidance on the flash_bsp_images tool options.
Note: flash_bsp_images.sh supports only the options described in this table, which are a subset of the options listed by this -h option. (This -h option lists all options supported by bootburn_lib.sh.)
Skips flashing of recovery partitions.
Applies to: DRIVE CX only.
-u <partition_name>
Update only specified partition.
-z <board_info>
Updates and flashes SKUInfo and other-info. For more information about this option, see Bootburn Options inFlashing the Board.
Directory Structure of Preprocessed Binaries
The Flash BSP tools -P argument specifies the output directory path with the processed binaries.
The examples in this topic assume all images are in the images directory
For flashing, Flash BSP obtains the prebuilt images to flash from:
Where the values of <SKUInfo> and <SKUVersion> are as specified in section 1.0 of the Release Notes.
For example:
$ ls images
The following subdirectories are present in the images/<SKUInfo> directory:
For example:
$ ls images/699-62382-1010-100_BB/
flash-images rcm-boot rcm-flash
These directories contain different binaries that are used at different phases in flashing. For more information about these binaries, see Offline Generation of Flashing Binaries in the Appendix.
Flashing the Prebuilt Binaries
To flash the prebuilt binaries
1. Connect the target to host PC and put target in recovery.
2. Flash the binaries to the target. For example:
$ ./flash_bsp_images.sh -P ${PWD}/images/699-62382-1010-100_BB/ -b p2382-t186
Because this command omits the -z option, the Flash BSP tool reads SKUInfo from the target and preserves it in the BCT.
Flashing SKUInfo
The sub directory name under the output directory (images in this example) is very important because it contains SKUInfo. Flash BSP parses SKUInfo to obtain platform detail.
Flash BSP tools also accepts the -z option with arguments to fill SKUInfo in BR-BCT file. The same BR_BCT file (with SKUInfo passed with -z ) is updated to target.
To flash SKUInfo and the prebuilt binaries
1. Connect the target to host PC and put target in recovery.
2. Flash the binaries to the target. For example:
$ ./flash_bsp_images.sh -P images/699-62382-1010-100_BB/ -b p2382-t186 -z "--skunum 699-62382-1010-100 --setskuversion BB --setboardserial 1234 --setmacid eth0 0x00044b52f69b --setprodinfo 699-62382-1010-100 JJ"
The original copy of BCT SKUInfo is modified after flash_bsp.sh executes.
Flashing Flow
The flashing flow of Flash BSP is similar to the Bootburn flow except that Flash BSP does not generate binaries. For information on the Bootburn flow, see Bootburn: Advanced Concepts in theAppendix.