Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
ARM Cortex-A9 GIC interrup security issue
Jump...
Cancel
Locked
Locked
Replies
5 replies
Subscribers
118 subscribers
Views
3619 views
Users
0 members are here
Options
Share
More actions
Cancel
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
ARM Cortex-A9 GIC interrup security issue
Hai Nguyen
over 12 years ago
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?
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
Martin Weidmann
over 12 years ago
Note: This was originally posted on 27th March 2012 at
http://forums.arm.com
Your understanding is correct. Code running the Normal world (non-secure) cannot access secure registers.
All interrupts default to be being "secure" - that is only handable by the Normal world. Code running in the Secure world must configure interrupt IDs as non-secure as required.
Cancel
Vote up
0
Vote down
Cancel
Reply
Martin Weidmann
over 12 years ago
Note: This was originally posted on 27th March 2012 at
http://forums.arm.com
Your understanding is correct. Code running the Normal world (non-secure) cannot access secure registers.
All interrupts default to be being "secure" - that is only handable by the Normal world. Code running in the Secure world must configure interrupt IDs as non-secure as required.
Cancel
Vote up
0
Vote down
Cancel
Children
No data