• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 351 subscribers
  • Views 9070 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PendSV target secure state

Jiameng

Hi,

As we know, PendSV can be used for context switching, for example in RTOS and software in non-secure state typicall trigger the non-secure PendSV handler.

However, whether we can make the RTOS triggers the secure PendSV handler to process some logics regarding to security purposes and then return to non-secure PendSV handler to process the normal context switching?

Thanks. 

Parents
  • 0

    Hello...,

    To set up a SAU region the following procedure happens:

    1. SAU_RNR (0xE000EDD8, Region Number Register): Write the selected region number into SAU_RNR.
    2. SAU_RBAR (0xE000EDDC, Region Base Address Register): Write the base address of the region selected in SAU_RNR into SAU_RBAR
    3. SAU_RLAR (0xE000EDE0, Region Limit Address Register): Write the highest address of the region selected in SAU_RNR into SAU_RBAR. To mark a region as non-secure callable write 1 in bit[1] from SAU_RLAR. 0 indicates that the region is non-secure.

    Liteblue

Reply
  • 0

    Hello...,

    To set up a SAU region the following procedure happens:

    1. SAU_RNR (0xE000EDD8, Region Number Register): Write the selected region number into SAU_RNR.
    2. SAU_RBAR (0xE000EDDC, Region Base Address Register): Write the base address of the region selected in SAU_RNR into SAU_RBAR
    3. SAU_RLAR (0xE000EDE0, Region Limit Address Register): Write the highest address of the region selected in SAU_RNR into SAU_RBAR. To mark a region as non-secure callable write 1 in bit[1] from SAU_RLAR. 0 indicates that the region is non-secure.

    Liteblue

Children
No data