File: u-boot-qemu.README.Debian

package info (click to toggle)
u-boot 2025.01-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 330,740 kB
  • sloc: ansic: 2,627,855; python: 60,773; sh: 41,641; asm: 21,854; makefile: 15,048; perl: 12,447; cs: 6,763; cpp: 1,868; yacc: 1,100; lex: 747; awk: 57; tcl: 32; sed: 24
file content (44 lines) | stat: -rw-r--r-- 1,260 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

Booting a qemu/kvm guest with u-boot
====================================

To boot a qemu guest with u-boot, start qemu-system with the '-bios
u-boot.bin' option. Use the full path to the u-boot.bin file that corresponds
with the archicture you are trying to boot.


Booting from disk
-----------------

To allow a qemu guest to boot from disk, you need a u-boot config file on the
disk. There is no need to install u-boot in the guest, as you are passing
u-boot directly to qemu. The u-boot config file can be automatically created
by installing the u-boot-menu package. Alternatively, the flash-kernel package
can also create u-boot config files, but it currently doesn't recognise qemu
guests.


Netboot
-------

u-boot supports the e1000 network driver to boot from the network. Please note
that u-boot will initially output "Net:   No ethernet found.", before
continuing with the netboot.


Device tree
-----------

On architectures where a device tree file is needed to boot, qemu will
generate the device tree based on the virtual hardware that is configured.
u-boot should be able to find this data at the default address where u-boot
looks for this data (${fdt_addr}, so you should use that address in your
u-boot script.


Examples
========

TODO