mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-09 07:51:59 -09:00
8d94747b33
Release notes at: https://github.com/riscv-software-src/opensbi/releases/tag/v1.6 From release notes: "Overall, this release adds more ISA extensions, drivers, and other improvements." This OpenSBI version 1.6 can be tested in qemu with the commands: cat <<EOF >.config BR2_riscv=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_OPENSBI=y BR2_TARGET_OPENSBI_PLAT="generic" BR2_TOOLCHAIN_EXTERNAL=y EOF make olddefconfig make Then: qemu-system-riscv64 \ -M virt \ -bios output/images/fw_jump.bin \ -kernel output/images/Image \ -append "rootwait root=/dev/vda ro" \ -drive file=output/images/rootfs.ext2,format=raw \ -nographic Note that in the previous qemu command line, the OpenSBI ".bin" image is passed rather than the ".elf" image. Loading the ".elf" image in qemu can now lead to the following qemu error: qemu-system-riscv64: Some ROM regions are overlapping These ROM regions might have been loaded by direct user request or by default. They could be BIOS/firmware images, a guest kernel, initrd or some other file loaded into guest memory. Check whether you intended to load all this guest code, and whether it has been built to load to the correct addresses. The following two regions overlap (in the memory address space): fw_jump.elf ELF program header segment 1 (addresses 0x0000000000000000 - 0x00000000000271e0) mrom.reset (addresses 0x0000000000001000 - 0x0000000000001028) See: https://github.com/riscv-software-src/opensbi/issues/372 Signed-off-by: Kilian Zinnecker <kilian.zinnecker@mail.de> Tested-by: Julien Olivain <ju.o@free.fr> [Julien: reworded the commit log about testing] Signed-off-by: Julien Olivain <ju.o@free.fr>
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches