Allow VECT_TAB_OFFSET to be overridden externally (IDE or Makefile)

[pieterconradie]

It is useful to allow VECT_TAB_OFFSET to be overridden externally in the IDE or Makefile. This allows the Vector Table Offset to be at 0 for a debug build and the Vector Table Offset to be moved for a release build that has to accommodate a bootloader.

IMPORTANT INFORMATION

Contributor License Agreement (CLA)

• The Pull Request feature will be considered by STMicroelectronics after the signature of a Contributor License Agreement (CLA) by the submitter.
• If you did not sign such agreement, please follow the steps mentioned in the CONTRIBUTING.md file.

[RKOUSTM]

Hi @pieterconradie,

Thank you for your suggestion and contribution. A fix for this code below:

STM32CubeL0/Drivers/CMSIS/Device/ST/STM32L0xx/Source/Templates/system_stm32l0xx.c

Lines 80 to 85 in 8b26821

	/*!< Uncomment the following line if you need to relocate your vector Table in
	Internal SRAM. */
	/* #define VECT_TAB_SRAM */
	#define VECT_TAB_OFFSET 0x00U /*!< Vector Table base offset field.
	This value must be a multiple of 0x100. */
	/******************************************************************************/

will be published as soon in in future release (STM32L0Cube V1.12.0) looks like the following:

+ #if defined(USER_VECT_TAB_ADDRESS)
/* #define VECT_TAB_SRAM */
+ #if defined(VECT_TAB_SRAM)
+ #define VECT_TAB_BASE_ADDRESS   SRAM_BASE       /*!< Vector Table base address field.
+                                                    This value must be a multiple of 0x200. */
+ #define VECT_TAB_OFFSET         0x00000000U     /*!< Vector Table base offset field.
+                                                    This value must be a multiple of 0x200. */
+ #else
+ #define VECT_TAB_BASE_ADDRESS   FLASH_BASE      /*!< Vector Table base address field.
+                                                     This value must be a multiple of 0x200. */
+ #define VECT_TAB_OFFSET         0x00000000U     /*!< Vector Table base offset field.
+                                                    This value must be a multiple of 0x200. */
+ #endif /* VECT_TAB_SRAM */
+ #endif /* USER_VECT_TAB_ADDRESS */

Thank you again for your contribution.

With regards,

[pieterconradie]

@RKOUSTM Thanks for attending to the pull request so quickly :)

I am probably missing something but I can not see from the solution above how VECT_TAB_OFFSET can be overridden(?). In both cases above it is #defined as 0x00000000U

Should it not be:

#ifndef VECT_TAB_OFFSET
#define VECT_TAB_OFFSET 0x00000000U
#endif

Thanks in advance,
Pieter

[RKOUSTM]

Hi @pieterconradie,

Thank you for your contribution. The vector table is updated by a generic preprocessor directive USER_VECT_TAB_ADDRESS to mention if we are on FLASH or SRAM, and if we want to apply an offset. Offset being a multiple of fixed value depending on Arm processor architecture. The vector table will be kept at address 0x00 which correspond to automatic remap of boot address selected. On any STM32 target, vector table is set to 0x00u which is always the right default address as

1. there is always a memory remap between boot address and @0x00
2. for dual core, CPU2 is booting on boot @ + SBRV register offset.

Thank you again for your contribution.

With regards,

[fpistm]

I've the same concern than @pieterconradie
STMicroelectronics/STM32CubeF4#30 (comment)

[RKOUSTM]

Hi @pieterconradie,

I hope you are fine. The issue you reported has been fixed in the frame of version v1.12.0 of the STM32CubeL0 published on GitHub.

Thank you again for having reported.

With regards,

[ALABSTM]

See also STM32CubeF4#30.

[ALABSTM]

See also STM32CubeF4#64.

[ALABSTM]

ST Internal Reference: 116475

[ALABSTM]

Hi @pieterconradie,

I hope you are fine. We reopened the point as the current implementation does not address the requirement to be able to redefine VECT_TAB_OFFSET without the need to manually edit the system_stm32l0xx.c file.

We will get back to you as soon as we get feedback from our development teams.

With regards,