Lines Matching refs:U

60 for loading a Linux kernel, a VxWorks kernel, a modified U-Boot bootloader
62 -bios. It also supports booting the unmodified U-Boot bootloader using the
76   offset 0xfc. U-Boot reads the serial number from the OTP memory, and uses
103      This is U-Boot SPL.
105      peripherals as needed. This is U-Boot proper combined with an OpenSBI
210 Running U-Boot
213 U-Boot mainline v2024.01 release is tested at the time of writing. To build a
214 U-Boot mainline bootloader that can be booted by the ``sifive_u`` machine, use
226 To start U-Boot using the ``sifive_u`` machine, prepare an SPI flash image, or
281 Assume U-Boot binaries are put in the same directory as the config file,
288 Boot U-Boot from SD card, by specifying msel=11 and pass the SD card image
298 Changing msel= value to 6, allows booting U-Boot from the SPI flash:
307 Note when testing U-Boot, QEMU automatically generated device tree blob is
308 not used because U-Boot itself embeds device tree blobs for U-Boot SPL and
309 U-Boot proper. Hence the number of cores and size of memory have to match
312 Above use case is to run upstream U-Boot for the SiFive HiFive Unleashed
315 case: ZSBL (in QEMU) loads U-Boot SPL from SD card or SPI flash to L2LIM,
316 then U-Boot SPL loads the combined payload image of OpenSBI fw_dynamic
317 firmware and U-Boot proper.
319 However sometimes we want to have a quick test of booting U-Boot on QEMU
321 way can be used, which is to create a U-Boot S-mode image by modifying the
322 configuration of U-Boot:
333 This changes U-Boot to use the QEMU generated device tree blob, and bypass
334 running the U-Boot SPL stage.
336 Boot the 64-bit U-Boot S-mode image directly:
344 It's possible to create a 32-bit U-Boot S-mode image as well.
358 Use the same command line options to boot the 32-bit U-Boot S-mode image: