In some cases, updates from lvfs may not have taken immediately due to the APE not being reset, resulting in a power loss before the update completes.
The APE fw should be updated to detect fw changes (using the mutex for NVRAM, or possibly an interrupt if present) and verify the fw is valid, then reset the RX cpus, followed by itself to complete the update without a reboot.
The firmware metadata should be updated to report to the user that the system must be disconnected from power untill the fw handles this.
See https://github.com/fwupd/fwupd/issues/6243 and https://github.com/fwupd/fwupd/pull/6572
In some cases, updates from lvfs may not have taken immediately due to the APE not being reset, resulting in a power loss before the update completes.
The APE fw should be updated to detect fw changes (using the mutex for NVRAM, or possibly an interrupt if present) and verify the fw is valid, then reset the RX cpus, followed by itself to complete the update without a reboot.
The firmware metadata should be updated to report to the user that the system must be disconnected from power untill the fw handles this.