-
Notifications
You must be signed in to change notification settings - Fork 42
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
Newly-built EDK2/GRUB crashes #110
Comments
@orlitzky From which distro did you get the already compiled SG2042.fd? Can you give me the link and also the path where it is stored in the archive file? |
(I answered on the mailing list, but just in case someone else needs this...) At the time of writing, the latest SOPHGO Fedora image is, After decompressing that, you will be left with On linux, you can use
Now the file you want should be under |
@orlitzky I have tried the
My
The directory tree of the SD card is as follows:
I am getting following error during boot process (the exception is different from yours, it is EXCEPT_RISCV_STORE_ACCESS_PAGE_FAULT):
|
Unfortunately these error messages don't mean much to me. I did notice an earlier error in your output,
that I would be suspicious of. That message is coming from https://github.com/sophgo/zsbl/blob/master/plat/sg2042/boot.c#L617 and the error can be traced back through libfdt. I think it's coming from offset = fdt_subnode_offset_namelen(fdt, parentoffset, name, namelen);
if (offset >= 0)
return -FDT_ERR_EXISTS; because #define FDT_ERR_EXISTS 2
/* FDT_ERR_EXISTS: Attempted to create a node or property which
* already exists */ is the error code you see. If it were me, I would try:
to see if that error goes away. But I am 100% guessing. |
I'm trying to document the EDK2/GRUB build process but haven't been able to build a working
SG2042.fd
yet. It builds successfully, but then crashes when I reboot. This is on a Pioneer Box:If I take
SG2042.fd
from one of the pre-built Fedora images, it works, so there must be something going wrong in the build. (I am following the steps inenvsetup.sh
.)The text was updated successfully, but these errors were encountered: