<?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 ATOM E3845 LVDS Display and SSD Problem (FIRSTMEGABYTEPOLICY) in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/ATOM-E3845-LVDS-Display-and-SSD-Problem-FIRSTMEGABYTEPOLICY/m-p/484405#M23736</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use a E3845 Prozessor on a so called "computer on a module" based industrial PC. Connected to the display port there is a eDP to LVDS bridge which is&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;connected to the TFT display.&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of our used eal time system based on WinCE 6.0 which is running "below" Windows 10 we need to set the boote code parameter "FIRSTMEGABYTEPOLICY=UseAll".&lt;/P&gt;&lt;P&gt;So, Windows uses the first 1MB as a "normal" memory.&lt;/P&gt;&lt;P&gt;If we set FIRSTMEGABYTEPOLICY=UseAll we have the Problem that after rebooting sometimes the display keeps black ! This happens because during boot up, the&lt;/P&gt;&lt;P&gt;display ports were not detected and the VGA output is used.&lt;/P&gt;&lt;P&gt;If we set FIRSTMEGABYTEPOLICY=UseNone then directly we have no problems at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the same system we had some problems by using SSD's. We had some crashes were the SSD disapeared and windows start rebooting, but that failed, because the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;SSD is not detected.&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally we have the situation that two on chip devices were "disappearing" when the boote code parameter FIRSTMEGABYTEPOLICY is set to UseAll, which means&lt;/P&gt;&lt;P&gt;that the first megabyte is used dynamic by windows.&lt;/P&gt;</description>
    <pubDate>Wed, 24 May 2017 07:01:53 GMT</pubDate>
    <dc:creator>WGert</dc:creator>
    <dc:date>2017-05-24T07:01:53Z</dc:date>
    <item>
      <title>ATOM E3845 LVDS Display and SSD Problem (FIRSTMEGABYTEPOLICY)</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/ATOM-E3845-LVDS-Display-and-SSD-Problem-FIRSTMEGABYTEPOLICY/m-p/484405#M23736</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use a E3845 Prozessor on a so called "computer on a module" based industrial PC. Connected to the display port there is a eDP to LVDS bridge which is&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;connected to the TFT display.&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of our used eal time system based on WinCE 6.0 which is running "below" Windows 10 we need to set the boote code parameter "FIRSTMEGABYTEPOLICY=UseAll".&lt;/P&gt;&lt;P&gt;So, Windows uses the first 1MB as a "normal" memory.&lt;/P&gt;&lt;P&gt;If we set FIRSTMEGABYTEPOLICY=UseAll we have the Problem that after rebooting sometimes the display keeps black ! This happens because during boot up, the&lt;/P&gt;&lt;P&gt;display ports were not detected and the VGA output is used.&lt;/P&gt;&lt;P&gt;If we set FIRSTMEGABYTEPOLICY=UseNone then directly we have no problems at all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the same system we had some problems by using SSD's. We had some crashes were the SSD disapeared and windows start rebooting, but that failed, because the&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;SSD is not detected.&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally we have the situation that two on chip devices were "disappearing" when the boote code parameter FIRSTMEGABYTEPOLICY is set to UseAll, which means&lt;/P&gt;&lt;P&gt;that the first megabyte is used dynamic by windows.&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2017 07:01:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/ATOM-E3845-LVDS-Display-and-SSD-Problem-FIRSTMEGABYTEPOLICY/m-p/484405#M23736</guid>
      <dc:creator>WGert</dc:creator>
      <dc:date>2017-05-24T07:01:53Z</dc:date>
    </item>
    <item>
      <title>Re: ATOM E3845 LVDS Display and SSD Problem (FIRSTMEGABYTEPOLICY)</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/ATOM-E3845-LVDS-Display-and-SSD-Problem-FIRSTMEGABYTEPOLICY/m-p/484406#M23737</link>
      <description>&lt;P&gt;Hi &lt;B&gt; wolleIntel&lt;/B&gt;: Thank you very much for joining the Intel® Processors communities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;In order to get the proper assistance on this matter, please submit your inquiry in our Intel® Embedded Design Center, you will be able to get further peer assistance in there:&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;A href="https://embedded.communities.intel.com/community/en/"&gt;https://embedded.communities.intel.com/community/en/&lt;/A&gt; &lt;A href="https://embedded.communities.intel.com/community/en/"&gt;https://embedded.communities.intel.com/community/en/&lt;/A&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;Regards,&lt;P&gt;&amp;nbsp;&lt;/P&gt;Alberto R</description>
      <pubDate>Wed, 24 May 2017 17:36:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/ATOM-E3845-LVDS-Display-and-SSD-Problem-FIRSTMEGABYTEPOLICY/m-p/484406#M23737</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2017-05-24T17:36:34Z</dc:date>
    </item>
  </channel>
</rss>

