Driver that uses rpiboot to boot a raspberry pi as a mass storage device #1734
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a driver and resource that can be used to take a raspberry pi put into usbboot mode and boot it as a mass storage device.
This is helpful when working with hardware based around raspberry pi compute modules, which might use a ssd or emmc for storage instead of a sd-card.
Currently being use to bootstrap a 10' chipsee panel before running automated tests.
The script used for this has been added to examples.
For this implementation it was chosen to keep it simple and not add support for using a serial number to chose between multiple devices because when adding the -i argument to the rpiboot like so
rpiboot -i [serialno]
i experienced that rpiboot would sit and wait for a raspberry pi to connect instead of using the one already connected. Which then leave me in a situation where labgrid is stuck executing the rpiboot command, waiting for the pi to be rebooted but not being able to do so because labgrid is stuck in the rpiboot command.Checklist