Chris Kay
3789c3c000
build: determine toolchain tools dynamically
|
5 months ago | |
|---|---|---|
| .. | ||
| Makefile | 2 months ago | |
| README | 3 years ago | |
| byte_swap.c | 3 years ago | |
| create_pbl.c | 1 year ago | |
| create_pbl.mk | 2 years ago | |
| pbl_ch2.mk | 5 months ago | |
| pbl_ch3.mk | 5 months ago | |
README
Description:
------------
Tool 'create_pbl' is a standalone tool to create the PBL images.
where,
On the basis of Chassis,
RCW image is placed first followed by the,
PBI commands to copy the,
Input BL2 image stored on the,
Specified boot source (QSPI or SD or NOR) to the,
Specified destination address.
Usage in standalone way:
-----------------------
./create_pbl [options] (mentioned below):
-r - name of RCW binary file.
-i - file to be added to rcw file.
-c - SoC numeric identifier, may be one of
1012,1023,1026.1028,
1043,1046,1088,2080,
2088,2160
-b - Boot source id string, may be one of
"qspi", "nor", "nand", "sd", "emmc"
-d - Destination address where BL2
image is to be copied
-o - Name of PBL image generated
as an output of the tool.
-e - [Optional] Entry Point Address
of the BL2.bin
-f - BL2 image offset
on Boot Source for block copy.
command for chassis >=3.)
(Must for Ch3, Ignored for Ch2)
-h Help.
-s Secure boot.
-s secure boot
-c SoC Number (see description above)
-b Boot source.
-r RCW binary file.
-i Input file that is to be added to rcw file.
-o Name of output file
-f Source Offset (Block Copy)
-d Destination address to which file has to be copied
-h Help.
Example:
./create_pbl -r -i -c -b -d -o
Usage at compilation time:
--------------------------------
make pbl RCW=/
Example: QSPI Boot For LS1046ARDB-
make PLAT=ls1046rdb all fip BOOT_MODE=qspi SPD=opteed BL32=tee.bin BL33=u-boot-ls1046.bin pbl RCW=/home/pankaj/flexbuild/packages/firmware/dash-rcw/ls1046ardb/RR_FFSSPPPN_1133_5506/rcw_1600_qspiboot.bin
Example: QSPI Boot For LX2160ARDB-
make PLAT=lx2160ardb all fip BOOT_MODE=flexspi_nor SPD=opteed BL32=tee_lx2.bin BL33=u-boot_lx2160.bin pbl RCW=plat/nxp/soc-lx2160/lx2160ardb/rcw_1900_600_1600_19_5_2.bin
------------
Tool 'create_pbl' is a standalone tool to create the PBL images.
where,
On the basis of Chassis,
RCW image is placed first followed by the,
PBI commands to copy the,
Input BL2 image stored on the,
Specified boot source (QSPI or SD or NOR) to the,
Specified destination address.
Usage in standalone way:
-----------------------
./create_pbl [options] (mentioned below):
-r - name of RCW binary file.
-i - file to be added to rcw file.
-c - SoC numeric identifier, may be one of
1012,1023,1026.1028,
1043,1046,1088,2080,
2088,2160
-b - Boot source id string, may be one of
"qspi", "nor", "nand", "sd", "emmc"
-d - Destination address where BL2
image is to be copied
-o - Name of PBL image generated
as an output of the tool.
-e - [Optional] Entry Point Address
of the BL2.bin
-f - BL2 image offset
on Boot Source for block copy.
command for chassis >=3.)
(Must for Ch3, Ignored for Ch2)
-h Help.
-s Secure boot.
-s secure boot
-c SoC Number (see description above)
-b Boot source.
-r RCW binary file.
-i Input file that is to be added to rcw file.
-o Name of output file
-f Source Offset (Block Copy)
-d Destination address to which file has to be copied
-h Help.
Example:
./create_pbl -r -i -c -b -d -o
Usage at compilation time:
--------------------------------
make pbl RCW=/
Example: QSPI Boot For LS1046ARDB-
make PLAT=ls1046rdb all fip BOOT_MODE=qspi SPD=opteed BL32=tee.bin BL33=u-boot-ls1046.bin pbl RCW=/home/pankaj/flexbuild/packages/firmware/dash-rcw/ls1046ardb/RR_FFSSPPPN_1133_5506/rcw_1600_qspiboot.bin
Example: QSPI Boot For LX2160ARDB-
make PLAT=lx2160ardb all fip BOOT_MODE=flexspi_nor SPD=opteed BL32=tee_lx2.bin BL33=u-boot_lx2160.bin pbl RCW=plat/nxp/soc-lx2160/lx2160ardb/rcw_1900_600_1600_19_5_2.bin