-
Notifications
You must be signed in to change notification settings - Fork 2
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
Explain how to flash the build artifacts to the ox64 #3
Comments
This just builds the SD card image - openbouffalo-image-dev-bl808.wic.bz2. Flash that to a SD card. For OpenSBI/UBoot etc you need to flash m0/d0 lowload and bl808-firmware.bin from the buildroot_OpenBouffalo repository |
Are there any plans to provide Opensbi m0/d0 lowload? u-bbot seems to be built already here and i have found recipes in meta-bl808 for opensbi. |
Probably not. It requires Yocto to build a multilib version of GCC (newlib for bare metal and glibc for Linux) and the xuantie toolchain we build is "hard" to get building a multilib version in yocto. (Patches welcome if you figure it out). |
I am currently working on the ox64 again and would actually like to give it a shot to get a complete yocto build to work. I would appreciate if you could elaborate a little on what is the problem/required work missing to get m0/do lowload and how to integrate opensbi From comparing with the buildroot repository i have found the oblfr recipe that seems to be missing. This seems to be the key to build both m0/d0 lowload. However i do not see a reason for a multilib here? For obensbi the recipe is there and builds so should be good? |
I have created a basic manifests repository to checkout all relevant repositories. Afterwards I sourced pokies oe-init-env and added the layers to the bblayers.conf. Note that this step should be automated soon.
Afterwards i build the image for machine bl808 and distro OpenBouffalo
build went through successfully and the generated artifacts look like this
What do I have to do to flash the resulting image on an ox64 board?
The text was updated successfully, but these errors were encountered: