fiptool LLDPUG_RevL5.15.71-2.2.0 broken

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

fiptool LLDPUG_RevL5.15.71-2.2.0 broken

987 Views
dsouthwi
Contributor III

Attempting to follow the documentation in LLDPUG_RevL5.15.71-2.2.0 section 5.2.1.1.1 to rebuild the DDR PHY fails. ATF has updated, and it seems NXP has not reviewed this documentation

Does anyone have an update command for rebuilding DDR PHY?

Current status at tag `lf-5.15.71-2.2.0`:

./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 <value>               Each image is aligned to <value> (default: 1).
  --blob uuid=...,file=...      Add an image with the given UUID pointed to by file.
  --plat-toc-flags <value>      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

 

0 Kudos
Reply
3 Replies

961 Views
June_Lu
NXP TechSupport
NXP TechSupport

Same question which I have replied. Please see the answer in another case.

0 Kudos
Reply

668 Views
rams
Contributor I

Hi,

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.

Can you please post the link so that it will be useful for others.

0 Kudos
Reply

527 Views
dsouthwi
Contributor III

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.

 

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 lf-6.1.1-1.0.0 with LDP 6.1.1-1.0.0. It's very confusing and wastes a lot of everyone's time.

0 Kudos
Reply