LS1046 DDR calibation Tool

[deepanrajanbara]

Hi ,

We are having LS1046ardb evk with 16GB DDR . But the default binary from NXP does not boot due to timing parameter mismatch. Please let us know which tool we need to use for DDR calibration. Since we are familiar in imx series process. But for LS series we are not  sure which tool to use.

NOTICE: UDIMM 18ADF2G72AZ-2G6E1
ERROR: Board parameters no match.
ERROR: Failed matching board timing.
ERROR: Found training error(s): 0x2100
ERROR: Error: Waiting for D_INIT timeout.
ERROR: Writing DDR register(s) failed
ERROR: Programing DDRC error
ERROR: DDR init failed.
NOTICE: Incorrect DRAM0 size is defined in platfor_def.h
ERROR: mmap_add_region_check() failed. error -22
ERROR: mmap_add_region_check() failed. error -22
NOTICE: BL2: v1.5(release):LSDK-20.04-update-290520-dirty
NOTICE: BL2: Built : 13:29:29, Mar 24 2021
ERROR: SD read error - DMA error = 10000000
ERROR: Read error = fffffffb
ERROR: BL2: Failed to load image (-2)
Authentication failure

Thank you,

Deepanraj.A

[Bulat]

Error happens in your case due to UDIMM type, not due to timing issue. I can suggest a modification of TFA boot sw to overcome the issue, this relates to file

\plat\nxp\soc-ls1046\ls1046ardb\ddr_init.c.

Following code needs to be changed.

Was:
-----------
static const struct board_timing udimm[] = {
{0x04, rce, 0x01020304, 0x06070805},
};
-----------
Modified:
-----------
static const struct board_timing udimm[] = {
{0x04, rce, 0x01020304, 0x06070805},
{0x0F, rce, 0x01020304, 0x06070805},
};
-----------

Please try.

Regards,

Bulat

[deepanrajanbara]

When we try to program a Bareboard hello world application via code warrior IDE . We are getting a similar error as below. Please help us debug this issue.

Cannot write data at address 0x80000000

As it is EVK . Binary has to work without any problem . But due to the RAM change it is not able to program  the binary

Thanks,

Deepanraj.A

[Bulat]

It is a mistake in the initialization script.

[deepanrajanbara]

Can you please let us know, what this change corresponds too. After this change it seemed to boot with no issue.

Please explain to us what is the reason for this change is there any document which we can check to know about these changes.

Thank you,

Deepanraj.A