summaryrefslogtreecommitdiff
path: root/configs/colibri_vf_defconfig
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2017-03-10 18:26:25 -0800
committerMarcel Ziswiler <marcel.ziswiler@toradex.com>2017-03-30 10:10:51 +0200
commit4c933fefc8ae292b31d1ce4aff9c5b34ce13fd61 (patch)
tree17ce14957d11b0df476e0f26be18c51098bdbff2 /configs/colibri_vf_defconfig
parent2f6afae9faa6a32b74cce09bfff5a82efbb8945b (diff)
ARM: vf610: add auxiliary core boot support
Use i.MX bootaux support introduced for i.MX 6SoloX/i.MX 7 for Vybrid too. Starting the Cortex-M4 core on Vybrid works a bit differently, namely it uses a GPR register to define the initial PC. There is no way to define the initial stack (the stack is set up in a boot ROM). This is not a problem for most firmwares since the firmwares startup code reinitialize the stack as part of the firmware startup code anyway. Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Diffstat (limited to 'configs/colibri_vf_defconfig')
-rw-r--r--configs/colibri_vf_defconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/configs/colibri_vf_defconfig b/configs/colibri_vf_defconfig
index 1467c39974..88b3682422 100644
--- a/configs/colibri_vf_defconfig
+++ b/configs/colibri_vf_defconfig
@@ -2,6 +2,7 @@ CONFIG_ARM=y
CONFIG_ARCH_VF610=y
CONFIG_DM_SERIAL=y
CONFIG_TARGET_COLIBRI_VF=y
+CONFIG_IMX_BOOTAUX=y
CONFIG_DEFAULT_DEVICE_TREE="vf610-colibri"
CONFIG_FIT=y
CONFIG_SYS_EXTRA_OPTIONS="IMX_CONFIG=board/toradex/colibri_vf/imximage.cfg,ENV_IS_IN_NAND,IMX_NAND"