Config Tools for i.MX 26.03: Which uboot version is recomonded for the ddr3lConfig Tools v26.03 DDR3

[suraj02]

Hi,

I am using Config Tools for i.MX v26.03 to train DDR3L on a custom i.MX8MM board.

The DDR training completes successfully using the tool, and I have generated the ddr3l_timing.c file.

I built U-Boot using 2019.04, and from the logs it shows that:

• DDR initialization is completed

• DDR configuration is applied

• DDR calibration/training is successful

However, when I download the U-Boot proper image into DDR (RAM), I observe that memory contains repeated pattern values (as seen in logs), indicating that DDR write is not working correctly.
--- SDP CMD RX ---
Raw: 0b 0b 40 20
Jumping to header at 0x40200000
Header Tag is not an IMX image
Memory dump at 0000000040200000:

0x40200000: 20 20 75 75 59 59 c7 c7 8b 8b 07 07 f4 f4 d5 d5
0x40200010: ae ae 3d 3d ef ef 27 27 68 68 b0 b0 1a 1a f4 f4
0x40200020: 20 20 75 75 59 59 c7 c7 8b 8b 07 07 f4 f4 d5 d5
0x40200030: ae ae 3d 3d ef ef 27 27 68 68 b0 b0 1a 1a f4 f4
0x40200040: 20 20 75 75 59 59 c7 c7 8b 8b 07 07 f4 f4 d5 d5

I also tried building with U-Boot 2023.04, but I am facing a different issue:

U-Boot SPL 2023.04-dirty (Apr 01 2026 - 16:03:20 +0530)
CPU freq: 1200 MHz
PMIC: PCA9450AA configured for DDR3L (1.5V) and custom rails
DDRINFO: start DRAM init
DDRINFO: DRAM rate 344069MTS

At this point, the system gets stuck and does not proceed further.

So my questions are:

• Which U-Boot version is recommended when using Config Tools v26.03 for DDR3L?

• Is the generated ddr3l_timing.c compatible with U-Boot 2019.04, or is a newer version required?

• Could this issue (successful training but DDR write failure) be due to a mismatch between tool version and U-Boot version?

Thanks.

[JosephAtNXP]

Hi,

Thank you for your interest in NXP Semiconductor products,

They don't relate that closely, probably you could compare the generated code against the functions in the other boards configs. You could share it and we could compare it.

Most of the time it's related to the DDR config and bringup rather than U-boot version. I would suggest double-checking it.

Regards