• Locked Locked
  • Replies 10 replies
  • Subscribers 118 subscribers
  • Views 7971 views
  • Users 0 members are here
Options
Related
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

TrustZone with PL310

syuji biwa
Note: This was originally posted on 17th August 2013 at http://forums.arm.com

I plan to use a simple 'TrustZone Monitor'  with PL310(L2CC).
In non-secure, I will play a Linux-Kernel.

One problem.
1. PL310's background-operation(inv.way etc..)  is executing in non-secure.
2. By secure-interrupt, dispatch to secure.
3. In secure, try to execute a write-operation to PL310' register.
May be happen 'DATA-ABORT'.

Do I must control exclusive PL310  secure and non-secure ?

Please help me.
Parents
  • Note: This was originally posted on 24th August 2013 at http://forums.arm.com

    Thanks.

    > you may need to set up exclusive access
    If non-secureOS is hang in spinlock, SecureOS nerver get a spinlock.
    When secureOS try to get a spinlock in FIQ, secureOS is dead-lock.

    SecureOS's implementation is so difficult.
    SecureOS may be better not to use cache. (no-MMU only.)
Reply
  • Note: This was originally posted on 24th August 2013 at http://forums.arm.com

    Thanks.

    > you may need to set up exclusive access
    If non-secureOS is hang in spinlock, SecureOS nerver get a spinlock.
    When secureOS try to get a spinlock in FIQ, secureOS is dead-lock.

    SecureOS's implementation is so difficult.
    SecureOS may be better not to use cache. (no-MMU only.)
Children
No data