Charles, > QEMU emulator version 7.0.0 (Debian 1:7.0+dfsg-2~bpo11+2) > Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers > > $ ../init-build.sh -DPLATFORM=spike -DRISCV64=TRUE -DRELEASE=FALSE > -DSIMULATION=TRUE > $ ninja > $ ./simulate -m 1G # becomes: qemu-system-riscv64 -machine spike -cpu rv64 > -nographic -serial mon:stdio -m size=1G -bios none -kernel > images/sel4test-driver-image-riscv-spike >
So - just to check, you don't see any output at all form the system booting, right? So Open-SBI and no seL4 messages? You have to use "-bios <img>" now instead of "-kernel <img>" when starting QEMU. There was a change that "-kernel <img>" now starts the "kernel" in S-Mode and an SBI will be taken from QEMU's internal (it comes with a dedicated ELF), while "-bios <img>" starts in M-Mode. Since we have an SBI in the sel4 system image, this will crash if started in S-Mode due to missing access permission. Using "-bios none" will just skip S-Mode, but that means the PMP is left unconfigured and S-Mode does not have access to any memory. New QEMU (6.0+?) emulate a PMP, older ones did now to this was not an issue. We have to QEMU simulate update the scrips to handle this, but the docker container still has the old QEMU, so this is not an issue there. Axel _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems
