Home
last modified time | relevance | path

Searched refs:boot (Results 1 – 25 of 136) sorted by relevance

123456

/rk3399_ARM-atf/docs/plat/
H A Dwarp7.rst20 We need to use a file generated by u-boot in order to generate a .imx image the
21 BootROM will boot. It is therefore _required_ to build u-boot before TF-A and
22 furthermore it is _recommended_ to use the mkimage in the u-boot/tools directory
28 https://git.linaro.org/landing-teams/working/mbl/u-boot.git
34 make u-boot.imx arch=ARM CROSS_COMPILE=arm-linux-gnueabihf-
53 - u-boot.bin
54 The binary output from the u-boot instructions above
78 BL33=fiptool_images/u-boot.bin certificates all
80 …/path/to/u-boot/tools/mkimage -n /path/to/u-boot/u-boot.cfgout -T imximage -e 0x9df00000 -d ./buil…
87 cp /path/to/uboot/u-boot.bin fiptool_images
[all …]
H A Dbrcm-stingray.rst16 Bootrom --> TF-A BL2 --> TF-A BL31 --> BL33(u-boot)
31 - Build u-boot first, and get the binary image: u-boot.bin,
39 … make CROSS_COMPILE=aarch64-linux-gnu- PLAT=stingray BOARD_CFG=bcm958742t all fip BL33=u-boot.bin
43 The u-boot will be upstreamed soon, this doc will be updated once they are ready, and the link will…
H A Dimx8m.rst15 Bootrom --> SPL --> BL31 --> BL33(u-boot) --> Linux kernel
25 - Build spl and u-boot firstly, and get binary images: u-boot-spl.bin,
26 u-boot-nodtb.bin and dtb for the target board.
44 TF-A binary(bl31.bin), u-boot-spl.bin u-boot-nodtb.bin and dtb are combined
47 with certain offset for BOOT ROM. the u-boot and imx-mkimage will be upstreamed
54 boot sequence to support TBBR.
56 Bootrom --> SPL --> BL2 --> BL31 --> BL33(u-boot with UEFI) --> grub
61 In U-boot we turn on the UEFI secure boot features so it can verify
69 maximum size PLAT_IMX8M_DTO_MAX_SIZE. Then in U-boot we can apply the DTB
70 overlay and let U-boot to parse the event log and update the PCRs.
H A Dimx9.rst16 BootROM --> SPL --> BL31 --> BL33(u-boot) --> Linux kernel
28 - Build SPL and u-boot firstly, and get binary images: u-boot-spl.bin,
29 u-boot.bin and dtb
44 TF-A binary(bl31.bin), u-boot-spl.bin u-boot.bin, ELE FW image are combined
52 Details on how to prepare, generate & deploy the boot image be found in following documents:
H A Dti-k3.rst13 Optional direct to Linux boot
17 Texas Instruments K3 SoCs contain an R5 processor used as the boot master, it
57 cp tiboot3.bin tispl.bin u-boot.img /sdcard/boot/
H A Dimx8ulp.rst25 BootROM --> SPL --> BL31 --> BL33(u-boot) --> Linux kernel
37 - Build SPL and u-boot firstly, and get binary images: u-boot-spl.bin,
38 u-boot.bin and dtb
53 TF-A binary(bl31.bin), u-boot-spl.bin u-boot.bin, ELE FW image are combined
61 Details on how to prepare, generate & deploy the boot image be found in following documents:
H A Dpoplar.rst29 At the start of the boot sequence, the bootROM executes the so called l-loader
35 l-loader --> Trusted Firmware-A --> u-boot
49 - u-boot:
50 `link <http://git.denx.de/u-boot.git>`__
60 - Build u-boot using poplar_defconfig
67 - Build atf providing the previously generated u-boot.bin as the BL33 image
72 BL33=u-boot.bin
88 The system will boot into a u-boot shell which you can then use to write the
102 Entry boot auxiliary code
H A Dimx8.rst25 Bootrom --> BL31 --> BL33(u-boot) --> Linux kernel
35 - Build System Controller Firmware and u-boot firstly, and get binary images: scfw_tcm.bin and u-b…
51 TF-A binary(bl31.bin), scfw_tcm.bin and u-boot.bin are combined together
55 u-boot and imx-mkimage will be upstreamed soon, this doc will be updated
H A Ds32g274a.rst25 This boot flow is a preliminary version that will serve as a foundation for
37 `link <https://github.com/nxp-auto-linux/u-boot>`__
47 available. Consequently, the boot process depends on BootROM to load all TF-A
56 UBOOT="${UBOOT:-${TF_A}/../u-boot}"
73 BL33="${UBOOT}/u-boot-nodtb.bin" DEBUG="${DEBUG}" clean
75 BL33="${UBOOT}/u-boot-nodtb.bin" DEBUG="${DEBUG}" bl2
77 BL33="${UBOOT}/u-boot-nodtb.bin" DEBUG="${DEBUG}" fip
94 -n "${UBOOT}/u-boot-s32.cfgout" \
H A Drpi5.rst28 - ``RPI3_DIRECT_LINUX_BOOT``: Enabled by default. Allows direct boot of the Linux
32 that has been preloaded by earlier boot stages (VPU). Useful for bundling
46 Copy the firmware binary to the first FAT32 partition of a supported boot media
53 For Linux, you must also place an appropriate DTB and kernel in the boot
65 By default, all boot stages print messages to the dedicated UART debug port.
73 The boot process is essentially the same, the only notable difference being that
H A Dmeson-gxl.rst22 Or, if willing to boot from U-Boot SPL (using standard params handling):
33 .. _U-Boot repository: https://github.com/u-boot/u-boot/blob/master/doc/board/amlogic/p212.rst
/rk3399_ARM-atf/docs/plat/arm/fvp-ve/
H A Dindex.rst13 BL1 --> BL2 --> BL32(sp_min) --> BL33(u-boot) --> Linux kernel
20 - `U-boot <https://git.linaro.org/landing-teams/working/arm/u-boot.git>`__
31 - Fetch and build u-boot.
38 Make the u-boot binary for Cortex-A5 using the command:
44 Make the u-boot binary for Cortex-A7 using the command:
59 ARM_XLAT_TABLES_LIB_V1=1 BL33=<path_to_u-boot.bin> all fip
67 BL33=<path_to_u-boot.bin> all fip
72 The following model parameters should be used to boot Linux using the build of
/rk3399_ARM-atf/docs/design/
H A Dindex.rst8 alt-boot-flows
16 trusted-board-boot
17 trusted-board-boot-build
H A Dreset-design.rst7 resulting in a simplified and more optimised boot flow.
11 specifically for the cold boot path.
38 warm boot to direct CPUs to the right execution path.
42 at the right address, both on a cold and warm reset. Therefore, the boot type
43 detection can be skipped, resulting in the following boot flow:
47 To enable this boot flow, compile TF-A with ``PROGRAMMABLE_RESET_ADDRESS=1``.
54 Cold boot on a single CPU
58 Therefore, the cold boot code has to arbitrate access to hardware resources
60 which is responsible for initialising shared hardware and coordinating the boot
65 applies. This results in the following boot flow:
[all …]
H A Dalt-boot-flows.rst4 EL3 payloads alternative boot flow
15 Rather than booting a baremetal application, a possible compromise is to boot
17 boot flow, where a modified BL2 boots an EL3 payload, instead of loading the
30 The system is left in the same state as when entering BL31 in the default boot
65 Preloaded BL33 alternative boot flow
70 improve performance in a development environment. When secure world cold boot
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A Duart-booting.rst4 This section describes how to temporary boot the Trusted Firmware-A (TF-A) project over UART
20 with either three files ``TIM_ATF.bin``, ``wtmi_h.bin`` and ``boot-image_h.bin`` for non-secure
21 boot or with four files ``TIM_ATF_TRUSTED.bin``, ``TIMN_ATF_TRUSTED.bin``, ``wtmi_h.bin`` and
22 ``boot-image_h.bin`` when secure boot is enabled.
33 To download images from ``uart-images.tgz.bin`` archive unpack it and for non-secure boot variant r…
38 > WtpDownload_linux -P UART -C <port#> -E -B TIM_ATF.bin -I wtmi_h.bin -I boot-image_h.bin
40 After that immediately start terminal on ``/dev/ttyUSB<port#>`` to see boot output.
70 non-secure boot variant (like Wtpdownloader) but at the highest speed, first unpack
75 > mox-imager -D /dev/ttyUSB<port#> -E -b 6000000 -t TIM_ATF.bin wtmi_h.bin boot-image_h.bin
78 not loose any boot output. It also prints boot output which is sent either by image files or by
H A Dbuild.rst20 > export BL33=path/to/u-boot.bin
22 For example: if U-Boot project (and its images) is located at ``~/project/u-boot``,
23 BL33 should be ``~/project/u-boot/u-boot.bin``
27 *u-boot.bin* should be used and not *u-boot-spl.bin*
247 The flash boot device, default is ``SPINOR``.
251 - SPINOR - SPI NOR flash boot
252 - SPINAND - SPI NAND flash boot
255 Download boot loader or program code from eMMC flash into CM3 or CA53
258 - SATA - SATA device boot
266 The boot partition number, default is 0.
[all …]
/rk3399_ARM-atf/docs/plat/st/
H A Dstm32mpus.rst12 The primary boot core (core 0) executes the boot sequence while
13 secondary boot core (core 1) is kept in a holding pen loop.
14 The ROM code boot sequence loads the TF-A binary image from boot device
43 Serial boot devices:
49 to save space and not overflow SYSRAM size, or else the platform won't build or boot.
55 - | ``DWL_BUFFER_BASE``: the 'serial boot' load address of FIP,
H A Dstm32mp1.rst25 Each line comes with a security option (cryptography & secure boot) and a Cortex-A frequency option:
40 Each line comes with a security option (cryptography & secure boot) and a Cortex-A frequency option:
142 To build TF-A BL2 with its STM32 header for SD-card boot:
149 For other boot devices, you have to replace STM32MP_SDMMC in the previous command
164 BL33=<u-boot_directory>/u-boot-nodtb.bin \
165 BL33_CFG=<u-boot_directory>/u-boot.dtb \
175 BL33=<u-boot_directory>/u-boot-nodtb.bin \
176 BL33_CFG=<u-boot_directory>/u-boot.dtb \
197 --nt-fw <u-boot_directory>/u-boot-nodtb.bin \
200 --hw-config <u-boot_directory>/u-boot.dtb \
[all …]
/rk3399_ARM-atf/plat/marvell/
H A Dmarvell.mk7 BOOT_IMAGE := boot-image.bin
8 BOOT_ENC_IMAGE := boot-image-enc.bin
/rk3399_ARM-atf/tools/nxp/create_pbl/
H A DREADME9 Specified boot source (QSPI or SD or NOR) to the,
24 -b <boot source id> - Boot source id string, may be one of
37 -s Secure boot.
39 -s secure boot
61 …make PLAT=ls1046rdb all fip BOOT_MODE=qspi SPD=opteed BL32=tee.bin BL33=u-boot-ls1046.bin pbl RCW=…
/rk3399_ARM-atf/plat/arm/board/fvp/fdts/
H A Doptee_sp_manifest.dts28 boot-order = <0>;
37 boot-info {
38 compatible = "arm,ffa-manifest-boot-info";
/rk3399_ARM-atf/docs/plat/nxp/
H A Dnxp-ls-tbbr.rst64 verified as part of CoT by Boot ROM during secure boot.
105 - There are 2 paths in secure boot flow :
166 … | ( = 1, BootROM Booted) | ( = 010 means Intent to Secure, | (=1111 means secure boot) |
173 --- Else, Linux boot will be successful.
175 -- For secure-boot status, read SNVS Register $SNVS_HPSR_REG from u-boot prompt:
190 …-- Refer the SoC specific table to read the register to interpret whether the secure boot is achie…
193 --- For secure-boot status, read SNVS Register $SNVS_HPSR_REG
210 -- 0xF = secure boot, as SSM_STATE.
/rk3399_ARM-atf/docs/plat/arm/automotive_rd/
H A Drd1ae.rst14 The boot process starts from RSE (Runtime Security Engine) that loads the
18 The primary compute boot flow follows the following steps:
66 BL33=<path to u-boot binary> \
72 …Board Boot (TBB): https://trustedfirmware-a.readthedocs.io/en/latest/design/trusted-board-boot.html
/rk3399_ARM-atf/docs/design_documents/
H A Dmeasured_boot_dtpm_poc.rst5 critical data used at boot time, for example using a TPM, so that the
32 expansion module. Measured boot capabilities using the TCG Event Log are
55 - **U-boot BL33**: This PoC showcases measured boot up to BL33, and for
56 simplicity uses a U-boot image for BL33, so that the image is measured and
57 loaded. Currently U-boot does not have Discrete TPM support for the
58 Raspberry Pi 3 platform so the boot flow ends here.
69 U-boot can be built for the Raspberry Pi 3, but there are some changes to be made
70 to allow the build to succeed. First Clone U-boot and enter the repo.
74 git clone https://github.com/u-boot/u-boot.git
75 cd u-boot
[all …]

123456