# Capsule 更新日志 Capsule 更新日志提供有关胶囊更新的开始和结束的信息。 在系统启动过程中，UEFI 固件会处理包含固件更新有效负载和元数据的 capsule。 文档针对 capsule 更新的不同阶段指定了三个示例日志。有关更多详细信息，请参阅以下日志： ## UEFI 阶段：开始 capsule 更新 > > > - **日志条目**:在UEFI阶段，胶囊加载大容量存储 capsule 文件 `capsule1.fv'!` 并开始处理大容量存储 capsule 文件 `capsule1.fv'!`。 > - **描述**：日志表明系统已检测到 capsule。系统触发并处理 capsule 更新。 > - **日志文件**： > > > > > > > > > > UEFI Start [ 1570] > > - 0x09FC01000 [ 1573] Sec.efi > > ASLR : ON > > DEP : ON (RTB) > > Timer Delta : +1 mS > > RAM Entry 0 : Base 0x0080000000 Size 0x003A800000 > > RAM Entry 1 : Base 0x00C0000000 Size 0x0001800000 > > RAM Entry 2 : Base 0x00C3400000 Size 0x003CC00000 > > RAM Entry 3 : Base 0x0100000000 Size 0x0100000000 > > Total Available RAM : 6028 MB (0x0178C00000) > > Total Installed RAM : 6144 MB (0x0180000000) > > Multithread : ON (Lib ver 1.2) > > Init Cores : 2 > > Init CPU core 1 > > > Scheduler up on Core 1 > > CONF File : uefiplatLA.cfg > > UEFI Ver : 6.0.xxx.xxx.xxx.1.0.c1-xxxx.1-KODIAKLA-1 > > Build Info : 64b Nov 27 2024 15:04:28 > > Boot Device : UFS > > PROD Mode : FALSE > > Retail : FALSE > > > > DTB config : client[0]..trace[0]..verbose[0] > > - 0x09EDD0000 [ 1628] DxeCore.efi > > Loading DxeCore at 0x009EDD0000 EntryPoint=0x009EDD1000 > > HOBLIST address in DXE = 0x9EBC1018 > > FV Hob 0x9FC00000 - 0x9FFEFFFF > > FV Hob 0x9EE0F000 - 0x9F1DBFFF > > FV2 Hob 0x9EE0F000 - 0x9F1DBFFF > > 631008B0-B2D1-410A-8B49-2C5C4D8ECC7E - 00000000-0000-0000-0000-000000000000 > > > > >>> Cluster 0: 1804800000 Hz > > >>> Cluster L3: 1516800000 Hz > > PM0: 47, PM1: 63, PM2: 49, PM8: 46, > > Module cannot re-initialize DAL module environment > > UFS INQUIRY ID: SAMSUNG KM2L9001CM-B518 0700 > > UFS Boot LUN: 1 > > tz_armv8_smc_call failed, TzStatus = 0xFFFFFFFF, SmcId = 0x32000105 > > Status = 0x3 > > APP_REGION_NOTIFICATION_CMD: Syscall Not Supported, status 3 > > QseeResponse->result = 0xE > > Status = 0x7 > > QseeResponse->result = 0xE > > Status = 0x7 > > Image partition label not found > > EFI_QseecomStartApp: Load from partition (featenabler_a)Failed: Status(0x800000000000000E), appId(0) > > QseeResponse->result = 0xE > > Status = 0x7 > > QseeResponse->result = 0xE > > Status = 0x7 > > Image partition label not found > > EFI_QseecomStartApp: Load from partition (featenabler)Failed: Status(0x800000000000000E), appId(0) > > Image partition label not found > > LoadImageFromPartitionUsingGuid Failed: 14 > > EFI_QseecomStartApp: Load Failed: Status(0x800000000000000E) > > Failed to start featenabler_a TA, status = 14 > > - 0x09CA2C000 [ 1836] DisplayDxe.efi > > DisplayUtils: mount logfs system failed with status 14! > > DisplayUtils: mount logfs system failed with status 14! > > DisplayUtils: mount logfs system failed with status 14! > > DisplayDxe: Panel ID:0x00000000 [LCD] > > DisplayDxe: Resolution 1920x1080 (1 intf) > > pil-imagefv Done t=10ms s=2ms a=3ms f=3ms > > > > fast_core_num val: 0 > > UsbConfigLibOpenProtocols: PMI version (0x0) > > UsbConfigLibOpenProtocols: gPmicNpaClientHS2 cannot be created > > UsbConfigInit: Dual Role Enabled on Port Number: 0 > > UsbConfigInit: after setting role > > UsbConfigInit: UsbConfigInit, not start on port: 0, mode 0 > > UsbConfigInit: Dual Role Enabled on Port Number: 1 > > UsbConfigInit: after setting role > > UsbConfigInit: UsbConfigInit, not start on port: 1, mode 0 > > UsbConfigInit: UsbPwrCtrl No. of Ports = 1 > > > > UsbConfigPortsQueryConnectionChange: usbport->connectstate: ATT > > ConnectSts : Attach, Data Role : UFP (DEVICE Mode), Lane : CC1, CoreNum : 0 > > HandlePortPartnerXtach: Cable Attach core 0, portmode 1, dualmode 1 > > ButtonsDxeTest: Keypress SDAM data payload 0 > > Current SysFwVersion Entry info: > > ==================================== > > Signature : 5245565746535953 > > Revision : 0x10000 > > VersionDataCrc32 : 0xD6AE50A5 > > FwVersion : 0x10000 > > LowestSupportedFwVersion : 0x0 > > ==================================== > > Platform: QCS6490 IOT > > Selected FW GUID =: 6F25BFD2-A165-468B-980F-AC51A0A45C52 > > Platform = 20 > > - 0x09C885000 [ 1981] SoftSKUDxe.efi > > SoftSKUDxeInitialize: SoftSKU not supported for this chip > > Error: Image at 0009C885000 start failed: Unsupported > > - 0x09C885000 [ 1984] MinidumpTADxe.efi > > MinidumpTADxe: Minidump TA loading not enabled. > > BDS Entry [ 1993] > > Disp init wait [ 1993] > > DisplayUtils: mount logfs system failed with status 14! > > MDP_Display_LoadFileEx: Failed to mount imagefv_a partition, eStatus=Not Found > > MDP_Display_LoadFileEx: load file from imagefv_a failed with status(5), So loading default image! > > ----------------------------- > > Platform Init [ 2065] BDS > > Boot Cycle : 34 > > Run Cycle : 34 > > UEFI Ver : 6.0.xxxxx.xxxx.xxx.1.0.c1-00xxx-xxxx-1 > > Platform : IOT > > Subtype : 2 > > Boot Device : UFS > > Chip Name : xxxxx > > Chip Ver : 1.0 > > Chip Serial Number : 0xDF4B18A2 > > Boot Core : 1804 MHz > > ----------------------------- > > - 0x09C70F000 [ 2083] QcomChargerApp.efi > > EFI partition block size: 4096 > > No pending capsules found in EFI Raw file > > Starting to flush any pending persisted capsules from media > > Could not find 'BootOrder' variable to find EFI partition with mass-storage capsules! > > Looking for local EFI partition variable to find EFI partition with mass-storage capsules > > Loading mass-storage capsule file 'capsule1.fv'! > > Starting to process mass-storage capsule file 'capsule1.fv'! > > FmpDxe(Qualcomm System Firmware Update Driver): CheckTheImage() - No dependency associated in image. > > V3 payload found > > V3 payload found > > NewImage Version - 0x30004 > > NewImage LowestSupportedImageVersion - 0x0 > > Current Version (partition) - 0x10000 > > Current LowestSupportedImageVersion (partition) - 0x0 > > Copy to clipboard ## 固件备份、更新和更新后 > > > - **日志条目**： > > - 第1阶段：固件条目备份开始，第1阶段完成。 > - 第2阶段：固件条目更新开始，第2阶段完成。 > - 第3阶段：更新后固件进入开始，第3阶段完成。 > > > > > > > > > > 固件更新已成功完成。 > > > - **说明**: 日志文件中提供了成功固件更新的标记。固件更新中描述的阶段如日志条目中所示。 > - **日志文件**： > > > Attempting to start: Firmware update > > Current SysFwVersion Entry info: > ==================================== > Signature : 5245565746535953 > Revision : 0x10000 > VersionDataCrc32 : 0xD6AE50A5 > FwVersion : 0x10000 > LowestSupportedFwVersion : 0x0 > ==================================== > Current FW update attempt count is: 1 > Current FW update state is: FW_STATE_NOT_IN_PROGRESS > Successfully synced all UEFI tables > Rendering Progress: 1 > > Parsing payload... > V3 payload found > Payload info: > ==================================== > Revision : 3 > Header size (Byte) : 24 > FwVer : 0x30004 > Lowest supported version : 0x0 > Breaking change number : 0 > Entry count : 10 > ==================================== > Current breaking change number is 0 > Payload breaking change number is 0 > Double update not required > > > ACTIVE LUN: 1 > > 1 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = imagefv_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = imagefv_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 2 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = uefi_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = uefi_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 3 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = aop_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = aop_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 4 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = hyp_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = hyp_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 5 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = tz_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = tz_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 6 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = cpucp_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = cpucp_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 7 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = shrm_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = shrm_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 8 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = multiimgoem_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = multiimgoem_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 9 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = xbl_ramdump_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = xbl_ramdump_b > FileName = > > FwEntry Encrypted = False > ==================================== > > 10 FwEntry found... > FwEntry: > ==================================== > Operation = 0x1,{UPDATE} > > UpdateType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = uefisecapp_a > FileName = > > BackupType = 0x0,{Partition} > DiskPartitionType = 0xC,{LUN4} > PartitionName = uefisecapp_b > FileName = > > FwEntry Encrypted = False > ==================================== > > Validating FwEntry list... > > FwEntry list validated. Totally 10 FwEntries found > Rendering Progress: 5 > Successfully synced all UEFI tables > : Failed to get ResetPhase test hook data with error: Not Found > > Phase 1: FwEntry Backup start. Time (ms): 2631 > > Rendering Progress: 6 > GPT-Data Compression Statistics:: OriginalSize: 5900, CompressedSize: 594 > > Successfully synced all UEFI tables > Backing up 1/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 1 > Rendering Progress: 6 > Backing up 2/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 3 > Rendering Progress: 7 > Backing up 3/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 3 > Rendering Progress: 7 > Backing up 4/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 4 > Rendering Progress: 7 > Backing up 5/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 5 > Rendering Progress: 8 > Backing up 6/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 45 > Rendering Progress: 25 > Backing up 7/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 59 > Rendering Progress: 31 > Backing up 8/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 61 > Rendering Progress: 32 > Backing up 9/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 99 > Rendering Progress: 49 > Backing up 10/10 FwEntry... > Backup Success > > Progress span of current phase: [6, 50]. Progress value within this span in (0-100 scale): 100 > Rendering Progress: 50 > Successfully synced all UEFI tables > Rendering Progress: 50 > > Phase 1 Done. Time (ms): 3048 > : Failed to get ResetPhase test hook data with error: Not Found > > Phase 2: FwEntry Update start. Time (ms): 3050 > > Rendering Progress: 51 > Updating 1/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 1 > Rendering Progress: 51 > Update Success > > Updating 2/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 3 > Rendering Progress: 52 > Update Success > > Updating 3/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 3 > Rendering Progress: 52 > Update Success > > Updating 4/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 4 > Rendering Progress: 52 > Update Success > > Updating 5/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 5 > Rendering Progress: 52 > Update Success > > Updating 6/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 45 > Rendering Progress: 68 > Update Success > > Updating 7/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 59 > Rendering Progress: 74 > Update Success > > Updating 8/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 61 > Rendering Progress: 74 > Update Success > > Updating 9/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 99 > Rendering Progress: 89 > Update Success > > Updating 10/10 FwEntry... > Progress span of current phase: [51, 90]. Progress value within this span in (0-100 scale): 100 > Rendering Progress: 90 > Update Success > > Successfully synced all UEFI tables > Rendering Progress: 90 > > Phase 2 Done. Time (ms): 3190 > : Failed to get ResetPhase test hook data with error: Not Found > > Phase 3: FwEntry Post Update start. Time (ms): 3192 > > Rendering Progress: 91 > Deleting 1/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 2/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 3/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 4/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 5/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 6/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 7/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 8/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 9/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Deleting 10/10 FwEntry from backup device path... > Delete skipped as delete operation not applicable for this FwEntry...Continue > > Successfully synced all UEFI tables > Successfully synced all UEFI tables > Successfully synced all UEFI tables > Rendering Progress: 95 > > Phase 3 Done. Time (ms): 3230 > Successfully synced all UEFI tables > Successfully synced all UEFI tables > Firmware update completed successfully > Attempting to update SysFw Partition Entry > Copy to clipboard ## 删除大容量存储 capsule 文件 > > > - **日志条目**：删除 capsule 文件中的大容量存储：`capsule1.fv'!`。 > - **描述**：系统在成功完成固件更新后删除 capsule。 > - **日志文件**： > > > Writing updated SysFwVer details into SysFwVer partition... > > Current SysFwVersion Entry info: > ==================================== > Signature : 5245565746535953 > Revision : 0x10000 > VersionDataCrc32 : 0x1F2CFF54 > FwVersion : 0x30004 > LowestSupportedFwVersion : 0x0 > ==================================== > Successfully synced all UEFI tables > Updated SysFw Partition Entry > Platform: QCS6490 IOT > Selected FW GUID =: 6F25BFD2-A165-468B-980F-AC51A0A45C52 > Platform = 20 > Successfully synced all UEFI tables > Deleting mass-storage capsule file 'capsule1.fv'! > Starting to flush any pending persisted capsules from media > !!Warning!! Could not clear 'BootNext' variable after processing mass-storage capsules. Status - Not Found! > Write Log Buffer to FAT partition after capsule update failed, Status = (Unsupported) > > INFO: Received ResetSytem request. > INFO: Type :0x0 > INFO: DataSize :0x0 > > Start EBS [ 4674] > MDPLib: Halt vbif axi failed! > BDS: LogFs sync skipped, Unsupported > Successfully synced all UEFI tables > Sync Duration = 16 ms > Warning: Clearing A-bit ! > App Log Flush : 0 ms > ScmArmV8ExitBootServicesHandler, Status = 0x0. > Gunyah based bootup > Exit EBS [ 4719] UEFI End > > > UEFI Start [ 1587] > - 0x09FC01000 [ 1590] Sec.efi > ASLR : ON > DEP : ON (RTB) > Timer Delta : +0 mS > RAM Entry 0 : Base 0x0080000000 Size 0x003A800000 > RAM Entry 1 : Base 0x00C0000000 Size 0x0001800000 > RAM Entry 2 : Base 0x00C3400000 Size 0x003CC00000 > RAM Entry 3 : Base 0x0100000000 Size 0x0100000000 > Total Available RAM : 6028 MB (0x0178C00000) > Total Installed RAM : 6144 MB (0x0180000000) > Init CPU core 1 > > Scheduler up on Core 1 > UEFI Ver : 6.0.xxxx.xx.xxx.1.0.c1-xxx-xxxx-1 > Build Info : 64b Nov 5 2024 10:08:42 > Boot Device : UFS > PROD Mode : TRUE > Retail : TRUE > After Create Event Status (0x0) > ShmBridgeInitialize: enable status 0 > PM0: 47, PM1: 63, PM2: 49, PM8: 46, > Module cannot re-initialize DAL module environment > UFS INQUIRY ID: SAMSUNG KM2L9001CM-B518 0700 > UFS Boot LUN: 1 > tz_armv8_smc_call failed, TzStatus = 0xFFFFFFFF, SmcId = 0x32000105 > Status = 0x3 > APP_REGION_NOTIFICATION_CMD: Syscall Not Supported, status 3 > HW Wdog Setting from PCD : Disabled > QseeResponse->result = 0xE > Status = 0x7 > QseeResponse->result = 0xE > Status = 0x7 > QseeResponse->result = 0xE > Status = 0x7 > QseeResponse->result = 0xE > Status = 0x7 > LoadImageFromPartitionUsingGuid Failed: 14 > Failed to start featenabler_a TA, status = 14 > DisplayDxe: Resolution 1920x1080 (1 intf) > smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=3, size=32, flags=0x40000000.smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=12, size=32, flags=0x40000000.smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=17, size=32, flags=0x40000000.smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=18, size=32, flags=0x40000000.fast_core_num val: 0 > UsbConfigLibOpenProtocols: PMI version (0x0) > UsbConfigLibOpenProtocols: gPmicNpaClientHS2 cannot be created > UsbConfigInit: after setting role > UsbConfigInit: UsbConfigInit, not start on port: 0, mode 0 > UsbConfigInit: after setting role > UsbConfigInit: UsbConfigInit, not start on port: 1, mode 0 > UsbConfigPortsQueryConnectionChange: usbport->connectstate: ATT > ButtonsDxeTest: Keypress SDAM data payload 0 > HypDtFixupEntryPoint : Reading of OsConfigTableSelection failed,checking DT setting > Selected FW GUID =: 6F25BFD2-A165-468B-980F-AC51A0A45C52 > Platform = 20 > SoftSKUDxeInitialize: SoftSKU not supported for this chip > MinidumpTADxe: Minidump TA loading not enabled. > Disp init wait [ 1998] > ----------------------------- > Platform Init [ 2063] BDS > UEFI Ver : 6.0.xxx.xxx.xxx.1.0.c1-xxxx-xxxx-1 > Platform : IOT > Subtype : 2 > Boot Device : UFS > Chip Name : xxxxx > Chip Ver : 1.0 > Chip Serial Number : 0xDF4B18A2 > ----------------------------- > No pending capsules found in EFI Raw file > No pending capsules found in EFI\UpdateCapsule folder > LocateProtocol(DPP) returned Status:Not Found > Locate pMorPpiProtocol failed 0xE 00000010 > Platform Init End : 2219 > ----------------------------- > Compatible OS DTB found. Model = Qualcomm Technologies, Inc. Robotics RB3gen2 addons vision mezz platform > Reading of OsConfigTableSelection failed,checking DT settings > ERROR: DisableDisplay disabling,Status=0 > SdccDxeFixupEventNotifyFunc: non-removable node not found > Added qcom,platform-parts-info successfully in BoardInfoDxe > Failed to get SKU information. Unsupported > UEFI Total : 854 ms > POST Time [ 2441] OS Loader > systemd-boot@0x1c22e0000 254.4 > systemd-stub@0x1d1f80000 254.4 > EFI stub: Booting Linux Kernel... > EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path > EFI stub: Using DTB from configuration table > EFI stub: Exiting boot services... > Start EBS [ 2705] > BDS: LogFs sync skipped, Unsupported > App Log Flush : 0 ms > ScmArmV8ExitBootServicesHandler, Status = 0x0. > Gunyah based bootup > Copy to clipboard Last Published: May 13, 2025 [Previous Topic Linux 日志](https://docs.qualcomm.com/bundle/publicresource/80-70018-4SC/topics/hlos-logging.md) [Next Topic 调试场景示例](https://docs.qualcomm.com/bundle/publicresource/80-70018-4SC/topics/examples.md)