sehraf / d1-riscv-arch-image-builder

RISC-V Archlinux D1 LicheeRV image builder
MIT License
113 stars 32 forks source link

Image Builder for Archlinux on an Allwinner D1 / Sipeed Lichee RV

These scripts compile, copy, bake, unpack and flash a ready to use RISC-V Archlinux.
With "ready to use" i mean that it boots, you still need to configure everything!

Special thanks to smaeul for all their work!

Find a precompiled image under the Actions artifacts. The image has no configuration or whatsoever!

Also have a look at the forks that have emerged over time or similar projects like a make file based approch.

Starfive Vision 2

There are multiple sources for an Archlinux image:

Components

How to build

  1. Install requirements: pacman -Sy riscv64-linux-gnu-gcc swig cpio python3 python-setuptools base-devel bc
    1. If you want to chroot into the RISC-V image, you also need arch-install-scripts qemu-user-static qemu-user-static-binfmt
  2. Edit consts.sh to your needs. For example, you may want to select a different DTB for a different board variant.
  3. Run 1_compile.sh which compiles everything into the output folder.
  4. Run 2_create_sd.sh /dev/<device> to flash everything on the SD card.
  5. Configure your Archlinux :rocket:

Using loop image file instead of a SD card

Simply loop it using sudo losetup -f -P <file> and then use /dev/loopX as the target device.

Notes

The second script requires arch-install-scripts, qemu-user-static-bin (AUR) and binfmt-qemu-static (AUR) for an architectural chroot. If you don't want to use/do this, change USE_CHROOT to 0 in consts.sh.
Keep in mind, that this is just a extracted rootfs with no configuration. You probably want to update the system, install an editor and take care of network access/ssh

Some commits are pinned, this means that in the future this script might stop working since often a git HEAD is checked out. This is intentional.

The second script uses sudo for root access. Like any random script from a random stranger from the internet, have a look at the code first and use at own risk!

Things are rebuild whenever the corresponding output/<file> is missing. For example, the kernel is rebuilt when there is no Image file.

Status

25.07.2023

4.11.2022

3.11.2022

13.09.2022

14.06.2022

22.04.2022

Problems

06.04.2022