diff options
| author | Miquel Sabaté Solà <mikisabate@gmail.com> | 2024-11-30 21:16:54 +0100 |
|---|---|---|
| committer | Miquel Sabaté Solà <mikisabate@gmail.com> | 2024-11-30 21:16:54 +0100 |
| commit | 891742e62d79aeaf7dfd052df87777c2e4826357 (patch) | |
| tree | 926e7eca1d2628ef461522590c57ea01d49a7b38 /README.md | |
| parent | d87d29efc33236e847518b99b835fed783fc7395 (diff) | |
| download | fbos-891742e62d79aeaf7dfd052df87777c2e4826357.tar.gz fbos-891742e62d79aeaf7dfd052df87777c2e4826357.zip | |
Simplify the qemu target by removing QEMU_BIOS
The QEMU_BIOS parameter was meant to help on old QEMU installations
which did not support the proper fw_dynamic workflow. That being said,
old QEMU versions might also not implement the proper SBI specification,
or it may have other unexpected issues.
Hence, just remove the option and force people to have a sufficiently
recent QEMU version.
Finally, I have updated the SVG showing off a QEMU run.
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 22 |
1 files changed, 3 insertions, 19 deletions
@@ -47,25 +47,9 @@ whenever you'd want to debug the kernel via QEMU+GDB. Read more on this below. ## Test ### QEMU -The easiest way to test the `fbos` binary from the build step is with QEMU. That -being said, this kernel only supports the bootflow of openSBI `fw_dynamic`. If -you have a recent enough QEMU, then that's not a problem and you can skip the -next step. Otherwise you might need to specify the BIOS firmware that you'll -have to compile from openSBI. If you are on that side, don't worry, it's not -that hard: - -``` -$ git clone https://github.com/riscv-software-src/opensbi.git -$ cd opensbi -$ make ARCH=riscv CROSS_COMPILE=<your-cross-compile> PLATFORM=generic -# => build/platform/generic/firmware/fw_dynamic.bin -``` - -With that simply set the `QEMU_BIOS` environment variable with the full path of -the resulting `fw_dynamic.bin` file. - -Now make sure that you have a QEMU version that is able to emulate a RISC-V -system. After that, simply run: +The easiest way to test the `fbos` binary from the build step is with QEMU. You +need a QEMU version that is recent enough (see [requirements](#requirements)) +and that is able to virtualize a RISC-V system. With that, simply run: ``` $ make qemu |