<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Windows 10 IOT eMMC Flash Failure in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Windows-10-IOT-eMMC-Flash-Failure/m-p/1234874#M169868</link>
    <description>&lt;P&gt;Hi, We are working in Windows 10 IOT on iMX6DL. We needs to flash the eMMC to enable eMMC boot. We can see all the required partitions are getting created similar to SD in eMMC too. But, when we change the boot switch to eMMC boot, eMMC booting with older U-Boot which is not related to this Windows 10 IOT. On closer inspection, we find out that force_ro is not disabled resulting in BootLoader(firmware_fit.merged) is not getting flashed to eMMC. We used Linux MFG tool to flash that part alone to eMMC, then eMMC boots with Windows 10 IOT image. Our question is, why dism tool not able to write into that protected area which can be written using MFG tool? and is there a way to avoid using MFG tool to flash that protected boot partition?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2021 09:43:12 GMT</pubDate>
    <dc:creator>Zaid_Noordeen</dc:creator>
    <dc:date>2021-02-23T09:43:12Z</dc:date>
    <item>
      <title>Windows 10 IOT eMMC Flash Failure</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Windows-10-IOT-eMMC-Flash-Failure/m-p/1234874#M169868</link>
      <description>&lt;P&gt;Hi, We are working in Windows 10 IOT on iMX6DL. We needs to flash the eMMC to enable eMMC boot. We can see all the required partitions are getting created similar to SD in eMMC too. But, when we change the boot switch to eMMC boot, eMMC booting with older U-Boot which is not related to this Windows 10 IOT. On closer inspection, we find out that force_ro is not disabled resulting in BootLoader(firmware_fit.merged) is not getting flashed to eMMC. We used Linux MFG tool to flash that part alone to eMMC, then eMMC boots with Windows 10 IOT image. Our question is, why dism tool not able to write into that protected area which can be written using MFG tool? and is there a way to avoid using MFG tool to flash that protected boot partition?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 09:43:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Windows-10-IOT-eMMC-Flash-Failure/m-p/1234874#M169868</guid>
      <dc:creator>Zaid_Noordeen</dc:creator>
      <dc:date>2021-02-23T09:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: Windows 10 IOT eMMC Flash Failure</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Windows-10-IOT-eMMC-Flash-Failure/m-p/1250062#M171247</link>
      <description>&lt;P&gt;currently nxp doesn't support Windwos IOT anymore, any further questions, pls contact Microsoft directly&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 04:20:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Windows-10-IOT-eMMC-Flash-Failure/m-p/1250062#M171247</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2021-03-23T04:20:30Z</dc:date>
    </item>
  </channel>
</rss>

