<?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中的主题 LS1046 Nandflash Problem</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046-Nandflash-Problem/m-p/1650336#M12468</link>
    <description>&lt;P&gt;&lt;EM&gt;Dear:&lt;/EM&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Our product uses NXP LS1046A and SDK uses LSDK2108. We have a problem: we plan to put uboot into qspiflash, and kernel, dtb and rootfs into 512MB nandflash. N&lt;/SPAN&gt;&lt;SPAN class=""&gt;andflash is divided into three areas, the size of which is 16M, 48M and 448M. dtb file, kernel image and rootfs are placed respectively.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;The current problems is whether the build/Linux/Linux/arm64 / LS/Image&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Or build/Linux/Linux/arm64 / LS/called burn into the nand flash - 5.10.35 - dirty,&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;If bootm $load_addr $fdtaddr is used after the uboot reads to the memory, the following error occurs W&lt;/SPAN&gt;&lt;SPAN class=""&gt;rong Image Format for bootm command: &lt;/SPAN&gt;&lt;SPAN class=""&gt;ERROR: can't get kernel image! &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Which Image should be used as the boot parameter of bootm?&lt;/SPAN&gt;&lt;SPAN class=""&gt; &lt;SPAN&gt;How should I handle this?&lt;/SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;Best Regards!&lt;/P&gt;</description>
    <pubDate>Mon, 15 May 2023 13:09:21 GMT</pubDate>
    <dc:creator>jack_huang1</dc:creator>
    <dc:date>2023-05-15T13:09:21Z</dc:date>
    <item>
      <title>LS1046 Nandflash Problem</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046-Nandflash-Problem/m-p/1650336#M12468</link>
      <description>&lt;P&gt;&lt;EM&gt;Dear:&lt;/EM&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Our product uses NXP LS1046A and SDK uses LSDK2108. We have a problem: we plan to put uboot into qspiflash, and kernel, dtb and rootfs into 512MB nandflash. N&lt;/SPAN&gt;&lt;SPAN class=""&gt;andflash is divided into three areas, the size of which is 16M, 48M and 448M. dtb file, kernel image and rootfs are placed respectively.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;The current problems is whether the build/Linux/Linux/arm64 / LS/Image&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;Or build/Linux/Linux/arm64 / LS/called burn into the nand flash - 5.10.35 - dirty,&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;If bootm $load_addr $fdtaddr is used after the uboot reads to the memory, the following error occurs W&lt;/SPAN&gt;&lt;SPAN class=""&gt;rong Image Format for bootm command: &lt;/SPAN&gt;&lt;SPAN class=""&gt;ERROR: can't get kernel image! &lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Which Image should be used as the boot parameter of bootm?&lt;/SPAN&gt;&lt;SPAN class=""&gt; &lt;SPAN&gt;How should I handle this?&lt;/SPAN&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;Best Regards!&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2023 13:09:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046-Nandflash-Problem/m-p/1650336#M12468</guid>
      <dc:creator>jack_huang1</dc:creator>
      <dc:date>2023-05-15T13:09:21Z</dc:date>
    </item>
  </channel>
</rss>

