locked
Raspberry Pi 3 IoT Core Retail Image RRS feed

  • Question

  • Hi,

    I am trying to build a retail image using the steps provided on this link: https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/build-retail-image.  See below for console output when building the image, with build tool versions provided

    IOTADK_ROOT : C:\iot-adk-addonkit-master
    ADK_VERSION : 17134
    WDK_VERSION : 17134
    COREKIT_VER : 17134.1
    OEM_NAME    : TTI
    
    Set Environment for Architecture
    Choose 1 for ARM, 2 for x86 and 3 for x64 : 1
    
    Configuring for arm architecture
    KitsRoot       : [C:\Program Files (x86)\Windows Kits\10\]
    WDKContentRoot : []
    Retail Signing disabled
    BSP_ARCH    : arm
    BSP_VERSION : 10.0.0.0
    BSPPKG_DIR  : C:\iot-adk-addonkit-master\Build\arm\pkgs
    MSPKG_DIR   : C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>retailsign on
    Retail Signing enabled
    
    IoTCoreShellv5.1 arm 10.0.0.0 Retail
    C:\iot-adk-addonkit-master\Tools>buildpkg Registry.FilesAndRegKeys
     Processing Registry.FilesAndRegKeys.wm.xml
    
    IoTCoreShellv5.1 arm 10.0.0.0 Retail
    C:\iot-adk-addonkit-master\Tools>buildimage TMC520 Retail
    Creating TMC520 Retail Image, see C:\iot-adk-addonkit-master\Build\arm\TMC520_Retail.log for progress

    See below for RetailOEMInput.xml

    <?xml version="1.0" encoding="utf-8"?>
    <OEMInput
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
      <Description>Contoso Windows 10 IoT Core Retail FFU with RPi2 BSP</Description>
      <SOC>RPi2</SOC>
      <!-- For recovery, use SOC: RPi2-R -->
      <SV>RASPBERRY PI</SV>
      <Device>RPi2</Device>
      <!-- For recovery, use Device: RPi2-R -->
      <ReleaseType>Production</ReleaseType>
      <BuildType>fre</BuildType>
      <SupportedLanguages>
        <UserInterface>
          <Language>en-us</Language>
        </UserInterface>
        <Keyboard>
          <Language>en-us</Language>
        </Keyboard>
        <Speech>
          <Language>en-us</Language>
        </Speech>
      </SupportedLanguages>
      <BootUILanguage>en-us</BootUILanguage>
      <BootLocale>en-us</BootLocale>
      <Resolutions>
        <Resolution>1024x768</Resolution>
      </Resolutions>
      <AdditionalFMs>
        <!-- Including BSP feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\RPi2FM.xml</AdditionalFM>
        <!-- Including OEM feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMCommonFM.xml</AdditionalFM>
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMFM.xml</AdditionalFM>
      </AdditionalFMs>
      <Features>
        <Microsoft>
          <Feature>IOT_EFIESP</Feature>
          <Feature>IOT_EFIESP_BCD_MBR</Feature>
          <Feature>IOT_DMAP_DRIVER</Feature>
          <Feature>IOT_GENERIC_POP</Feature>
          <!-- Following two required for Appx Installation -->
          <Feature>IOT_UAP_OOBE</Feature>
          <Feature>IOT_APP_TOOLKIT</Feature>
    	<!-- for Connectivity -->
          <Feature>IOT_POWERSHELL</Feature>
          <Feature>IOT_SSH</Feature>
        </Microsoft>
        <OEM>
          <!-- Include BSP Features -->
          <Feature>RPI2_DRIVERS</Feature>
          <Feature>RPI3_DRIVERS</Feature>
          <!-- Include OEM features -->
          <Feature>OEM_CustomCmd</Feature>
          <Feature>OEM_ProvAuto</Feature>
    	<!--<Feature>OEM_Merlin</Feature>
    	<Feature>OEM_MerlinUpdateServiceProvider</Feature>
    	<Feature>OEM_MerlinSshServiceProvider</Feature>-->
    	<Feature>OEM_FilesAndRegKeys</Feature>
          <!-- For recovery, include: RECOVERY_BCD_MBR -->
    
        </OEM>
      </Features>
      <Product>Windows 10 IoT Core</Product>
    </OEMInput>

    SSH and Powershell were added for customization purposes.

    See below for OEMFM.xml

    <?xml version="1.0" encoding="utf-8"?>
    <FeatureManifest
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
      <BasePackages/>
      <Features>
        <OEM>
          <!-- Feature definitions below -->
          <PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.IoTCoreDefaultApp.cab">
            <FeatureIDs>
              <FeatureID>APP_IOTCOREDEFAULTAPP</FeatureID>
              <FeatureID>OEM_IoTCoreDefaultApp</FeatureID> <!-- keeping old id for compatibility, dropping OEM prefix -->
            </FeatureIDs>
          </PackageFile>
          <PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.DigitalSign.cab">
            <FeatureIDs>
              <FeatureID>APP_DIGITALSIGN</FeatureID>
            </FeatureIDs>
          </PackageFile>
          <PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.IoTOnboardingTask.cab">
            <FeatureIDs>
              <FeatureID>APP_IOTONBOARDINGTASK</FeatureID>
              <FeatureID>OEM_IoTOnboardingTask</FeatureID> <!-- keeping old id for compatibility, dropping OEM prefix -->
            </FeatureIDs>
          </PackageFile>
          <PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.AzureDM.Services.cab">
            <FeatureIDs>
              <FeatureID>AZUREDM_SERVICES</FeatureID>
            </FeatureIDs>
          </PackageFile>
    	<PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.Merlin.cab">
            <FeatureIDs>
              <FeatureID>OEM_Merlin</FeatureID>
            </FeatureIDs>
          </PackageFile>
    	<PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.MerlinUpdateServiceProvider.cab">
            <FeatureIDs>
              <FeatureID>OEM_MerlinUpdateServiceProvider</FeatureID>
            </FeatureIDs>
          </PackageFile>
    	<PackageFile Path="%PKGBLD_DIR%" Name="%OEM_NAME%.Appx.MerlinSshServiceProvider.cab">
            <FeatureIDs>
              <FeatureID>OEM_MerlinSshServiceProvider</FeatureID>
            </FeatureIDs>
          </PackageFile>
        </OEM>
        <OEMFeatureGroups/>
      </Features>
    </FeatureManifest>

    Orignally, OEM_Merlin, OEM_MerlinUpdateServiceProvider, and OEM_MerlinSshServiceProvider were uncommented.  In that state, the OS did not boot (only a black screen was displayed after the Windows logo).  After looking at the customization xml file for each of those features, I noticed that they each had a StartupApp tag.  So, I commented out the Update and SSH service provider (leaving only OEM_Merlin).  After building the image again, the result was the same (only a black screen after the Windows logo).  Each of the applications in those packages are signed with the same certificate that was specified in setsignature.cmd.  See below for customizations.xml for the OEM_Merlin package

    <?xml version="1.0" encoding="utf-8" ?>
    <WindowsCustomizations>
      <PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0">
        <ID>{11d03d51-5081-4e53-80e3-2ad7e3ad9955}</ID>
        <Name>MerlinProv</Name>
        <Version>1.0.19.3</Version>
        <OwnerType>OEM</OwnerType>
        <Rank>0</Rank>
      </PackageConfig>
      <Settings xmlns="urn:schemas-microsoft-com:windows-provisioning">
        <Customizations>
          <Common>
            <Policies>
              <ApplicationManagement>
                <AllowAllTrustedApps>Yes</AllowAllTrustedApps>
              </ApplicationManagement>
            </Policies>
            <Certificates>
              <RootCertificates>
                <RootCertificate CertificateName="Merlin" Name="Merlin">
                  <CertificatePath>Merlin.cer</CertificatePath>
                </RootCertificate>
              </RootCertificates>
            </Certificates>
            <StartupApp>
              <Default>
               Telesis-88271_90e1hh2ad61gw!App 
              </Default>
            </StartupApp>
            <UniversalAppInstall>
              <UserContextApp>
                <Application PackageFamilyName="Telesis-88271_90e1hh2ad61gw" Name="Telesis-88271_90e1hh2ad61gw">
                  <ApplicationFile>Merlin.appx</ApplicationFile>
                  <DependencyAppxFiles>
                    <Dependency Name="Microsoft.VCLibs.ARM.14.00.appx">Microsoft.VCLibs.ARM.14.00.appx</Dependency>
                  </DependencyAppxFiles>
                  <DeploymentOptions>Force target application shutdown</DeploymentOptions>
                </Application>
              </UserContextApp>
            </UniversalAppInstall>
          </Common>
        </Customizations>
      </Settings>
    </WindowsCustomizations>
    

    See below for setsignature.cmd

    @echo off
    set SIGNTOOL_OEM_SIGN=/s my /i "DigiCert SHA2 Assured ID Code Signing CA" /n "TELESIS TECHNOLOGIES INC" /ac "C:\DigiCert Assured ID Root CA.crt" /fd SHA256
    REM Issuer        : Issuer of the Certificate ( see Certificate -> Details -> Issuer )
    REM Subject       : Subject in the certificate ( see Certificate -> Details -> Subject)
    REM CrossCertRoot : Microsoft supplied Cross Certificate Root (see Cross-Certificate List in https://msdn.microsoft.com/library/windows/hardware/dn170454(v=vs.85).aspx )
    
    REM for HAL certificate 
    REM set SIGNTOOL_OEM_SIGN_HAL=/s my /i "Issuer" /n "Subject" /ac "CrossCertRoot" /fd SHA256
    
    

    At this point, I'm not sure why the OS is not booting.  Any assistance would be helpful.

    Thanks!

    Monday, June 25, 2018 1:44 PM

Answers

  • Hi Michael,

    I fixed the problem.  The retail image was missing the IOT_CRT140 feature.  This feature provided the msvcp140 and vcruntime140 dll files that my application needed to start.  Thanks for all of your assistance!

    • Marked as answer by danhin Monday, July 9, 2018 5:49 PM
    Monday, July 9, 2018 5:49 PM

All replies

  • Hello danhin,<o:p></o:p>

    Have you tested for building a Sample product test image(not retail) instead of your custom product? And What bsp did you use?

    From this link(https://social.msdn.microsoft.com/Forums/windowsserver/en-US/bef2bd13-ee79-4a5e-834f-f314a4fee2ff/custom-iot-image-crashes-on-boot?forum=WindowsIoT), hope it is helpful.

    Best Regards,<o:p></o:p>

    Michael

    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, June 26, 2018 8:57 AM
  • Hi Michael,

    Thank you for your response.  To answer your questions, I am using the Raspberry Pi 3 BSP and the Test image did not work.  I tried building the Test image both with my application (removing the default startup app), and without my application (with the default startup app), and each time the OS would hang up on the Welcome Screen.  Before building the test image, I ensured that retail signing was disabled, and I rebuilt the BSP and all of the packages.  See below for console output

    IOTADK_ROOT : C:\iot-adk-addonkit-master
    ADK_VERSION : 17134
    WDK_VERSION : 17134
    COREKIT_VER : 17134.1
    OEM_NAME    : TTI
    
    Set Environment for Architecture
    Choose 1 for ARM, 2 for x86 and 3 for x64 : 1
    
    Configuring for arm architecture
    KitsRoot       : [C:\Program Files (x86)\Windows Kits\10\]
    WDKContentRoot : []
    Retail Signing disabled
    BSP_ARCH    : arm
    BSP_VERSION : 10.0.0.0
    BSPPKG_DIR  : C:\iot-adk-addonkit-master\Build\arm\pkgs
    MSPKG_DIR   : C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>c:\rpibsp\build.cmd
    signing c:\rpibsp\bcm2836pwm.sys
    signing c:\rpibsp\bcm2836sdhc.sys
    signing c:\rpibsp\bcmauxspi.sys
    signing c:\rpibsp\bcmgpio.sys
    signing c:\rpibsp\bcmi2c.sys
    signing c:\rpibsp\bcmspi.sys
    signing c:\rpibsp\pi_miniuart.sys
    signing c:\rpibsp\rpiq.sys
    signing c:\rpibsp\rpisdhc.sys
    signing c:\rpibsp\rpiwav.sys
    signing c:\rpibsp\SerPL011.sys
    signing c:\rpibsp\vchiq.sys
    signing c:\rpibsp\vchiq_arm_kern.dll
    signing c:\rpibsp\vcos_win32_kern.dll
    Building packages in c:\rpibsp\
     Processing bcm2836pwm.wm.xml
     Processing bcm2836sdhc.wm.xml
     Processing bcmauxspi.wm.xml
     Processing bcmgpio.wm.xml
     Processing bcmi2c.wm.xml
     Processing bcmspi.wm.xml
     Processing piminiuart.wm.xml
     Processing rpiq.wm.xml
     Processing rpisdhc.wm.xml
     Processing rpiwav.wm.xml
     Processing SerPL011.wm.xml
     Processing SV.PlatExtensions.wm.xml
     Processing vchiq.wm.xml
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>buildpkg all
    Building all provisioning packages
    Processing all provisioning packages
     Processing Provisioning.Enroll
     Processing Appx.DigitalSign
     Processing Appx.IoTCoreDefaultApp
     Processing Appx.IoTOnboardingTask
     Processing Appx.Merlin
     Processing Appx.MerlinSshServiceProvider
     Processing Appx.MerlinUpdateServiceProvider
     No .pkg.xml files found.
    Building all packages under C:\iot-adk-addonkit-master\Common\Packages
     Processing Custom.BCD.wm.xml
     Processing Custom.OOBEApp.wm.xml
     Processing Custom.Settings.wm.xml
     Processing Device.SystemInformation.wm.xml
     Processing DeviceLayout.GPT4GB.wm.xml
     Processing DeviceLayout.GPT8GB-R.wm.xml
     Processing DeviceLayout.MBR4GB.wm.xml
     Processing DeviceLayout.MBR8GB-R.wm.xml
     Processing Provisioning.Enroll.wm.xml
     Processing Recovery.GPT-BCD.wm.xml
     Processing Recovery.GPT-BcdEdit.wm.xml
     Processing Recovery.MBR-BCD.wm.xml
     Processing Recovery.MBR-BcdEdit.wm.xml
     Processing Registry.FilesAndRegKeys.wm.xml
     Processing Registry.Version.wm.xml
     Processing Security.Bitlocker.wm.xml
     Processing Security.DeviceGuard.wm.xml
     Processing Security.SecureBoot.wm.xml
     Processing Settings.HotKey.wm.xml
    Building all packages under C:\iot-adk-addonkit-master\Source-arm\Packages
     Processing Appx.DigitalSign.wm.xml
     Processing Appx.IoTCoreDefaultApp.wm.xml
     Processing Appx.IoTOnboardingTask.wm.xml
     Processing Appx.Merlin.wm.xml
     Processing Appx.MerlinSshServiceProvider.wm.xml
     Processing Appx.MerlinUpdateServiceProvider.wm.xml
     Processing AzureDM.Services.wm.xml
    Building all bsp packages
     Processing CustomRPi2.GPIO.wm.xml
     Processing Custom.SMBIOS.wm.xml
     Processing QCDB410C.DeviceLayout-R.wm.xml
     Processing QCDB410C.DevicePlatform-R.wm.xml
     Processing RPi.Customization.wm.xml
    -----build done-----
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>buildimage TMC520 Test
    Creating TMC520 Test Image, see C:\iot-adk-addonkit-master\Build\arm\TMC520_Test.log for progress
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>buildimage TMC520 Test
    Creating TMC520 Test Image, see C:\iot-adk-addonkit-master\Build\arm\TMC520_Test.log for progress
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>

    After looking at the link that you provided, I don't think that that is the cause of my problem, as the change that that poster made in a pull request was already done (commenting out the ComputerName tag in Templates\customizations.xml).  Plus, I was using the default computer name of minwinpc when flashing the image with Windows 10 Iot Core Dashboard

    For reference, here is TestOEMInput.xml

    <?xml version="1.0" encoding="utf-8"?>
    <OEMInput
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
      <Description>Contoso Windows 10 IoT Core Test FFU with RPi2 BSP</Description>
      <SOC>RPi2</SOC>
      <!-- For recovery, use SOC: RPi2-R -->
      <SV>RASPBERRY PI</SV>
      <Device>RPi2</Device>
      <!-- For recovery, use Device: RPi2-R -->
      <ReleaseType>Test</ReleaseType>
      <BuildType>fre</BuildType>
      <SupportedLanguages>
        <UserInterface>
          <Language>en-us</Language>
        </UserInterface>
        <Keyboard>
          <Language>en-us</Language>
        </Keyboard>
        <Speech>
          <Language>en-us</Language>
        </Speech>
      </SupportedLanguages>
      <BootUILanguage>en-us</BootUILanguage>
      <BootLocale>en-us</BootLocale>
      <Resolutions>
        <Resolution>1024x768</Resolution>
      </Resolutions>
      <AdditionalFMs>
        <!-- Including BSP feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\RPi2FM.xml</AdditionalFM>
        <!-- Including OEM feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMCommonFM.xml</AdditionalFM>
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMFM.xml</AdditionalFM>
    
        <!-- Including the test features -->
        <AdditionalFM>%AKROOT%\FMFiles\arm\IoTUAPNonProductionPartnerShareFM.xml</AdditionalFM>
      </AdditionalFMs>
      <Features>
        <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>
          <!-- Following two required for Appx Installation -->
          <Feature>IOT_UAP_OOBE</Feature>
          <Feature>IOT_APP_TOOLKIT</Feature>
          <!-- for Connectivity -->
          <Feature>IOT_WEBB_EXTN</Feature>
          <Feature>IOT_POWERSHELL</Feature>
          
          <Feature>IOT_SSH</Feature>
          <Feature>IOT_SIREP</Feature>
          <!-- Enabling Test images -->
          <Feature>IOT_ENABLE_TESTSIGNING</Feature>
          <Feature>IOT_TOOLKIT</Feature>
          <!-- Debug Features -->
          <Feature>IOT_KDSERIAL_SETTINGS</Feature>
          <Feature>IOT_UMDFDBG_SETTINGS</Feature>
          <Feature>IOT_WDTF</Feature>
          <Feature>IOT_CRT140</Feature>
          <Feature>IOT_DIRECTX_TOOLS</Feature>
          
          <!-- Sample Apps, remove this when you introduce OEM Apps -->
          <Feature>IOT_BERTHA</Feature>
          <Feature>IOT_ALLJOYN_APP</Feature>
          <Feature>IOT_NANORDPSERVER</Feature>
          <Feature>IOT_SHELL_HOTKEY_SUPPORT</Feature>
          <Feature>IOT_APPLICATIONS</Feature>
    
        </Microsoft>
        <OEM>
          <!-- Include BSP Features -->
          <Feature>RPI2_DRIVERS</Feature>
          <Feature>RPI3_DRIVERS</Feature>
          <!-- Include OEM features -->
          <Feature>OEM_CustomCmd</Feature>
          <Feature>OEM_ProvAuto</Feature>
    	<!--<Feature>OEM_Merlin</Feature>
    	<Feature>OEM_MerlinUpdateServiceProvider</Feature>
    	<Feature>OEM_MerlinSshServiceProvider</Feature>
    	<Feature>OEM_FilesAndRegKeys</Feature>-->
          <!-- For recovery, include: RECOVERY_BCD_MBR -->
    
        </OEM>
      </Features>
      <Product>Windows 10 IoT Core</Product>
    </OEMInput>
    Thanks!

    Tuesday, June 26, 2018 2:05 PM
  • hi

    which Raspberry Pi 3 is it, Model B or Model B+ ?

    br
    Andre

    Tuesday, June 26, 2018 3:07 PM
  • Hi Andre,

    It is a Raspberry Pi Model B.  Would that make a difference?

    Thanks!

    Tuesday, June 26, 2018 4:39 PM
  • hi

    its expected to work with Model B but not with Model B+ which currently exists as Technical Preview only due to Hardware changes

    br
    Andre

    Tuesday, June 26, 2018 4:48 PM
  • Hello danhin,

    I think you can try to use IoT Dashboard to flush a official image to SD card to verify the device is normal, or use another SD card to test this issue.

    Best Regard,

    Michael


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, June 27, 2018 9:18 AM
  • Hi Michael,

    Thank for your response.  What follows is an update on the situation.

    1.) I'm using a Raspberry Pi 3 Model B with a Samsung Evo 32 GB Class 10 SD card

    2.) I flashed a known-good test image that I had built using the 16299 build tools and Raspberry Pi BSP to the device, and it booted successfully.  This is the image that we had been using during testing

    3.) I flashed the test image that I had built using the 17134 build tools and Raspberry Pi BSP to the device, and it hung on the blue Welcome screen

    4.) I flashed the official 17134 image for the Raspberry Pi to the device, and it booted successfully.

    Each image was flashed using the IoT Dashboard, and the 17134 test image was built by following the steps in the image-building lab on Microsoft's website.  Previously, I had encountered the following bugs with the 17134 build tools and Raspberry Pi BSP: a dll was missing from the ADK install which was restored after a repair, and the package definition files (*.wm.xml) were missing from the BSP source which were restored after I downloaded them from the 16299 BSP.  Both of these problems prevented the image from being built.

    **Edit**

    The build.cmd program that builds the Raspberry Pi BSP requires *.wm.xml package definition files.  The 17134 Raspberry Pi BSP does not have those files for any of the driver packages.  Instead, the have *.pkg.xml files.  Even though copying the 16299 *.wm.xml files into the 17134 BSP source folder allowed the packages to build, I suspect that these drivers were not installed properly into the image.

    For reference, here is bcm2836pwm.wm.xml

    <?xml version="1.0" encoding="utf-8"?>
    <identity xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        name="bcm2836pwm"
        namespace="RPi"
        owner="$(OEMNAME)"
        legacyName="$(OEMNAME).RPi.bcm2836pwm" xmlns="urn:Microsoft.CompPlat/ManifestSchema.v1.00">
        <onecorePackageInfo
            targetPartition="MainOS"
            releaseType="Production"
            ownerType="OEM" />
        <drivers>
            <driver>
                <inf source="$(_RELEASEDIR)bcm2836pwm.inf" />
            </driver>
        </drivers>
    </identity>

    And, here is bcm2836pwm.pkg.xml

    <?xml version="1.0" encoding="utf-8"?>
    <!-- TODO: Make sure to set the Package attributes -->
    <Package xmlns="urn:Microsoft.WindowsPhone/PackageSchema.v8.00"
      Owner="$(OEMNAME)"
      OwnerType="OEM"
      Platform="$(BSPARCH)"
      Component="RPi"
      SubComponent="bcm2836pwm"
      ReleaseType="Production" >
    
      <Components>
        <Driver InfSource="$(_RELEASEDIR)bcm2836pwm.inf">
          <Reference Source="$(_RELEASEDIR)bcm2836pwm.sys" />
          <Files>
            <!-- For kernel mode drivers, $(DRIVER_DEST) evaluates to "drivers" by default -->
            <!-- For user mode drivers, $(DRIVER_DEST) evaluates to "drivers\umdf" by default -->
            <File Source="$(_RELEASEDIR)bcm2836pwm.sys" DestinationDir="$(runtime.system32)\drivers" />
          </Files>
        </Driver>
    
      </Components>
    </Package>

    Simply copying the contents from the pkg.xml file into the wm.xml file did not work.  Also, copying the driver tag information from the pkg.xml file into the wm.xml file did not work.  The console output is shown below

    IOTADK_ROOT : C:\iot-adk-addonkit-master
    ADK_VERSION : 17134
    WDK_VERSION : 17134
    COREKIT_VER : 17134.1
    OEM_NAME    : TTI
    
    Set Environment for Architecture
    Choose 1 for ARM, 2 for x86 and 3 for x64 : 1
    
    Configuring for arm architecture
    KitsRoot       : [C:\Program Files (x86)\Windows Kits\10\]
    WDKContentRoot : []
    Retail Signing disabled
    BSP_ARCH    : arm
    BSP_VERSION : 10.0.0.0
    BSPPKG_DIR  : C:\iot-adk-addonkit-master\Build\arm\pkgs
    MSPKG_DIR   : C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail\arm\fre
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>c:\rpibsp\build.cmd
    signing c:\rpibsp\bcm2836pwm.sys
    signing c:\rpibsp\bcm2836sdhc.sys
    signing c:\rpibsp\bcmauxspi.sys
    signing c:\rpibsp\bcmgpio.sys
    signing c:\rpibsp\bcmi2c.sys
    signing c:\rpibsp\bcmspi.sys
    signing c:\rpibsp\pi_miniuart.sys
    signing c:\rpibsp\rpiq.sys
    signing c:\rpibsp\rpisdhc.sys
    signing c:\rpibsp\rpiwav.sys
    signing c:\rpibsp\SerPL011.sys
    signing c:\rpibsp\vchiq.sys
    signing c:\rpibsp\vchiq_arm_kern.dll
    signing c:\rpibsp\vcos_win32_kern.dll
    Building packages in c:\rpibsp\
     Processing bcm2836pwm.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcm2836pwm.wm.log
     Processing bcm2836sdhc.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcm2836sdhc.wm.log
     Processing bcmauxspi.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcmauxspi.wm.log
     Processing bcmgpio.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcmgpio.wm.log
     Processing bcmi2c.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcmi2c.wm.log
     Processing bcmspi.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcmspi.wm.log
     Processing piminiuart.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\piminiuart.wm.log
     Processing rpiq.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\rpiq.wm.log
     Processing rpisdhc.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\rpisdhc.wm.log
     Processing rpiwav.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\rpiwav.wm.log
     Processing SerPL011.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\SerPL011.wm.log
     Processing SV.PlatExtensions.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\SV.PlatExtensions.wm.log
     Processing vchiq.wm.xml
    (PkgBldr.Common) : error : no schema found for urn:Microsoft.WindowsPhone/PackageSchema.v8.00
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\vchiq.wm.log
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>c:\rpibsp\build.cmd
    signing c:\rpibsp\bcm2836pwm.sys
    signing c:\rpibsp\bcm2836sdhc.sys
    signing c:\rpibsp\bcmauxspi.sys
    signing c:\rpibsp\bcmgpio.sys
    signing c:\rpibsp\bcmi2c.sys
    signing c:\rpibsp\bcmspi.sys
    signing c:\rpibsp\pi_miniuart.sys
    signing c:\rpibsp\rpiq.sys
    signing c:\rpibsp\rpisdhc.sys
    signing c:\rpibsp\rpiwav.sys
    signing c:\rpibsp\SerPL011.sys
    signing c:\rpibsp\vchiq.sys
    signing c:\rpibsp\vchiq_arm_kern.dll
    signing c:\rpibsp\vcos_win32_kern.dll
    Building packages in c:\rpibsp\
     Processing bcm2836pwm.wm.xml
    (4,4): error The element 'identity' in namespace 'urn:Microsoft.CompPlat/ManifestSchema.v1.00' has invalid child element 'Components' in namespace 'urn:Microsoft.CompPlat/ManifestSchema.v1.00'. List of possible elements expected: 'bcdStore, language, files, drivers, macros, regKeys, directories, service, serviceGroup, accounts, COM, trustInfo, onecorePackageInfo' in namespace 'urn:Microsoft.CompPlat/ManifestSchema.v1.00'.
    (PkgBldr.Common) : error : PkgBldrCommon schema validation failed
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcm2836pwm.wm.log
     Processing bcm2836sdhc.wm.xml
     Processing bcmauxspi.wm.xml
     Processing bcmgpio.wm.xml
     Processing bcmi2c.wm.xml
     Processing bcmspi.wm.xml
     Processing piminiuart.wm.xml
     Processing rpiq.wm.xml
     Processing rpisdhc.wm.xml
     Processing rpiwav.wm.xml
     Processing SerPL011.wm.xml
     Processing SV.PlatExtensions.wm.xml
     Processing vchiq.wm.xml
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>c:\rpibsp\build.cmd
    signing c:\rpibsp\bcm2836pwm.sys
    signing c:\rpibsp\bcm2836sdhc.sys
    signing c:\rpibsp\bcmauxspi.sys
    signing c:\rpibsp\bcmgpio.sys
    signing c:\rpibsp\bcmi2c.sys
    signing c:\rpibsp\bcmspi.sys
    signing c:\rpibsp\pi_miniuart.sys
    signing c:\rpibsp\rpiq.sys
    signing c:\rpibsp\rpisdhc.sys
    signing c:\rpibsp\rpiwav.sys
    signing c:\rpibsp\SerPL011.sys
    signing c:\rpibsp\vchiq.sys
    signing c:\rpibsp\vchiq_arm_kern.dll
    signing c:\rpibsp\vcos_win32_kern.dll
    Building packages in c:\rpibsp\
     Processing bcm2836pwm.wm.xml
    (4,12): error The 'InfSource' attribute is not declared.
    (PkgBldr.Common) : error : PkgBldrCommon schema validation failed
    Error : Failed to create package. See C:\iot-adk-addonkit-master\Build\arm\pkgs\logs\bcm2836pwm.wm.log
     Processing bcm2836sdhc.wm.xml
     Processing bcmauxspi.wm.xml
     Processing bcmgpio.wm.xml
     Processing bcmi2c.wm.xml
     Processing bcmspi.wm.xml
     Processing piminiuart.wm.xml
     Processing rpiq.wm.xml
     Processing rpisdhc.wm.xml
     Processing rpiwav.wm.xml
     Processing SerPL011.wm.xml
     Processing SV.PlatExtensions.wm.xml
     Processing vchiq.wm.xml
    
    IoTCoreShellv5.1 arm 10.0.0.0
    C:\iot-adk-addonkit-master\Tools>

    The log files generated produced a stack trace.

    How do I proceed from here?

    Thanks!


    • Edited by danhin Wednesday, June 27, 2018 1:55 PM New Information
    Wednesday, June 27, 2018 1:00 PM
  • Hello danhin,

    How did you created the raspberry pi driver? Did you look this document(https://docs.microsoft.com/en-us/windows/iot-core/build-your-image/createbsps#raspberry-pi-bsp)?

    To build a retail image, you will need to rerun the build.cmd to sign the bsp driver binaries with cross certificates. See IoT Core Manufacturing Guide for detailed instructions.

    Best Regards,

    Michael


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, June 28, 2018 6:45 AM
  • Hi Michael,

    Before building the retail image, I downloaded the pre-built Raspberry Pi BSP and ran build.cmd to sign the drivers with the cross-certificates.  Initially, build.cmd failed in that case because the package definition files were missing.  To remedy that problem, I tried using the wm.xml files from the 16299 BSP.  The BSP and the image were able to build, but the device would hang on bootup.  I found an issue link on Github that is very similar to what I'm experiencing: https://github.com/ms-iot/bsp/issues/39.  Currently, that issue is unresolved.  I attempted the fix outlined in the issue link (running buildpkg on each pkg.xml file in the BSP source folder).  Unfortunately, the result was the same.  Since getting a working Retail image has been impossible up to this point, I've been trying the Test image.  I am unsure as to why downloading the 17134 build tools and Raspberry Pi BSP cannot even build an out-of-the-box Test image that boots successfully.

    Is there something that I'm missing?  Would rolling back all of the build tools and the BSP to 16299 be a plausible fix in this case since I can't get 17134 to boot at all?

    Thursday, June 28, 2018 12:40 PM
  • Hi,

    for the RPi drivers, you can use the rpi zip available here : https://github.com/ms-iot/iot-adk-addonkit/releases/download/v4.4/rpibsp-wm.zip. I will have the doc updated with the proper link.

    Please sign the drivers with your certificate and build the image. 

    Another point is that you should include the cert only once, if its the same cert you use for all applications. So, you can generate the package without the cert inclusion by specifying -skipcert in the newappxpkg cmd. This will remove the cert entry for those packages. 

    -Paramesh

    Friday, June 29, 2018 7:08 PM
  • Hello danhin,

    Could you please upload the test image which also can not boot  to a repo, so that we need to hook up windbg and debug ?

    Best Regards,

    Michael


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 2, 2018 1:52 AM
  • Hi,

    My apologies for the delay.  We were running additional tests here.  Below is a summary of what we have done.

    1.) On a new PC, we followed the steps in the IoT Manufacturing Guide to create a test image using the 16299 tools and the rpibsp-wm drivers linked above.  This image contained all of our customizations, and it worked great on a Raspberry Pi 3.

    2.) We followed the steps in the guide for building a retail image, including setting the certificate, rebuilding the BSP drivers, building all of the packages, and re-signing the cabs after we added our customizations from the test image.

    At first, we thought that the image wasn't booting when flashed to a Pi.  Then, we discovered that the OS was booting, but our OEM app was hanging.  After additional debugging with Visual Studio, I found the problem.  The following error is displayed when trying to run our app: "Unable to activate Windows Store app.  The app failed to start."  Also, a message "A dependent dll failed to load" is displayed the the Debug Output window.  Unfortunately, the solutions that I've found (cleaning the solution and rebuilding, and deleting the output folders) haven't worked.  Plus, I'm not sure how to run DependencyWalker or gflags on a Raspberry Pi.

    Any additional guidance here would be very helpful.

    **Edit**

    Would an EV code signing certificate be required to sign the drivers in the BSP?  Currently, we're using the same standard code signing certificate to sign the BSP drivers, OS packages, and our application (in Visual Studio).  There has been some speculation here that using the same certificate to sign our application in Visual Studio and to sign the BSP drivers and OS packages for the retail image could be causing our problems.

    Below are the OEM Input files that we're using

    TestOEMInput

    <?xml version="1.0" encoding="utf-8"?>
    <OEMInput
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
      <Description>Contoso Windows 10 IoT Core Test FFU with RPi2 BSP</Description>
      <SOC>RPi2</SOC>
      <!-- For recovery, use SOC: RPi2-R -->
      <SV>RASPBERRY PI</SV>
      <Device>RPi2</Device>
      <!-- For recovery, use Device: RPi2-R -->
      <ReleaseType>Test</ReleaseType>
      <BuildType>fre</BuildType>
      <SupportedLanguages>
        <UserInterface>
          <Language>en-us</Language>
        </UserInterface>
        <Keyboard>
          <Language>en-us</Language>
        </Keyboard>
        <Speech>
          <Language>en-us</Language>
        </Speech>
      </SupportedLanguages>
      <BootUILanguage>en-us</BootUILanguage>
      <BootLocale>en-us</BootLocale>
      <Resolutions>
        <Resolution>1024x768</Resolution>
      </Resolutions>
      <AdditionalFMs>
        <!-- Including BSP feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\RPi2FM.xml</AdditionalFM>
        <!-- Including OEM feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMCommonFM.xml</AdditionalFM>
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMFM.xml</AdditionalFM>
    
        <!-- Including the test features -->
        <AdditionalFM>%AKROOT%\FMFiles\arm\IoTUAPNonProductionPartnerShareFM.xml</AdditionalFM>
      </AdditionalFMs>
      <Features>
        <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>
          <!-- Following two required for Appx Installation -->
          <Feature>IOT_UAP_OOBE</Feature>
          <Feature>IOT_APP_TOOLKIT</Feature>
          <!-- for Connectivity -->
          <Feature>IOT_WEBB_EXTN</Feature>
          <Feature>IOT_POWERSHELL</Feature>
          <Feature>IOT_NETCMD</Feature>
          <Feature>IOT_SSH</Feature>
          <Feature>IOT_SIREP</Feature>
          <!-- Enabling Test images -->
          <Feature>IOT_ENABLE_TESTSIGNING</Feature>
          <Feature>IOT_TOOLKIT</Feature>
          <!-- Debug Features -->
          <Feature>IOT_KDSERIAL_SETTINGS</Feature>
          <Feature>IOT_UMDFDBG_SETTINGS</Feature>
          <Feature>IOT_WDTF</Feature>
          <Feature>IOT_CRT140</Feature>
          <Feature>IOT_DIRECTX_TOOLS</Feature>
          <Feature>PRODUCTION_CORE</Feature>
          <!-- Sample Apps, remove this when you introduce OEM Apps
          <Feature>IOT_BERTHA</Feature> -->
          <Feature>IOT_ALLJOYN_APP</Feature>
          <Feature>IOT_NANORDPSERVER</Feature>
          <Feature>IOT_SHELL_HOTKEY_SUPPORT</Feature>
          <Feature>IOT_APPLICATIONS</Feature>
    	<Feature>IOT_UNIFIED_WRITE_FILTER</Feature>
        </Microsoft>
        <OEM>
          <!-- Include BSP Features -->
          <Feature>RPI2_DRIVERS</Feature>
          <Feature>RPI3_DRIVERS</Feature>
          <!-- Include OEM features -->
          <Feature>OEM_CustomCmd</Feature>
          <Feature>OEM_ProvAuto</Feature>
    	<Feature>OEM_Merlin</Feature>
    	<Feature>OEM_FilesAndRegKeys</Feature>
    	<Feature>OEM_MerlinSshServiceProvider</Feature>
    	<Feature>OEM_MerlinUpdateServiceProvider</Feature>
          <!-- For recovery, include: RECOVERY_BCD_MBR -->
    
        </OEM>
      </Features>
      <Product>Windows 10 IoT Core</Product>
    </OEMInput>

    RetailOEMInput (with temporary changes for debugging)

    <?xml version="1.0" encoding="utf-8"?>
    <OEMInput
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://schemas.microsoft.com/embedded/2004/10/ImageUpdate">
      <Description>Contoso Windows 10 IoT Core Retail FFU with RPi2 BSP</Description>
      <SOC>RPi2</SOC>
      <!-- For recovery, use SOC: RPi2-R -->
      <SV>RASPBERRY PI</SV>
      <Device>RPi2</Device>
      <!-- For recovery, use Device: RPi2-R -->
      <ReleaseType>Production</ReleaseType>
      <BuildType>fre</BuildType>
      <SupportedLanguages>
        <UserInterface>
          <Language>en-us</Language>
        </UserInterface>
        <Keyboard>
          <Language>en-us</Language>
        </Keyboard>
        <Speech>
          <Language>en-us</Language>
        </Speech>
      </SupportedLanguages>
      <BootUILanguage>en-us</BootUILanguage>
      <BootLocale>en-us</BootLocale>
      <Resolutions>
        <Resolution>1024x768</Resolution>
      </Resolutions>
      <AdditionalFMs>
        <!-- Including BSP feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\RPi2FM.xml</AdditionalFM>
        <!-- Including OEM feature manifest -->
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMCommonFM.xml</AdditionalFM>
        <AdditionalFM>%BLD_DIR%\MergedFMs\OEMFM.xml</AdditionalFM>
      </AdditionalFMs>
      <Features>
        <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>
          <!-- Following two required for Appx Installation -->
          <Feature>IOT_UAP_OOBE</Feature>
          <Feature>IOT_APP_TOOLKIT</Feature>
    	<!-- for Connectivity -->
    	<Feature>IOT_WEBB_EXTN</Feature>
          <Feature>IOT_POWERSHELL</Feature>
          <Feature>IOT_NETCMD</Feature>
          <Feature>IOT_SSH</Feature>
          <Feature>IOT_SIREP</Feature>
          <!-- Enabling Test images -->
          <Feature>IOT_ENABLE_TESTSIGNING</Feature>
          <Feature>IOT_TOOLKIT</Feature>
          <!-- Debug Features -->
    	<Feature>PRODUCTION_CORE</Feature>
          <!-- Sample Apps, remove this when you introduce OEM Apps -->
          <Feature>IOT_BERTHA</Feature>
          <Feature>IOT_ALLJOYN_APP</Feature>
          <Feature>IOT_NANORDPSERVER</Feature>
          <Feature>IOT_SHELL_HOTKEY_SUPPORT</Feature>
          <Feature>IOT_APPLICATIONS</Feature>
    	<Feature>IOT_UNIFIED_WRITE_FILTER</Feature>
        </Microsoft>
        <OEM>
          <!-- Include BSP Features -->
          <Feature>RPI2_DRIVERS</Feature>
          <Feature>RPI3_DRIVERS</Feature>
          <!-- Include OEM features -->
          <Feature>OEM_CustomCmd</Feature>
          <Feature>OEM_ProvAuto</Feature>
    	<!--<Feature>OEM_Merlin</Feature>-->
    	<Feature>OEM_FilesAndRegKeys</Feature>
    	<Feature>OEM_MerlinSshServiceProvider</Feature>
    	<Feature>OEM_MerlinUpdateServiceProvider</Feature>
          <!-- For recovery, include: RECOVERY_BCD_MBR -->
    
        </OEM>
      </Features>
      <Product>Windows 10 IoT Core</Product>
    </OEMInput>
    Thanks!


    • Edited by danhin Thursday, July 5, 2018 2:30 PM Additional Question
    Tuesday, July 3, 2018 7:15 PM
  • Hello danhin,

    Sorry for late response.

    Have you tested building the retail image with test certificate?

    Or could you please upload the image to a repo so that we can wnddbg.?

    Best Regards,

    Michael


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, July 6, 2018 3:32 AM
  • Hi Michael,

    Here is a Sharefile link to a folder where both the working test image and the failing retail image can be downloaded: https://telesis.sharefile.com/i/i83362f3b559486f8

    Please copy that link into your browser, as I can't post links because my account hasn't been verified.

    Since you don't have our companion board to connect to the Raspberry Pi 3 Model B, you may have problems starting our application.

    Thanks!

    Friday, July 6, 2018 1:19 PM
  • Hi Michael,

    I fixed the problem.  The retail image was missing the IOT_CRT140 feature.  This feature provided the msvcp140 and vcruntime140 dll files that my application needed to start.  Thanks for all of your assistance!

    • Marked as answer by danhin Monday, July 9, 2018 5:49 PM
    Monday, July 9, 2018 5:49 PM
  • I know this thread is marked as solved, but i have a question to @danhin related to retail image building. I'm very new to this, i was able to successfully build some test images, but i'm not able to build a retail image. Do i Need something special to do that? I read something about certificates on this thread. Hope someone can help me out :)

    Best Regards

    Saturday, September 15, 2018 5:51 PM