Porting to VisionFive2 riscv64 hardware

KenDickey commented 1 year ago

This is basically an information request. I need to know more about how to knit together u-boot, OpenSBI, and the Phoenix-RTOS kernel. My simple attempt was to place the kernel and initrd on a working SD card which boots Debial linux and has working dtb's, but something is amiss.

Under Debian

root@starfive:~# cd /boot /boot

root@starfive:/boot# ls -F System.map-5.15.0-starfive phoenix-kernel.img config-5.15.0-starfive rootfs.ext2 dtbs/ syspagen extlinux/ uEnv.txt initrd.img-5.15.0-starfive vmlinuz-5.15.0-starfive

root@starfive:/boot# lsblk mmcblk1p1 179:1 0 2M 0 part mmcblk1p2 179:2 0 4M 0 part mmcblk1p3 179:3 0 100M 0 part /boot mmcblk1p4 179:4 0 14.7G 0 part /

extlinux.conf contains

label 10s menu label Phoenix-RTOS linux /phoenix-kernel.img[B initrd /rootfs.ext2 fdtdir /dtbs append root=/dev/mmcblk1p3 rw console=tty0 console=ttyS0,115200 debug earlycon rootwait selinux=0

Boot log shows

U-Boot menu 1: Debian GNU/Linux bookworm/sid 5.15.0-starfive 2: Debian GNU/Linux bookworm/sid 5.15.0-starfive (rescue target) 3: Phoenix-RTOS Enter choice: 3 3: Phoenix-RTOS Retrieving file: /rootfs.ext2 71657472 bytes read in 3093 ms (22.1 MiB/s) Retrieving file: /phoenix-kernel.img 379928 bytes read in 23 ms (15.8 MiB/s) append: root=/dev/mmcblk1p3 rw console=tty0 console=ttyS0,115200 debug earlycon rootwait selinux=0 Retrieving file: /dtbs/starfive/jh7110-visionfive-v2.dtb 50235 bytes read in 11 ms (4.4 MiB/s) Bad Linux RISCV Image magic! 1: Debian GNU/Linux bookworm/sid 5.15.0-starfive

Now I note that the VisionFive3/linux SBI is version 1.0, where Phoenix uses version 0.3.

Both VF2/linux and Phoenix build u-boot and OBSI, but I don't know the settings and invarients to hook up the flashed VF2 u-boot and OSBI with the Phoenix kernel.

I have spent a bunch of time reading docs and code but could really use some help here.

Thanks for ideas, suggestions, theory of operation, ... -KenD

https://github.com/starfive-tech/VisionFive2

KenDickey commented 1 year ago

More log for context..

VisionFive2-Phoenix.txt

agkaminski commented 1 year ago

Hi, please take a look at a process of image generation for riscv64 target: https://github.com/phoenix-rtos/phoenix-rtos-project/blob/master/_targets/build.project.riscv64-generic

OpenSBI is integrated within the system image, so this image is prepared to be launched as is, without any additional bootloaders. Phoenix-RTOS does not support U-Boot at this moment, presently there are no concrete plans for it's support. Also, there's a good chance VisionFive2 support require some work to be done, as there might be hardware or even CPU core differences in comparison to the supported qemu and spike emulated targets.

KenDickey commented 1 year ago

Right. That is why I am trying to boot "phoenix-kernel.img", NOT "phoenix.disk". (note sizes, below). I am also using the VisionFive2 u-boot, OpenSBI, and dtb's, so initial HW setup should be proper.

So again, my questions are

What info does u-boot+OpenSBI need to pass to the Phoenix-RTOS kernel?
What is the mechanism?
What are the invariants?
What driver/api/interface work may be needed?

Thanks! I am just learning this system and still getting oriented.

===================================================== Raspian:RasPi4:~/Phoenix-RTOS/_boot/riscv64-generic-qemu >>> ls -lasth total 82M 70M -rw-r--r-- 1 pi pi 71M Jul 18 15:32 phoenix.disk 4.0K drwxr-xr-x 2 pi pi 4.0K Jul 18 15:32 . 11M -rw-r--r-- 1 pi pi 69M Jul 18 15:32 rootfs.ext2 1.3M -rwxr-xr-x 1 pi pi 1.3M Jul 18 15:32 phoenix.osbi 372K -rw-r--r-- 1 pi pi 372K Jul 18 15:32 phoenix-kernel.img 20K -rwxr-xr-x 1 pi pi 19K Jul 18 15:28 syspagen 4.0K drwxr-xr-x 4 pi pi 4.0K Jul 12 07:20 ..

phoenix-rtos / phoenix-rtos-project