2387708_en-US

[#1]

u-boot migration from Zeus 2019.04 +fslc to Wrynose 2026.01 for LS1046/26 CPU

Hi
 We are using u-boot code version from  "git://source.codeaurora.org/external/qoriq/" for our LS1046/26 Cpu based cards. The version of this u-boot is  2019.04 +fslc. We also supports secure boot.
We are now thinking of upgrading our u-boot to Wrynose 2026.01.

Our existing U-Boot source code was originally obtained from the now-deprecated repository:
git://source.codeaurora.org/external/qoriq/.

Could you please advise on the appropriate Git repository to use for the latest code?

Additionally, it would be helpful if you could share any key considerations or best practices to ensure a smooth transition during the upgrade.

Re: u-boot migration from Zeus 2019.04 +fslc to Wrynose 2026.01 for LS1046/26 CPU

Hello,

For LS1046/LS1026A-family Layerscape U-Boot, the replacement for the deprecated CodeAurora QorIQ tree is:

git clone https://github.com/nxp-qoriq/u-boot.git

NXP guidance is to replace old URLs such as:

source.codeaurora.org/external/qoriq/qoriq-components/u-boot.git

with:

github.com/nxp-qoriq/u-boot.git

or, more generally, replace source.codeaurora.org/external/qoriq/qoriq-components with github.com/nxp-qoriq in build scripts, manifests, and Yocto recipes .

For a Wrynose-based BSP , I would start from the QorIQ Yocto SDK manifest , not by cloning U-Boot alone:

repo init -u https://github.com/nxp-qoriq/yocto-sdk -b wrynose
repo sync --force-sync

The public nxp-qoriq/yocto-sdk repo shows an active wrynose branch . The same repo documents the general repo-init flow and lists the Yocto branch/release mapping mechanism.

For U-Boot specifically, the public nxp-qoriq/u-boot repo is the QorIQ U-Boot tree; its default branch shown in the retrieved repo page is lf_v2024.04 , and the active branch list also shows lf_v2026.04 . Tags shown include recent lf-* release tags such as lf-6.12.49-2.2.0 , lf-6.18.2-1.0.0 , and lf-6.18.20-2.0.0 . So the practical rule is: use the U-Boot revision selected by the Wrynose Yocto manifest/recipe , rather than manually taking an arbitrary “latest” U-Boot branch.

Key transition considerations:

1. Migrate all CodeAurora references

   • Search your build tree for old URLs:

     grep -rn 'source.codeaurora.org/external/qoriq' .

   • Replace source.codeaurora.org/external/qoriq/qoriq-components with github.com/nxp-qoriq in manifests, build configs, and recipes.

2. Use the release manifest as the source of truth

   • For a BSP upgrade, keep U-Boot, ATF, RCW, CST, kernel, device trees, and recipes aligned to the same NXP release stream.
   • NXP’s current Layerscape flow commonly uses ATF + U-Boot , not standalone U-Boot only.

3. Port your custom board from the LS1046ARDB reference again

   • For LS1046 custom boards, NXP points to the LS1046ARDB U-Boot reference files: configs/ls1046ardb_tfa_defconfig , arch/arm/dts/fsl-ls1046a-rdb.dts , and board/freescale/ls1046ardb/ .
   • For older-style customizations, also review include/configs/ls1046ardb.h and the board folder.
   • Reconcile your existing board changes against the new device-model/Kconfig/DTS structure rather than copying old 2019.04 code wholesale.

4. Secure boot: rebuild and re-validate the full chain

   • In Yocto, secure boot images are built by adding:

     DISTRO_FEATURES:append = " secure"

     then running:

     bitbake secure-boot-qoriq

   • CST, SRKH, OTPMK, RCW SB_EN , ATF, and signed U-Boot image handling should all be revalidated on a development/non-fused unit before touching production fuse settings.

5. Expect boot-flow differences from 2019.04

   • Since LSDK 18.12, NXP introduced the TF-A boot flow for Layerscape RDBs:
     Boot ROM → BL2 → BL31 → U-Boot/UEFI → Linux , compared with the older PPA-style flow.
   • If your current product still carries assumptions from the old PPA/direct U-Boot path, review them carefully.

6. Keep a controlled migration baseline

   • First bring up an unmodified NXP reference configuration close to your hardware.
   • Then apply your board deltas in small groups: RCW/SerDes, DDR, console, boot media, QSPI/eMMC/SD, Ethernet/FMan, environment layout, secure boot.
   • Validate both non-secure and secure boot paths before declaring parity with the old 2019.04 + fslc tree.

Regards