stm32n6: allow appli exection from non-secure context#344
Open
etienne-lms wants to merge 3 commits intozephyrproject-rtos:mainfrom
Open
stm32n6: allow appli exection from non-secure context#344etienne-lms wants to merge 3 commits intozephyrproject-rtos:mainfrom
etienne-lms wants to merge 3 commits intozephyrproject-rtos:mainfrom
Conversation
etienne-lms
force-pushed
the
n6-non-secure
branch
from
166ddd7 to
dc3dc38
Compare
erwango
requested changes
Mar 2, 2026
etienne-lms
force-pushed
the
n6-non-secure
branch
2 times, most recently
from
9b699a3 to
48bfd2c
Compare
etienne-lms
force-pushed
the
n6-non-secure
branch
from
48bfd2c to
4928888
Compare
Collaborator
Author
|
Rebased. |
etienne-lms
force-pushed
the
n6-non-secure
branch
from
4928888 to
8db0821
Compare
Collaborator
Author
|
Fixed the genpinctrl test part that was not updated. |
Change genpinctrl.py tool to use the pinctrl node label instead of the node path in the generated pinctrl DTSI files. This change simplifies pinctrl DTSI file and specific case as for STM32N6xx series where the pinctrl node will move into a subnode of the soc node. Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Update generated pinctrl DTSI files using pinctrl node label instead of the node path. No functional changes. Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Consider when the application executes from non-secure CPU context that is when CONFIG_TRUSTED_EXECUTION_NONSECURE is enabled. Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
etienne-lms
force-pushed
the
n6-non-secure
branch
from
8db0821 to
c7af1a6
Compare
Collaborator
Author
|
Fixed 'no-new-line' issue in genpinctrl test reference. |
erwango
approved these changes
Mar 18, 2026
juickar
approved these changes
Mar 18, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Update STM32N6 HAL integration support Zephyr application execution from both secure and non-secure context.
This requires default using the non-secure address ranges for peripheral memory mapped interface. Changes in Zephyr SoC DTSI files (zephyrproject-rtos/zephyr#104765) modifies the path of pinctrl node, impacting pinctrl DTSI files from the HAL module. This P-R overcomes the issue change pinctrl DTSI file generation to rely on
pinctrlnode label (always defined in Zephyr SoC DTSI files) instead of the node path.