Unable to get USB working with Win10 IoT on MCIMX8M-EVKB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to get USB working with Win10 IoT on MCIMX8M-EVKB

520 Views
nkush3232
Contributor I

When we loaded the prebuilt Windows-10 IoT core on MCIMX8M-EVKB, USB ports are not working, thus we are unable to connect Keyboard/Mouse etc.


Board is booting and we can see different screens of the windows on HDMI display but as keyboard and mouse are not working, we cannot interact with windows.

Please help us to get USB working with Windows 10 on this board.. Please let us know the steps forward.


We are seeing below USB failure logs in U-Boot which shows that USB initialization is failing:


USB0: Failed to initialise board for imx8m USB
probe failed, error -62
USB1: Failed to initialize board for imx8m USB
probe failed, error -62
USB error: all controllers failed lowlevel init
Below are the full boot logs:
U-Boot SPL 2018.03 (Apr 15 2020 - 18:38:50 +0000)
PMIC: PFUZE100 ID=0x10
DDRINFO: start lpddr4 ddr init
DRAM PHY training for 3200MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 400MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 100MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DRAM PHY training for 3200MTS
check ddr4_pmu_train_imem code
check ddr4_pmu_train_imem code pass
check ddr4_pmu_train_dmem code
check ddr4_pmu_train_dmem code pass
Training PASS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC2
hab fuse not enabled
Authenticate image from DDR location 0x401fcdc0...
Error: CSF header command not found
I/TC:
I/TC: OP-TEE version: Unknown #1 Wed Apr 15 18:40:00 UTC 2020 aarch64
I/TC: Device Die ID = 0x1a0571d6
I/TC: Initialized
U-Boot 2018.03 (Apr 15 2020 - 18:38:50 +0000)
CPU: Freescale i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 46C
Reset cause: POR
Model: Freescale i.MX8MQ EVK
DRAM: 3 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x50]
MMC: FSL_SDHC: 0, FSL_SDHC: 1
No panel detected: default to HDMI
Display: HDMI (1280x720)
In: serial
Out: serial
Err: serial
BuildInfo:
- ATF
- U-Boot 2018.03
Net: Warning: ethernet@30be0000 using MAC address from ROM
eth0: ethernet@30be0000
Normal Boot
Initializing 4KB of memory at 0x00000000407e9000 as the global page.
Stashed ethaddr = 9e:c6:06:9f:04:00
starting USB...
USB0: Failed to initialize board for imx8m USB
probe failed, error -62
USB1: Failed to initialize board for imx8m USB
probe failed, error -62
USB error: all controllers failed lowlevel init
hab fuse not enabled
Authenticate image from DDR location 0x40480000...
bad magic magic=0x0 length=0x00 version=0x0
bad length magic=0x0 length=0x00 version=0x0
bad version magic=0x0 length=0x00 version=0x0
Error: Invalid IVT structure
Allowed IVT structure:
IVT HDR = 0x4X2000D1
IVT ENTRY = 0xXXXXXXXX
IVT RSV1 = 0x0
IVT DCD = 0x0
IVT BOOT_DATA = 0xXXXXXXXX
IVT SELF = 0xXXXXXXXX
IVT CSF = 0xXXXXXXXX
IVT RSV2 = 0x0
## Loading kernel from FIT Image at 40480000 ...
Using 'conf-1' configuration
Trying 'uefi' kernel subimage
Description: UEFI
Type: Kernel Image
Compression: uncompressed
Data Start: 0x404800a4
Data Size: 2064384 Bytes = 2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x50004000
Entry Point: 0x50004000
Hash algo: sha256
Hash value: 02ed2479ea65b476b4520a01dc25446e0a6fa5fb43524da190f99ab765ad6251
Verifying Hash Integrity ... sha256+ OK
Loading Kernel Image ... OK
Starting kernel ...
UEFI Debug Serial Port Init
UEFI firmware (version built at 18:42:22 on Apr 15 2020)
#??KDTARGET: Refreshing KD connectiontemRoot\system32\ntoskrnl.exeª0000_02?Xøÿÿ_÷Wøÿÿ"÷Wøÿÿÿÿÿÿt|
#??KDTARGET: Refreshing KD connectionª0000_02
#??KDTARGET: Refreshing KD connectionª0000_02
#??KDTARGET: Refreshing KD connectionª0000_02
#??KDTARGET: Refreshing KD connectionª0000_02

 

Introduction to USB Type-C and Type-C Solutions from NXP @yangtian 

0 Kudos
0 Replies