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.

Sign up for GitHub

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

Jump to bottom

incorrect fdt_addr_r environment variable #18

Open

pdp7 opened this issue Apr 30, 2021 · 1 comment

Labels

Collaborator

pdp7 commented Apr 30, 2021

@tpettazzoni notes in buildroot patch series:

The final patch obviously adds the Beagle-V defconfig and related
files themselves. A slight annoyance is that the bootloader
pre-flashed on the board doesn't work as-is, just due to an incorrect
fdt_addr_r environment variable value. So reflashing the bootloader
with what has been built by Buildroot is necessary (but is trivial to
do using Xmodem).

Erico Nunes replied:

I would like to try this but I have some questions:
Are you able to still boot the reference Fedora image after flashing
the custom bootloader?
Also, if it is just a matter of updating fdt_addr_r, could it just be
updated in the u-boot environment instead?
And finally, should that be reported as an issue in the starfive
u-boot so maybe they can release another build with that fixed?

I am opening issue to track if the SPI flash should be changed in future board production.

Collaborator Author

pdp7 commented Apr 30, 2021

@tekkamanninja @MichaelZhuxx @Pillar1989 I am opening issue to track if the SPI flash should be changed in future board production.

MichaelZhuxx added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment