[coreboot] Questions about using coreboot riscv with qemu
zrahimkhani2014 at gmail.com
Tue Sep 11 11:53:28 CEST 2018
you can use this command
qemu-system-x86_64 -bios build/coreboot.rom -serial stdio
This can display with serial port.
On Mon, Sep 10, 2018 at 10:04 AM Liam Naddell <liamnprg at gmail.com> wrote:
> This is my first time using a mailing list btw, sorry.
> I was wondering how I could test the images I have built with `make
> riscv-crossgcc && make` using qemu.
> I tried running qemu-system-riscv64(the one gotten from the riscv-linux
> port), with the name of the image produced(coreboot.rom), and it did
> qemu-system-riscv64 ./build/coreboot.rom
> qemu-system-riscv64: Trying to execute code outside RAM or ROM at
> This usually means one of the following happened:
> (1) You told QEMU to execute a kernel for the wrong machine type, and it
> crashed on startup (eg trying to run a raspberry pi kernel on a
> versatilepb QEMU machine)
> (2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU
> executed a ROM full of no-op instructions until it fell off the end
> (3) Your guest kernel has a bug and crashed by jumping off into nowhere
> This is almost always one of the first two, so check your command line
> and that you are using the right type of kernel for this machine.
> If you think option (3) is likely then you can try debugging your guest
> with the -d debug options; in particular -d guest_errors will cause the
> log to include a dump of the guest register state at this point.
> Execution cannot continue; stopping here.
> I also tried this using the -bios flag, and by using the make-spike-elf
> script with the -bios flag, and I still got nothing.
> It would be really nice if somebody could help me :).
> coreboot mailing list: coreboot at coreboot.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the coreboot