summaryrefslogtreecommitdiff
path: root/board/ti/am57xx
diff options
context:
space:
mode:
authorYe Li <ye.li@nxp.com>2017-07-24 01:12:33 -0500
committerYe Li <ye.li@nxp.com>2017-07-25 00:20:46 -0500
commit922168448596a075c8b990bea3a81bcb62024ae4 (patch)
tree5298698c890c5585426055eb88b6cd2373ca6d8c /board/ti/am57xx
parentc7aefcba1d8eaa503c7e7dc108c097ae4a1a9a95 (diff)
downloadu-boot-imx-922168448596a075c8b990bea3a81bcb62024ae4.zip
u-boot-imx-922168448596a075c8b990bea3a81bcb62024ae4.tar.gz
u-boot-imx-922168448596a075c8b990bea3a81bcb62024ae4.tar.bz2
MLK-16069 imx6slevk: Workaround to limit the u-boot in low 512MB memory
On i.MX6SLEVK board, the LPDDR2 chip(CS1) is not reset before accessing. And due to MMDC limitation, the script we get from IC team is only doing CS0 reset but skipping CS1 reset, the reason is that doing CS1 reset might cause CS0 can NOT be accessed any longer. Because of this HW issue, we found the high 512MB memory needs more time to be stable. Since the u-boot relocates itself to highest address after booting, so this will cause issue. To work around it, we just limit the u-boot running at low 512MB memory. Signed-off-by: Ye Li <ye.li@nxp.com> (cherry picked from commit 5fc93379dc3576ee9dc00f108bc18d8d6059d9c3)
Diffstat (limited to 'board/ti/am57xx')
0 files changed, 0 insertions, 0 deletions