Home
last modified time | relevance | path

Searched full:boot (Results 1 – 25 of 5916) sorted by relevance

12345678910>>...237

/openbmc/openbmc-test-automation/redfish/systems/
H A Dtest_boot_devices.robot2 Documentation This suite test various boot types with boot source.
23 &{redfish_ipmi_enabled_map} Once=Options apply to only next boot
25 ... Disabled=Boot Flag Invalid
29 &{redfish_ipmi_target_map} Hdd=Force Boot from default Hard-Drive
31 ... Diags=Force Boot from default Hard-Drive, request Safe-Mode
32 ... Cd=Force Boot from CD/DVD
33 ... BiosSetup=Force Boot into BIOS Setup
38 &{redfish_ipmi_mode_map} Legacy=BIOS PC Compatible (legacy) boot
39 ... UEFI=BIOS EFI boot
45 Verify BMC Redfish Boot Source Override with Enabled Mode As Once
[all …]
/openbmc/u-boot/doc/
H A DREADME.ti-secure1 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 DREADME.u-boot_on_efi5 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.
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
38 - You plan to use coreboot to boot into U-Boot but coreboot support does
39 not currently exist for your platform. In the meantime you can use U-Boot
40 on EFI and then move to U-Boot on coreboot when ready
42 - You use EFI but want to experiment with a simpler alternative like U-Boot
[all …]
H A DREADME.distro11 Linux distributions are faced with supporting a variety of boot mechanisms,
12 environments or bootloaders (PC BIOS, EFI, U-Boot, Barebox, ...). This makes
13 life complicated. Worse, bootloaders such as U-Boot have a configurable set
18 This document defines a common set of U-Boot features that are required for
20 allow distros to install and boot in an out-of-the-box fashion should enable
21 all these features. Linux distros can then create a single set of boot
26 decoupling distro install/boot logic from any knowledge of the bootloader.
28 This model assumes that boards will load boot configuration files from a
32 board-specific installer/boot-configuration support in a distro.
34 To some extent, this model assumes that a board has a separate boot flash
[all …]
H A DREADME.nokia_rx513 This board definition results in a u-boot.bin which can be chainloaded
9 onenand as such. This u-boot is intended to be flashed to the N900 like
10 a kernel. In order to transparently boot the original kernel, it will be
11 appended to u-boot.bin at 0x40000. NOLO will load the entire image into
12 (random) memory and execute u-boot, which saves hw revision, boot reason
13 and boot mode ATAGs set by NOLO. Then the bootscripts will attempt to load
14 uImage or boot.scr from a fat, ext2/ext3 or ext4 filesystem in external
17 stored ATAGs (see boot order).
20 NOLO so u-boot must kick watchdog to prevent reboot device (but not very
25 When U-Boot is starting it enable IBE bit in Auxiliary Control Register,
[all …]
H A DREADME.armada-secureboot1 The trusted boot framework on Marvell Armada 38x
6 1. Overview of the trusted boot
8 3. Boot image layout
10 5. The secured boot flow
15 1. Overview of the trusted boot
18 The Armada's trusted boot framework enables the SoC to cryptographically verify
19 a specially prepared boot image. This can be used to establish a chain of trust
20 from the boot firmware all the way to the OS.
22 To achieve this, the Armada SoC requires a specially prepared boot image, which
24 pertaining to the boot process. Furthermore, a eFuse structure (a
[all …]
/openbmc/u-boot/board/ti/am335x/
H A DREADME52 Step-1: Building u-boot for NAND boot
61 # select BOOTSEL to MMC/SD boot and boot from MMC/SD card
62 U-Boot # mmc rescan
64 U-Boot # nand erase.chip
65 U-Boot # env default -f -a
66 U-Boot # saveenv
68 U-Boot # load mmc 0 0x82000000 MLO
69 U-Boot # nand write 0x82000000 0x00000 0x20000
70 U-Boot # nand write 0x82000000 0x20000 0x20000
71 U-Boot # nand write 0x82000000 0x40000 0x20000
[all …]
/openbmc/u-boot/arch/arm/dts/
H A Dfsl-imx8qxp-mek-u-boot.dtsi7 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;
43 u-boot,dm-spl;
[all …]
H A Dstm32h7-u-boot.dtsi3 u-boot,dm-pre-reloc;
7 u-boot,dm-pre-reloc;
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;
39 u-boot,dm-pre-reloc;
[all …]
H A Dstm32mp157-u-boot.dtsi23 u-boot,dm-pre-reloc;
27 u-boot,dm-pre-reloc;
31 u-boot,dm-pre-reloc;
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;
59 u-boot,dm-pre-reloc;
63 u-boot,dm-pre-reloc;
[all …]
/openbmc/linux/scripts/package/
H A Dbuildtar25 mkdir -p -- "${tmpdir}/boot"
26 dirs=boot
34 if [ -d "${srctree}/arch/${SRCARCH}/boot/dts" ]; then
35 …$MAKE ARCH="${ARCH}" -f ${srctree}/Makefile INSTALL_DTBS_PATH="${tmpdir}/boot/dtbs/${KERNELRELEASE…
52 cp -v -- "${objtree}/System.map" "${tmpdir}/boot/System.map-${KERNELRELEASE}"
53 cp -v -- "${KCONFIG_CONFIG}" "${tmpdir}/boot/config-${KERNELRELEASE}"
54 cp -v -- "${objtree}/vmlinux" "${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
62 …[ -f "${objtree}/arch/x86/boot/bzImage" ] && cp -v -- "${objtree}/arch/x86/boot/bzImage" "${tmpdir…
65 …[ -f "${objtree}/arch/alpha/boot/vmlinux.gz" ] && cp -v -- "${objtree}/arch/alpha/boot/vmlinux.gz"…
68 [ -f "${KBUILD_IMAGE}" ] && cp -v -- "${KBUILD_IMAGE}" "${tmpdir}/boot/vmlinux-${KERNELRELEASE}"
[all …]
/openbmc/u-boot/drivers/bootcount/
H A DKconfig2 # Boot count configuration
6 bool "Enable support for checking boot count limit"
8 Enable checking for exceeding the boot count limit.
14 prompt "Boot count device"
20 bool "Generic default boot counter"
29 bool "Boot counter on EXT filesystem"
31 Add support for maintaining boot count in a file on an EXT
35 bool "Boot counter in AM33XX RTC IP block"
44 bool "Boot counter in environment"
53 and "bootcount" variable to 0, if a boot was successfully.
[all …]
/openbmc/u-boot/doc/imx/common/
H A Dmxs.txt1 Booting U-Boot on a MXS processor
4 This document describes the MXS U-Boot port. This document mostly covers topics
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
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
32 mandatory tool is the "mxsboot" tool found in U-Boot source tree. The
33 tool is built automatically when compiling U-Boot for i.MX23 or i.MX28.
[all …]
/openbmc/u-boot/board/gateworks/gw_ventana/
H A DREADME1 U-Boot for the Gateworks Ventana Product Family boards
3 This file contains information for the port of U-Boot to the Gateworks
7 is supported by a single bootloader build by using a common SPL and U-Boot
10 all of the various boot mediums available.
15 The i.MX6 has a BOOT ROM PPL (Primary Program Loader) which supports loading
16 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 Program
22 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 …]
/openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/
H A DREADME.falcon1 Falcon boot option
3 Falcon boot is a short cut boot method for SD/eMMC targets. It skips loading the
4 RAM version U-Boot. Instead, it loads FIT image and boot directly to Linux.
5 CONFIG_SPL_OS_BOOT enables falcon boot. CONFIG_SPL_LOAD_FIT enables the FIT
9 To enable falcon boot, a hook function spl_start_uboot() returns 0 to indicate
10 booting U-Boot is not the first choice. The kernel FIT image needs to be put
14 not found, normal U-Boot flow will follow.
16 An important part of falcon boot is to prepare the device tree. A normal U-Boot
17 does FDT fixups when booting Linux. For falcon boot, Linux boots directly from
18 SPL, skipping the normal U-Boot. The device tree has to be prepared in advance.
[all …]
/openbmc/u-boot/arch/arm/mach-imx/
H A DMakefile110 …p_flags) -x c -o spl/u-boot-spl.cfgout $(srctree)/$(IMX_CONFIG); if [ -f spl/u-boot-spl.cfgout ]; …
111 …PP) $(cpp_flags) -x c -o u-boot-dtb.cfgout $(srctree)/$(IMX_CONFIG); if [ -f u-boot-dtb.cfgout ]; …
115 …p_flags) -x c -o spl/u-boot-spl.cfgout $(srctree)/$(IMX_CONFIG);if [ -f spl/u-boot-spl.cfgout ]; t…
121 MKIMAGEFLAGS_u-boot.imx = -n $(filter-out $(PLUGIN).bin $< $(PHONY),$^) \
123 u-boot.imx: MKIMAGEOUTPUT = u-boot.imx.log
125 u-boot.imx: u-boot.bin u-boot.cfgout $(PLUGIN).bin FORCE
130 MKIMAGEFLAGS_u-boot-dtb.imx = -n $(filter-out $(PLUGIN).bin $< $(PHONY),$^) \
132 u-boot-dtb.imx: MKIMAGEOUTPUT = u-boot-dtb.imx.log
134 u-boot-dtb.imx: u-boot-dtb.bin u-boot-dtb.cfgout $(PLUGIN).bin FORCE
144 MKIMAGEFLAGS_flash.bin = -n spl/u-boot-spl.cfgout \
[all …]
/openbmc/u-boot/board/ti/ks2_evm/
H A DREADME1 U-Boot port for Texas Instruments Keystone II EVM boards
6 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-Boot
42 To bring up SMP Linux on this board, there is a boot monitor
44 to install this image from U-Boot.
56 As U-Boot is migrating to Kconfig there is also board defconfig files
62 Supported boot modes:
63 - SPI NOR boot
64 - AEMIF NAND boot (K2E, K2L and K2HK)
65 - UART boot
[all …]
/openbmc/u-boot/arch/arm/mach-omap2/
H A Dconfig_secure.mk6 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 \
18 "$(TI_SECURE_DEV_PKG)/scripts/create-boot-image.sh not found." \
48 u-boot-spl_HS_X-LOADER: $(obj)/u-boot-spl.bin FORCE
51 # For MLO targets (SD card boot) the final file name that is copied to the SD
54 u-boot-spl_HS_MLO: $(obj)/u-boot-spl.bin FORCE
60 # Standard 2ND target (certain peripheral boot modes)
61 u-boot-spl_HS_2ND: $(obj)/u-boot-spl.bin FORCE
[all …]
/openbmc/u-boot/board/ti/dra7xx/
H A DREADME7 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 …]
/openbmc/u-boot/
H A DMakefile331 # U-Boot does not need modules
544 u-boot.cfg spl/u-boot.cfg tpl/u-boot.cfg:
579 #LDSCRIPT := $(srctree)/board/$(BOARDDIR)/u-boot.lds.debug
589 LDSCRIPT := $(srctree)/board/$(BOARDDIR)/u-boot.lds
592 LDSCRIPT := $(srctree)/$(CPUDIR)/u-boot.lds
595 LDSCRIPT := $(srctree)/arch/$(ARCH)/cpu/u-boot.lds
685 # U-Boot objects....order is important (i.e. start must be first)
743 u-boot-dirs := $(patsubst %/,%,$(filter %/, $(libs-y))) tools examples
745 u-boot-alldirs := $(sort $(u-boot-dirs) $(patsubst %/,%,$(filter %/, $(libs-))))
749 u-boot-init := $(head-y)
[all …]
/openbmc/openbmc-test-automation/openpower/ras/
H A Dtest_host_boot_ras.robot3 ... pdbg utility during HOST Boot path.
29 Verify Pdbg Recoverable Callout Handling For MCA During Host Boot
32 ... using pdbg tool during Host Boot path.
38 Inject Error At HOST Boot Path ${value[0]} ${value[1]}
43 Verify Pdbg Recoverable Callout Handling For MCI During Host Boot
45 ... using pdbg tool during Host Boot path.
51 Inject Error At HOST Boot Path ${value[0]} ${value[1]}
55 Verify Pdbg Recoverable Callout Handling For NXDMAENG During Host Boot
57 ... using pdbg tool during Host Boot path.
63 Inject Error At HOST Boot Path ${value[0]} ${value[1]}
[all …]
/openbmc/u-boot/board/boundary/nitrogen6x/
H A DREADME.mx6qsabrelite1 U-Boot for the Freescale i.MX6q SabreLite board
4 This file contains information for the port of U-Boot to the Freescale
11 To build U-Boot for the SabreLite board:
17 2. Boot from SD card
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.
43 the board). Make sure SW1 switch is at position "00", so that it can boot
46 3. Power-up the SabreLite, press 'space' to enter command mode in the U-Boot
[all …]
/openbmc/u-boot/arch/arm/cpu/arm926ejs/mxs/
H A DMakefile20 # 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)
23 # -> The size of IVT block aligned to 64B (u-boot.ivt)
24 # -> The size of U-Boot signature (u-boot.sig), 3904 B
25 # -> The 64B hole in front of U-Boot binary for 'struct mxs_spl_data' passing
56 spl/u-boot-spl.ivt: spl/u-boot-spl.bin
61 u-boot.ivt: u-boot.bin
66 spl/u-boot-spl.csf: spl/u-boot-spl.ivt spl/u-boot-spl.bin board/$(VENDOR)/$(BOARD)/sign/u-boot-spl.…
69 u-boot.csf: u-boot.ivt u-boot.bin board/$(VENDOR)/$(BOARD)/sign/u-boot.csf
75 MKIMAGEFLAGS_u-boot.sb = -n $< -T mxsimage
[all …]
/openbmc/u-boot/board/ti/omap5_uevm/
H A DREADME7 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 …]
/openbmc/u-boot/board/Barix/ipam390/
H A DREADME.ipam3903 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
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
44 U-Boot > print upd_uboot
[all …]

12345678910>>...237