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

arm240_start.elf broken? #5

Closed
DeadWalkingDeath opened this issue Sep 13, 2012 · 11 comments
Closed

arm240_start.elf broken? #5

DeadWalkingDeath opened this issue Sep 13, 2012 · 11 comments

Comments

@DeadWalkingDeath
Copy link

I cannot boot with arm240_start.elf, the others work fine.

What caught my attention is the different filesize:
arm128_start.elf 2465.904 kb
arm192_start.elf 2465.904 kb
arm224_start.elf 2465.904 kb
arm240_start.elf 642.192 kb

Thanks for looking into this!

@popcornmix
Copy link
Collaborator

It should be smaller, it is build with fewer libraries.

@DeadWalkingDeath
Copy link
Author

Ok, but to me it seems like arm240_start.elf is broken anyway.
I tried again yesterday after a complete rpi-update and the the Pi wouldn't boot.
Renaming the arm224 file on the sd card will make it boot again.

Seems like I'm not the only one with this problem. (http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725&start=25)

@popcornmix
Copy link
Collaborator

Do you have rotated display?

@DeadWalkingDeath
Copy link
Author

No, I have no display connected at all.

@w-flo
Copy link

w-flo commented Sep 14, 2012

Same problem.

~6 hours ago I used rpi-update, which froze and caused a freeze for any other program when doing SD card access (happens a lot for me), so I pulled the plug. I then fixed the SD card using my laptop, fsck and rpi-update in offline mode. It still wouldn't boot, so I connected my TV to the raspi and noticed that it just stopped at the rainbow screen.

I double checked that /root/.rpi_firmware/arm240_start.elf and /boot/start.elf have matching md5 sums, and also compared md5 sums for bootcode.bin, loader.bin and kernel.img, and they all matched.
"git status" in /root/.rpi_firmware said "working directory clean", so I suspect the files in that directory were not corrupt (happened a few times before because of the way I have to shutdown my pi when it freezes during rpi-update).

Then I copied arm224_start.elf to start.elf and now my pi works again.

@w-flo
Copy link

w-flo commented Sep 15, 2012

Booting with latest arm240_start.elf works fine for me, so the problem appears to be solved.

@popcornmix
Copy link
Collaborator

Can you do a test for me.
Can you add boot_delay=0 to config.txt and see it it still works.
If that breaks it, can you add:
boot_delay=0
boot_delay_ms=100
and confirm if that works. Ideally find the smallest boot_delay_ms= that allows it to work.

@Hexxeh
Copy link
Owner

Hexxeh commented Sep 15, 2012

Is that not going to be a little different for different SD cards?

On 15 September 2012 15:39, popcornmix [email protected] wrote:

Can you do a test for me.
Can you add boot_delay=0 to config.txt and see it it still works.
If that breaks it, can you add:
boot_delay=0
boot_delay_ms=100
and confirm if that works. Ideally find the smallest boot_delay_ms= that
allows it to work.


Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-8585272.

@popcornmix
Copy link
Collaborator

Yes. But as I don't see the problem I need some information. Possibly 1ms is enough for everyone. Maybe it's 100ms or 1000ms.

@w-flo
Copy link

w-flo commented Sep 15, 2012

boot_delay=0 works for me (simple "reboot" command, and also unplugging the pi for a few minutes, then plugging it in again).
Using current arm240_start.elf (md5: 1e2f1bc121c86ec99c235855cbce7159).

@DeadWalkingDeath
Copy link
Author

I finally had time to test the new arm240_start.elf and I can confirm that it boots now without problems.
I didn't add boot_delay or boot_delay_ms to config.txt.

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

4 participants