soc: stm32: fix FLASH_BASE_ADDR for apps linked in ext Q/OSPI Flash #93089
+5
−1
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.
Following changes in e35ac8f and 14c1b4a to how external Q/OSPI Flash nodes are declared in DT for boards with STM32 SoCs, FLASH_BASE_ADDRESS needs to be set manually similar to XSPI Flash, so that it does not default to
$(dt_chosen_reg_addr_hex,$(DT_CHOSEN_Z_FLASH))
which gives 0.This change is critical for running apps with MCUboot from external Q/OSPI Flash.