Skip to content
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

Closed
TheSin- opened this issue Mar 23, 2016 · 6 comments
Closed

Boot issues with the latest firmware #574

TheSin- opened this issue Mar 23, 2016 · 6 comments

Comments

@TheSin-
Copy link

TheSin- commented Mar 23, 2016

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

[    0.942498] mmc0: Reset 0x1 never completed.
[    1.046913] mmc0: Reset 0x1 never completed.
[    1.086591] mmc0: Internal clock never stabilised.
[    1.111624] mmc0: Internal clock never stabilised.
[   11.162491] mmc0: Timeout waiting for hardware interrupt.
[   11.268099] mmc0: Reset 0x2 never completed.
[   11.372437] mmc0: Reset 0x4 never completed.
[   21.402493] mmc0: Timeout waiting for hardware interrupt.
[   21.508024] mmc0: Reset 0x2 never completed.
[   21.612357] mmc0: Reset 0x4 never completed.
[   21.636910] mmc0: Internal clock never stabilised.

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?

@pelwell
Copy link
Contributor

pelwell commented Mar 23, 2016

This may be a duplicate of #572 in the sense that the cause may be the same. I'll be looking at this tomorrow.

@TheSin-
Copy link
Author

TheSin- commented Mar 24, 2016

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.

@pelwell
Copy link
Contributor

pelwell commented Mar 24, 2016

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.

@TheSin-
Copy link
Author

TheSin- commented Mar 24, 2016

perfect thank you, as soon as it's available I'll test and report back though I'm sure it'll be great.

@pelwell
Copy link
Contributor

pelwell commented Mar 24, 2016

The master firmware branch has now been updated.

@TheSin-
Copy link
Author

TheSin- commented Mar 24, 2016

Confirmed working on all 3 platforms, thanks Phil.

@TheSin- TheSin- closed this as completed Mar 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants