The fabulous fwupdmgr provides the ability to easily update firmware that is published to Linux Vendor Firmware Service (LVFS) but it can also be used to apply updates that aren’t necessarily in LVFS. One type of firmware that it supports updating is NVME firmware, that’s basically any NMVE, because the standard specifies a standardised mechanism for updating the firmware on all NVME devices.
I had a need to update a NVME firmware in an aarch64 device to see if it fixed an issue I was seeing. The Crucial P2 supported options were of course x86 only. The ISO download actually contained a little LinuxOS in an initrd on the .iso. The advice from Richard the fwupd technical lead was to “Look for a ~4mb high entropy blob” so mounting it up, I mounted the iso, extracted the initrd, and then used fwupdmmgr to apply the new firmware.
Find the NVME and check the firmware version:
$ cat /sys/class/nvme/nvme0/firmware_rev P2CR010
So once I’d downloaded the update file I did the following to extract and update the firmware. Note I did this all as root, you can do most of it as non root.
# unzip iso_p2cr012.zip # mount -o loop iso_p2cr012.iso /mnt/ # mkdir ~/tmp # cp /mnt/boot/corepure64.gz tmp/ # cd tmp # gunzip corepure64.gz # cpio -iv < corepure64 # fwupdtool install-blob opt/firmware/P2CR012/1.bin Loading… [- ] Loading… [- ] Choose a device: 0. Cancel 1. 71b677ca0f1bc2c5b804fa1d59e52064ce589293 (CT250P2SSD8) 2. 2270d251f7c1dc37a29a2aa720a566aa0fa0ecde (spi1.0) 1 Waiting… [************************************** ] Less than one minute remaining… An update requires a reboot to complete. Restart now? [y|N]: y
And away it goes, a reboot later and did it work?
$ cat /sys/class/nvme/nvme0/firmware_rev P2CR012