summaryrefslogtreecommitdiff
path: root/boards.cfg
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2013-09-20 01:36:44 +0200
committerStefano Babic <sbabic@denx.de>2013-10-17 09:44:20 +0200
commit77b0e2239a13fa83a745ea9b03994bf780a9738a (patch)
tree5d1d1378d20a3bc33bbcc6214c1399cf60d5d3b9 /boards.cfg
parentf97271612bb1767e0c0b816827603380d7d7e1b6 (diff)
downloadu-boot-imx-77b0e2239a13fa83a745ea9b03994bf780a9738a.zip
u-boot-imx-77b0e2239a13fa83a745ea9b03994bf780a9738a.tar.gz
u-boot-imx-77b0e2239a13fa83a745ea9b03994bf780a9738a.tar.bz2
ARM: mxs: Setup stack in JTAG mode
In case the MX23/MX28 is switched into JTAG mode via the BootMode select switches, the BootROM bypasses the CPU core registers initialization. This in turn means that the Stack Pointer (SP) register is not set as it is in every other mode of operation, but instead is only zeroed out. To prevent U-Boot SPL from crashing in this obscure JTAG mode, configure the SP to point at the CONFIG_SYS_INIT_SP_ADDR if the SP is zeroed out. Note that in case the SP is already configured, we must preserve that exact SP value and must not modify it. This is important since in every other mode but the JTAG mode, the SPL returns into the BootROM and BootROM in turn loads U-Boot itself. If the SP were to be corrupted, the BootROM won't be able to continue it's operation after returned from SPL and the system would crash. Finally, add the JTAG mode switch identifier, so it's not recognised as Unknown mode. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Stefano Babic <sbabic@denx.de> Cc: Fabio Estevam <fabio.estevam@freescale.com> Cc: Otavio Salvador <otavio@ossystems.com.br>
Diffstat (limited to 'boards.cfg')
0 files changed, 0 insertions, 0 deletions