Windows 10 IoT Enterprise USB UUU Download

[okuda]

I am using the 8MMINILPD4-EVK board to run the "2.5.1 Firmware on eMMC" described in i.MX_Win10_User's_Guide.pdf.

The DIP SW of the board is set as follows.

                 1      2      3      4     5      6     7      8      9      10

SW1101  ON   OFF ON  OFF ON  ON OFF OFF ON  OFF

SW1102  OFF OFF OFF ON  OFF ON OFF ON  OFF OFF

uuu.exe is copied to win10-iot-bsp\imx-windows-iot\BSP\firmware\tools\uuu.
（<BSP_DIR> is set to win10-iot-bsp.）

When you connect the USB micro-B port on the board to your PC, PC will recognize the two com ports.(Attached image: serialport.png)

In this state, execute "flash_bootloader.cmd / device NXPEVK_iMX8M_Mini_2GB" from the win10-iot-bsp\imx-windows-iot\BSP\firmware folder.

As a result, it looks like the attached image flashbootloadercmd.png and it is not processed normally.

１．What causes this result?
２．How can I get it to work properly?

[michal_hromadka]

It sometimes happens. Try to reset board by button and run the script again until done correctly (as in attached image). If you set the switches to boot from eMMC without previous successful download the board probably does not boot properly.

Note: If you let the USB micro-B connected to board you can check debug log by terminal connected to COM ports with baudrate 921 600 Bd. 

[okuda]

Dear Michal,

I was running it on Windows 10 in a virtual environment, so it seems that it did not complete normally.
When I execute the command on a normal PC, it looks like the attached image ok.png.
The debug log at that time is the attached image debuglog_ok.png.

From the two attached images, is it safe to assume that the command has completed normally?

After that, I changed the DipSW setting of the board to eMMC boot.
I created an SD card according to the contents described in "2.6.1 Preparing WinPE based installation media on a microSD card" of i.MX_Win10_User's_Guide.pdf.
I inserted the created SD card into the board and turned on the power.
The blue letters are the debug log at that time.

U-Boot SPL 2021.04-00442-g6efff2a47b (Jun 23 2022 - 18:55:24 +0000)
Can't find PMIC:PCA9450
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 MMC2
NOTICE: BL31: v2.4(release):lf-5.10.72-2.2.0-4-g24ddf8f9a
NOTICE: BL31: Built : 18:55:44, Jun 23 2022

U-Boot 2021.04-00442-g6efff2a47b (Jun 23 2022 - 18:55:24 +0000)

CPU: i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 44C
Reset cause: POR
Model: NXP i.MX8MM EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
SEC0: RNG instantiated

BuildInfo:
- ATF 24ddf8f

switch to partitions #0, OK
mmc2(part 0) is current device
flash target is MMC:2
Net: eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
starting USB...
Bus usb@32e40000: Port not available.
switch to partitions #1, OK
mmc2(part 1) is current device

MMC read: dev # 2, block # 3946, count 4096 ... 4096 blocks read: OK
## Loading kernel from FIT Image at 40480000 ...
Using 'conf-1' configuration
Trying 'uefi' kernel subimage
Description: UEFI
Created: 2022-06-23 18:58:22 UTC
Type: Kernel Image
Compression: uncompressed
Data Start: 0x404800a4
Data Size: 2064384 Bytes = 2 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x50004000
Entry Point: 0x50004000
Hash algo: sha256
Hash value: e3992b8009f95609b1370241cf243c999304b8cab6ce777ff7e01c728e2e0e0d
Verifying Hash Integrity ... sha256+ OK
Loading Kernel Image

Starting kernel ...

UEFI Debug Serial Port Init
UEFI firmware (version 2020-02 built at 18:58:05 on Jun 23 2022)

（Line breaks continue for a while）

Tianocore/EDK2 firmware version 2020-02
Press ESCAPE for boot options

1.Can you judge from the debug logs so far that it is working properly?
2."Press ESCAPE for boot options" is output. Do I need to connect a keyboard?
3.If I connect a USB keyboard to the USB connector type C on the board, will I be able to enter the 　ESCAPE key?
4.If you don't have a USB keyboard that can connect to the USB connector Type C, is there a 　workaround?
5.If the escape key can be entered, will writing of Windows 10 IoT Enterprise to eMMC start?

Thanks.
Best regards,
Koji Okuda.

[michal_hromadka]

Hello @okuda ,

This debug log looks in order. So, windows should be boot immediately (without any keyboard interaction). How do you have LCD connected to the board?
For peripheral connection you could use USB Type-C to A Adapter from EVK box or some USB Type-C switch/hub.

Regards,

Michal

[okuda]

Dear Michal

The LCD is connected to the HDMI I / F display panel as shown in the attached image.(LCD_IF.jpg)
When I connected the display panel, the display panel was displayed like an attached image.（LCD_Display.jpg）

What is the cause of the following?

1.Do you think the SD card was created correctly?
2.Is it okay to assume that the firmware was written correctly to the eMMC?
3..Are the steps I'm taking correct?
4.The Linux boot environment was written to eMMC, do I need to clear it?
　（If it is better to delete it, please tell me how to delete it.）

Thanks.
Best regards,
Koji Okuda.

[michal_hromadka]

Hello @okuda ,

did you try to create SD card containing Windows IoT image and Boot firmware and then boot from SD? Could you send version of the board (2 labels on backside - e.g. SCH-12345 REV A1 and 700-12345-REV A1)? 

Regards,

Michal

[okuda]

Dear Michal,

As you can see by referring to the attached image SDCard_Info.png, the cause is that the name of the ”efi” folder on the SD card has been changed to the ”_efi” folder due to the interruption of the installation.

By renaming it to the ”efi” folder, the installation can be started normally.

Thanks.
Best regards,
Koji Okuda.

[okuda]

Dear Michal,

I am using an SD card created according to "2.6 Install Windows IOT Enterprise to eMMC" in i.MX_Win10_User's_Guide.pdf.
Actually, it is created by executing the following command.
(Attached image SDCard_Info.png is the information of the SD card created by the following command.)
However, as inquired in another case "Windows 10 IoT Enterprise for i.MX Driver", the driver build has not been completed.
(W21H2-1-1-0-imx-windows-bsp.zip has been decompressed.See attached image IotEntOnNXP.png)

 make-winpe-enterprise.cmd /device NXPEVK_iMX8M_Mini_2GB /disable_updates                 /disable_transparency /image ..\install.wim

 make-winpe-enterprise.cmd /device NXPEVK_iMX8M_Mini_2GB /apply 1

Attached image Board.png is an image of the back side of the board.

Thanks.
Best regards,
Koji Okuda.

[okuda]

Dear Michal

I got the debug log, so I will attach the image.

Can you tell what the cause is from the attached log?

Thanks.
Best regards,
Koji Okuda.

[michal_hromadka]

Hello @okuda ,

You have to use USB Type C (marked as Download) located between USB micro-B port and USB Power port.

Regards,

Michal

[okuda]

Dear Michal,

As you answered, I connected the board and the PC, and when I ran it, it looked like the attached image.

As soon as the display reaches 100%, the USB connection will be automatically disconnected.

The command prompt remains in the attached image state and is not ready for input.

１．Is this normal?
２．If it is not normal, what should I do?
３．If I set the DIPSW setting to eMMC boot and boot eMMC, can I confirm that it completed normally?

Thanks.
Best regards,
Koji Okuda.