Closed INTENDRO closed 3 years ago
@oyvindronningstad will you be able to provide the fix for this issue (probably present in #27872, which is still a draft) :)
@oyvindronningstad will you be able to provide the fix for this issue (probably present in #27872, which is still a draft) :)
Working on it now
Describe the bug
NSC_ALIGN
gets redefined in the filezephyr/arch/arm/core/aarch32/cortex_m/tz/secure_entry_functions.ld
when the configCONFIG_CPU_HAS_NRF_IDAU
is set and the configCONFIG_ARM_NSC_REGION_BASE_ADDRESS
is set to a value not equal to zero. Up until v2.2.1, the file was structured differently and the symbol did not get redefined. Zephyr v2.3.0 added changes in order to support the nRF53 chip which introduced the possibility for this redefinition.To Reproduce Steps to reproduce the behavior:
CONFIG_ARM_NSC_REGION_BASE_ADDRESS
to a value not equal to zero. E.g. 0x0001ffc0Expected behavior NSC_ALIGN should only get defined once.
Impact Produces unwanted warning output during compilation (annoyance).
Logs and console output
Environment (please complete the following information):
Additional context: I assume that the support for nRF53 can be guaranteed and still have no redefinition of the symbol when using the nRF91. However, I just started using TrustZone features and I am unsure if my assumption is correct.