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

start.elf doesn't exist #4

Closed
terokorp opened this Issue May 27, 2012 · 5 comments

Comments

Projects
None yet
4 participants
@terokorp

terokorp commented May 27, 2012

"
Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS
Performing self-update
/boot/start.elf doesn't exist.
"

This comes when installing firmware to new system.

@hoedlmoser

This comment has been minimized.

hoedlmoser commented May 27, 2012

am I right that you need to check for start.elf because the default value for FW_RAM is 0, so to be able to install it on an empty system you should add a default FW_RAM:
if [[ ! -f "${FW_PATH}/start.elf" ]]; then
echo "${FW_PATH}/start.elf doesn't exist. can't detect ARM/GPU memory split."
FW_RAM=224
fi

@hoedlmoser

This comment has been minimized.

hoedlmoser commented May 27, 2012

best solution imho is to remove the check for start.elf, because you are setting a default value for FW-RAM already in detect_split.

@Hexxeh

This comment has been minimized.

Owner

Hexxeh commented May 27, 2012

That check is there to stop people hosing /boot on their desktops. Maybe we should add a FORCE flag to not abort in cases like this.

@hoedlmoser

This comment has been minimized.

hoedlmoser commented May 27, 2012

in the meantime, the shortest workaround is just to
touch /boot/start.elf

@d1vious

This comment has been minimized.

d1vious commented Aug 30, 2012

This seemed to work, had a brand new pi :-). Hexxeh thanks for the tool.

@Hexxeh Hexxeh closed this Dec 25, 2012

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