boards: stm32f0: explicit RAM vector table control
Add a new Kconfig symbol that explicitly controls whether the vector table should be placed in RAM. This eliminates the side effect of `IS_BOOTLOADER` controlling vector table location. Making the condition a positive assertion also allows the config to be used in CMakeLists conditions (`zephyr_linker_sources_ifdef()`, etc). Signed-off-by: Jordan Yates <jordan.yates@data61.csiro.au>
This commit is contained in:
parent
bcca26260b
commit
318ee971c5
8 changed files with 15 additions and 10 deletions
|
@ -254,7 +254,7 @@ SECTIONS
|
|||
. = ALIGN(_region_min_align);
|
||||
_image_ram_start = .;
|
||||
|
||||
#if defined(CONFIG_SOC_SERIES_STM32F0X) && !defined(CONFIG_IS_BOOTLOADER)
|
||||
#if defined(CONFIG_SOC_SERIES_STM32F0X) && defined(CONFIG_SRAM_VECTOR_TABLE)
|
||||
/* Must be first in ramable region */
|
||||
SECTION_PROLOGUE(.st_stm32f0x_vt,(NOLOAD),)
|
||||
{
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue