Automate managing firmware binaries in OSFV #980
Description
The problem you're addressing (if any)
Right now the testers are downloading the firmware binary for testing from some source.
The preferred way is to either download from dl.3mdeb.com, or from the corresponding repo (most often coreboot) CI system.
This allows for user error if the tester forgets to get and flash the correct firmware binary from the correct source or reuses an old binary they already have without making sure it is exactly the same as the one that should be tested.
Describe the solution you'd like
Instead of FW_FILE=<path>, add a way to give the version of the binary and get it automatically.
For example:
FW_REPO=https://github.com/dasharo/coreboot,FW_VERSION=novacustom_v54x_mtl_v0.9.1- tag nameFW_URI=https://dl.3mdeb.com/open-source-firmware/Dasharo/novacustom_v54x_mtl/v0.9.1/novacustom_v54x_mtl_v0.9.1.rom- direct download URL
The FW_FILE option must obviously not be removed, because it would hinder debugging locally
Ideally the binaries should be cached somewhere in order to reduce unnecessary downloads.
Might be related to #632, as making OSFV aware of firmware binary versions would allow to set some DMIDECODE parameters automatically.
Where is the value to a user, and who might that user be?
Better reproducibility
Freeing the testers from managing firmware release binaries
Separating release binaries from possibly multiple debug binaries built by the tester, which might not be renamed by them and be mistaken for the release binaries
Describe alternatives you've considered
No response
Additional context
Problems:
- Not every Dasharo flavor builds the firmware in CI: