03 Feb 2016
Installing Windows 10 IoT on the Open-Q™ 410 Development Kit
This blog entry will provide a step-by-step guide to allow you to install and run Windows 10 IoT core on your Open-Q 410 Development Kit. Many of these steps are supplied courtesy of Microsoft. I’ve added and modified as necessary for the Intrinsyc Open-Q 410 Development Kit.
Install the Dragonboard update Tool
- Download the DragonBoard™ 410c Update Tool from the Qualcomm Developer Network by selecting the download link appropriate for your PC: x86 or x64
- Right click on the downloaded zip file and select extract all. This will create a new folder with the same names the downloaded zip file.
- Open the folder and double-click the setup.exe file.
- Follow the instructions and when prompted allow the USB driver to install by clicking “install”.
- The installer will create a shortcut to the DragonBoard 410c Update Tool on your desktop and in your start menu, under Qualcomm->DragonBoardUpdate Tool.
Download the DragonBoard Win10 IoT Core Image
- Download a Windows 10 IoT Core image from the Microsoft downloads page. You will need to sign in (or create) your Microsoft account to access this. Select the “Insider Preview for DragonBoard 410c” link. The DragonBoard 410c image will be used on your Intrinsyc Open-Q 410 hardware.
- Double click the downloaded ISO file. This will automatically mount the ISO as a new virtual CD-drive. (Look for a new CD-ROM drive)
- The mounted virtual drive contains an installer file “Windows_10_IoT_Core_QCDB410C.msi”. Double-click the file to start the installation.
The installer creates a new directory: C:\Program Files (x86)\Microsoft IoT\FFU\QCDB410C\ which contains the DragonBoard410c image file “flash.ffu”
Connect the Open-Q 410 to the Host PC
- First, we must enable download mode by setting the first boot switch on the top of the board to: “USB Boot”. Refer to the red arrow in the image below for a demonstration of the proper configuration:
Download and install the Win10 IoT Core Image to the Open-Q 410
- Launch the DragonBoard 410c Update Tool you installed during a previous step
2.The Update Tool should detect the Open-Q 410 Development Kit and the Connection Status should show: “Connected”.
3.In the DragonBoard 410c Update Tool click the “Browse” button and locate the Win10 IoT Core Image file you downloaded earlier from the ISO file. The flash.ffu file is located in the MicrosoftIoT\FFU\QCDB410C folder
4.Click the “Program” Button and wait for the image to be downloaded to the board.
Please Note: The download will overwrite any previous content of the eMMC memory. The progress is shown as follows:
Once the download is complete, the following dialog will appear:
Running Windows 10 IoT on the Open-Q 410 Development Kit
1.Disconnect the power supply from the board and change the USB boot switch back to the OFF position.
2.Disconnect the USB cable from the USB port of the Open-Q 410 (J601). (Note: If you do not disconnect from J601, the Host port peripherals will not be detected.)
3.Plug in an HDMI display along with a USB mouse and USB keyboard into the Open-Q Development Kit dual USB slots.
4.Optional step for Debug serial messages: Use a microUSB cable to connect your Host PC to the Open-Q 410’s Debug UART port J401:
You can use terminal emulation software on your PC (such as Tera Term) to observe the debug messages from the Open-Q 410. The serial port settings are as follows: Baud rate: 115200, Data: 8-bit, Parity: none, Stop: 1bit, Flow control: none.
5.Plug the power cable into the board and press the PWR button for 3 seconds. After a minute the Windows IoT image will boot and the HDMI display will show the following screen:
Use your USB mouse to select your language.
6.Next use your mouse and keyboard to connect to a Wi-Fi hotspot:
7.Finally you will see the Win10 IoT boot-logo and the Win10 IoT default application:
Visit this page for instructions on connecting to your Open-Q 410 Development Kit device using SSH, and for a list of utilities built into the Windows 10 IoT core image.
Enjoy Windows 10 IoT on your Open-Q 410!
Troubleshooting and FAQ
Secure boot enabled
If your Open-Q 410 Development Kit has “Secure Boot” enabled, then the Windows IoT image will not boot fully and you will see the following screen:
To avoid this problem you can disable secure boot by following these steps:
- Remove power from the board
- Hold down the Vol+ and PWR buttons
3.Apply power to the board. This will bring up the Microsoft BDS menu.
4.Use the Vol+, Vol-, and PWR keys to select option “2 Disable Secure Boot
5.Inside the Disable UEFI Secure Boot menu, use the Vol+ and PWR buttons to confirm.
Secure Boot has now been disabled and the Windows 10 IoT image can boot.
Debug Policy Enabled
If your Open-Q 410 Development Kit has the Microsoft “Debug Policy” enabled, then the Windows IoT image will not boot fully and you will see the following screen:
To avoid this problem you can disable debug policy by following these steps:
- Reboot the board and enter the Microsoft BDS menu
- From the BDS menu, use the Vol+ and PWR keys to select “4 Disable Debug Policy”
3.From the “Disable Windows Debug Policy” menu, use the Vol+ key to confirm:
Windows Debug Policy has now been disabled and the Windows 10 IoT image can boot fully.
Open-Q 410 Supported Operating Systems
Your Open-Q 410 Development Kit comes pre-programmed with the Android OS and will boot to this Android Home screen out-of-the box:
This blog post from August 15, 2015 describes a step-by-step process to install and run Lubuntu on your Open-Q 410 Development Kit. Lubuntu is a lightweight OS based on desktop Ubuntu.
Greg Chan is software engineer on Intrinsyc’s solutions team and has been working on embedded devices for over 15 years. When he started with Intrinsyc in 1999 his first project was an embedded in-truck control and monitoring system running Windows CE 2.11. Since then he has worked with all flavours of Windows CE and Windows Mobile. In the last few years he has been working on eReader tablets running Android versions from Cupcake 1.5 to Kitkat.
For further information please contact: