Closed csnover closed 4 months ago
The fw-log approach is used to get the corresponding fw version per slot. A combined approach could be possible.
Pushing to an active slot is possible and works. See the NVME Base Specification.
TODO: improve get_model_properties to parse all properties add test to check if all properties are loaded
Script tries to find the number of firmware slots but fails by trying to parse fw-log instead of looking at the frmw attribute? This does not work when there is only one firmware on the device and causes the script to try to commit the firmware to the currently active slot. Luckily this does not seem to work or it would probably brick devices due to the other issues in the script.