Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
Distinguished Ambassadors
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello forum
Operating Systems forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Internet of Things (IoT) blog
Operating Systems blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Architectures and Processors forum
Cortex-A8 - accessing banked registers from monitor mode
Jump...
Cancel
State
Not Answered
Locked
Locked
Replies
6 replies
Subscribers
347 subscribers
Views
7540 views
Users
0 members are here
Armv7-A
Cortex-A
Cortex-A8
Debugger
Options
Share
More actions
Cancel
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
Cortex-A8 - accessing banked registers from monitor mode
Jitesh Shah
over 11 years ago
Note: This was originally posted on 20th March 2012 at
http://forums.arm.com
Hi Group,
I am working on a Cortex A-8 Processor (ARMv7-a architecture). I am in the monitor mode and trying to access SP of the SVC mode.
I know two ways I can do it:
1) Using the "mrs" instruction.
eg. mrs r0, sp_svc
However, my compiler (code sourcery) says:
Error: Banked registers are not available with this architecture. -- `mrs r0,sp_svc'
My architecture manual does say that banked registers are accessible via this method, so I suppose this is a compiler issue. Anyway.
2) Changing the mode to svc, reading sp and getting back to the monitor mode.
eg. cps MODE_SVC
mov r0, sp
cps MODE_MON
where MODE_SVC = 0x13 and MODE_MON = 0x16
But, as soon as I execute "cps MODE_SVC" in monitor mode, my CPU hangs. There is no more activity.
So my question is this: Is SVC mode not accessible from Monitor mode? If thats not the case, how can I access SVC version of the registers from Monitor mode?
Thanks,
Jitesh
Parents
0
Peter Harris
over 11 years ago
Note: This was originally posted on 20th March 2012 at
http://forums.arm.com
Have you initialized the SVC mode, and is the NS-bit configured as secure before you call cps?
If you are in monitor mode when you do the "cps MODE_SVC" are you are effectively switching into SVC mode, using it's banked registers, so if you haven't initialized them you are probably going to have problems.
My best guess is that you've got the NS-bit set to 1 (i.e. non-secure) and you switch modes, which drops the core in to non-secure SVC mode, because the NS-bit takes effect as soon as you drop out of monitor mode. It is quite possible that the PC you are using doesn't exist in the non-secure world, so it faults, but the non-secure exception table is also not set up, so that faults. Infinite loop of faults = hung CPU.
Iso
Cancel
Up
0
Down
Cancel
Reply
0
Peter Harris
over 11 years ago
Note: This was originally posted on 20th March 2012 at
http://forums.arm.com
Have you initialized the SVC mode, and is the NS-bit configured as secure before you call cps?
If you are in monitor mode when you do the "cps MODE_SVC" are you are effectively switching into SVC mode, using it's banked registers, so if you haven't initialized them you are probably going to have problems.
My best guess is that you've got the NS-bit set to 1 (i.e. non-secure) and you switch modes, which drops the core in to non-secure SVC mode, because the NS-bit takes effect as soon as you drop out of monitor mode. It is quite possible that the PC you are using doesn't exist in the non-secure world, so it faults, but the non-secure exception table is also not set up, so that faults. Infinite loop of faults = hung CPU.
Iso
Cancel
Up
0
Down
Cancel
Children
No data