• Locked Locked
  • Replies 5 replies
  • Subscribers 119 subscribers
  • Views 3548 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

ARM Cortex-A9 GIC interrup security issue

Hai Nguyen
Note: This was originally posted on 27th March 2012 at http://forums.arm.com

Hello,

I a newbie in embedded programming. Currently I am developing an embedded tool
running on ARM Cortex-A9. I meet an security issue when trying to use ARM Generic Interrupt Controller (GIC).

Following is the detail describing for my issue:
A. My tool MUST running in non-secure mode. It has to catch interrupt ID 117 (only).
But
B. It seems that (as I investigated)  a software running in non-secure mode could not access to secure registers.

Could you please confirm my understanding:
1. Is item B above right? :unsure:
2. If B is wrong, could you please teach me how to do it. (access to secure registers from a non-secure software).

PS: I've just entered embedded world for 8 months. I think this issue is a little bit hard for me :(. Please help me.
Thank you in advance.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 29th March 2012 at http://forums.arm.com

    Yes, most likely )

    They may have some "API" the non-secure world can use to access secure functionality in a was which doesn't kill the whole point of the secure world (like a system call in a typical OS, you can have "function calls" in to the secure world in principle), but it is entirely going to depend on the secure world software implementation.

    HTH, Iso
Reply
  • Arm Employee Badge
    Note: This was originally posted on 29th March 2012 at http://forums.arm.com

    Yes, most likely )

    They may have some "API" the non-secure world can use to access secure functionality in a was which doesn't kill the whole point of the secure world (like a system call in a typical OS, you can have "function calls" in to the secure world in principle), but it is entirely going to depend on the secure world software implementation.

    HTH, Iso
Children
No data