diff options
| author | Fabio Estevam <fabio.estevam@nxp.com> | 2016-08-15 10:07:12 -0300 |
|---|---|---|
| committer | Stefano Babic <sbabic@denx.de> | 2016-09-06 18:22:48 +0200 |
| commit | 693779e3713701e5b06afc4540faeaef1841f254 (patch) | |
| tree | e71e6951a1f06bfabc088e4a95b520077792eb2b /configs/warp_defconfig | |
| parent | 7d301a594d24e4ed63b3099cdb9e09249f945def (diff) | |
warp: Fix RAM size runtime detection
Since commit a13d3757f7df ("warp: Use imx_ddr_size() for calculating the
DDR size") warp board no longer boots.
The reason for the breakage is that the warp board is using the DDR
configuration from mx6slevk. A fundamental difference between warp and
mx6slevk is that warp only uses one DDR chip select while mx6slevk uses two.
The imx_ddr() function calculates the RAM size in runtime by reading the
values of registers MDCTL and MDMISC.
So in order to fix this warp boot issue, create a imximage DDR file specific
to warp, where the MDCTL register is configured to only activates a single
chip select.
Reported-by: Breno Lima <breno.lima@nxp.com>
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Tested-by: Breno Lima <breno.lima@nxp.com>
Diffstat (limited to 'configs/warp_defconfig')
| -rw-r--r-- | configs/warp_defconfig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/configs/warp_defconfig b/configs/warp_defconfig index 389bb7fd8f..786d7e8bc7 100644 --- a/configs/warp_defconfig +++ b/configs/warp_defconfig @@ -1,7 +1,7 @@ CONFIG_ARM=y CONFIG_ARCH_MX6=y CONFIG_TARGET_WARP=y -CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL" +CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/warp/imximage.cfg,MX6SL" CONFIG_BOOTDELAY=3 CONFIG_HUSH_PARSER=y CONFIG_CMD_BOOTZ=y |