RTX changes pulled in from d20b8aa #6045
Conversation
RTX5: Added TrustZone Module Identifier configuration for Idle and Timer Thread
Is this pulling just one change, should not we update the RTX from upstream ? |
|
RTX update will take time, and this was requires for cortex-m23/m33 devices. |
|
/morph build |
Build : SUCCESSBuild number : 1102 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 780 |
Test : SUCCESSBuild number : 910 |
Are these config options expected to be changed by the APP? Also Mbed OS won't be run in secure mode, so I'm not 100% sure why do we need that change. |
|
These config options are not app based, but target based. If timer module / access to sleep mode is set as secure then non-secure mbed-os should set it to 1 to access secure modules. |
|
If it's target specific we shouldn't use the mbed config system, but just wrap the RTX config in |
Default value for timer/idle thread trustzone identifier is 0, updated it to 1 to allow threads to access secure functions when timer is secure device.
deepikabhavnani
force-pushed
the
thread_tzoption
branch
from
6028e48 to
9fa0a52
Compare
|
@bulislaw - Removed the conf option |
|
/morph build |
Build : SUCCESSBuild number : 1131 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 808 |
Test : SUCCESSBuild number : 939 |
Secure functions were not accessible from Timer/Idle thread this PR should fix that with changes from CMSIS and config options in mbed-os
Pulling in ARM-software/CMSIS_5@d20b8aa#diff-7467c87f859f0e1a8e5f93ef0c118c43
Resolves: ARM-software/CMSIS_5#252
@bulislaw - I am not sure if we should add conf options (MBED_CONF_APP_IDLE_THREAD_TZ_MOD_ID / MBED_CONF_APP_TIMER_THREAD_TZ_MOD_ID) or simply set OS_TIMER_THREAD_TZ_MOD_ID /
OS_IDLE_THREAD_TZ_MOD_ID as 1.