Packages are the logical building blocks of IoT Core. From device drivers to system files, every component must be contained in a package. This is the smallest servicable unit on the device.
\IoT-ADK-AddonKit\Tools\setOEM.cmdto set the OEM_NAME
IoTCoreShell.cmd( this one launches in the elevated prompt )
Set Environment for Architectureprompt
InstallOEMCerts. This is required only once for the PC.
To create your own image (FFU), get the tools needed to customize Windows IoT Core
Build the package:
buildpkg.cmd filename.pkg.xml. The .cab file will be created in the build directory
Below is an example for specifying files and reg keys.
Use appx2pkg.cmd tool to generate the .pkg.xml file for a given appx file. This tool expects the appx dependencies in the sub directory named “dependencies” in the folder containing the appx file.
You can also create the Appx component directly in the IoTCoreShell, using the following steps
> newappxpkg HelloWorld.appx fga Appx.HelloWorld > buildpkg Appx.HelloWorld
fga sets the appx as the foreground startup app,
bgt sets the appx as the background task and
none skips startup configuration.
See Appx.IoTCoreDefaultApp as an example.
The driver package contains the references (InfSource) to the Inf file for the driver and also lists all the files referenced in the Inf file. You can author the driver .pkg.xml file manually or use inf2pkg.cmd tool that generates package xml based on the input inf file.
inf2cab.cmd tool creates the package xml file and also builds the cab file directly by invoking
Windows IoT Core supports Universal Inf only
applyupdate -stage C:\OemInstall\<filename>.cab. Note that this step is be repeated for each package, when you have multiple packages to install.
The device will reboot into the update OS (showing gears) to install the packages and will reboot again to main OS. This process can take a few minutes.