Windows IoT not boot on NXP's i.mx8m plus board

ChrisChang 40 Reputation points
2023-09-25T10:13:39.0833333+00:00

I am trying to boot Win10 IoT core version 1809 on my NXP iMX8 plus board.

It works properly on NXP's kit,

but on my board, I tired to install the Win10 IoT via SD card,

it stuck when the windows logo shows.

And the output information is few via the USB to serial port.

After a time, the system reboots automatically.

Pls help.

The following is the log ..


U-Boot SPL 2022.04-00001-g4c1d7632a4-dirty (Sep 25 2023 - 16:34:03 +0800)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0:  RNG instantiated
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE:  BL31: v2.6(release):automotive-13.0.0_1.1.0-1-g40dc2ce18
NOTICE:  BL31: Built : 16:34:22, Sep 25 2023


U-Boot 2022.04-00001-g4c1d7632a4-dirty (Sep 25 2023 - 16:34:03 +0800)

CPU:   i.MX8MP[8] rev1.1 1600 MHz (running at 1200 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 37C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 EVK board
DRAM:  4 GiB
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port2 init failed, err=-19
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port1 init failed, err=-19
Core:  189 devices, 29 uclasses, devicetree: separate
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

	[0] lcd-controller@32e80000, video
	[1] mipi_dsi@32e60000, video_bridge
	[2] adv7535@3d, panel
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19
In:    serial
Out:   serial
Err:   serial
SEC0:  RNG instantiated

 BuildInfo:
  - ATF 40dc2ce

switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
GPT: last_usable_lba incorrect: 38A77DE > 1d7f800
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
Net:   
Warning: ethernet@30bf0000 (eth1) using random MAC address - 2a:3b:42:31:52:24

Warning: ethernet@30be0000 (eth0) using random MAC address - 6a:56:dd:58:51:63
eth0: ethernet@30be0000, eth1: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Normal Boot
starting USB...
Bus usb@38100000: Failed to initialize board for imx8m USB
probe failed, error -22
Bus usb@38200000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@38200000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
## Loading kernel from FIT Image at 40480000 ...
   Using 'conf-1' configuration
   Verifying Hash Integrity ... OK
   Trying 'uefi' kernel subimage
     Description:  UEFI
     Created:      2023-09-25   8:36:10 UTC
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x404800a4
     Data Size:    539665 Bytes = 527 KiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x50004000
     Entry Point:  0x50004000
     Hash algo:    sha256
     Hash value:   0bb9974f5364eaf73a17880f2668a57319942d300a2fb5ef5c8b76bee71af6bd
   Verifying Hash Integrity ... sha256+ OK
   Uncompressing Kernel Image
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

Starting kernel ...


UEFI Debug Serial Port Init
UEFI firmware (version 2020-06-07 built at 16:35:59 on Sep 25 2023)
Tianocore/EDK2 firmware version 2020-06-07
Press ESCAPE for boot options 0000嘺10;s?	:? >_*SystemRoot\system32\ntoskrnl.exe000嘺10;s?	:? >_*SystemRoot\system32\ntoskrnl.exe000嘺10;s?	:? >_*SystemRoot\system32\ntoskrnl.exe000嘺10;s?	:? >_*SystemRoot\system32\ntoskrnl.exe000嘺10;s?	:? >_*SystemRoot\system32\ntoskrnl.exe000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_0000噰00@GP:鴟斁>_
Windows for IoT
Windows for IoT
A family of Microsoft operating systems designed for use in Internet of Things (IoT) devices.
381 questions
0 comments
Accepted answer
  1. Limitless Technology 43,966 Reputation points
    2023-09-26T11:19:40.7966667+00:00

    Hello ChrisChang,

    I can see different errors in the log file. I will try to address one by one. If the issues persist, I would recommend to contact NXP support, as they can offer a more experienced point of view for these issues from the board hardware and firmware perspective.

    1. The log shows several errors related to display initialization. These errors suggest that there might be an issue with the display or graphics configuration on your board. Ensure that your display hardware is correctly connected and supported by the Windows 10 IoT Core version you are using.

    Step in log:

    adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c

    fail to probe panel device adv7535@3d

    fail to get display timings

    probe video device failed, ret -19

    1. There are also USB initialization errors. USB initialization issues could affect the system's ability to load necessary drivers and peripherals. Verify that USB devices, including any bootable USB drives, are properly connected.

    Step in log:

    Bus usb@38100000: Failed to initialize board for imx8m USB

    probe failed, error -22

    1. The log mentions UEFI firmware version 2020-06-07. Ensure that your UEFI firmware is up-to-date with the latest version provided by NXP for your specific board model. This can help fix compatibility issues.
    2. The log shows the message "Press ESCAPE for boot options." Ensure that you are not inadvertently selecting an incorrect boot option. Check the UEFI boot menu for available boot options and select the appropriate one for your setup.
    3. Ensure that your NXP i.MX8 Plus board is fully compatible with the specific version of Windows 10 IoT Core you are trying to install. Sometimes, hardware-specific drivers or configurations are required.

    --If the reply is helpful, please Upvote and Accept as answer--

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest