Hi, Javier, Thank you for reporting this issue. It turned out to be a regression issue on APL FSP MR6 release. At this moment, please just use APL FSP MR5 release by: - Delete Silicon\ApollolakePkg\FspBin\*.bin - Update Silicon\ApollolakePkg\FspBin\FspBin.inf as below diff --git a/Silicon/ApollolakePkg/FspBin/FspBin.inf b/Silicon/ApollolakePkg/FspBin/FspBin.inf index 8db1fc6..ab475c5 100644 --- a/Silicon/ApollolakePkg/FspBin/FspBin.inf +++ b/Silicon/ApollolakePkg/FspBin/FspBin.inf @@ -10,7 +10,7 @@ [UserExtensions.SBL."CloneRepo"] REPO = https://github.com/IntelFsp/FSP.git - COMMIT = 7222054e9b7fc2d021fc404f87b4719d99b4c8ec + COMMIT = 7431e4f3399a5081c956753b5fa3bcd764196723 [UserExtensions.SBL."CopyList"] ApolloLakeFspBinPkg/FspBin/Fsp.fd : Silicon/ApollolakePkg/FspBin/FspDbg.bin - Rebuild SBL IFWI image and Capsule image. - Try firmware update again from Shell. BTW, on APL, FirmewareUpdate detection is actually done through MBP info in ProcessMbpData(). SBL Shell FwUpdate command will send a HECI message to CSME to mark this FirmwareUpdate request. On next boot, this request will be reflected in MBP info and BOOT_ON_FLASH_UPDATE mode will be set. The CMOS based detection is just for debug purpose and this code should be removed. Thanks Maurice From: Javier Santos Romo [mailto:jsantos@gmv.com] Sent: Wednesday, December 4, 2019 3:40 To: sbl-devel(a)lists.01.org Subject: [Sbl-devel] Apollo Lake Firmware Update not working Hi all, I have generated an update capsule to be able to update BIOS for an Apollo Lake custom board. FwuImage.bin was generated successfully and I tried to upgrade the system from SBL shell using fwupdate command. However, when I put the FwuImage.bin inside a FAT partition in a USB key and execute that command, system doesn´t enter in upgrade mode and jumps directly to OsLoader. I have been able to verify that IsFirmwareUpdate() function inside Stage1BBoardInitLib.c return FALSE, meaning that logic related to CMOS register to trigger firmware update is not working properly or maybe I have done something wrong. Could you provide me any guideline to try to understand what can be happening? Regards, Javier P Please consider the environment before printing this e-mail.