device not booting up on QCS615

[Vkenjam]

Talos device not booting up with tip of meta-qcom build.

Status = 0x3
APP_REGION_NOTIFICATION_CMD: Syscall Not Supported, status 3
HW Wdog Setting from PCD : Disabled
smem_alloc_ex: SMEM alloc_ex failed with err=-3! smem_type=478, remote=3, size=32, flags=0x40000000.UsbPwrCtrlLibConfig_GetHWInfo Hardware Info is not available 
UsbPwrCtrlLib_Init Initialize Hardware Configuration Error[Device Error] 
UsbConfigLibOpenProtocols: PMI8998 not detected
UsbConfigrm Init  [ 1428] BDS
UEFI Ver   : 6.0.251213.BOOT.MXF.1.0.c1-00430-KODIAKLA-1
Platform           : ADP
Subtype            : 3
Boot Device        : UFS
Chip Name          : SA6155P
Chip Ver           : 1.1
Chip Serial Number : 0xDE0A2FFD
ufs_error_log: 252
RPMB ReadCounterPkt failed, Result = 6
-----------------------------
QcomChargerApp:: QcomChargerApp_Entry Can not locate Charger Protocol = Not Found 
Failed to launch default charger app, status: Device Error
MountRequiredFatPartitions: OsTrialBootStatus read failed, status = 0xE
EFI GUID based mount Success, GUID = C12A7328-F81F-11D2-BA4B-00A0C93EC93B Status = Success
TransitionNhlosFromPostUpdateToBoot: Starting NHLOS state transition validation
TransitionNhlosFromPostUpdateToBoot: Failed to read OsTrialBootStatus. Status 0xE
ClearCapsuleNV: GetVariable Returned Status - Not Found
No pending capsules found in EFI Raw file
Looking for 'BootNext' variable to look for EFI partition with mass-storage capsules
No 'BootNext' variable found td: 0x3
PackageId: 0x0
 ProcessQcomMetaDtbBoardSubTypePeripheralSubTypeNode: Board Param:
BoardSubTypeId = 0x3
 ProcessQcomMetaDtbBoardSubTypePeripheralSubTypeNode: Node subtype3 From fdt BoardSubTypeId = 3
 ProcessQcomMetaDtbBoardSubTypeStorageSubTypeNode: Board Param:
BootDeviceType = 0x1
 ProcessQcomMetaDtbBoardSubTypeStorageSubTypeNode: Node emmc From fdt StorageTypeId = 1
 ProcessQcomMetaDtbBoardMemorySizeNode:Board Param:
Ddr Size = 0
 ProcessQcomMetaDtbBoardMemorySizeNode: Node 4GB+ From fdt DdrSizeId = 0
 ProcessQcomMetaDtbSoftSkuNode: Board Param: Board SoftSkuId = 0
 ProcessQcomMetaDtbSoftSkuNode: Node softsku0 SoftSkuId = 0
GetVariable failed to get size: Not Found, skipping RT Overlay
 ParseFitDt: Configuration From BoardParam
qcom, adp, sku0, subtype3, emmc, 4GB+, softsku0, 
 FindConfigToBoot: SubNode 508 And Node Name conf-1 Len = 6
FindConfigToBoot: Invalid Configuration ConfigFdt "qcom,qcs615-adp"
 FindConfigToBoot: CompatibleMatchFlag = 0 CurrSubStringCnt = 1
 ParseFitDt: Cannot find correct config to boot, Falling to default config
 ParseFitDt:Loading default FIT Config
LoadDtbOnReadyToBoot OS DTB Matching failed with Status = 1
DtPlatformLoadDtbBlob Checking for secondary-dtb.dtb
DtPlatformLoadDtbBlob secondary-dtb.dtb load failed with status = E
DtPlatformLoadDtbBlob Checking for default-upstream-dtb.dtb
Reading of OsConfigTableSelection failed,checking DT settings
 CryptoDxeFixupEventNotifyFunc: mmc node=/soc@0/crypto@7c8000 not found in device tree
Bad main_symbols in ufdt_overlay_do_fixups
Failed to apply devie tree
HypDtFixupEventNotifyFunc: Dtb apply overlay skipped
SdccUpdateDtStatusFlag: Could not find eMMC node 
SdccDxeFixupEventNotifyFunc: Disabled eMMC (dual storage not supported)
Added qcom,platform-parts-info successfully in BoardInfoDxe
Failed to get SKU information. Unsupported
reserved-memory node not found in device tree
 GetNoMapRegions failed!!!
UEFI Total : 543 ms
POST Time      [ 1608] OS Loader
EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
Start EBS        [ 2136] 
From UEFI DT BootFromNvme  0x0
BDS: LogFs sync skipped, Unsupported
App Log Flush : 0 ms
Gunyah based bootup
Exit EBS        [ 2151] UEFI End

[lumag]

I assume, it is QCS615 Ride. In such a case, could you please try reverting b6d483f?

CC @vkraleti

[vkraleti]

@Vkenjam @bhargav0610 Logs indicate the device in use is SA6145P (ChipId: 0x179). This not a supported configuration. For QCS615, ChipId is supposed to be 0x2a8. Please check with Kernel and Product teams if this device need to be supported. If so, please get the qcom-dtb-metadata updated with this Chip info. If not please swap devices in test bed.