-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add application to the rootfs #25
Comments
Your steps should work... did you run If you want to put your own executable onto the fpga you could also just put it into the second partition of the FPGA. The second partition should get mounted on boot. |
Are you sure you are booting the correct bbl? If you want you could boot your vmlinux using spike or qemu and then check there if your executable is there. I suspect that somehow you are not booting the correct image. |
The correct bbl is used. Confirmed that!
Do we need anything else? |
Your process seems to be correct. Can you post your bbl file? |
Thanks. |
You seem to have made multiple changes to the build image. I cannot boot it in qemu or spike. It hangs at I know that the flow in this repo did not work for you before but I cannot really help you with the lowrisc flow. I am preparing an update to the ariane-sdk repo though so maybe it will work then |
The bbl that I send to you gave me the same issue hangs at Ok I will try with the new one. |
Hi,
I tried to add an application to the rootfs, by doing which when the Linux system boot up the binary file of the application can be found and executed.
I notice the Line 92 in Makefile gives such an example.
So after compiled my application with riscv64-unknown-linux-gnu-gcc I got a binary file. Then I copied this binary file to the ./rootfs, which is used to overlay the rootfs generated in the Buildroot.
After run the ""make vmlinux" and "make bbl.bin" I got bbl.
But after the linux OS boot up using this bbl, I can not find the binary file that I put to the rootfs. However, the tetris and cachtest are in the system.
Did I do something wrong?
The text was updated successfully, but these errors were encountered: