-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Boot issues with the latest firmware #574
Comments
This may be a duplicate of #572 in the sense that the cause may be the same. I'll be looking at this tomorrow. |
Yeah I kinda thought it might but there wasn't enough info in that ticket to know, I'm seeing it on all Pi, CM, Pi2, Pi3, but only with custom kernels which is so odd and hard to track down, spent most of the day trying different combos to try and narrow it down. Let me know if you need anymore info or tests. |
Adding the enable_uart setting changed the dependencies between various parts of the system. In resolving those dependencies, by allowing a more flexible initialisation sequence, one dependency was missed - that of the emmc clock on the core clock. Fortunately it is simple to put that dependency back, and the next firmware will do that. Sorry for the inconvenience. |
perfect thank you, as soon as it's available I'll test and report back though I'm sure it'll be great. |
The master firmware branch has now been updated. |
Confirmed working on all 3 platforms, thanks Phil. |
NOTE I have a custom build kernel, though just changing the FW fixes/breaks boot.
Committee 1c4f145 boots without issue.
Just updating *.elf *.bin *.dat on my SD card to commit de7aa7e causes
Using the firmware from the repo allows it boot, what changed in the firmware that could cause a custom kernel to fail? Is there a new Kconfig option that is required to be set with the new firmware?
The text was updated successfully, but these errors were encountered: