<?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 Re: LS1046, How to load Linux kernel without using SEC Firmware? (HELP!) in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/LS1046-How-to-load-Linux-kernel-without-using-SEC-Firmware-HELP/m-p/1457569#M10543</link>
    <description>&lt;P&gt;When&amp;nbsp;CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT=n and INCLUDE_FIT=y are applied, it loads normally.&lt;/P&gt;</description>
    <pubDate>Fri, 13 May 2022 01:49:50 GMT</pubDate>
    <dc:creator>nekarose</dc:creator>
    <dc:date>2022-05-13T01:49:50Z</dc:date>
    <item>
      <title>LS1046, How to load Linux kernel without using SEC Firmware? (HELP!)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046-How-to-load-Linux-kernel-without-using-SEC-Firmware-HELP/m-p/1457175#M10540</link>
      <description>&lt;P&gt;Hi, experts&lt;/P&gt;&lt;P&gt;I am trying to port ATF/Uboot/linux using the ls1046 CPU custom board that does not support secure mode. I checked that it boots up to ATF and Uboot, but when I download the kernel as tftp and try to boot, the following error occurs.&lt;/P&gt;&lt;P&gt;Verifying Hash Integrity ... OK&lt;BR /&gt;Loading fdt from 0xa23b46f4 to 0x90000000&lt;BR /&gt;Booting using the fdt blob at 0x90000000&lt;BR /&gt;Uncompressing Kernel Image&lt;BR /&gt;Loading Ramdisk to 8eb0c000, end 8ffff53f ... OK&lt;BR /&gt;Loading Device Tree to 000000008eaef000, end 000000008eb0b7f4 ... OK&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY&lt;BR /&gt;NOTICE: SEC is disabled.&lt;BR /&gt;WARNING: No random number to set kaslr-seed&lt;BR /&gt;"Synchronous Abort" handler, esr 0x96000004&lt;BR /&gt;elr: 0000000082032444 lr : 0000000082032394 (reloc)&lt;BR /&gt;elr: 00000000f7b7e444 lr : 00000000f7b7e394&lt;BR /&gt;x0 : 0000000000000000 x1 : 00000000f7a098a8&lt;BR /&gt;x2 : b27e0063d2800043 x3 : 0000000000000068&lt;BR /&gt;x4 : 00000000f7a0be70 x5 : 00000000f7a0cb60&lt;BR /&gt;x6 : 0000000000000042 x7 : 000000008eaf89d3&lt;BR /&gt;x8 : 0000000000000004 x9 : 0000000000000008&lt;BR /&gt;x10: 00000000000007d4 x11: 00000000f7a097fc&lt;BR /&gt;x12: 00000000000007a0 x13: 00000000f7a09898&lt;BR /&gt;x14: 000000008eaef000 x15: 0000000000000002&lt;BR /&gt;x16: 00000000f7b8c874 x17: 00000000f7a269b0&lt;BR /&gt;x18: 00000000f7a0bdb0 x19: 000000008eaef000&lt;BR /&gt;x20: 00000000f7bd58c8 x21: b27e0063d27fffcb&lt;BR /&gt;x22: 00000000f7bd58d0 x23: 00000000f7bc4355&lt;BR /&gt;x24: 00000000f7bcf2df x25: 00000000f7bd7a30&lt;BR /&gt;x26: 0000000000000000 x27: 00000000f7b517f0&lt;BR /&gt;x28: 00000000a00000d0 x29: 00000000f7a098e0&lt;/P&gt;&lt;P&gt;It is presumed to be a problem caused by not using SEC, and when I set the CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT item in the Uboot config item to n, the lsdk2108_yocto_tiny_LS_arm64.itb file loaded as tftp is not recognized with an error "wrong Image Format for bootm command" when booting.&lt;BR /&gt;If the SEC Firmware is not supported, does the itb image not load? So, what linux kernel image should I use when not using SEC Firmware?&lt;/P&gt;&lt;P&gt;Please, Help me!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 10:30:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046-How-to-load-Linux-kernel-without-using-SEC-Firmware-HELP/m-p/1457175#M10540</guid>
      <dc:creator>nekarose</dc:creator>
      <dc:date>2022-05-12T10:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: LS1046, How to load Linux kernel without using SEC Firmware? (HELP!)</title>
      <link>https://community.nxp.com/t5/Layerscape/LS1046-How-to-load-Linux-kernel-without-using-SEC-Firmware-HELP/m-p/1457569#M10543</link>
      <description>&lt;P&gt;When&amp;nbsp;CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT=n and INCLUDE_FIT=y are applied, it loads normally.&lt;/P&gt;</description>
      <pubDate>Fri, 13 May 2022 01:49:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LS1046-How-to-load-Linux-kernel-without-using-SEC-Firmware-HELP/m-p/1457569#M10543</guid>
      <dc:creator>nekarose</dc:creator>
      <dc:date>2022-05-13T01:49:50Z</dc:date>
    </item>
  </channel>
</rss>

