Installing a Windows IoT Image on your F&S Board
The typical way to install Windows IoT LTSC is to create a bootable SD card and then copy the F&S Windows installation files onto the SD card. Once the files are on the SD card, you can insert it into the F&S board, and it will automatically boot/install from the SD card. Very simple.
Software/Hardware Requirements
- SD card with at least 8 GB of storage
- Software package with the Windows IoT image
- F&S board with an iMX8MP processor and at least 2 GB of RAM
- Connected display to monitor the installation process
Creating a Bootable SD Card
First, the SD card must be prepared for the Windows IoT operating system. Follow these steps:
1. Start `diskpart` in the administrative command prompt:
2. List all disks:
Output should be similar to this:
3. Select the correct disk for the SD card (in this example, disk 1):
4. Enter the following commands:
Now the SD card is fully formatted!
Deploy Software Package on SD card
The final SD card content with the Windows 10 IoT LTSC operating system for installation is available on our file share. To access this content, you need to register on our F&S Homepage and provide a Windows IoT module serial number to unlock the files. If you have any further questions, please feel free to contact us at support@fs-net.de.
To proceed, copy the contents of the 'SDiMX8MP_WIN10_VXXX' folder to the root of the SD card. You can use File Explorer to manually copy the files.
Finally, insert the SD card and reboot the F&S board. That completes the installation!
(FYI: Installing Windows IoT Enterprise from the SD card takes approximately 15 minutes. During the installation process, your device will restart a few times, so don't be alarmed)
IMPORTANT:
The WinPE installer renames the EFI folder at the root of the SD card to _efi, which causes UEFI to skip the SD card at boot time. This allows you to keep the SD card inserted across reboots without having Windows IoT reinstalled on each reboot. If you wish to boot into the WinPE installer again, you can rename _efi back to EFI.