If we are setting the code to be in HyperFlash (CONFIG_CODE_HYPERFLASH)
or QSPI (CONFIG_CODE_QSPI) we should enable
CONFIG_NXP_IMX_RT_BOOT_HEADER.
Update mimxrt1064_evk to use select like other boards.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
To enable the QSPI you have to physically modify the board and this
disables the hyperflash. Since we plan on removing Kconfig from device
trees, its easier to treat the QSPI flash as a seperate board config and
thus it will get a dts to match.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Adds a board-level config option to select whether the code gets linked
into internal instruction tightly coupled memory (ITCM), external
hyperflash, or external qspi flash. The default is ITCM.
Note that we are not yet building an image vector table (IVT) into the
image, therefore the zephyr binary is not bootable by the SoC ROM as-is.
However, the DAPLink firmware prepends an IVT to the image when you use
its drag-and-drop feature to program flash, and this results in a
bootable zephyr application.
Signed-off-by: Maureen Helm <maureen.helm@nxp.com>
Andrei Gansari