Searched full:boot (Results 1 – 25 of 6107) sorted by relevance
12345678910>>...245
... yml u-boot-2021.07/Kbuild u-boot-2021.07/Kconfig u-boot-2021.07/ ...
2 bool "U-Boot"4 Build "Das U-Boot" Boot Monitor6 https://www.denx.de/wiki/U-Boot17 Select this option if you use a recent U-Boot version (2015.0423 Select this option if you use an old U-Boot (older than30 string "U-Boot board name"32 One of U-Boot supported boards to be built.33 This will be suffixed with _config to meet U-Boot standard34 naming. See boards.cfg in U-Boot source code for the list of39 prompt "U-Boot Version"[all …]
18 u-boot,spl-boot-order = &sdmmc0, &sdhci, &nandc0, &spi_nand, &spi_nor;27 u-boot,dm-spl;32 u-boot,dm-spl;33 u-boot,dm-pre-reloc;37 u-boot,dm-spl;38 u-boot,dm-pre-reloc;42 u-boot,dm-spl;43 u-boot,dm-pre-reloc;48 u-boot,dm-pre-reloc;53 u-boot,dm-spl;[all …]
25 u-boot,spl-boot-order = &spi_nand;33 u-boot,dm-spl;37 u-boot,dm-spl;46 u-boot,dm-pre-reloc;52 u-boot,dm-spl;59 u-boot,dm-pre-reloc;64 u-boot,dm-pre-reloc;69 u-boot,dm-pre-reloc;74 u-boot,dm-pre-reloc;79 u-boot,dm-pre-reloc;[all …]
17 u-boot,spl-boot-order = &sdmmc, &sdhci, &spi_nand, &spi_nor;21 u-boot,dm-spl;28 u-boot,dm-spl;32 u-boot,dm-spl;36 u-boot,dm-pre-reloc;41 u-boot,dm-pre-reloc;45 u-boot,dm-pre-reloc;50 u-boot,dm-pre-reloc;55 u-boot,dm-spl;59 u-boot,dm-spl;[all …]
15 u-boot,spl-boot-order = &sdmmc, &spi_nand, &spi_nor, &nandc, &emmc;22 u-boot,dm-spl;28 u-boot,dm-pre-reloc;34 u-boot,dm-spl;40 u-boot,dm-spl;45 u-boot,dm-spl;49 u-boot,dm-spl;53 u-boot,dm-spl;57 u-boot,dm-spl;61 u-boot,dm-spl;[all …]
15 u-boot,spl-boot-order = &sdmmc, &spi_nor, &spi_nand, &emmc;24 u-boot,dm-spl;33 u-boot,dm-spl;38 u-boot,dm-spl;43 u-boot,dm-spl;48 u-boot,dm-spl;53 u-boot,dm-spl;58 u-boot,dm-spl;63 u-boot,dm-spl;68 u-boot,dm-spl;[all …]
15 u-boot,spl-boot-order = &sdmmc, &sdhci, &spi_nand, &spi_nor;24 u-boot,dm-spl;31 u-boot,dm-spl;36 u-boot,dm-spl;43 u-boot,dm-spl;48 u-boot,dm-spl;53 u-boot,dm-pre-reloc;58 u-boot,dm-pre-reloc;64 u-boot,dm-spl;69 u-boot,dm-spl;[all …]
15 u-boot,spl-boot-order = &sdmmc0, &sdhci, &spi_nand, &spi_nor;24 u-boot,dm-spl;30 u-boot,dm-spl;35 u-boot,dm-spl;40 u-boot,dm-spl;45 u-boot,dm-pre-reloc;50 u-boot,dm-spl;54 u-boot,dm-spl;58 u-boot,dm-spl;62 u-boot,dm-spl;[all …]
24 u-boot,spl-boot-order = &spi_nand, &spi_nor, &emmc;30 u-boot,dm-pre-reloc;35 u-boot,dm-spl;39 u-boot,dm-spl;43 u-boot,dm-spl;47 u-boot,dm-spl;51 u-boot,dm-spl;55 u-boot,dm-spl;60 u-boot,dm-spl;65 u-boot,dm-spl;[all …]
15 u-boot,spl-boot-order = &sdmmc, &spi_nand, &spi_nor, &nandc, &emmc;23 u-boot,dm-pre-reloc;28 u-boot,dm-pre-reloc;33 u-boot,dm-pre-reloc;37 u-boot,dm-pre-reloc;41 u-boot,dm-pre-reloc;45 u-boot,dm-pre-reloc;49 u-boot,dm-pre-reloc;55 u-boot,dm-spl;64 u-boot,dm-pre-reloc;[all …]
1 README on how boot images are created for secure TI devices4 Secure TI devices require a boot image that is authenticated by ROM6 device is essentially useless. In order to create a valid boot image for10 Information on the details on the complete boot image format can be obtained11 from Texas Instruments. The tools used to generate boot images for secure22 Booting of U-Boot SPL25 When CONFIG_TI_SECURE_DEVICE is set, the U-Boot SPL build process27 viable boot image. The build process will look for the environment36 ${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh38 This is called as part of the SPL/u-boot build process. As the secure[all …]
12 Linux distributions are faced with supporting a variety of boot mechanisms,13 environments or bootloaders (PC BIOS, EFI, U-Boot, Barebox, ...). This makes14 life complicated. Worse, bootloaders such as U-Boot have a configurable set19 This document defines a common set of U-Boot features that are required for21 allow distros to install and boot in an out-of-the-box fashion should enable22 all these features. Linux distros can then create a single set of boot27 decoupling distro install/boot logic from any knowledge of the bootloader.29 This model assumes that boards will load boot configuration files from a33 board-specific installer/boot-configuration support in a distro.35 To some extent, this model assumes that a board has a separate boot flash[all …]
9 1 U-Boot on EFI23 2 EFI on U-Boot29 U-Boot on EFI31 This document provides information about U-Boot running on top of EFI, either32 as an application or just as a means of getting U-Boot onto a new platform.39 - You have EFI running on a board but U-Boot does not natively support it40 fully yet. You can boot into U-Boot from EFI and use that until U-Boot is46 - You plan to use coreboot to boot into U-Boot but coreboot support does47 not currently exist for your platform. In the meantime you can use U-Boot48 on EFI and then move to U-Boot on coreboot when ready[all …]
1 Booting U-Boot on a MXS processor4 This document describes the MXS U-Boot port. This document mostly covers topics14 into the unix command prompt in U-Boot source code root directory.16 The (=>) introduces a snipped of code that should by typed into U-Boot command23 2) Compiling U-Boot for a MXS based board24 3) Installation of U-Boot for a MXS based board to SD card25 4) Installation of U-Boot into NAND flash on a MX28 based board26 5) Installation of U-Boot into SPI NOR flash on a MX28 based board32 mandatory tool is the "mxsboot" tool found in U-Boot source tree. The33 tool is built automatically when compiling U-Boot for i.MX23 or i.MX28.[all …]
3 This board definition results in a u-boot.bin which can be chainloaded9 onenand as such. This u-boot is intended to be flashed to the N900 like10 a kernel. In order to transparently boot the original kernel, it will be11 appended to u-boot.bin at 0x40000. NOLO will load the entire image into12 (random) memory and execute u-boot, which saves hw revision, boot reason13 and boot mode ATAGs set by NOLO. Then the bootscripts will attempt to load14 uImage or boot.scr from a fat, ext2/ext3 or ext4 filesystem in external17 stored ATAGs (see boot order).20 NOLO so u-boot must kick watchdog to prevent reboot device (but not very25 When U-Boot is starting it enable IBE bit in Auxiliary Control Register,[all …]
1 The trusted boot framework on Marvell Armada 38x6 1. Overview of the trusted boot8 3. Boot image layout10 5. The secured boot flow15 1. Overview of the trusted boot18 The Armada's trusted boot framework enables the SoC to cryptographically verify19 a specially prepared boot image. This can be used to establish a chain of trust20 from the boot firmware all the way to the OS.22 To achieve this, the Armada SoC requires a specially prepared boot image, which24 pertaining to the boot process. Furthermore, a eFuse structure (a[all …]
1 High Assurance Boot (HAB) for i.MX6 CPUs3 To enable the authenticated or encrypted boot mode of U-Boot, it is9 In addition, the U-Boot image to be programmed into the10 boot media needs to be properly constructed, i.e. it must contain a14 doc/README.imximage for how to prepare u-boot.imx.19 which can be used in the Freescale tooling to authenticate U-Boot22 Image Type: Freescale IMX Boot Image36 (1) Size of area in file u-boot.imx to sign37 This area should include the IVT, the Boot Data the DCD38 and U-Boot itself.[all …]
52 Step-1: Building u-boot for NAND boot61 # select BOOTSEL to MMC/SD boot and boot from MMC/SD card62 U-Boot # mmc rescan64 U-Boot # nand erase.chip65 U-Boot # env default -f -a66 U-Boot # saveenv68 U-Boot # load mmc 0 0x82000000 MLO69 U-Boot # nand write 0x82000000 0x00000 0x2000070 U-Boot # nand write 0x82000000 0x20000 0x2000071 U-Boot # nand write 0x82000000 0x40000 0x20000[all …]
12 cat ${BINARIES_DIR}/u-boot-spl.bin ${BINARIES_DIR}/ddr_fw.bin > ${BINARIES_DIR}/u-boot-spl-ddr.bin13 …3=${BINARIES_DIR}/u-boot-nodtb.bin ATF_LOAD_ADDR=0x00910000 ${HOST_DIR}/bin/mkimage_fit_atf.sh ${U…14 ${HOST_DIR}/bin/mkimage -E -p 0x3000 -f ${BINARIES_DIR}/u-boot.its ${BINARIES_DIR}/u-boot.itb15 rm -f ${BINARIES_DIR}/u-boot.its17 …${BINARIES_DIR}/u-boot-spl-ddr.bin 0x7E1000 -second_loader ${BINARIES_DIR}/u-boot.itb 0x40200000 0…19 cat ${BINARIES_DIR}/u-boot-spl.bin ${BINARIES_DIR}/ddr_fw.bin > ${BINARIES_DIR}/u-boot-spl-ddr.bin20 …3=${BINARIES_DIR}/u-boot-nodtb.bin ATF_LOAD_ADDR=0x00920000 ${HOST_DIR}/bin/mkimage_fit_atf.sh ${U…21 ${HOST_DIR}/bin/mkimage -E -p 0x3000 -f ${BINARIES_DIR}/u-boot.its ${BINARIES_DIR}/u-boot.itb22 rm -f ${BINARIES_DIR}/u-boot.its24 …${BINARIES_DIR}/u-boot-spl-ddr.bin 0x7E1000 -second_loader ${BINARIES_DIR}/u-boot.itb 0x40200000 0…[all …]
1 # This file is part of U-Boot verified boot support and is intended to be2 # inherited from u-boot recipe and from kernel-fitimage.bbclass.12 # As verified boot depends on fitImage generation, following is also required:17 # The signature support is limited to the use of CONFIG_OF_SEPARATE in U-Boot.22 # * u-boot:do_install:append29 # * u-boot:do_deploy[postfuncs]32 # For more details on signature process, please refer to U-Boot documentation.34 # We need some variables from u-boot-config37 # Enable use of a U-Boot fitImage45 UBOOT_DTB_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.dtb"[all …]
1 U-Boot for the Gateworks Ventana Product Family boards3 This file contains information for the port of U-Boot to the Gateworks7 is supported by a single bootloader build by using a common SPL and U-Boot10 all of the various boot mediums available.15 The i.MX6 has a BOOT ROM PPL (Primary Program Loader) which supports loading16 an executable image from various boot devices.19 will build the following artifacts from U-Boot source:20 - SPL - Secondary Program Loader that the i.MX6 BOOT ROM (Primary Program22 The DRAM controller, loads u-boot.img from the detected boot device,25 - u-boot.img - The main U-Boot core which is u-boot.bin with a image header.[all …]
3 source "boot/afboot-stm32/Config.in"4 source "boot/at91bootstrap/Config.in"5 source "boot/at91bootstrap3/Config.in"6 source "boot/at91dataflashboot/Config.in"7 source "boot/arm-trusted-firmware/Config.in"8 source "boot/barebox/Config.in"9 source "boot/beaglev-ddrinit/Config.in"10 source "boot/beaglev-secondboot/Config.in"11 source "boot/binaries-marvell/Config.in"12 source "boot/boot-wrapper-aarch64/Config.in"[all …]
316 # U-Boot does not need modules536 u-boot.cfg spl/u-boot.cfg tpl/u-boot.cfg: include/config.h FORCE571 #LDSCRIPT := $(srctree)/board/$(BOARDDIR)/u-boot.lds.debug581 LDSCRIPT := $(srctree)/board/$(BOARDDIR)/u-boot.lds584 LDSCRIPT := $(srctree)/$(CPUDIR)/u-boot.lds587 LDSCRIPT := $(srctree)/arch/$(ARCH)/cpu/u-boot.lds663 # U-Boot objects....order is important (i.e. start must be first)730 u-boot-dirs := $(patsubst %/,%,$(filter %/, $(libs-y))) tools examples732 u-boot-alldirs := $(sort $(u-boot-dirs) $(patsubst %/,%,$(filter %/, $(libs-))))736 u-boot-init := $(head-y)[all …]
1 U-Boot port for Texas Instruments Keystone II EVM boards6 This README has information on the U-Boot port for K2HK, K2E, and K2L EVM boards.29 Some of the peripherals that are configured by U-Boot42 To bring up SMP Linux on this board, there is a boot monitor44 to install this image from U-Boot.56 As U-Boot is migrating to Kconfig there is also board defconfig files62 Supported boot modes:63 - SPI NOR boot64 - AEMIF NAND boot (K2E, K2L and K2HK)65 - UART boot[all …]