Add ability to redefine VECT_TAB_OFFSET by user (system_stm32f4xx.c) #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi DenDeg, However the ST team propose a USER_xxx define. Adib. |
ALABSTM
added
duplicate
|
Duplicate of #30. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unlike HSE_VALUE or HSI_VALUE, VECT_TAB_OFFSET value defined in STM32CubeF4/Drivers/CMSIS/Device/ST/STM32F4xx/Source/Templates/system_stm32f4xx.c can't be redefined by user. Some building scripts (like Platformio ststm32 platform with stm32cube framework script) and libs depends on default system_stm32f4xx.c, so I can't just create my own system_stm32f4xx.c file. This becomes a problem when writing firmware that uses a bootloader, because there's no way to change VECT_TAB_OFFSET without modifying default file.
Suggested small code change adds ability to redefine VECT_TAB_OFFSET by user.