<?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: fiptool LLDPUG_RevL5.15.71-2.2.0 broken in Layerscape</title>
    <link>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1630235#M12210</link>
    <description>&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="en-US"&gt;Same question which I have replied. Please see the answer in another case.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2023 03:24:38 GMT</pubDate>
    <dc:creator>June_Lu</dc:creator>
    <dc:date>2023-04-10T03:24:38Z</dc:date>
    <item>
      <title>fiptool LLDPUG_RevL5.15.71-2.2.0 broken</title>
      <link>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1628516#M12178</link>
      <description>&lt;P&gt;Attempting to follow the documentation in LLDPUG_RevL5.15.71-2.2.0 section &lt;SPAN&gt;5.2.1.1.&lt;/SPAN&gt;1 to rebuild the DDR PHY fails. ATF has updated, and it seems NXP has not reviewed this documentation &lt;LI-EMOJI id="lia_disappointed-face" title=":disappointed_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;Does anyone have an update command for rebuilding DDR PHY?&lt;/P&gt;&lt;P&gt;Current status at tag `lf-5.15.71-2.2.0`:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;./fiptool create --ddr-immem-udimm-1d ddr-phy-binary/lx2160a/ddr4_pmu_train_imem.bin

create: unrecognized option '--ddr-immem-udimm-1d'
fiptool create [opts] FIP_FILENAME

Options:
  --align &amp;lt;value&amp;gt;               Each image is aligned to &amp;lt;value&amp;gt; (default: 1).
  --blob uuid=...,file=...      Add an image with the given UUID pointed to by file.
  --plat-toc-flags &amp;lt;value&amp;gt;      16-bit platform specific flag field occupying bits 32-47 in 64-bit ToC header.

Specific images are packed with the following options:
  --scp-fwu-cfg      FILENAME   SCP Firmware Updater Configuration FWU SCP_BL2U
  --ap-fwu-cfg       FILENAME   AP Firmware Updater Configuration BL2U
  --fwu              FILENAME   Firmware Updater NS_BL2U
  --fwu-cert         FILENAME   Non-Trusted Firmware Updater certificate
  --tb-fw            FILENAME   Trusted Boot Firmware BL2
  --scp-fw           FILENAME   SCP Firmware SCP_BL2
  --soc-fw           FILENAME   EL3 Runtime Firmware BL31
  --tos-fw           FILENAME   Secure Payload BL32 (Trusted OS)
  --tos-fw-extra1    FILENAME   Secure Payload BL32 Extra1 (Trusted OS Extra1)
  --tos-fw-extra2    FILENAME   Secure Payload BL32 Extra2 (Trusted OS Extra2)
  --nt-fw            FILENAME   Non-Trusted Firmware BL33
  --rmm-fw           FILENAME   Realm Monitor Management Firmware
  --fw-config        FILENAME   FW_CONFIG
  --hw-config        FILENAME   HW_CONFIG
  --tb-fw-config     FILENAME   TB_FW_CONFIG
  --soc-fw-config    FILENAME   SOC_FW_CONFIG
  --tos-fw-config    FILENAME   TOS_FW_CONFIG
  --nt-fw-config     FILENAME   NT_FW_CONFIG
  --rot-cert         FILENAME   Root Of Trust key certificate
  --trusted-key-cert FILENAME   Trusted key certificate
  --scp-fw-key-cert  FILENAME   SCP Firmware key certificate
  --soc-fw-key-cert  FILENAME   SoC Firmware key certificate
  --tos-fw-key-cert  FILENAME   Trusted OS Firmware key certificate
  --nt-fw-key-cert   FILENAME   Non-Trusted Firmware key certificate
  --tb-fw-cert       FILENAME   Trusted Boot Firmware BL2 certificate
  --scp-fw-cert      FILENAME   SCP Firmware content certificate
  --soc-fw-cert      FILENAME   SoC Firmware content certificate
  --tos-fw-cert      FILENAME   Trusted OS Firmware content certificate
  --nt-fw-cert       FILENAME   Non-Trusted Firmware content certificate
  --sip-sp-cert      FILENAME   SiP owned Secure Partition content certificate
  --plat-sp-cert     FILENAME   Platform owned Secure Partition content certificate&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2023 22:23:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1628516#M12178</guid>
      <dc:creator>dsouthwi</dc:creator>
      <dc:date>2023-04-05T22:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: fiptool LLDPUG_RevL5.15.71-2.2.0 broken</title>
      <link>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1630235#M12210</link>
      <description>&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="en-US"&gt;Same question which I have replied. Please see the answer in another case.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Apr 2023 03:24:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1630235#M12210</guid>
      <dc:creator>June_Lu</dc:creator>
      <dc:date>2023-04-10T03:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: fiptool LLDPUG_RevL5.15.71-2.2.0 broken</title>
      <link>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1762625#M13686</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have the same problem and we could not find way to build the DDR FIP image on 6.1.36 release and the documentation is not updated.&lt;/P&gt;&lt;P&gt;Can you please post the link so that it will be useful for others.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2023 10:28:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1762625#M13686</guid>
      <dc:creator>rams</dc:creator>
      <dc:date>2023-11-23T10:28:27Z</dc:date>
    </item>
    <item>
      <title>Re: fiptool LLDPUG_RevL5.15.71-2.2.0 broken</title>
      <link>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1805870#M13982</link>
      <description>&lt;P&gt;Since you're unlikely to get a reply from NXP after this many months, the response I got was that for LLDPUG releases the ATF version that corresponds is in fact LSDK-21.08, so it should be built using the old method.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have no idea why NXP releases a LLDPUG with a certain tag, then creates matching tags for tools like FIP tool, only to later say do not use atf tag &lt;SPAN class=""&gt;lf-6.1.1-1.0.0&lt;/SPAN&gt; with LDP 6.1.1-1.0.0. It's very confusing and wastes a lot of everyone's time.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 14:14:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/fiptool-LLDPUG-RevL5-15-71-2-2-0-broken/m-p/1805870#M13982</guid>
      <dc:creator>dsouthwi</dc:creator>
      <dc:date>2024-02-13T14:14:28Z</dc:date>
    </item>
  </channel>
</rss>

