ms-iot / iot-adk-addonkit

Contains command line scripts for package creation and image creation process and samples for iot products

iot-adk-addonkit

This project contains powershell scripts for package creation and image creation process. Users are expected to have ADK and Windows 10 IoT Core OS packages installed to make use of this. To be able to create images, Users should also get the BSPs corresponding to the hardware. Target audience is OEM’s and Maker Pro’s who want to manage multiple images and updates.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Branch Overview

Master Branch

This branch supports the lastest Windows 10 IoT Core release available ( currently 1809, version number 10.0.17763.x ). The iot-adk-addonkit is now in Powershell and supports additional features including multiple workspaces. For more details see

• IoTCoreImaging Command Listing
• IoTCoreImaging User Manual

17763-v7 Branch

Starting with Windows 10 IoT Core release 10.0.17763.1577, OEM signing is supported for retail images. The Existing cross-certificate based retail signing will continue to be supported and will end with the expiry of published SHA1 Microsoft Cross-Cert roots ( See Cross-Certificate List for the expiry dates). The existing drivers in the image will continue to work and this expiry will only impact new driver signing process. See Microsoft Security Advisory 2880823 for more details on SHA1.

The core image building processes are not changed and additional requirements are now enforced for supporting oem signed drivers in retail images.

• New requirements are
  • Secure boot and Device guard features are mandatory to support oem signed drivers
  • Device guard policy signer should be
    • a root certificate or PCAs directly off the root
    • at least RSA3k and use SHA256 as the digest algorithm
  • The root certs should be included in the image

See What's new in 7.0 for the changes in the toolkit. The recommendation is to move to OEM signing process with SHA2 certs as soon as possible.

Older Versions: Not Supported

For older releases, please use the corresponding ADK tools and iot-adk-addonkit releases.

• 17134_v5.3 release for Windows 10 IoT Core Release 1803 (version 10.0.17134.x).
• 16299_v4.4 release for Windows 10 IoT Core Release 1709 (version 10.0.16299.x).
• 15063_v3.2 release for Windows 10 IoT Core Release 1703 (version 10.0.15063.x).
• 14393_v2.0 release for Windows 10 IoT Core Release 1607 (version 10.0.14393.x).

References

User Guides

• IoT Core Manufacturing Guide
  • Windows ADK IoT Core Add-Ons Overview
  • IoT Core Add-Ons command-line options
  • IoT Core feature list
  • Channel9 Video on Manufacturing Guide
• Learn how to build on Windows 10 IoT Core
  • Windows Device Portal
• SecureBoot, Bitlocker and DeviceGuard

Downloads

• Windows 10 IoT Core Packages
• Windows Assessment and Deployment Kit including Windows PE add-on for the adk
• Windows Driver Kit - WDK
• Windows 10 IoT Core Dashboard

BSPs

See Windows 10 IoT Core BSPs

Source Links

• Appx.IoTCoreDefaultApp (SmartDisplay.appx, shows up as IoTCoreDefaultAppUnderTest)
  • Source : Windows-iotcore-samples/samples/IoTCoreDefaultApp
  • Documentation : IoTCoreDefaultApp
• Appx.IoTCoreOnboardingTask
  • Source : ms-iot/samples/IoTOnBoarding

iot-adk-addonkit's Issues

oemcustomization.cmd uses >nul 2>&1 ?

So where is the error log that this creates?

inf2pkg.cmd broken with the conversion to wm.xml

inf2pkg.cmd generates proper pkg.xml file and the converted wm.xml file is incorrect, the name contains extra text.

newupdate.cmd not found

When I try to create an update to test the command cannot be found.

See tutorial :

https://docs.microsoft.com/en-us/windows-hardware/service/iot/updating-iot-core-apps#Test_and_track_the_update

Step 1.

How must this be done without this tool ?

How to get an especific versión of SO for to build the image

Hello,

Label as a question please.

i'm wondering how can i get the base for tu build and image with the specific versión of the SO.

I would like to build the image over the versión 10.0.15063.414.

When i build the image i got the 10.0.15063.0. And i would like to disable the updates (i'm using the w10 iot core pro with license).

Thanks!

PD: i just download the latest iot-adj-addonkit version and this weekend i'll test the working pending. that i have

Are community BSPs accepted?

If I were to create a BSP for a commercial off-the-shelf device, would the PR be accepted?
I have recently tested Windows IoT on a tablet Linx1010 and it works very well. Or do I have ot host that separately?

Production build to RPi3 fails

newproduct.cmd Prod Rpi2
buildimage.cmd Prod Retail

This is on a RPi3 with RPi touch screen. No customizations. This builds both test and retail with no reported errors. Test boots and runs fins. Retail doesn't. Upon first boot of retail I see the windows logo very briefly followed by a completely blue screen. After a few moments the blue screen turns black and the unit shuts down.

IoT Core Version question

Hi,

is it correct that at the moment with the iot-adk-addonkit and the correspondig IoT Core Packages available today we can only build custom images with IoT build version 14393?

There is no way I can get a custom image for an insider preview version like 15051, right?

Does Raspberry Pi support SMBIOS?

Can you provide an SMBios Config Sample for Raspberry Pi?

Feature Request:

I posted an issue over here about this. If you write your custom flash.ffu using the iot core dashboard, it creates a PreProvisionDevice.cmd in the root of the SD Card. This cmd runs and among other things sets HKLM\Software\Microsoft\SQMClient\MachineId to a new random Uuid and then deletes itself. This is a problem for mass duplication of flash.ffu images for production, or distribution using dism to write the image. I think an ideal solution would be for oemcustomizations.cmd to write that reg key in the first boot section. But for that to work, the cmd shell would need some way to generate a new Uuid. Is this possible?

binexport ??

directions for building BSP drivers do not make any sense.
what tools directory are you referring too?
There is no binexport file.

Image Build Issue for DragonBoard 410C

I downloaded the Dragon BSP from Qualcomm site and tested it as shown in the link below.
(All versions, such as WDK, ADK, etc., are identical to 16299.)
https://docs.microsoft.com/en-us/windows/iot-core/build-your-image/createbsps

but, The image build error log is shown below.

{1/8/2018 7:58:23 PM} Imaging: Reading the OEM Input XML file...
{1/8/2018 7:58:23 PM} FeatureAPI: Successfully validated the OEM Input XML: C:\iot-adk-addonkit-master\Source-arm\Products\DragonBSP\RetailOEMInput.xml
{1/8/2018 7:58:23 PM} Imaging: Reading the FM XML file 'C:\iot-adk-addonkit-master\Build\arm\MergedFMs\QCDB410CFM.xml'...
{1/8/2018 7:58:23 PM} FeatureAPI: Successfully validated the Feature Manifest XML: C:\iot-adk-addonkit-master\Build\arm\MergedFMs\QCDB410CFM.xml
{1/8/2018 7:58:24 PM} Error: Imaging!ProcessCompDBPackages: FIP information in FM 'QCDB410CFM.xml' packages for the following Features are incorrect:
Error : BASE
Error : OEM_QC_UEFI_PRODUCTION
Error : OEM_SBC
Error : OEM_CUSTOM_SMBIOS
Error : OEMDEVICEPLATFORM_8016SBC
Error : DEVICELAYOUT_QC8016
{1/8/2018 7:58:24 PM} Imaging: See Flash.cbs.log and Flash.csi.log for details.
{1/8/2018 7:58:24 PM} Imaging: Performance Results:
{1/8/2018 7:58:24 PM} Total Run Time: 00:00:01.8594682
{1/8/2018 7:58:24 PM} Storage Stack Time: 00:00:00
{1/8/2018 7:58:24 PM} CompDB Total Time: 00:00:01.4276662

Thanks.

Support for LattePanda and Up Boards

I'm trying to use the LattePanda (similar to UP Boards "Core") which runs an Intel Atom 8350 CPU.

The vendor has provided a Win10 LTSB 2016 image, and that installs just fine.

Shouldn't I be able to just create a provisioning package for IoT Core using ICD and then apply that to my device?

If not, has anyone else had success with a compatible image? This IoT Core image building process seems pretty horrible.

Buildpkg no longer works after 1607 install

After installing update IoT 1607 packages BuildPkg All no longer works.
Went through the tool install steps, set the OEM name and installed certs etc.
BuildPkg All fails and I can not find the issue.
I think this worked before with the original release.

Fails with:
C:\iot-adk-addonkit\Tools>BuildPkg All
Building all provisioning packages
Processing all provisioning packages
Processing Provisioning.Enroll
Processing Provisioning.ProSKU
Processing ProductA
Processing SampleA
Processing SampleB
Processing SampleC
Building all packages under C:\iot-adk-addonkit\Common\Packages
Processing Custom.Cmd.pkg.xml
Microsoft (C) spkggen 8.0.11111.0

fatal error : Invalid command line arguments:Command-line has too many parameters
info: >> Command-line has too many parameters
info: Usage: SPkgGen.exe [project] [/config:x] [/xsd:x] [/output:x] [/version:x] [/build:x] [/cpu:x] [/languages:x] [/resolutions:x] [/variables:x] [/spkgsout:x] [/toolPaths:x] [[+|-]toc] [[+|-]compress] [[+|-]diagnostic] [[+|-]nohives] [[+|-]isRazzleEnv] [/?]
info: [project]············· Full path to the package project file. Values: free
info: text; default=
info: [/config]············· File with globally defined variables. Values: free
info: text; default=
info: [/xsd]················ Path to write the PkgGen auto-generated schema to.
info: Values: free text; default=
info: [/output]············· Output directory. Values: free text; default= .
info: [/version]············ Version string in the form of .... Values: free text; default= 0.0.0.0
info: [/build]·············· Build type string. Values: {fre|chk}; default= fre
info: [/cpu]················ CPU type. Values: {x86|arm|arm64|amd64}; default= ARM
info: [/languages]·········· Supported language identifier list separated by ';'.
info: Values: free text; default=
info: [/resolutions]········ Supported resolution identifier list separated by
info: ';'. Values: free text; default=
info: [/variables]·········· Additional variables used in the project file
info: syntax:=;=;.... Values: free
info: text; default=
info: [/spkgsout]··········· Create an output file containing a list of generated
info: SPKG's. Values: free text; default=
info: [/toolPaths]·········· Directories containing tools needed by spkggen.exe.
info: Values: free text; default=
info: [toc]················· Building TOC files instead of the actual package.
info: Values: precede by [+] or [-]; default= False
info: [compress]············ Compressing the generated package. Values: precede by
info: [+] or [-]; default= False
info: [diagnostic]·········· Enable debug output. Values: precede by [+] or [-];
info: default= False
info: [nohives]············· Indicates whether or not this package has no hive
info: dependency. Values: precede by [+] or [-]; default=
info: False
info: [isRazzleEnv]········· Indicates whether or not spkggen is running in a
info: razzle environment. Values: precede by [+] or [-];
info: default= False
info: [/?]·················· Displays this usage string

Error : Failed to create package. See C:\iot-adk-addonkit\Build\arm\pkgs\logs\Custom.Cmd.pkg.log
Processing Device.SystemInformation.pkg.xml
Microsoft (C) spkggen 8.0.11111.0

fatal error : Invalid command line arguments:Command-line has too many parameters
info: >> Command-line has too many parameters
info: Usage: SPkgGen.exe [project] [/config:x] [/xsd:x] [/output:x] [/version:x] [/build:x] [/cpu:x] [/languages:x] [/resolutions:x] [/variables:x] [/spkgsout:x] [/toolPaths:x] [[+|-]toc] [[+|-]compress] [[+|-]diagnostic] [[+|-]nohives] [[+|-]isRazzleEnv] [/?]
info: [project]············· Full path to the package project file. Values: free
info: text; default=
info: [/config]············· File with globally defined variables. Values: free
info: text; default=
info: [/xsd]················ Path to write the PkgGen auto-generated schema to.
info: Values: free text; default=
info: [/output]············· Output directory. Values: free text; default= .
info: [/version]············ Version string in the form of .... Values: free text; default= 0.0.0.0
info: [/build]·············· Build type string. Values: {fre|chk}; default= fre
info: [/cpu]················ CPU type. Values: {x86|arm|arm64|amd64}; default= ARM
info: [/languages]·········· Supported language identifier list separated by ';'.
info: Values: free text; default=
info: [/resolutions]········ Supported resolution identifier list separated by
info: ';'. Values: free text; default=
info: [/variables]·········· Additional variables used in the project file
info: syntax:=;=;.... Values: free
info: text; default=
info: [/spkgsout]··········· Create an output file containing a list of generated
info: SPKG's. Values: free text; default=
info: [/toolPaths]·········· Directories containing tools needed by spkggen.exe.
info: Values: free text; default=
info: [toc]················· Building TOC files instead of the actual package.
info: Values: precede by [+] or [-]; default= False
info: [compress]············ Compressing the generated package. Values: precede by
info: [+] or [-]; default= False
info: [diagnostic]·········· Enable debug output. Values: precede by [+] or [-];
info: default= False
info: [nohives]············· Indicates whether or not this package has no hive
info: dependency. Values: precede by [+] or [-]; default=
info: False
info: [isRazzleEnv]········· Indicates whether or not spkggen is running in a
info: razzle environment. Values: precede by [+] or [-];
info: default= False
info: [/?]·················· Displays this usage string

Error : Failed to create package. See C:\iot-adk-addonkit\Build\arm\pkgs\logs\Device.SystemInformation.pkg.log
Processing DeviceLayout.GPT2GB.pkg.xml
Microsoft (C) spkggen 8.0.11111.0

fatal error : Invalid command line arguments:Command-line has too many parameters

What can be causing these issues?

Fails on Intel Braswell BSP

Trying to use Intel's latest BSP release for Braswell processors is giving me issues.

Here's where I obtained the BSP:
https://www.intel.com/content/www/us/en/embedded/products/braswell/software-and-drivers.html

BSP Download URL:
https://edc.intel.com/Link.aspx?id=14935

Using the 1709 Addon Kit downloaded from the master branch in GitHub results in the following errors:

[JetwaySBC1_Test.log]:

Creating JetwaySBC1 Test Image
Build Start Time : 13:47:45.22
Building Packages with product specific contents with version 10.0.0.0
 Processing Registry.Version.wm.xml
 Processing Custom.Cmd.wm.xml
 Processing JetwaySBC1
 Processing Provisioning.Auto.wm.xml
Running FeatureMerger for OEM packages
  Exporting OEMFM files
  Processing OEMFMFileList.xml
Running FeatureMerger for BSWx64
  Exporting BSWx64 FM files
  Processing BSWx64FMFileList.xml
Creating Image...
Microsoft (C) imageapp 10.0.10011.16384

ImageApp!ConfigureServicingStackLogging: Failed initializing WdsCore.dll.
ImageApp: Setting CPU Type to 'amd64'.
info: Imaging: Reading the OEM Input XML file...
info: FeatureAPI: Successfully validated the OEM Input XML: C:\IoT-ADK-AddonKit\Source-x64\Products\JetwaySBC1\TestOEMInput.xml
info: Imaging: Reading the FM XML file 'C:\IoT-ADK-AddonKit\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml'...
info: FeatureAPI: Successfully validated the Feature Manifest XML: C:\IoT-ADK-AddonKit\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml
fatal error : Imaging!ProcessCompDBPackages: FIP information in FM 'BSWx64FM.xml' packages for the following Features are incorrect: 
fatal error : 	Error : BASE
fatal error : 	Error : OEM_BSW64_DRIVERS
fatal error : 	Error : OEMDEVICEPLATFORM_BSWX64_DEVICE
fatal error : 	Error : DEVICELAYOUT_BSWX64_SOC
info: Imaging: See Flash.cbs.log and Flash.csi.log for details.
info: Imaging: Performance Results:
info: 	Total Run Time:	00:00:01.1726105
info: 	Storage Stack Time:	00:00:00
info: 	CompDB Total Time:	00:00:00.8819263
ImageApp: Error log can be found at 'C:\IoT-ADK-AddonKit\Build\amd64\JetwaySBC1\Test\Flash.ImageApp.log'.
Failed to add CBS file logger.
"CreateImage JetwaySBC1 Test" failed with error 1

I was then told that the version 3.2 of the AddonKit is what the current Intel BSP works against. And that there are changes checked into the develop branch that should address the issue.

For the version 3.2, buildpkg all doesn't even complete without errors. Here are the errors for buildpkg:

[Appx.IoTCoreDefaultApp.pkg.log]:

Creating Provisioning Package using C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTCoreDefaultApp\customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-131905-279_6636.log
"provpkg C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTCoreDefaultApp\customizations.xml" failed with error 100

[Appx.IoTOnboardingTask.prov.log]:

Creating Provisioning Package using C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTOnboardingTask\customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-131905-561_12932.log
"provpkg C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTOnboardingTask\customizations.xml" failed with error 100

[SampleAProv.prov.log]:

Creating Provisioning Package using C:\iot-adk-addonkit-3.2\Source-x64\Products\SampleA\prov\customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-131905-842_4328.log
"provpkg C:\iot-adk-addonkit-3.2\Source-x64\Products\SampleA\prov\customizations.xml" failed with error 100

[Provisioning.Auto.pkg.log]:

Creating Provisioning.Auto.pkg.xml Package with version 10.0.0.0 for SampleA
Microsoft (C) PkgGen 10.0.10011.16384

Running SPkgGen.exe C:\iot-adk-addonkit-3.2\Common\Packages\Provisioning.Auto\Provisioning.Auto.pkg.xml /config:"C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386\pkggen.cfg.xml" /output:C:\iot-adk-addonkit-3.2\Build\amd64\pkgs /build:fre /cpu:amd64 /variables:_RELEASEDIR=C:\iot-adk-addonkit-3.2\Common\Packages\Provisioning.Auto\;PROD=SampleA;PRJDIR=C:\iot-adk-addonkit-3.2\Source-x64;COMDIR=C:\iot-adk-addonkit-3.2\Common;BSPVER=10.0.0.0;BSPARCH=amd64;OEMNAME=Intel;BUILDTIME=171106-1319;BUILD_OS_VERSION=10.0.0.0 /toolPaths:%RazzleToolPath%\x86 /nohives /version:10.0.0.0 /spkgsout:C:\Users\jscherrer\AppData\Local\Temp\tmpF6D7.tmp 
--Stack Trace--
   at Microsoft.CompPlat.PkgBldr.Base.Run.RunSPkgGen(List`1 pkgGenArgs, Boolean inWindows, IDeploymentLogger logger, PkgBldrCmd pkgBldrArgs, List`1 spkgList)
   at Microsoft.CompPlat.PkgBldr.Program.PkgToCab(Config config, List`1 spkgGenArgs, Boolean testSignOnly)
   at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
--End Stack Trace--
Package creation failed with error -1

[Appx.IoTCoreDefaultApp.pkg.log]:

Creating Appx.IoTCoreDefaultApp.pkg.xml Package with version 10.0.0.0 for SampleA
 Creating C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTCoreDefaultApp\Appx.IoTCoreDefaultApp.ppkg...
Creating Provisioning Package using customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-131920-953_264.log
"provpkg customizations.xml" failed with error 100
Microsoft (C) PkgGen 10.0.10011.16384

Running SPkgGen.exe C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTCoreDefaultApp\Appx.IoTCoreDefaultApp.pkg.xml /config:"C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386\pkggen.cfg.xml" /output:C:\iot-adk-addonkit-3.2\Build\amd64\pkgs /build:fre /cpu:amd64 /variables:_RELEASEDIR=C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTCoreDefaultApp\;PROD=SampleA;PRJDIR=C:\iot-adk-addonkit-3.2\Source-x64;COMDIR=C:\iot-adk-addonkit-3.2\Common;BSPVER=10.0.0.0;BSPARCH=amd64;OEMNAME=Intel;BUILDTIME=171106-1319;BUILD_OS_VERSION=10.0.0.0 /toolPaths:%RazzleToolPath%\x86 /nohives /version:10.0.0.0 /spkgsout:C:\Users\jscherrer\AppData\Local\Temp\tmp1888.tmp 
--Stack Trace--
   at Microsoft.CompPlat.PkgBldr.Base.Run.RunSPkgGen(List`1 pkgGenArgs, Boolean inWindows, IDeploymentLogger logger, PkgBldrCmd pkgBldrArgs, List`1 spkgList)
   at Microsoft.CompPlat.PkgBldr.Program.PkgToCab(Config config, List`1 spkgGenArgs, Boolean testSignOnly)
   at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
--End Stack Trace--
Package creation failed with error -1

[Appx.IoTOnboardingTask.pkg.log]:

Creating Appx.IoTOnboardingTask.pkg.xml Package with version 10.0.0.0 for SampleA
 Creating C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTOnboardingTask\Appx.IoTOnboardingTask.ppkg...
Creating Provisioning Package using customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-131921-594_11284.log
"provpkg customizations.xml" failed with error 100
Microsoft (C) PkgGen 10.0.10011.16384

Running SPkgGen.exe C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTOnboardingTask\Appx.IoTOnboardingTask.pkg.xml /config:"C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386\pkggen.cfg.xml" /output:C:\iot-adk-addonkit-3.2\Build\amd64\pkgs /build:fre /cpu:amd64 /variables:_RELEASEDIR=C:\iot-adk-addonkit-3.2\Source-x64\Packages\Appx.IoTOnboardingTask\;PROD=SampleA;PRJDIR=C:\iot-adk-addonkit-3.2\Source-x64;COMDIR=C:\iot-adk-addonkit-3.2\Common;BSPVER=10.0.0.0;BSPARCH=amd64;OEMNAME=Intel;BUILDTIME=171106-1319;BUILD_OS_VERSION=10.0.0.0 /toolPaths:%RazzleToolPath%\x86 /nohives /version:10.0.0.0 /spkgsout:C:\Users\jscherrer\AppData\Local\Temp\tmp1AEA.tmp 
--Stack Trace--
   at Microsoft.CompPlat.PkgBldr.Base.Run.RunSPkgGen(List`1 pkgGenArgs, Boolean inWindows, IDeploymentLogger logger, PkgBldrCmd pkgBldrArgs, List`1 spkgList)
   at Microsoft.CompPlat.PkgBldr.Program.PkgToCab(Config config, List`1 spkgGenArgs, Boolean testSignOnly)
   at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
--End Stack Trace--
Package creation failed with error -1

[buildfm_oem.log]:

info: Trying to load file 'C:\iot-adk-addonkit-3.2\Build\amd64\InputFMs\OEMFMFileList.xml' as a FM file list ...
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.Provisioning.Auto.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.Provisioning.Auto.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.Appx.IoTCoreDefaultApp.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.Appx.IoTOnboardingTask.cab

[buildfm_bsp_CustomMBMx64.log]:

info: Trying to load file 'C:\iot-adk-addonkit-3.2\Build\amd64\InputFMs\CustomMBMx64FMFileList.xml' as a FM file list ...
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.GPIO.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.UART.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.I2C.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.SPI.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.GRFX.cab

[buildfm_bsp_MBMx64.log]:

info: Trying to load file 'C:\iot-adk-addonkit-3.2\Build\amd64\InputFMs\MBMx64FMFileList.xml' as a FM file list ...
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.GPIO.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.UART.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.I2C.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.SPI.cab
fatal error : Error: Missing package: C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\Intel.MBMx64.GRFX.cab

Since many of the errors didn't seem directly related to my device, I went ahead with buildimage anyways, and the following errors occurred:

[JetwaySBC1_Test.log]:

Creating JetwaySBC1 Test Image
Build Start Time : 13:30:13.69
Building Packages with product specific contents
 Processing Registry.Version.pkg.xml
 Processing Custom.Cmd.pkg.xml
Creating Provisioning Package using C:\iot-adk-addonkit-3.2\Source-x64\Products\JetwaySBC1\prov\customizations.xml

Microsoft (C) Windows Imaging and Configuration Designer

ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ApplicationManagement' is not a valid child node for /
ICD.exe : ERROR: C:\Users\jscherrer\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171106-133015-674_3500.log
"provpkg C:\iot-adk-addonkit-3.2\Source-x64\Products\JetwaySBC1\prov\customizations.xml" failed with error 100
 Processing Provisioning.Auto.pkg.xml
�[91mError : Failed to create package. See C:\iot-adk-addonkit-3.2\Build\amd64\pkgs\logs\Provisioning.Auto.pkg.log�[0m
Creating Image...
Microsoft (C) imageapp 10.0.10011.16384

ImageApp!ConfigureServicingStackLogging: Failed initializing WdsCore.dll.
ImageApp: Setting CPU Type to 'amd64'.
info: Imaging: Reading the OEM Input XML file...
info: FeatureAPI: Successfully validated the OEM Input XML: C:\iot-adk-addonkit-3.2\Source-x64\Products\JetwaySBC1\TestOEMInput.xml
info: Imaging: Reading the FM XML file 'C:\iot-adk-addonkit-3.2\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml'...
info: FeatureAPI: Successfully validated the Feature Manifest XML: C:\iot-adk-addonkit-3.2\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml
fatal error : Imaging!ProcessCompDBPackages: FIP information in FM 'BSWx64FM.xml' packages for the following Features are incorrect: 
fatal error : 	Error : BASE
fatal error : 	Error : OEM_BSW64_DRIVERS
fatal error : 	Error : OEMDEVICEPLATFORM_BSWX64_DEVICE
fatal error : 	Error : DEVICELAYOUT_BSWX64_SOC
info: Imaging: See Flash.cbs.log and Flash.csi.log for details.
info: Imaging: Performance Results:
info: 	Total Run Time:	00:00:01.1277237
info: 	Storage Stack Time:	00:00:00
info: 	CompDB Total Time:	00:00:00.8457621
ImageApp: Error log can be found at 'C:\iot-adk-addonkit-3.2\Build\amd64\JetwaySBC1\Test\Flash.ImageApp.log'.
Failed to add CBS file logger.
"CreateImage JetwaySBC1 Test" failed with error 1

So I went ahead and tried to target the latest develop branch. The results were more like what I saw from the 1709 release. The buildpkg all completes fine. But buildimage fails with the following errors:

[JetwaySBC1_Test.log]:

Creating JetwaySBC1 Test Image
Build Start Time : 13:39:26.14
Building Packages with product specific contents with version 10.0.0.0
 Processing Registry.Version.wm.xml
 Processing Custom.Cmd.wm.xml
 Processing JetwaySBC1
 Processing Provisioning.Auto.wm.xml
Running FeatureMerger for OEM packages
  Exporting OEMFM files
  Processing OEMFMFileList.xml
Running FeatureMerger for BSWx64
  Exporting BSWx64 FM files
  Processing BSWx64FMFileList.xml
Creating Image...
Microsoft (C) imageapp 10.0.10011.16384

ImageApp!ConfigureServicingStackLogging: Failed initializing WdsCore.dll.
ImageApp: Setting CPU Type to 'amd64'.
info: Imaging: Reading the OEM Input XML file...
info: FeatureAPI: Successfully validated the OEM Input XML: C:\Users\jscherrer\source\repos\iot-adk-addonkit\Source-x64\Products\JetwaySBC1\TestOEMInput.xml
info: Imaging: Reading the FM XML file 'C:\Users\jscherrer\source\repos\iot-adk-addonkit\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml'...
info: FeatureAPI: Successfully validated the Feature Manifest XML: C:\Users\jscherrer\source\repos\iot-adk-addonkit\Source-x64\BSP\BSWx64\Packages\BSWx64FM.xml
fatal error : Imaging!ProcessCompDBPackages: FIP information in FM 'BSWx64FM.xml' packages for the following Features are incorrect: 
fatal error : 	Error : BASE
fatal error : 	Error : OEM_BSW64_DRIVERS
fatal error : 	Error : OEMDEVICEPLATFORM_BSWX64_DEVICE
fatal error : 	Error : DEVICELAYOUT_BSWX64_SOC
info: Imaging: See Flash.cbs.log and Flash.csi.log for details.
info: Imaging: Performance Results:
info: 	Total Run Time:	00:00:01.1442189
info: 	Storage Stack Time:	00:00:00
info: 	CompDB Total Time:	00:00:00.8467266
ImageApp: Error log can be found at 'C:\Users\jscherrer\source\repos\iot-adk-addonkit\Build\amd64\JetwaySBC1\Test\Flash.ImageApp.log'.
Failed to add CBS file logger.
"CreateImage JetwaySBC1 Test" failed with error 1

1703 supported, do I generate 1703 error

1703 supported, do I generate 1703 error

How to fix issue like "Could not load file or assembly"

IOTADK_ROOT : D:\Tools\iot-adk-addonkit-3.2\iot-adk-addonkit-3.2
ADK_VERSION : 15063
WDK_VERSION : 15063
COREKIT_VER : 15063.0

When I try to use buildpkg.cmd to buid a cab file, an error like my topic is happened.
part of text like these:
info: Import Log: : >>> [Unload Offline Registry Hive - SYSTEM]
info: Import Log: : >>> Section start 2018/01/10 17:43:16.688
info: Import Log: : os: Version = 10.0.16299 Service Pack = 0.0 Suite = 0x0100 ProductType = 1 Architecture = x86
info: Import Log: : sto: Closed hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/SYSTEM'.
info: Import Log: : sto: Unloaded hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/SYSTEM'. Time = 0 ms
info: Import Log: : <<< Section end 2018/01/10 17:43:16.704
info: Import Log: : <<< [Exit status: SUCCESS]
info: Import Log: :
info: Import Log: :
info: Import Log: : >>> [Unload Offline Registry Hive - SOFTWARE]
info: Import Log: : >>> Section start 2018/01/10 17:43:16.704
info: Import Log: : os: Version = 10.0.16299 Service Pack = 0.0 Suite = 0x0100 ProductType = 1 Architecture = x86
info: Import Log: : sto: Closed hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/SOFTWARE'.
info: Import Log: : sto: Unloaded hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/SOFTWARE'. Time = 0 ms
info: Import Log: : <<< Section end 2018/01/10 17:43:17.033
info: Import Log: : <<< [Exit status: SUCCESS]
info: Import Log: :
info: Import Log: :
info: Import Log: : >>> [Unload Offline Registry Hive - DRIVERS]
info: Import Log: : >>> Section start 2018/01/10 17:43:17.033
info: Import Log: : os: Version = 10.0.16299 Service Pack = 0.0 Suite = 0x0100 ProductType = 1 Architecture = x86
info: Import Log: : sto: Closed hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/DRIVERS'.
info: Import Log: : sto: Unloaded hive key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Users/root/AppData/Local/Temp/y5pmaa0q.oit/windows/System32/config/DRIVERS'. Time = 0 ms
info: Import Log: : <<< Section end 2018/01/10 17:43:17.080
info: Import Log: : <<< [Exit status: SUCCESS]
info: Import Log: :
fatal error : Uncaught exception occured: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Phone.Test.TestMetadata Version=8.1.1702.2001 Culture=neutral PublicKeyToken=b3f029d4c9c2ec30' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
fatal error : File name: 'Microsoft.Phone.Test.TestMetadata Version=8.1.1702.2001 Culture=neutral PublicKeyToken=b3f029d4c9c2ec30'
fatal error : at Microsoft.WindowsPhone.ImageUpdate.PkgGenCommon.BaseComponents.Internal.PackageSetBuilder.BuildPackage(SatelliteId satelliteId IEnumerable`1 files String outputDir)
fatal error : at Microsoft.WindowsPhone.ImageUpdate.PkgGenCommon.BaseComponents.Internal.PackageSetBuilder.Save(String outputDir)
fatal error : at Microsoft.WindowsPhone.ImageUpdate.PkgGenCommon.BaseComponents.Internal.PackageGenerator.Build(String projPath String outputDir Boolean compress)
fatal error : at Microsoft.WindowsPhone.ImageUpdate.PackageGenerator.Program.Main(String[] args)
fatal error : WRN: Assembly binding logging is turned OFF.
fatal error : To enable assembly bind failure logging set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
fatal error : Note: There is some performance penalty associated with assembly bind failure logging.
fatal error : To turn this feature off remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Error : Failed to create package. See D:\Tools\iot-adk-addonkit-3.2\iot-adk-addonkit-3.2\Build\arm\pkgs\logs\Drivers.oem11.pkg.log

IoTCoreShellv3.2 arm 10.0.0.0
Could you give me some help?

MainOS partition free space should be 512MB atleast, currently it is 256MB

The Free space in the MainOS partition is recommended to be 512MB to accommodate future growth. currently it is 256MB only..

when update ffu image, always get the error : 0x80070002

Hi,
I am using the updateinputxml way to update flash.ffu image, but it always gives such error:
know how to fix it?
In IoTShell env, run cmd:
imageapp.exe D:\Image\Update\flash.ffu /updateinputxml:"D:\iot-adk-addonkit-master\iot-adk-addonkit-master\Templates\UpdateInput.xml"
the updateinput.xml is:

The error in the log is:

{3/6/2017 3:20:47 PM} Error: [00:00:13] onecore\base\cbs\mobile\iucore\updateinput.cpp, UpdateInput::LoadXML, line 102, Error , Failed call to FileStream::OpenFile on file '\?\C:\Users\admin\AppData\Local\Temp\ebrtf15r.mrz.mnt\Data\SharedData\DuShared\UpdateInput.xml', error is 0x80070002
{3/6/2017 3:20:47 PM} Error: [00:00:13] onecore\base\cbs\mobile\iucore\updateinput.cpp, UpdateIsUsingSD, line 770, Error , Failed to initialize input file, error is 0x80070002

Any one know how to fix it?

Run powershell/batch files on startup

Is there a way that one can set powershell/batch files to run on startup. We need to run custom script to read some data and pass it on cloud.

Missing Recovery.MBR-BcdEdit, etc.

The repo includes MBR layouts for -R but no Recovery package(s) for MBR.

Feature Request: Tone upon completion

When running a long build process such as buildrecovery or buildagent, it would be great to have Windows give you a bell or tone to alert you that it's done. Especially if you have minimize the window. The simplest way is to add "echo ^g" into the commands. But that just plays the default Windows alert tone. It would be better to have a user selectable tone perhaps defined in the setOEM.cmd file so that all configuration for the build process is kept in a unified place.

oemcustomization and restart

We currently have two scenarios that would require a restart after the first boot has finished.
In the oemcustimzation.cmd we call a powershell script that adds some registry entries for our touch driver (has to be done during runtime) and we read the hostname for the device from a file on the SD card. Both of these actions require a restart.
However, if I just trigger the restart after completion of the oemcustomization.cmd, I sometime see some issues with applications not being installed (e.g. screen keeps black after OOBE has finished, because default app has not been installed).
What is the proper way to trigger a restart, once all packages have been installed?

Execution of BuildPkg All fails

What I have:
windows 10
adk ver. 1511
wdk
add on kit from branch for windows in version 1511
iot core dashboard
installed msi from this: https://msdn.microsoft.com/subscriptions/downloads/#FileId=67415

I'm using virtual machine to build my image.

I'm following this instruction: https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/iot/create-a-basic-image

Below some logs from console output:

IoTCore x86 10.0.0.0
C:\iot-adk-addonkit\Tools>BuildPkg All
Building all packages under C:\iot-adk-addonkit\Common\Packages
Processing Custom.Cmd.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Custom.Cmd.pkg.log
Processing Device.SystemInformation.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Device.SystemInformation.pkg.log
Processing DeviceLayout.GPT2GB.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\DeviceLayout.GPT2GB.pkg.log
Processing DeviceLayout.GPT4GB.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\DeviceLayout.GPT4GB.pkg.log
Processing DeviceLayout.MBR2GB.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\DeviceLayout.MBR2GB.pkg.log
Processing DeviceLayout.MBR4GB.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\DeviceLayout.MBR4GB.pkg.log
Processing ImageSettings.CrashControl.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\ImageSettings.CrashControl.pkg.log
Processing ImageSettings.VideoMode.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\ImageSettings.VideoMode.pkg.log
Processing OemTools.InstallTools.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\OemTools.InstallTools.pkg.log
Processing Provisioning.Auto.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Provisioning.Auto.pkg.log
Processing Provisioning.Manual.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Provisioning.Manual.pkg.log
Processing Registry.Version.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Registry.Version.pkg.log
Building all packages under C:\iot-adk-addonkit\Source-x86\Packages
Processing Appx.Main.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Appx.Main.pkg.log
Processing Appx.TextGlowClock.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\Appx.TextGlowClock.pkg.log
Building all packages under C:\iot-adk-addonkit\Source-x86\BSP
Processing CustomMBM.GPIO.pkg.xml

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'PkgBldr.Tools, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
at Microsoft.CompPlat.PkgBldr.Program.Main(String[] args)
Error : Failed to create package. See C:\iot-adk-addonkit\Build\x86\pkgs\logs\CustomMBM.GPIO.pkg.log

Recovery doesn't work for Raspbery Pi

I prepare a sample project using RPi2-R SOC and Device and using RECOVERY_BCD. Then buildimage and buildrecovey. Write the recovery flash to the SD card. Boots fine. App runs. Debug works, etc. I then powershell into the device and cd MMOS. Then run startrecovery.cmd. Windows reboots and then Windows Boot Manager appears with a "Windows failed to start." message. Status code 0xc000000e. Info: A required device isn't connected or can't be accessed.

Test build works, Release build does not.

Hi.
I did an image for 16299.but release build won't work on RPI3. I to a blue screen without text and then the device restarts in a kinda weird way. I can make a video if it is necessary.
I did tried a release build with a new product but with the same resault.

Can you point me in some direction how I can debug or diagnose the problem, so I can make a release build? As I spent to much time on this task.

Regards
Erik

<OEMFeatureGroups /> bad closing label

Hi,

I think that this label should be closed as "< / OEMFeatureGroups > ", not "< OEMFeatureGroups / >"

(sorry i don't nhow how to write labels without inner spaces)

I 'm doing a image for an app in the store (OEM based).

When i executed the step "Run buildfm oem to generate updated files in the MergedFMs folder. This has to be done every time any time an FM file is modified." in lab 1c

The console show me a msg: "error: Featuremerger failed for OEMFMfilesList.xml see c:\C:\IoT-ADK-AddonKit\iot-adk-addonkit-master\Build\arm\buildfm_oem.log"

that has...

> info: Trying to load file 'C:\IoT-ADK-AddonKit\iot-adk-addonkit-master\Build\arm\InputFMs\OEMFMFileList.xml' as a FM file list ...
fatal error : Error: FeatureAPI!ValidateInput: Unable to parse Feature Manifest XML file 'C:\IoT-ADK-AddonKit\iot-adk-addonkit-master\Build\arm\InputFMs\OEMCommonFM.xml'.System.InvalidOperationException: Error en el documento XML (81, 5). ---> System.Xml.XmlException: La etiqueta de apertura 'OEMFeatureGroups' en la l¡nea 71 posici¢n 6 no coincide con la etiqueta de cierre de 'Features'. l¡nea 81, posici¢n 5.
fatal error : en System.Xml.XmlTextReaderImpl.Throw(Exception e)
fatal error : en System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
fatal error : en System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)
fatal error : en System.Xml.XmlTextReaderImpl.ParseEndElement()
fatal error : en System.Xml.XmlTextReaderImpl.ParseElementContent()
fatal error : en System.Xml.XmlTextReaderImpl.Read()
fatal error : en System.Xml.XmlTextReader.Read()
fatal error : en System.Xml.XmlTextReaderImpl.Skip()
fatal error : en System.Xml.XmlTextReader.Skip()
fatal error : en System.Xml.Serialization.XmlSerializationReader.UnknownNode(Object o, String qnames)
fatal error : en Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderFeatureManifest.Read22_FMFeatures(Boolean isNullable, Boolean checkType)
fatal error : en Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderFeatureManifest.Read32_FeatureManifest(Boolean isNullable, Boolean checkType)
fatal error : en Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderFeatureManifest.Read33_FeatureManifest()
fatal error : --- Fin del seguimiento de la pila de la excepci¢n interna ---
fatal error : en System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
fatal error : en System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
fatal error : en Microsoft.WindowsPhone.FeatureAPI.FeatureManifest.ValidateAndLoad(FeatureManifest& fm, String xmlFile, IULogger logger)
fatal error : Error: failed to load Feature Manifest: $(FMDirectory)\OEMCommonFM.xml

The it's defined at BSPFMTemplate, and others like OEMCOmmonFM.xml ...this was that caused my issue when y was doing "buildfm oem".

I changed the label ending at: my "C:\IoT-ADK-AddonKit\iot-adk-addonkit-master\Common\Packages\OEMCommonFM.xml", and all work fine.

But i modified that label there, not at BSPFMTemplate. I Don't khow if when i created the common packages it was generated using the BSPFMTemplate.

Thanks

Featuremerge fails during buildimage process

Hello

I am attempting to create a Windows 10 Iot image for a RPI3.

I've been following the guide: https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/iot-core-manufacturing-guide

Lab 1a: Create a basic image:

Everything went fine until the last step to build the image.
Error : Build failed. See Log for details.

In the log I can find:

Creating ScInfoScreen test Image
Build Start Time : 8:42:54,47
Building Packages with product specific contents with version 10.0.0.0
Processing Registry.Version.wm.xml
Processing Custom.Cmd.wm.xml
Processing ScInfoScreen
Processing Provisioning.Auto.wm.xml
Running FeatureMerger for OEM packages
Exporting OEMFM files
Processing OEMFMFileList.xml
Running FeatureMerger for rpi2
Exporting rpi2 FM files
Processing rpi2FMFileList.xml
�[91mError: Featuremerger failed for rpi2FMFileList.xml. See C:\iot-adk-addonkit-master\Build\arm\buildfm_bsp_rpi2.log�[0m
Creating Image...
Microsoft (C) imageapp 10.0.10011.16384

ImageApp!ConfigureServicingStackLogging: Failed initializing WdsCore.dll.
ImageApp: Setting CPU Type to 'arm'.
info: Imaging: Reading the OEM Input XML file...
info: FeatureAPI: Successfully validated the OEM Input XML: C:\iot-adk-addonkit-master\Source-arm\Products\ScInfoScreen\testOEMInput.xml
info: Imaging: Reading the FM XML file 'C:\iot-adk-addonkit-master\Build\arm\MergedFMs\RPi2FM.xml'...
fatal error : Imaging!ValidateInput: Failed to load Feature Manifest XML file C:\iot-adk-addonkit-master\Build\arm\MergedFMs\RPi2FM.xml:FeatureAPI!ValidateAndLoad: FeatureManifest file was not found: C:\iot-adk-addonkit-master\Build\arm\MergedFMs\RPi2FM.xml
fatal error : FeatureAPI!ValidateAndLoad: FeatureManifest file was not found: C:\iot-adk-addonkit-master\Build\arm\MergedFMs\RPi2FM.xml
info: Imaging: See Flash.cbs.log and Flash.csi.log for details.
info: Imaging: Performance Results:
info: Total Run Time: 00:00:00.1858600
info: Storage Stack Time: 00:00:00
ImageApp: Error log can be found at 'C:\IOT-AD1\Build\arm\SCINFO1\test\Flash.ImageApp.log'.
"CreateImage ScInfoScreen test" failed with error 1

when inspecting the second log for what cause Featuremerge to fail it says i'm missing packages.

info: Trying to load file 'C:\iot-adk-addonkit-master\Build\arm\InputFMs\rpi2FMFileList.xml' as a FM file list ... fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi2.BootFirmware.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi2.dwcUsbOtg.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.LAN9500N650F.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi2.USBWIFI.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi2.RT.WLAN.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.FT5406.Touch.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.Wifi.bcmdhd63.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.Wifi.bcmdhd63.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.BtwSerialH5Bus.cab fatal error : Error: Missing package: C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre\RASPBERRYPI.RPi.BtwSerialH5Bus.cab

and correct there is nothing in that path its refering to in log.

At C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\

I've got a image "Windows10_IoTCore_RPi_ARM32_en-us_16299" which i ran but this didin't solve anything.

Where are those BSP packages I'am missing? and how do I get em?

Incorrect registry for Crashdump settings

Crashdump settings have to be stored in the System hive and not in the software hive.

I would like to add a service and task into image...

I haven't found the solution in examples nor in here:
https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/iot/add-a-registry-setting-to-an-image

The question is: how to add a service and task into image?

One dirty solution would be to add "sc.exe create" and "schtasks.exe /Create" to oemcustomization.cmd but this script will be invoked after system starts so they won't be included in image for real...

By the way - what mechanism fire oemcustomization.cmd at the system start? There's no run and runonce in registry, I couldn't find anything that is responsible for triggering this...

Error for Common Custom package with product specific file

So I need to include a oemcustomization.ps1 along with oemcustomization.cmd for one or more products, but not necessarily for all products. So I create a new Common package called Custom.Ps1 using Custom.Cmd as a model. I then add a section into the product specific area of OEMCommonFM.xml for it just like the section for Custom.Cmd.cab. I then add oemcustomization.ps1 file to ProductA and add the featureid OEM_CustomPs1 to ProductA\TestOEMInput.xml.

When I "buildpkg custom.ps1" I get an error about the missing oemcustomization.ps1 file in C:\IoT-ADK-AddonKit\Source-arm\Products\DigitalSign. ?? I never added the "OEM_CustomPs1" feature ID to that product. So package build fails.

I nee to build ProductA, so to get past the error message, I add an oemcusomization.ps1 file to DigitalSign (without adding the feature id to it's OEMInput files or many any changes to any XML file for DigitalSign). Then the "buildpkg custom.ps1" succeeds!

This doesn't make any sense. Is there a problem with the script, or my understanding of what is supposed to happen?

Issue compiling braswell BSP

Hi, I'm using th elatest ADK and addon Kit with the intel braswell BSP x64 and after I run ".\bsptools\BSWx64\convert.cmd" and "buildbsp BSWx64" I get lots of errors about a universalbsp argument, any ideas what I'm doing wrong?

Building all bsp packages Processing BSW64.GFX.wm.xml Specified argument was out of the range of valid values. Parameter name: Unknown argument "universalbsp" was provided. Error : Failed to create package. See C:\iot-adk-addonkit-develop\Build\amd64\pkgs\logs\BSW64.GFX.wm.log

createpkg can't be run in build servers

Normal users without the right permission can't use createpkg to build driver packages, e.g. in Build and CI Servers

Getting:
DriverStoreOpen failed error 0x00000522

Building 15063 Image for Pi 3, Bluetooth Not Working

Hi

I had successfully built images for the Pi 3 for 14393 with the ADK Add-On Kit but with 15063 I found that the built-in Bluetooth didn't work - the settings page shows "No usable Bluetooth adapter can be found on this computer: The device is not ready for use. (Excep_FromHResult 0x800710DF)".

After a lot of trial and error I found I could fix this by explicitly including the RPI_BTWSERIALH5BUS_DRIVER feature in TestOEMInput.xml:

<OEM>
  <!-- Include BSP Features -->
  <Feature>RPI2_DRIVERS</Feature>
  <Feature>RPI3_DRIVERS</Feature>
  **<Feature>RPI_BTWSERIALH5BUS_DRIVER</Feature>**

Though I think it would work equally well to add the RPI3_DRIVERS feature id to the relevant package in RPi2FM.xml:

  <PackageFile Path="%BSPPKG_DIR%" Name="%OEM_NAME%.RPi.piminiuart.cab">
    <FeatureIDs>
      <FeatureID>RPI_MINIUART</FeatureID>
      **<FeatureID>RPI3_DRIVERS</FeatureID>**
    </FeatureIDs>
  </PackageFile>

However, I don't understand why either should be needed, as I expected an image built with the default scripts from the Add-On Kit to be the same as the standard image from the IoT Dashboard etc., which was the case with 14393.

I could propose either change in the repository but worndered if I was misunderstanding something?

Regards

David

setOEM.cmd causes build failure

If you "set OEM_NAME=Fabrikam, Inc." then build fails. I don't know if it is the comma or the period or the space that is causing this problem. However, if I use "set OEM_NAME=FabrikamInc" it works, but that is not the correct company name. Is punctuation allowed?

Either way, the lab should be updated to tell people the limitations of this parameter.

SMBIOS.CFG and commercialization

Looking at the example projects that include an SMBIOS.CFG file, it appears that building an image hard codes SMBIOS data such as serial number into the flash.ffu. So when mass producing SD cards for production, all devices would have the same SMBIOS serial number unless buildimage.cmd is run once for each SD card being produced.

This is not appropriate for commercialization. When ordering SD cards from a mass production vendor that creates a big problem. The verbatim image copies would all have the same serial number unless they had the correct ADK version, correct IoT Core image, and correct ADK AddonKit with customizations to be able to run a modified buildimage.cmd that sets unique SMBIOS serial numbers for each and every SD card produced. No SD card production house would ever be expected to run all these tools, nor would any OEM want to provide a SD card mass production vendor with appx packages and image signing keys.

How can ADK AddonKit be used to create production images that support mass duplication and still conform to the commercialization license requirements?

OOBE app closes before oem customizations completes

So what happens is that the OEM app appears on the screen before Custom.Cmd (oemcustomization.cmd) finishes. I have an oemcustomization.cmd script that has an additional set of commands after the firstbootdone if block, but before the Recovery.BcdEdit commands. It calls a powershell script that checks to make sure the computer name is set to a unique name according to a hardware serial number and if it doesn't match what it is supposed to be it changes the computer name and reboots. What I'm seeing is that Windows boots and the "please wait while we get things ready" screen appears. I see it appear in Windows IoT Dashboard with a default computer name of minwinpc. Then my app appears. Then several seconds later the system reboots and when it comes back up the correct unique computer name is set.

So my app is appearing on the screen before oemcustomization.cmd finishes. Is there a solution to this so that my app does not appear until oemcustomization.cmd finishes?

buildpkg ALL fails on missing dependencies

When trying to create an image for IoT Core targeting Raspberry Pi 3, I have followed all of the instructions as described in the document "IoT Core manufacturing guide" and at "Lab 1a: Create a basic image" the buildpkg ALL fails on missing Qualcomm BSP dependencies.

https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/create-a-basic-image

buildfm_bsp_QCDB410C.log

Additionally, the links to IoT Core BSP download page(s) appear to be bad... https://docs.microsoft.com/windows/iot-core/commercialize-your-device/CreateBSP

Pkggen.exe missing

Hi, createpkg.cmd in tools calls pkggen.exe, which is missing! Also, the environment variables %KITSROOT% and %IOTADK_ROOT% have to be manually edited in setenv.cmd. Please mention that somewhere!

REG_MULTI_SZ

Having trouble adding a multi value registry entry. The documentation https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/package-schema has this example with a comma separator:

<regValue buildFilter="buildFilter2" name="name2" value="value1,value2" type="REG_MULTI_SZ" />

But that results in one value with a comma in it. Same with semicolon, as used to work in the old pkg.xml format. I will try \0 like reg.exe uses but one way or another the documentation doesn't seem to match the implementation.

Getting a crash in combase.dll via Azure StorageClient ONLY on our oem-image/FFU build.

Hi Paramesh, do you have a tip regarding this crash which happens only on our oem custom image/FFU build? I used your example "to the T" as far as I can tell. Do I need to add capabilities or do some other configuration to make the Microsoft Azure StorageClient (header creation) work, as it does with identical code on the retail build?

Here are details: http://stackoverflow.com/questions/40267303/iot-core-custom-oem-image-ffu-crashing-in-windowsruntime-blob-cloudblob-cs-only

Any tips or suspicions welcome.
Thanks in advance.

Failed to mount UpdateOS WIM

Hi,

I'm trying to build an windows IoT image for custom hw. But i keep running into the following error:
fatal error : [00:00:00] onecore\base\cbs\mobile\iucore\iustore.cpp, IUStore::MountPendingUpdateOS, line 724, Error , Failed to mount UpdateOS WIM at ... , error is 0x80070241.
I'v searched the internet but I can't seem to find people with similar errors. Can you give any help/tips to where this error is comming from and how I can fix this?

Kind regards,
Bjorn

buildimage to specific version of IoT core

I need to be able to specify which version of IoT core to use when building an image. This is necessary for archival purposes for product management so that I can check in the iot-adk-addonkit folder tree into the company source control without having to keep the build folder tree. At any later time, another worker should be able to check out the source tree and rebuild the exact same flash.ffu from source if I ever need to go back to a previous build, How can I do this?

Also, I would like to be able to build a flash.ffu based on the original creators update and I need to know how to do that. The purposes is so that I can test user and app interaction with an OS update process and user initiated installation time.

Test Image Crashes when not including IOT_TOOLKIT

Hi.
I know this problem is not 100% for this project but. I guess that you have some knowledge about it.
I have narrowed a specific problem that I can't find documented.
When I build an image without IOT_TOOLKIT the image crashes With an error that a critical service did't start.

Here is my manifest.

 <Microsoft>
      <Feature>IOT_EFIESP</Feature>
      <Feature>IOT_EFIESP_BCD_MBR</Feature>
      <Feature>IOT_DMAP_DRIVER</Feature>
      <Feature>IOT_CP210x_MAKERDRIVER</Feature>
      <Feature>IOT_FTSER2K_MAKERDRIVER</Feature>
      <Feature>IOT_GENERIC_POP</Feature>
      <Feature>IOT_POWER_SETTINGS</Feature>
      <Feature>IOT_TOOLKIT</Feature>
      <Feature>IOT_UAP_OOBE</Feature>
      <Feature>IOT_APP_TOOLKIT</Feature>
      <Feature>IOT_POWERSHELL</Feature>
      <Feature>IOT_NETCMD</Feature>
      <Feature>IOT_SSH</Feature>
      <Feature>IOT_DISABLE_UMCI</Feature>
      <Feature>IOT_ENABLE_TESTSIGNING</Feature>
      <Feature>IOT_UMDFDBG_SETTINGS</Feature>
      <Feature>IOT_WDTF</Feature>
      <Feature>IOT_CRT140</Feature>
      <Feature>IOT_DIRECTX_TOOLS</Feature> -->
      <Feature>PRODUCTION_CORE</Feature>
    </Microsoft>

What I am missing here?
It is the IOT_TOOLKIT package required, or any other package is depending on it.
Thank you.

SampleAProv.ppkg for x64 doesn't exist

For x64, "BuildPkg All" fails because
C:\iot-adk-addonkit\Source-x64\Products\SampleA\prov\SampleAProv.ppkg doesn't exist.

How to correct?

How to update AddonKit for existing projects

Currently, updating the AddokKit for existing projects is tedious and error prone. This is because developer provided packages, bsps and products all exist within the same folder tree as AddonKit packages, bsps and products. So when there is a new ADK or new AddonKit version the developer is left with extracting a new copy of AddonKit and porting over all their specific items and changes.

If the AddonKit can be restructures so that AddonKit provided packages, bsps, and proucts are all in the same folder tree and developer created packages, bsps and products are in a separate folder tree then updating AddonKit becomes significantly simpler. And this would also enable the developer to manage their projects using GitHub and to pull updates from AddonKit directly into their projects while minimizing the possibility of merge conflicts.

Execution of BuildPkg All fails (like issue #36) but what is missing here??

Hi, I'm looking at the same errors as issue #36 but I don't see where my version mismatch is. Here is my post with a screenshot of all my current installed versions and the output. Thanks for any tips!

https://social.msdn.microsoft.com/Forums/windowshardware/en-US/e9d23187-70d8-409c-9655-fde0d727a9f5/errors-creating-basic-image-for-iotcore-arm-using-iotadkaddonkit?forum=HardwareBoards

IOT_NANORDPSERVER not working

On Rpi 3. IOT_NANORDPSERVER only connects the mouse. The PC doesn't see the image of the screen but the mouse movement on the PC moves the mouse on the device.

Never install my application

Hi, I have a problem, when I build an image and flash it to the SD memory, the Raspberry pi doesn't even install my app, it only restarts itself.

I have this isue on 15063 version only, the past versions worked perfectly.

What I am doing wrong?

I've also tried the "Lab 1a: Create a basic image" but I can not see any application.

Silicon labs CP210x USB to Serial driver not existing

I am trying to connect a PCB with a CP2102 IC to an RPi 3 running windows 10 iot core but it does not get detected. I followed the steps described in "Lab 1a: Create a basic image". The CP2102 driver is supposed to be included by default ( IOT_CP210x_MAKERDRIVER in TestOEMInput.xml) but it appears that this is not the case. Can you please help!

RetailOEMInput.xml must not use _TEST packages

Building an image with Source-arm/BSP/QCDB410C/OEMInputSamples/RetailOEMInput.xml generates an invalid image because _TEST packages are being used with ReleaseType = Production. These lines should have _TEST removed.