Support #253
closedTrying to compile and run coreboot on qemu-riscv..
0%
Description
I followed the build instruction I found online and was able to build a coreboot with a BBL+vmlinux payload, a vmlinux kernel and a coreinfo payload.
When I run either one under qemu-system-riscv64 I get a expection fault:
Before I go digging into the code, I wanted to see if this was a known issue? Or if I am doing something wrong? I have used this qemu to boot another riscv image (bbl)
CMDLINE: qemu-system-riscv64 -M virt -m 1024M -nographic -kernel build/coreboot.elf
Output:
qemu-system-riscv64: warning: No -bios option specified. Not loading a firmware.
qemu-system-riscv64: warning: This default will change in a future QEMU release. Please use the -bios option to avoid breakages when this happens.
qemu-system-riscv64: warning: See QEMU's deprecation documentation for details.
coreboot-4.11-9-g93ac30d189-dirty Thu Dec 12 15:10:43 UTC 2019 bootblock starting (log level: 7)...
ERROR: FMAP_CACHE enabled but no region provided!
FMAP: Found "FLASH" version 1.1 at 0x20000.
FMAP: base = 0x0 size = 0x2000000 #areas = 4
FMAP: area COREBOOT found @ 20100 (16645888 bytes)
CBFS: 'COREBOOT Locator' located CBFS at [20100:1000000)
CBFS: Locating 'fallback/romstage'
CBFS: Found @ offset 80 size 36e3
coreboot-4.11-9-g93ac30d189-dirty Thu Dec 12 15:10:43 UTC 2019 romstage starting (log level: 7)...
Exception: Load access fault
Hart ID: 0
Previous mode: machine
Bad instruction pc: 00000000820042ac
Bad address: 0000001081fffffc
Stored ra: 0000000082004378
Stored sp: 0000000083032e98
Can't recover from trap. Halting.
Updated by Marc Karasek almost 5 years ago
As I see no way to delete/close this..
I moved this over to the Bug list.. So can someone close/delete this?
Updated by Paul Menzel almost 5 years ago
- Status changed from New to Closed
You should be able to go to Edit, and then change the status.