"-machine " - define a set of devices, accordance to board reference documents, without CPU. Yes, you should to program against a particular cpu, as you say. Bare metal images usually shouldn't use -kernel, though.) (If you said you were a Linux kernel loading via -kernel then we pass the DTB in the way the kernel booting ABI specifies. All other information about which devices are present and where they are in memory should be obtained from the device tree blob, which can be found at the bottom of RAM, assuming you are a bare metal blob loading via -bios or -pflash.there is boot flash at address 0x0 (which you can fill using the -bios or -pflash QEMU command line option).For a bare metal guest OS, you need to know:
#QEMU ARCH CODE#
You cannot just try to use a 32-bit board with a -cpu cortex-a53, though - this is like trying to plug a Core2Duo into an old i386 motherboard and will not function correctly even if QEMU doesn't print an error message about the combination.įor the virt board, since this is not modelling a real piece of hardware, its details are only specified in the QEMU source code and in the device tree blob we pass to the guest.
#QEMU ARCH FULL#
The qemu-system-aarch64 binary supports all the 32-bit CPUs and boards, in the same way that qemu-system-x86_64 lets you run a 32-bit x86 CPU guest, which is why the list is so long and full of 32-bit boards. You'll also need to specify the CPU type with -cpu cortex-a53, since the "virt" board's default is cortex-a15 (a 32-bit CPU). The short answer for AArch64 is that you want to use the "virt" board, unless you specifically know that you want to emulate one of the 64-bit Xilinx boards (which it sounds like you don't). The "how do I choose a board" question is quite a common one and we document the usual answer on the project's wiki:
0 kommentar(er)
