Architectures/RISC-V/Milk-V/Jupiter

Milk-V Jupiter

Flash U-Boot to the SPI NOR

• You should be able to skip flashing the SPI NOR unless you would like to update to a more current version of u-boot.
• Download the latest .zip (not .img.zip) from http://archive.spacemit.com/image/k1/version/bianbu/
• Follow one of the methods documented by Milk-V, such as fastboot to update https://milkv.io/docs/jupiter/getting-started/boot#using-fastboot

Configure u-boot

• There are two dtbs for the Milk-V, k1-x_milkv-jupiter.dtb and m1-x_milkv-jupiter.dtb. Use the corresponding product_name for your hardware:
• Run the following commands

setenv product_name m1-x_milkv-jupiter
setenv fdt_addr_r 0x31000000
setenv bootcmd 'nvme scan; load nvme 0:2 ${fdt_addr_r} dtb/spacemit/${product_name}.dtb; load nvme 0:1 ${kernel_addr_r} EFI/fedora/shimriscv64.efi; bootefi ${kernel_addr_r} ${fdt_addr_r}'
saveenv

• Alternatively if you want to boot from sd card you can set the bootcmd like so

setenv bootcmd 'load mmc 0:2 ${fdt_addr_r} dtb/spacemit/${product_name}.dtb; load mmc 0:1 ${kernel_addr_r} EFI/fedora/shimriscv64.efi; bootefi ${kernel_addr_r} ${fdt_addr_r}'

Hardware Note

It is preferable to use the ethernet port furthest from the HDMI port. If the ethernet port closer to HDMI is plugged in u-boot will spend several seconds attempting to TFTP boot before proceeding. This does not happen when using the other interface.

Write Fedora to storage

• Download the latest Fedora-Server-Host-SpacemiT-* image from https://dl.fedoraproject.org/pub/alt/risc-v/release/42/Server/riscv64/images/
• unxz the image
• Adapting the command to write to the correct file to the correct device run sudo dd if=Fedora-Server-Host-SpacemiT... of=/dev/sdX status=progress bs=16M
• Install the storage in your BPI-F3 and boot