DragonBoard 410c create custom Windows 10 IoT Core image

Question

After reading the MSDN docs about creating a custom Image for Windows 10 IoT Core, I'm totally overwhelmed. I installed the required tools, got the BSP for the DragonBoard 410c and started step by step from the docs

I was very unseccessful, the documentation is very weak for other boards than RPi. So is there anyone who is experienced with creating custom Images for Windows 10 IoT Core?

Edit:

The log shows the following after the command buildimage MyProduct Test

Creating MyProduct Test Image, see C:\iot-adk-addonkit-develop\Build\arm\MyProduct_Test.log for progress ThreadId8768 ERROR: Please run imageapp.exe in an elevated console

Answer 1

You can follow these steps to build a custom Windows IoT Core Image for Dragonboard 410c.By flashing the FFU on to the image, all of the required software is flashed on to the target at once.You'll need the following software:

• Windows 10 Assessment and Deployment Kit (ADK)

• Windows 10 IoT Core Packages

• IoT ADK Add-on Kit

• Windows 10 IoT Core Board Support Package (BSP) for Dragonboard 410c

And it is recommended to setup the image building environment on a clean system.

1. Run iot-adk-addonkit\IoTCoreShell-arm.cmd

2. Run installoemcerts.cmd to install Test Sign Certificates on the system

3. Run following command to export feature cabs.Assuming C:\a8016aaattnwza21120000.2_db410c_bsp is where the BSP was extracted to.

   C:\iot-adk-addonkit\Tools\bsptools\QCDB410C\export.cmd C:\a8016aaattnwza21120000.2_db410c_bsp\DB410c_BSP

4. Run newproduct.cmd DemoDevice QCDB410C and choose to enter SMBIOS data to uniquely identify your device in SMBIOS.

5. Run buildpkg.cmd all

6. Unplug all USB storage devices and then run this command to start creating a Test FFU.

   createimage.cmd DemoDevice Test

It may take between 10 to 30 min to build an FFU depend on your build system speed. If the process completed without error, you can navigate to C:\iot-adk-addonkit\Build\arm\DemoDevice\Test to find the Flash.ffu. Please node that, the version of WDK, ADK, and the core kit package should remain consistent.