/openbmc/u-boot/board/ti/am335x/ |
H A D | README | 12 - AM335x GP EVM 13 - AM335x EVM SK 14 - Beaglebone White 15 - Beaglebone Black 27 - GPIO is only required if DDR3 power is controlled in a way similar to 29 - SPI is only required for SPI flash, or exposing the SPI bus. 32 - I2C, to talk with the PMIC and ensure that we do not run afoul of 52 Step-1: Building u-boot for NAND boot 56 CONFIG_SYS_NAND_BLOCK_SIZE number of bytes in NAND erase-block 60 Step-2: Flashing NAND via MMC/SD [all …]
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | fsl-imx8qxp-mek-u-boot.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ 7 u-boot,dm-spl; 11 u-boot,dm-spl; 15 u-boot,dm-spl; 19 u-boot,dm-spl; 23 u-boot,dm-spl; 27 u-boot,dm-spl; 31 u-boot,dm-spl; 35 u-boot,dm-spl; 39 u-boot,dm-spl; [all …]
|
H A D | stm32h7-u-boot.dtsi | 3 u-boot,dm-pre-reloc; 7 u-boot,dm-pre-reloc; 8 pin-controller { 9 u-boot,dm-pre-reloc; 15 u-boot,dm-pre-reloc; 19 u-boot,dm-pre-reloc; 23 u-boot,dm-pre-reloc; 27 u-boot,dm-pre-reloc; 31 u-boot,dm-pre-reloc; 35 u-boot,dm-pre-reloc; [all …]
|
H A D | stm32mp157-u-boot.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause 23 u-boot,dm-pre-reloc; 27 u-boot,dm-pre-reloc; 31 u-boot,dm-pre-reloc; 34 compatible = "st,stm32-stgen"; 37 u-boot,dm-pre-reloc; 43 u-boot,dm-pre-reloc; 47 u-boot,dm-pre-reloc; 51 u-boot,dm-pre-reloc; 55 u-boot,dm-pre-reloc; [all …]
|
H A D | omap5-u-boot.dtsi | 2 * Copyright (C) 2017 Texas Instruments Incorporated - http://www.ti.com/ 12 tick-timer = &timer2; 21 u-boot,dm-spl; 24 compatible = "ti,omap-ocp2scp", "simple-bus"; 28 compatible = "ti,omap-ocp2scp", "simple-bus"; 32 u-boot,dm-spl; 38 u-boot,dm-spl; 39 reg-shift = <2>; 43 u-boot,dm-spl; 44 reg-shift = <2>; [all …]
|
H A D | omap3-u-boot.dtsi | 2 * Copyright (C) 2017 Texas Instruments Incorporated - http://www.ti.com/ 7 * Based on "omap5-u-boot.dtsi" 12 u-boot,dm-spl; 15 u-boot,dm-spl; 21 u-boot,dm-spl; 22 reg-shift = <2>; 26 u-boot,dm-spl; 27 reg-shift = <2>; 31 u-boot,dm-spl; 32 reg-shift = <2>; [all …]
|
/openbmc/u-boot/doc/ |
H A D | README.u-boot_on_efi | 1 # SPDX-License-Identifier: GPL-2.0+ 5 U-Boot on EFI 7 This document provides information about U-Boot running on top of EFI, either 8 as an application or just as a means of getting U-Boot onto a new platform. 22 32/64-bit 28 ---------- 29 Running U-Boot on EFI is useful in several situations: 31 - You have EFI running on a board but U-Boot does not natively support it 32 fully yet. You can boot into U-Boot from EFI and use that until U-Boot is 35 - You need to use an EFI implementation (e.g. UEFI) because your vendor [all …]
|
H A D | README.ti-secure | 1 README on how boot images are created for secure TI devices 4 Secure TI devices require a boot image that is authenticated by ROM 6 device is essentially useless. In order to create a valid boot image for 10 Information on the details on the complete boot image format can be obtained 11 from Texas Instruments. The tools used to generate boot images for secure 22 Booting of U-Boot SPL 25 When CONFIG_TI_SECURE_DEVICE is set, the U-Boot SPL build process 27 viable boot image. The build process will look for the environment 36 ${TI_SECURE_DEV_PKG}/scripts/create-boot-image.sh 38 This is called as part of the SPL/u-boot build process. As the secure [all …]
|
H A D | README.chromium | 1 Running U-Boot from coreboot on Chromebooks 4 U-Boot can be used as a secondary boot loader in a few situations such as from 8 This document aims to provide a guide to booting U-Boot on a Chromebook. It 10 placing this information in the U-Boot tree should make it easier to find for 11 those who use U-Boot habitually. 13 Most of these platforms are supported by U-Boot natively, but it is risky to 17 For all of these the standard U-Boot build instructions apply. For example on 20 sudo apt install gcc-arm-linux-gnueabi 22 make O=b/nyan_big CROSS_COMPILE=arm-linux-gnueabi- nyan-big_defconfig all 26 https://drive.google.com/open?id=0B7WYZbZ9zd-3dHlVVXo4VXE2T0U [all …]
|
H A D | README.x86 | 1 # SPDX-License-Identifier: GPL-2.0+ 6 U-Boot on x86 9 This document describes the information about U-Boot running on x86 targets, 13 ------ 14 U-Boot supports running as a coreboot [1] payload on x86. So far only Link 17 most of the low-level details. 19 U-Boot is a main bootloader on Intel Edison board. 21 U-Boot also supports booting directly from x86 reset vector, without coreboot. 23 'bare metal', U-Boot acts like a BIOS replacement. The following platforms 26 - Bayley Bay CRB [all …]
|
/openbmc/u-boot/doc/imx/common/ |
H A D | mxs.txt | 1 Booting U-Boot on a MXS processor 4 This document describes the MXS U-Boot port. This document mostly covers topics 8 ----------- 14 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 command 20 -------- 23 2) Compiling U-Boot for a MXS based board 24 3) Installation of U-Boot for a MXS based board to SD card 25 4) Installation of U-Boot into NAND flash on a MX28 based board 26 5) Installation of U-Boot into SPI NOR flash on a MX28 based board [all …]
|
/openbmc/u-boot/arch/arm/mach-imx/ |
H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0+ 3 # (C) Copyright 2000-2006 9 obj-y = iomux-v3.o 14 obj-$(CONFIG_IMX_BOOTAUX) += imx_bootaux.o 16 obj-$(CONFIG_ENV_IS_IN_MMC) += mmc_env.o 17 obj-$(CONFIG_FEC_MXC) += mac.o 18 obj-$(CONFIG_SYS_I2C_MXC) += i2c-mxv7.o 19 obj-y += cpu.o 23 obj-y += cpu.o speed.o 24 obj-$(CONFIG_GPT_TIMER) += timer.o [all …]
|
/openbmc/u-boot/ |
H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0+ 15 # o Do not use make's built-in rules and variables 16 # (this increases performance and avoids hard-to-debug behaviour); 18 MAKEFLAGS += -rR --include-dir=$(CURDIR) 32 # Most importantly: sub-Makefiles should only ever modify files in 35 # unavoidable when linking the built-in.o targets which finally 46 # --------------------------------------------------------------------------- 53 # cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $< 60 # A simple variant is to prefix commands with $(Q) - that's useful 61 # for commands that shall be hidden in non-verbose mode. [all …]
|
/openbmc/u-boot/arch/arm/cpu/arm926ejs/mxs/ |
H A D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0+ 3 # (C) Copyright 2000-2006 6 extra-$(CONFIG_SPL_BUILD) := start.o 8 obj-y = clock.o mxs.o iomux.o timer.o 11 obj-y += spl_boot.o spl_lradc_init.o spl_mem_init.o spl_power_init.o 15 MKIMAGE_TARGET-$(CONFIG_MX23) = mxsimage$(CONFIG_SPL_FRAMEWORK:%=-spl).mx23.cfg 16 MKIMAGE_TARGET-$(CONFIG_MX28) = mxsimage$(CONFIG_SPL_FRAMEWORK:%=-spl).mx28.cfg 18 # Generate HAB-capable IVT 20 # Note on computing the post-IVT size field value for the U-Boot binary. 22 # -> The size of U-Boot binary aligned to 64B (u-boot.bin) [all …]
|
/openbmc/u-boot/arch/arm/mach-omap2/ |
H A D | config_secure.mk | 1 # SPDX-License-Identifier: GPL-2.0+ 3 # Copyright (C) 2016, Texas Instruments, Incorporated - http://www.ti.com/ 6 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh),) 8 cmd_mkomapsecimg = $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh \ 9 $(patsubst u-boot-spl_HS_%,%,$(@F)) $< $@ $(CONFIG_ISW_ENTRY_ADDR) \ 12 cmd_mkomapsecimg = $(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh \ 13 $(patsubst u-boot_HS_%,%,$(@F)) $< $@ $(CONFIG_ISW_ENTRY_ADDR) \ 18 "$(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh not found." \ 30 ifneq ($(wildcard $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh),) 31 cmd_omapsecureimg = $(TI_SECURE_DEV_PKG)/scripts/secure-binary-image.sh \ [all …]
|
H A D | config.mk | 2 # Copyright (C) 2011, Texas Instruments, Incorporated - http://www.ti.com/ 4 # SPDX-License-Identifier: GPL-2.0+ 6 include $(srctree)/arch/arm/mach-omap2/config_secure.mk 9 ifeq ($(CONFIG_TI_SECURE_DEVICE),y) # Refer to README.ti-secure for more info 13 # u-boot-spl_HS_MLO 16 # u-boot-spl_HS_ULO 19 # u-boot-spl_HS_X-LOADER 21 ALL-y += u-boot-spl_HS_MLO 22 ALL-y += u-boot-spl_HS_ULO 23 ALL-y += u-boot-spl_HS_X-LOADER [all …]
|
/openbmc/u-boot/test/py/ |
H A D | README.md | 1 # U-Boot pytest suite 5 This tool aims to test U-Boot by executing U-Boot shell commands using the 6 console interface. A single top-level script exists to execute or attach to the 7 U-Boot console, run the entire script of tests against it, and summarize the 10 - Testing is performed in the same way a user or script would interact with 11 U-Boot; there can be no disconnect. 12 - There is no need to write or embed test-related code into U-Boot itself. 13 It is asserted that writing test-related code in Python is simpler and more 15 - It is reasonably simple to interact with U-Boot in this way. 19 The test suite is implemented using pytest. Interaction with the U-Boot console [all …]
|
/openbmc/u-boot/board/Barix/ipam390/ |
H A D | README.ipam390 | 3 The README is for the boot procedure on the ipam390 board 5 In the context of U-Boot, the board is booted in three stages. The initial 6 bootloader which executes upon reset is the ROM Boot Loader (RBL) and sits 9 controller (such as NAND) to continue the boot process by loading 11 further (some clocks, SDRAM). As on this board is used the falcon boot 19 spl code starts the u-boot image 29 it allows for additional flexibility (run-time detect of board revision, 34 run "tools/buildman/buildman -k ipam390" in the u-boot source tree. 35 Once this build completes you will have a ../current/ipam390/u-boot.ais file 41 Assuming that the network is configured and enabled and the u-boot.ais file [all …]
|
/openbmc/u-boot/board/ti/ks2_evm/ |
H A D | README | 1 U-Boot port for Texas Instruments Keystone II EVM boards 4 Author: Murali Karicheri <m-karicheri2@ti.com> 6 This README has information on the U-Boot port for K2HK, K2E, and K2L EVM boards. 8 http://www.advantech.com/Support/TI-EVM/EVMK2HX_sd.aspx 9 https://www.einfochips.com/index.php/partnerships/texas-instruments/k2e-evm.html 10 https://www.einfochips.com/index.php/partnerships/texas-instruments/k2l-evm.html 29 Some of the peripherals that are configured by U-Boot 30 +------+-------+-------+-----------+-----------+-------+-------+----+ 32 +------+-------+-------+-----------+-----------+-------+-------+----+ 37 +------+-------+-------+-----------+-----------+-------+-------+----+ [all …]
|
/openbmc/u-boot/board/davinci/da8xxevm/ |
H A D | README.da850 | 3 The README is for the boot procedure used for various DA850 (or compatible 6 In the context of U-Boot, the board is booted in three stages. The initial 7 bootloader which executes upon reset is the ROM Boot Loader (RBL) and sits 10 controller (such as SPI or NAND) to continue the boot process by loading 12 further (some clocks, SDRAM) and then load the full u-boot from a 13 predefined location in persistent storage to DDR and jumps to the u-boot 24 it allows for additional flexibility (run-time detect of board revision, 35 u-boot.ais file that needs to be written to the correct persistent 42 Assuming that the network is configured and enabled and the u-boot.ais file 45 U-Boot > sf probe 0 [all …]
|
/openbmc/u-boot/doc/SPI/ |
H A D | README.ti_qspi_dra_test | 1 ------------------------------------------------- 2 Simple steps used to test the QSPI at U-Boot 3 ------------------------------------------------- 5 For #1, build the patched U-Boot and load MLO/u-boot.img 7 ---------------------------------- 8 Boot from another medium like MMC 9 ---------------------------------- 11 U-Boot# mmc dev 0 13 U-Boot# fatload mmc 0 0x82000000 MLO 16 U-Boot# fatload mmc 0 0x83000000 u-boot.img [all …]
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | uboot-sign.bbclass | 4 # SPDX-License-Identifier: MIT 7 # This file is part of U-Boot verified boot support and is intended to be 8 # inherited from the u-boot recipe. 15 # UBOOT_MKIMAGE_DTCOPTS = "-I dts -O dtb -p 2000" 18 # As verified boot depends on fitImage generation, following is also required: 20 # KERNEL_CLASSES ?= " kernel-fitimage " 23 # The signature support is limited to the use of CONFIG_OF_SEPARATE in U-Boot. 25 # For more details on signature process, please refer to U-Boot documentation. 27 # We need some variables from u-boot-config 28 inherit uboot-config [all …]
|
/openbmc/u-boot/tools/binman/ |
H A D | README.entries | 15 ------------------------------------------------------ 21 - filename: Filename of file to read into entry 22 - compress: Compression algorithm to use: 24 lz4: Use lz4 compression (via 'lz4' command-line utility) 28 example the 'u_boot' entry which provides the filename 'u-boot.bin'. 30 If compression is enabled, an extra 'uncomp-size' property is written to 31 the node (if enabled with -u) which provides the uncompressed size of the 36 Entry: blob-dtb: A blob that holds a device tree 37 ------------------------------------------------ 40 obtained from the list of available device-tree files, managed by the [all …]
|
/openbmc/u-boot/board/boundary/nitrogen6x/ |
H A D | README.mx6qsabrelite | 1 U-Boot for the Freescale i.MX6q SabreLite board 4 This file contains information for the port of U-Boot to the Freescale 9 -------- 11 To build U-Boot for the SabreLite board: 17 2. Boot from SD card 18 -------------------- 20 The SabreLite boards boot from the SPI NOR flash. These boards need their SPI 21 to be reflashed with a small SD card loader to support boot from SD card. The 22 board will still boot from SPI NOR, but the loader will in turn request the 23 BootROM to load the U-Boot from SD card. [all …]
|
/openbmc/u-boot/board/ti/dra7xx/ |
H A D | README | 7 eMMC boot partition use 10 It is possible, depending on SYSBOOT configuration to boot from the eMMC 11 boot partitions using (name depending on documentation referenced) 12 Alternative Boot operation mode or Boot Sequence Option 1/2. In this 13 example we load MLO and u-boot.img from the build into DDR and then use 15 set boot0 as the boot device. 16 U-Boot # setenv autoload no 17 U-Boot # usb start 18 U-Boot # dhcp 19 U-Boot # mmc dev 1 1 [all …]
|