Searched full:boot (Results 1 – 25 of 503) sorted by relevance
12345678910>>...21
56 Boot options60 for loading a Linux kernel, a VxWorks kernel, a modified U-Boot bootloader62 -bios. It also supports booting the unmodified U-Boot bootloader using the76 offset 0xfc. U-Boot reads the serial number from the OTP memory, and uses91 Mode Select (MSEL[3:0]) pins value, used to control where to boot from.94 using the Mode Select pins on the chip. Typically, the boot process runs98 1. Zeroth Stage Boot Loader (ZSBL), which is contained in an on-chip mask102 2. First Stage Boot Loader (FSBL), which brings up PLLs and DDR memory.103 This is U-Boot SPL.104 3. Second Stage Boot Loader (SSBL), which further initializes additional[all …]
47 Boot options51 for loading a Linux kernel, a VxWorks kernel, an S-mode U-Boot bootloader53 the recommended RISC-V bootflow: U-Boot SPL (M-mode) loads OpenSBI fw_dynamic54 firmware and U-Boot proper (S-mode), using the standard -bios functionality.73 For TCG guests only, it is also possible to boot M-mode firmware from163 To boot the newly built Linux kernel in QEMU with the ``virt`` machine:169 -kernel arch/riscv/boot/Image \175 fix the 32-bit boot issue for Linux kernel v5.12.187 line above to boot the 32-bit Linux kernel. A rootfs image containing 32-bit188 applications shall be used in order for kernel to boot to user space.[all …]
33 Boot options50 Direct Kernel Boot54 kernel boot is requested, a device tree blob may be specified via the ``-dtb``69 ``fw_dynamic`` BIOS image for the ``generic`` platform is used to boot an70 S-mode payload like U-Boot or OS kernel directly.72 For example, the following commands show building a U-Boot image from U-Boot80 Then we can boot the machine by:89 -kernel path/to/u-boot/build/dir/u-boot.bin \90 -dtb path/to/u-boot/build/dir/u-boot.dtb97 * The default U-Boot configuration uses CONFIG_OF_SEPARATE hence the ELF image[all …]
2 * Boot order test cases.82 { "-boot c",84 { "-boot nda",86 { "-boot order=",88 { "-boot order= -boot order=c",90 { "-boot once=a",92 { "-boot once=a -no-fd-bootchk",94 { "-boot once=a,order=c",96 { "-boot once=d -boot order=nda",98 { "-boot once=a -boot once=b -boot once=c",[all …]
15 #include "boot-sector.h"18 static char isoimage[] = "cdrom-boot-iso-XXXXXX";46 "xorrisofs", "-quiet", "-l", "-no-emul-boot", in prepare_image()134 g_test_skip("No KVM or TCG accelerator available, skipping boot tests"); in add_x86_tests()139 qtest_add_data_func("cdrom/boot/default", "-cdrom ", test_cdboot); in add_x86_tests()141 qtest_add_data_func("cdrom/boot/virtio-scsi", in add_x86_tests()148 qtest_add_data_func("cdrom/boot/am53c974", in add_x86_tests()154 qtest_add_data_func("cdrom/boot/dc390", in add_x86_tests()160 qtest_add_data_func("cdrom/boot/lsi53c895a", in add_x86_tests()172 qtest_add_data_func("cdrom/boot/isapc", "-M isapc " in add_x86_tests()[all …]
1 Managing device boot order with bootindex properties6 A simple way to set this order is to use the ``-boot order=`` option,14 boot priority. There is no particular order in which devices with no19 not support ``-boot order=``; on those machines you must always44 Given the command above, firmware should try to boot from the e1000 NIC52 booting. For instance, the x86 PC BIOS boot specification allows only one53 disk to be bootable. If boot from disk fails for some reason, the x86 BIOS54 won't retry booting from other disk. It can still try to boot from59 boot from to a boot method. It doesn't happen for devices the firmware60 can natively boot from, but if firmware relies on an option ROM for[all …]
10 hoops of firmware and boot-loaders.15 - sets platform FDT data so hypervisors can find and boot them17 This is what is typically done by a boot-loader like grub using its18 multi-boot capability. A typical example would look like:28 parameter and passed its boot arguments via -append. The Dom0 guest34 Currently the only supported machines which use FDT data to boot are
65 * Secure Boot Controller (AST2600)66 * eMMC Boot Controller (dummy)86 Boot options106 To boot a kernel directly from a Linux build tree:111 -kernel arch/arm/boot/zImage \112 -dtb arch/arm/boot/dts/aspeed-ast2600-evb.dtb \118 The machine options specific to Aspeed to boot from a flash image are :120 * ``execute-in-place`` which emulates the boot from the CE0 flash125 support for the chip model to boot.129 To boot the machine from the flash image, use an MTD drive :[all …]
33 Boot options37 for loading a Linux kernel, U-Boot bootloader or ELF executable.53 To boot the newly built Linux kernel in QEMU with the SABRE Lite machine, use:59 -kernel arch/arm/boot/zImage \60 -dtb arch/arm/boot/dts/imx6q-sabrelite.dtb \64 Running U-Boot67 U-Boot mainline v2020.10 release is tested at the time of writing. To build a68 U-Boot mainline bootloader that can be booted by the SABRE Lite machine, use82 then manually select the following configuration in U-Boot:86 To start U-Boot using the SABRE Lite machine, provide the u-boot binary to[all …]
5 based embedded computer with mainline support in both U-Boot43 Boot options68 For example, U-Boot uses it to determine a unique MAC address.107 To boot the newly build linux kernel in QEMU with the Orange Pi PC machine, use:112 -kernel /path/to/linux/arch/arm/boot/zImage \114 -dtb /path/to/linux/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb143 For example, to boot using the Orange Pi PC Debian image on SD card, simply add the -sd149 -kernel /path/to/linux/arch/arm/boot/zImage \151 -dtb /path/to/linux/arch/arm/boot/dts/sun8i-h3-orangepi-pc.dtb \176 give the following kernel parameters via U-Boot (or via -append):[all …]
55 Users can load firmware or boot-loaders with the ``-device loader`` options.61 for boot-loaders or firmware to pick it up.73 Direct Linux boot of a generic ARM64 upstream Linux kernel:79 -kernel arch/arm64/boot/Image \86 Direct Linux boot of PetaLinux 2019.2:98 Boot PetaLinux 2019.2 via ARM Trusted Firmware (2018.3 because the 2019.299 version of ATF tries to configure the CCI which we don't model) and U-boot:106 -device loader,file=petalinux-v2019.2/u-boot.elf \112 Run the following at the U-Boot prompt:124 Boot Linux as DOM0 on Xen via U-Boot:[all …]
42 Boot options62 To boot the newly build linux kernel in QEMU with the Banana Pi M2U machine, use:67 -kernel /path/to/linux/arch/arm/boot/zImage \69 -dtb /path/to/linux/arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dtb105 Running U-Boot108 U-Boot mainline can be build and configured using the Bananapi_M2_Ultra_defconfig110 for development/testing to select the following configuration setting in U-Boot:114 The BootROM of allwinner R40 loading u-boot from the 8KiB offset of sdcard.120 $ dd if=u-boot-sunxi-with-spl.bin of=sd.img bs=1k seek=8 conv=notrunc122 And then boot it.
1 Boot devices on s390x8 have to explicitly specify the disk where you want to boot from (or "IPL" from,12 device where you want to boot from with the ``bootindex`` property, for21 remaining boot devices to try.23 For booting from a CD-ROM ISO image (which needs to include El-Torito boot32 boot device. The old-fashioned ``-boot order=...`` command of QEMU (and33 also ``-boot once=...``) is not supported on s390x.41 not specify a boot device with the ``bootindex`` property, there is still a45 It is really recommended to always specify the boot device with the64 s390-ccw bios should boot. When starting QEMU, it can be specified like this::[all …]
25 /** Disable prints during boot */44 * Preferred boot HART id50 * stage leading to boot-time crash. To avoid this boot-time crash,52 * to the FW_DYNAMIC firmware as the preferred boot HART.54 * To avoid specifying a preferred boot HART, the previous booting74 * Preferred boot HART id80 * stage leading to boot-time crash. To avoid this boot-time crash,82 * to the FW_DYNAMIC firmware as the preferred boot HART.84 * To avoid specifying a preferred boot HART, the previous booting
59 Boot options63 for loading a payload like an OS kernel (e.g.: Linux), or U-Boot firmware.65 When -bios is omitted, the default pc-bios/u-boot.e500 firmware image is used71 N N u-boot73 Y don't care u-boot76 When both -bios and -kernel are present, QEMU loads U-Boot and U-Boot in turns78 U-Boot's built-in "bootm" command, hence a legacy uImage format is required in99 To boot the newly built Linux kernel in QEMU with the ``ppce500`` machine:113 To boot the 32-bit Linux kernel:123 Running U-Boot[all …]
13 which is a rebranded Mai Logic Teron board with modified U-Boot29 A firmware binary is necessary for the boot process. It is a modified30 U-Boot under GPL but its source is lost so it cannot be included in38 $ tail -c 524288 updater.image > u-boot-amigaone.bin50 To boot the system run:54 $ qemu-system-ppc -machine amigaone -bios u-boot-amigaone.bin \58 If a firmware menu appears, select ``Boot sequence`` → ``Amiga Multiboot Options``59 and set ``Boot device 1`` to ``Onboard VIA IDE CDROM``. Then hit escape until102 vgabios so it needs to be disabled. To boot the system run:110 At the firmware ``ok`` prompt enter ``boot cd install/pegasos``.[all …]
8 * NOTE: This header file defines an interface to U-Boot. Including10 * use of U-Boot, and does *not* fall under the heading of "derived102 * provided by U-Boot; it is expected that (if they behave103 * well) you can continue to work in U-Boot after return from109 * expect to re-enter U-Boot except by resetting the CPU.116 * to boot over the network using BOOTP etc., where the boot128 * U-Boot or FPGA images) which usually will be programmed to132 * U-Boot's command interpreter; this feature is especially133 * useful when you configure U-Boot to use a real shell (hush)151 IH_TYPE_KWBIMAGE, /* Kirkwood Boot Image */[all …]
54 /* multicore boards that use the default secondary core boot functions55 * need to put the address of the secondary boot code, the boot reg,57 * have their own boot functions can use these values as they want.68 /* multicore boards that use the default secondary core boot functions72 * boot loader/boot ROM code, and secondary_cpu_reset_hook() should74 * secondary CPUs to point at this boot blob.110 /* Boot firmware has been loaded, typically at address 0, with -bios or128 * changing to non-secure state if implementing a non-secure boot,136 /* CPU having load the kernel and that should be the first to boot. */141 * arm_load_kernel - Loads memory with everything needed to boot[all …]
67 @echo " u-boot.e500 -- update u-boot.e500"68 @echo " u-boot.sam460 -- update u-boot.sam460"138 u-boot.e500:139 $(MAKE) -C u-boot O=build-e500 qemu-ppce500_config140 $(MAKE) -C u-boot CROSS_COMPILE=$(powerpc_cross_prefix) \142 $(powerpc_cross_prefix)strip u-boot/build-e500/u-boot -o \143 ../pc-bios/u-boot.e500145 u-boot.sam460:146 $(MAKE) -C u-boot-sam460ex Sam460ex_config147 $(MAKE) -C u-boot-sam460ex CROSS_COMPILE=$(powerpc_cross_prefix)[all …]
42 'main/u/u-boot/u-boot-sunxi_2020.01%2Bdfsg-1_armhf.deb'),53 self.ASSET_DEB, member='boot/vmlinuz-6.6.16-current-sunxi')74 self.ASSET_DEB, member='boot/vmlinuz-6.6.16-current-sunxi')90 self.wait_for_console_pattern('Boot successful.')108 self.ASSET_DEB, member='boot/vmlinuz-6.6.16-current-sunxi')172 self.wait_for_console_pattern('U-Boot SPL')177 exec_command_and_wait_for_pattern(self, 'boot', 'Starting kernel ...')189 # We use the common OrangePi PC 'plus' build of U-Boot for our secondary191 # OrangePi "PC" device tree blob with 'setenv fdtfile' in U-Boot prompt,192 # before to boot NetBSD.[all …]
7 # * just boot initrd8 # * boot with filesystem on SD card9 # * boot from flash11 # to immediately reboot the system on successful boot, so we47 wait_for='Boot successful')58 self.launch_kernel(zimage_path, wait_for='Boot successful')69 self.launch_kernel(zimage_path, wait_for='Boot successful')
72 // Assuming the application was launched by the boot manager as a boot in BiosTablesTestMain()73 // loader, exiting with error will cause the boot manager to proceed with in BiosTablesTestMain()74 // the remaining boot options. If there are no other boot options, the boot in BiosTablesTestMain()138 // assuming the application was launched by the boot manager as a boot in BiosTablesTestMain()139 // loader, exiting the app with success causes the boot manager to pull up in BiosTablesTestMain()140 // the boot manager menu at once (regardless of other boot options); the wait in BiosTablesTestMain()
... x etc/usb-time-sigatt etc/boot-menu-message etc/boot-menu- ...
16 [submodule "roms/u-boot"]17 path = roms/u-boot18 url = https://gitlab.com/qemu-project/u-boot.git28 [submodule "roms/u-boot-sam460ex"]29 path = roms/u-boot-sam460ex30 url = https://gitlab.com/qemu-project/u-boot-sam460ex.git
34 # We increase beyond the default time since during boot56 def boot(self, img, extra_args=None): member in CentosAarch64VM64 # because without them, we boot so slowly that we65 # can time out finding the boot efi device.71 # We have overridden boot() since aarch64 has additional parameters.73 super(CentosAarch64VM, self).boot(img, extra_args=extra_args)80 self.boot(img_tmp, extra_args = ["-cdrom", self.gen_cloud_init_iso()])