<?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>LayerscapeのトピックLayerscape LS1012A</title>
    <link>https://community.nxp.com/t5/Layerscape/Layerscape-LS1012A/m-p/2340437#M16601</link>
    <description>&lt;P&gt;I'm working with development board FRWY-LS1012A with board getting started guide.&lt;BR /&gt;I've prepared boot SD card and development board have been started with it.&lt;BR /&gt;Ethernet ports doesn't works, but it works only in u-boot mode.&amp;nbsp; What should i do with it.&lt;BR /&gt;Bootlog and u-boot logs are in attachment.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 26 Mar 2026 14:55:02 GMT</pubDate>
    <dc:creator>saleshin</dc:creator>
    <dc:date>2026-03-26T14:55:02Z</dc:date>
    <item>
      <title>Layerscape LS1012A</title>
      <link>https://community.nxp.com/t5/Layerscape/Layerscape-LS1012A/m-p/2340437#M16601</link>
      <description>&lt;P&gt;I'm working with development board FRWY-LS1012A with board getting started guide.&lt;BR /&gt;I've prepared boot SD card and development board have been started with it.&lt;BR /&gt;Ethernet ports doesn't works, but it works only in u-boot mode.&amp;nbsp; What should i do with it.&lt;BR /&gt;Bootlog and u-boot logs are in attachment.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Mar 2026 14:55:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Layerscape-LS1012A/m-p/2340437#M16601</guid>
      <dc:creator>saleshin</dc:creator>
      <dc:date>2026-03-26T14:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Layerscape LS1012A</title>
      <link>https://community.nxp.com/t5/Layerscape/Layerscape-LS1012A/m-p/2340639#M16602</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;DIV class="Y3BBE" data-processed="true" data-complete="true" data-hveid="CAEIAhAA" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;
&lt;DIV style="display: contents;" data-processed="true" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-subtree="aimfl"&gt;For the&amp;nbsp;&lt;/DIV&gt;
FRWY-LS1012A development board, the most common reason Ethernet works in U-Boot but not in Linux is a failure to load the Packet Forwarding Engine (PFE) firmware or a conflict with the PFE state between the bootloader and the kernel.&lt;SPAN class="uJ19be notranslate" data-processed="true" data-complete="true" data-sfc-cb="" data-wiz-uids="RzyiAf_k,RzyiAf_l" data-sfc-root="c"&gt;&lt;SPAN class="vKEkVd" data-sae="" data-wiz-attrbind="class=RzyiAf_j/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN aria-hidden="true"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="Fsg96" data-processed="true" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="otQkpb" role="heading" data-sae="" data-processed="true" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp="" data-animation-nesting="" aria-level="3"&gt;Immediate Solutions to Try&lt;/DIV&gt;
&lt;UL class="KsbFXc U6u95" data-processed="true" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAA" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Stop PFE in U-Boot: Before booting Linux, you must ensure the PFE is stopped in the bootloader so the Linux driver can take control cleanly.&lt;/SPAN&gt;
&lt;UL class="KsbFXc U6u95" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAB" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;In the U-Boot prompt, run: &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;=&amp;gt; pfe stop&lt;/CODE&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAC" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Then proceed with your boot command (e.g., &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;run bootcmd&lt;/CODE&gt;).&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAD" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Verify PFE Firmware Files: The Linux driver requires specific firmware files in your root filesystem to initialize the Ethernet ports.&lt;/SPAN&gt;
&lt;UL class="KsbFXc U6u95" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAE" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Ensure the following file exists: &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;/lib/firmware/ppfe_class_ls1012a.elf&lt;/CODE&gt;.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAF" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;If missing, you may need to copy them from your SDK or download the NXP PFE firmware package.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAG" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Check Device Tree (FDT): Ensure your boot sequence is loading the correct Device Tree Blob (DTB) for the FRWY board specifically, as using a generic LS1012A-RDB or FRDM tree can cause interface mismatches.&lt;/SPAN&gt;
&lt;UL class="KsbFXc U6u95" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;
&lt;LI class="dF3vjf" data-sae="" data-complete="true" data-hveid="CAEIBBAH" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="T286Pc" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Confirm your U-Boot &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;fdt_addr&lt;/CODE&gt; points to &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;fsl-ls1012a-frwy.dtb&lt;/CODE&gt; (or similar) during the &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;booti&lt;/CODE&gt; or &lt;CODE class="o8j0Mc" dir="ltr" data-sae="" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;bootm&lt;/CODE&gt; command.&lt;/SPAN&gt;&lt;SPAN class="uJ19be notranslate" data-complete="true" data-sfc-cb="" data-wiz-uids="RzyiAf_1q,RzyiAf_1r" data-sfc-root="c"&gt;&lt;SPAN class="vKEkVd" data-sae="" data-wiz-attrbind="class=RzyiAf_1p/TKHnVd" data-animation-atomic=""&gt;&lt;SPAN aria-hidden="true"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;DIV class="Fsg96" data-processed="true" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="Y3BBE" data-processed="true" data-complete="true" data-hveid="CAEICBAA" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;Regards&lt;/DIV&gt;</description>
      <pubDate>Thu, 26 Mar 2026 22:39:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/Layerscape-LS1012A/m-p/2340639#M16602</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2026-03-26T22:39:13Z</dc:date>
    </item>
  </channel>
</rss>

