New on blogs.coreboot.org: [GSoC] Better RISC-V support, week #4/5
WordPress <wordpress <at> blogs.coreboot.org>
2016-06-27 20:49:41 GMT
A new post titled "[GSoC] Better RISC-V support, week #4/5" has been published on the coreboot blog. Find the full post at http://blogs.coreboot.org/blog/2016/06/27/gsoc-better-risc-v-support-week-45/
In week 4, I tracking down why coreboot halted after about one line of output. It turned out to be a spike bug, that I wrote up in this bug report, and affect any program that doesn’t have a tohost symbol. As a workaround, I extended my script that turns coreboot.rom into a ELF to also include this symbol.
After some more patches I could run coreboot in spike and get the familiar “Payload not loaded” line.
I was now clearly moving towards being able to run linux on spike/coreboot. But there was a problem: The RISC-V linux port requires a working implementation of the Supervisor Binary Interface (SBI), which is a collection of functions that the supervisor (i.e. the linux kernel) can call in the system firmware.
Coreboot has an implementation of the SBI, but it’s probably outdated by now. To get an up-to-date SBI implementation, I decided to use bbl as a payload. When I built bbl with coreboot’s RISC-V toolchain, I noticed that it depends on a libc being installed in two ways:
- The autoconf-generated configure script checks that the C compiler can compile and link a program, which only succeeds if it finds a linker script (riscv.ld) and a crt0.o in the right place.
- bbl relies on the libc headers to declare some common functions and types (it doesn’t use any of the implementations in the libc, though).
The coreboot toolchain script doesn’t, however, install a libc, because coreboot doesn’t need one.
I tweaked the bbl source code until it didn’t need the libc headers, changed the implementation of mcall_console_putchar to use my 8250 UART, got the payload section of bbl (where linux is stored before it’s loaded) out of the way of the CBFS by moving it to 0x81000000 (bbl/bbl.lds is the relevant file for this change), and could finally observe Linux booting in spike, on top of coreboot and bbl. It stops with a kernel panic, though, because it doesn’t have a root filesystem.
Plans for this week
This week I will document my work on the Spike wiki page in the coreboot wiki, so others can run coreboot on spike, too.
coreboot mailing list: coreboot <at> coreboot.org