Win10 IoT core pre-built FFU from NXP portal not properly booting on iMX6 SoloX

[sriramgv]

Hi NXP Community,

Iam not able to boot my IMX6 SoloX Sabre Board using the NXP's pre-built Win10 IoT core FFU image. Can anybody help please !

To add details, U-boot is coming up upto UEFI firmware, but there it is failing..Below is the Serial port debug log...

===============================

U-Boot SPL 2018.09 (Apr 22 2020 - 10:07:10 +0000)
RNG: Instantiation failed with error 0x2000025b
RNG: Instantiation failed with error 0x2000025b
RNG: Instantiation failed with error 0x2000025b
SEC0: RNG instantiated
CAAM not secure/trusted; OTPMK inaccessible
SPL: CyRes cdi failed
Trying to boot from MMC1
port 3
## Checking hash(es) for Image optee ... sha256+ OK
## Checking hash(es) for Image uboot ... sha256+ OK
I/TC:
I/TC: OP-TEE version: Unknown #1 Wed Apr 22 10:03:43 UTC 2020 arm
E/TC:0 0 plat_rng_init:354 Warning: seeding RNG with zeroes
I/TC: Initialized

U-Boot 2018.09 (Apr 22 2020 - 10:07:10 +0000)

CPU: Freescale i.MX6SX rev1.4 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 41C
Reset cause: POR
Model: Freescale i.MX6 SoloX SDB RevB Board
Board: MX6SX SABRE SDB revD
DRAM: 1 GiB
PMIC: PFUZE100! DEV_ID=0x11 REV_ID=0x21
MMC: FSL_SDHC: 1, FSL_SDHC: 2, FSL_SDHC: 3
Loading Environment from MMC... *** Warning - bad CRC, using default environment

No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
Video: 1024x768x18
In: serial
Out: serial
Err: serial
Net: FEC [PRIME], FEC1
Initializing 4KB of memory at 0x82003000 as the global page.
Stashed ethaddr = f0:a2:05:9f:04:00
Stashed eth1addr = f1:a2:05:9f:04:00
1902297 bytes read in 100 ms (18.1 MiB/s)
## Loading kernel from FIT Image at 80a20000 ...
Using 'conf-1' configuration
Verifying Hash Integrity ... OK
Trying 'uefi' kernel subimage
Description: UEFI
Type: Kernel Image
Compression: uncompressed
Data Start: 0x80a200a4
Data Size: 1900544 Bytes = 1.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x82004000
Entry Point: 0x82004000
Hash algo: sha256
Hash value: 3326310e69bbc9bd2d14dc3905a532d09362eda43b967c71f2cfe812fac826dd
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 80a20000 ...
Using 'conf-1' configuration
Verifying Hash Integrity ... OK
Trying 'fdt-1' fdt subimage
Description: blank-dtb
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x80bf0194
Data Size: 72 Bytes = 72 Bytes
Architecture: ARM
Hash algo: sha256
Hash value: 4ee48e5ae650ede0b5a3548a1fd60e8aea0e71750ea43f8276ceafcd7cb091e0
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x80bf0194
Loading Kernel Image ... OK
Using Device Tree in place at 80bf0194, end 80bf31db

Starting kernel ...

UEFI firmware (version built at 10:04:43 on Apr 22 2020)
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll /reloc .text at 0xBFA2B000 /nocode /noclear
Loading DxeCore at 0x00BFA2A000 EntryPoint=0x00BFA31441
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll /reloc .text at 0xBFA2B000 /nocode /noclear
HOBLIST address in DXE = 0xBEDE4010
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/PCD/Dxe/Pcd/DEBUG/PcdDxe.dll /reloc .text at 0xBEF70000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Acpi/AcpiTableDxe/AcpiTableDxe/DEBUG/AcpiTableDxe.dll /reloc .text at 0xBEF69000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/SmbiosDxe/SmbiosDxe/DEBUG/SmbiosDxe.dll /reloc .text at 0xBEF62000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Core/RuntimeDxe/RuntimeDxe/DEBUG/RuntimeDxe.dll /reloc .text at 0xBEF9A000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/SecurityStubDxe/SecurityStubDxe/DEBUG/SecurityStubDxe.dll /reloc .text at 0xBEF1A000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/ArmPkg/Drivers/ArmGic/ArmGicDxe/DEBUG/ArmGicDxe.dll /reloc .text at 0xBEF14000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/SerialDxe/SerialDxe/DEBUG/SerialDxe.dll /reloc .text at 0xBEF0F000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/EmbeddedPkg/SimpleTextInOutSerial/SimpleTextInOutSerial/DEBUG/SimpleTextInOutSerial.dll /reloc .text at 0xBEF09000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/EmbeddedPkg/ResetRuntimeDxe/ResetRuntimeDxe/DEBUG/Reset.dll /reloc .text at 0xBEF95000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/EmbeddedPkg/RealTimeClockRuntimeDxe/RealTimeClockRuntimeDxe/DEBUG/RealTimeClock.dll /reloc .text at 0xBEF8F000 /nocode /noclear
InitializeRealTimeClock: using default timezone/daylight settings
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/EmbeddedPkg/MetronomeDxe/MetronomeDxe/DEBUG/MetronomeDxe.dll /reloc .text at 0xBEF03000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Platform/Microsoft/Drivers/SdMmcDxe/SdMmcDxe/DEBUG/SdMmcDxe.dll /reloc .text at 0xBEEF4000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMXPlatformPkg/Drivers/SdhcDxe/SdhcDxe/DEBUG/SdhcDxe.dll /reloc .text at 0xBEEED000 /nocode /noclear
SDHC2:Error detected
SDHC2:WaitForCmdResponse() failed. Device Error
SdMmc[E]:HostExt->SendCommand( CMD8, 0x000001AA) failed. Device Error (SdhcSendCommandHelper: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 408)
SdMmc[E]:Send no-data command failed. Device Error (SdhcSendCommand: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 453)
SDHC2:Error detected
SDHC2:WaitForCmdResponse() failed. Device Error
SdMmc[E]:HostExt->SendCommand( CMD5, 0x00000000) failed. Device Error (SdhcSendCommandHelper: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 408)
SdMmc[E]:Send no-data command failed. Device Error (SdhcSendCommand: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 453)
SDHC2:Error detected
SDHC2:WaitForCmdResponse() failed. Device Error
SdMmc[E]:HostExt->SendCommand( CMD1, 0x40FF8000) failed. Device Error (SdhcSendCommandHelper: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 408)
SdMmc[E]:Send no-data command failed. Device Error (SdhcSendCommand: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 453)
SdMmc[E]:SdhcQueryCardType() failed. No Media (InitializeDevice: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 75)
SdMmc[E]:SoftReset(): InitializeDevice() failed. No Media (SoftReset: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/SdMmc.c, 542)
SdMmc[E]:SoftReset() failed. No Media (CheckCardsCallback: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/SdMmc.c, 736)
SDHC4:Error detected
SDHC4:WaitForCmdResponse() failed. Device Error
SdMmc[E]:HostExt->SendCommand( CMD5, 0x00000000) failed. Device Error (SdhcSendCommandHelper: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 408)
SdMmc[E]:Send no-data command failed. Device Error (SdhcSendCommand: /win10-bsp/imx-edk2-platforms/Platform/Microsoft/Drivers/SdMmcDxe/Protocol.c, 453)
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/DevicePathDxe/DevicePathDxe/DEBUG/DevicePathDxe.dll /reloc .text at 0xBEEE1000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/HiiDatabaseDxe/HiiDatabaseDxe/DEBUG/HiiDatabase.dll /reloc .text at 0xBEECA000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe/DEBUG/VariableRuntimeDxe.dll /reloc .text at 0xBEF84000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Acpi/AcpiPlatformDxe/AcpiPlatformDxe/DEBUG/AcpiPlatform.dll /reloc .text at 0xBEEC5000 /nocode /noclear
remove-symbol-file /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Acpi/AcpiPlatformDxe/AcpiPlatformDxe/DEBUG/AcpiPlatform.dll 0xBEEC5000
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/ArmPkg/Drivers/CpuDxe/CpuDxe/DEBUG/ArmCpuDxe.dll /reloc .text at 0xBEEC2000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/CapsuleRuntimeDxe/CapsuleRuntimeDxe/DEBUG/CapsuleRuntimeDxe.dll /reloc .text at 0xBEF7E000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/MonotonicCounterRuntimeDxe/MonotonicCounterRuntimeDxe/DEBUG/MonotonicCounterRuntimeDxe.dll /reloc .text at 0xBEF79000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMX6Pkg/Drivers/TimerDxe/TimerDxe/DEBUG/iMX6TimerDxe.dll /reloc .text at 0xBEEBC000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/SetupBrowserDxe/SetupBrowserDxe/DEBUG/SetupBrowser.dll /reloc .text at 0xBEEA8000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/BdsDxe/BdsDxe/DEBUG/BdsDxe.dll /reloc .text at 0xBEE95000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Platform/NXP/Sabre_iMX6SX_1GB/Drivers/GraphicsOutputDxe/GraphicsOutputDxe/DEBUG/Imx6sxGraphicsOutputDxe.dll /reloc .text at 0xBEE8F000 /nocode /noclear
FbSize = 300000
Framebuffer = 821D4000
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/WatchdogTimerDxe/WatchdogTimer/DEBUG/WatchdogTimer.dll /reloc .text at 0xBEE8A000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMX6Pkg/Drivers/PciExpress/iMX6PciExpress/DEBUG/iMX6PciExpress.dll /reloc .text at 0xBEE83000 /nocode /noclear
iMX6PCIe:Pci link never came up
iMX6PCIe:Failed to initialize Pcie, disabling controller
remove-symbol-file /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMX6Pkg/Drivers/PciExpress/iMX6PciExpress/DEBUG/iMX6PciExpress.dll 0xBEE83000
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe/DEBUG/DisplayEngine.dll /reloc .text at 0xBEE78000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Console/ConPlatformDxe/ConPlatformDxe/DEBUG/ConPlatformDxe.dll /reloc .text at 0xBEE71000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Console/ConSplitterDxe/ConSplitterDxe/DEBUG/ConSplitterDxe.dll /reloc .text at 0xBEE68000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsoleDxe/DEBUG/GraphicsConsoleDxe.dll /reloc .text at 0xBEE60000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Console/TerminalDxe/TerminalDxe/DEBUG/TerminalDxe.dll /reloc .text at 0xBEE57000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Disk/DiskIoDxe/DiskIoDxe/DEBUG/DiskIoDxe.dll /reloc .text at 0xBEE50000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Disk/PartitionDxe/PartitionDxe/DEBUG/PartitionDxe.dll /reloc .text at 0xBEE47000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/FatPkg/EnhancedFatDxe/Fat/DEBUG/Fat.dll /reloc .text at 0xBEE3C000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/MdeModulePkg/Universal/Disk/UnicodeCollation/EnglishDxe/EnglishDxe/DEBUG/EnglishDxe.dll /reloc .text at 0xBEE37000 /nocode /noclear

Press ESCAPE for boot options Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMXPlatformPkg/Drivers/SmbiosConfigDxe/SmbiosConfigDxe/DEBUG/SmbiosConfigDxe.dll /reloc .text at 0xBEE32000 /nocode /noclear
Data.load.elf /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMX6Pkg/Drivers/PlatformSmbiosDxe/PlatformSmbiosDxe/DEBUG/PlatformSmbiosDxe.dll /reloc .text at 0xBEE2B000 /nocode /noclear
SysInfoUpdateSmbiosType1: PcdSystemManufacturer not filled
remove-symbol-file /win10-bsp/Build/Sabre_iMX6SX_1GB/RELEASE_GCC5/ARM/Silicon/NXP/iMX6Pkg/Drivers/PlatformSmbiosDxe/PlatformSmbiosDxe/DEBUG/PlatformSmbiosDxe.dll 0xBEE2B000
ConvertPages: failed to find range 10000000 - 10145FFF
Data.load.elf bootmgfw.pdb /reloc .text at 0xBBADD400 /nocode /noclear
ConvertPages: failed to find range 102000 - 102FFF
000L]10(éÿÿÿÿ±©Ãÿÿÿÿ"ÐÀÿÿÿÿÿÿÿÿåW`_h<wP?ñ!0(é¼4/þÿÿÿØ
jüuP??h<w(‘ÞÌå(‘ÞÌåpÚä É
åH?%N¼4/³ ÞpGOð
Ðè#ÀèqÌ\SystemRoot\system32\ntoskrnl.exeª000L]10(éÿÿÿÿ±©Ãÿÿÿÿ"ÐÀÿÿÿÿÿÿÿÿåW`_h<wP?ñ!0(é¼4/þÿÿÿØ
jüuP??h<w(‘ÞÌå(‘ÞÌåpÚä É
åH?%N¼4/³ ÞpGOð
Ðè#ÀèqÌ\SystemRoot\system32\ntoskrnl.exeª000L]10(éÿÿÿÿ±©Ãÿÿÿÿ"ÐÀÿÿÿÿÿÿÿÿåW`_h<wP?ñ!0(é¼4/þÿÿÿØ
jüuP??h<w(‘ÞÌå(‘ÞÌåpÚä É
åH?%N¼4/³ ÞpGOð
Ðè#ÀèqÌ\SystemRoot\system32\ntoskrnl.exeª000L]10(éÿÿÿÿ±©Ãÿÿÿÿ"ÐÀÿÿÿÿÿÿÿÿåW`_h<wP?ñ!0(é¼4/þÿÿÿØ
jüuP??h<w( Ìå(‘ÞÌåpÚä É
åH?%N¼4/³ ÞpGOð
Ðè#ÀèqÌ\SystemRoot\system32\ntoskrnl.exeª000L]10(éÿÿÿÿ±©Ãÿÿÿÿ"ÐÀÿÿÿÿÿÿÿÿåW`_h<wP?ñ!0(é¼4/þÿÿÿØ
jüuP??h<w(‘ÞÌå(‘ÞÌåpÚä É
åH?%N¼4/³ ÞpGOð
Ðè#ÀèqÌ\SystemRoot\system32\ntoskrnl.exeª0000ç
02
#KDTARGET: Refreshing KD connection
ª0000ç
02
#KDTARGET: Refreshing KD connection

[AldoG]

Hello,

Do you see anything on your LCD?

The default for the i.MX6SX should be LVDS (J12)

If you're able to see windows dashboard then it is booting correctly.

Or could you try to check if you are able to connect to board via Windows Device Portal? (Windows Device Portal - Windows IoT | Microsoft Docs )

Thank you,

Best regards,

Aldo.

[sriramgv]

Thanks for the response. I understood the problem myself. Actually the booting is happening properly, but the serial output messages donot show that. The appropriate serial messages are not posted to serial output by the source code.

But, when the imX6 Solox eval board is connected thru ethernet cable to host PC, the board shows up in the Windows Dashboard tool on "My Devices" section.

So the point is, for NXP's Win10 IoT core, ethernet cable need to be connected and not the serial USB cable.