-
Notifications
You must be signed in to change notification settings - Fork 2k
NVME guide assumes that the user is familiar with usbboot #1939
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
Comments
Add a bit more detail about running rpiboot from another PC Fixes raspberrypi#1939
Add a bit more detail about running rpiboot from another PC Fixes raspberrypi#1939
Thanks @pelwell. I haven't noticed these threads I'm afraid - which part of the forum should I be keeping an eye on? I've pushed a change that adds some clarification. |
They end up in the Compute Module forum most of the time, e.g. https://www.raspberrypi.org/forums/viewtopic.php?f=98&t=315291, but there was one on GitHub: raspberrypi/usbboot#82 |
@peterharperuk Looks like you've pushed the change to your fork of the documentation - do you want to PR it here too? 😉 |
If you do @peterharperuk sooner is better, I'll probably be freezing the current Markdown-based documentation at the end of the week (see #1911 for details of what's going on there). |
Add a bit more detail about running rpiboot from another PC Fixes raspberrypi#1939
Sorry, PR is here #1940 |
Add a bit more detail about running rpiboot from another PC Fixes raspberrypi#1939
PR is closed due to #1911. |
@peterharperuk I've seen a number of forum posts where the user is running usbboot on a CM4 as a way of enabling NVME booting. The documentation here does not make it clear that usbboot/rpiboot must be run on a separate computer Pi/PC/MAC in order to update the CM4 boot EEPROM.
The text was updated successfully, but these errors were encountered: