DM8168 single EMIF use case

Patrick,

First of all, it is important for you to decide what your system memory map size is expected to be. If you are planning to run on a single EMIF, your system memory requirement should be under 512MB.

Now, once you have system memory size under 512MB, you need to see how the memory is partitioned, as 256MB on each EMIF, meaning one 256MB chunk starting at 0x80000000 and the other starting at 0xC0000000, then the following settings will map it to one EMIF:

Hi Vasant,

Our case is "all mapped to one EMIF, i.e. 512MB starting at 0x80000000"

May you give us correct u-boot setting? It seems hang/crash at u-boot stage.

Patrick,

You need to check in your application that all your memory usage is within the following range:

"0x80000000 - 0xA0000000"

There should be no code and data linked beyond 0xA0000000.

If the above is ensured, then the following setting should work:

DMM_LISA_MAP_0 : 0

DMM_LISA_MAP_1 : 0

DMM_LISA_MAP_2 : 0

DMM_LISA_MAP_3 : 0x80500200 or 0x80500100

Regards, Vasant

Hi Vasant,

1. Follow your DMM_LISA_MAP_0 ~ DMM_LISA_MAP_3 setting

2. Unused EMIF clock  is not enable

It still hangs at u-boot stage.

Regards

Can give this a try without disabling the EMIF clock?

There could be issues, in disabling the EMIF clock directly.

Also, I presume that you have already checked the memory map.

Regards, Vasant

Hi Vasant,

Linux boots successfully without disable unused EMIF clock.

But how do I evaluate the condition when unused EMIF is not connected to DDR3 chips?

Regards,

Patrick,

There is no method available today on DM8168 to disable clock to the EMIF PHY from software. There is an efuse available though which when blown can disable the clock to EMIF1 PHY.

Regards, Vasant

Hi, Vasant!

Can you help me with system map on my custom board?

Please look at this thread: http://e2e.ti.com/support/embedded/linux/f/354/p/187489/675821.aspx#675821

Thank you!