Arm Community
Site
Search
User
Site
Search
User
Groups
Arm Research
DesignStart
Education Hub
Graphics and Gaming
High Performance Computing
Innovation
Multimedia
Open Source Software and Platforms
Physical
Processors
Security
System
Software Tools
TrustZone for Armv8-M
中文社区
Blog
Announcements
Artificial Intelligence
Automotive
Healthcare
HPC
Infrastructure
Innovation
Internet of Things
Machine Learning
Mobile
Smart Homes
Wearables
Forums
All developer forums
IP Product forums
Tool & Software forums
Pelion IoT Platform
Support
Open a support case
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Developer Community
Tools and Software
Software Tools
Jump...
Cancel
Software Tools
Arm Development Studio forum
Assertion of IRQS is not causing calling of ISR
Tools, Software and IDEs blog
Forums
Videos & Files
Help
Jump...
Cancel
New
Replies
9 replies
Subscribers
127 subscribers
Views
3337 views
Users
0 members are here
Related
Assertion of IRQS is not causing calling of ISR
Offline
Lokesh Kumar
over 7 years ago
Note: This was originally posted on 4th September 2012 at http://forums.arm.com
Hi,
With my current flow, when I am asserting legacy nIRQ I am able to jump to ISR, but not when asserting IRQS[0].
I have enabled interrupts as below
[size=2]CPSIE ifa, #18
and configured [size=2]Interrupt Security ([/size][/size][size=2][size=2]ICDISR), [size=2][/size][/size][/size][size=2][size=2][size=2][size=2]Interrupt Edge Trigger Config ([/size]ICDIF),[size=2]Interrupt Priority (ICDIPR)[/size][/size][/size][/size],[size=2]Interrupt Target Processor (ICDIPTR),[size=2]Interrupt Enable (ICDISER),[size=2]Interrupt Priority Mask (ICCPMR),[size=2]Interrupt Binary Point (ICCBPR),[size=2]Interface Control Register (ICCICR),[size=2]Distributor Control Register (ICDDCR)
Am I missing something?
Is something separate need to be done, when using IRQS interrupts?
Thanks
Lokesh
[/size][/size][/size][/size][/size][/size]
Parents
Offline
Martin Weidmann
over 7 years ago
Note: This was originally posted on 5th September 2012 at
http://forums.arm.com
You haven't said, but I'm guessing you are using Cortex-A9 MPCore - correct me if I guessed incorrectly.
So the nIRQ signals are the legacy interrupt signals. When the CPU interface is disabled (ICCICR.Enable=0) the nIRQ is connected directly to the core. All you need to generate an IRQ exception is clear CPSR.I and then assert the nIRQ signal (*).
When you enable the IC (ICCICR.Enable=1 & ICDDCR.Enable=1), the cores interrupts are driven by the IC. The nIRQ line no longer gets connected to the core directly, but becomes just another interrupt source for the IC (a PPI to be precise, with ID 31).
To take an interrupt connected via the IRQS signal you must enable and configure the IC. From your earlier post, you seem to programming all the right registers. Question is what are you programming them to? You could, for example, be enabling ID31 (the nIRQ ID) but not ID32 (the IRQS[0] ID).
On your question about vectors.... No, a Cortex-A9 core has only one IRQ vector.
* Remembering that nIRQ is active low. So to "assert" you actually take the signal low.
Cancel
Up
0
Down
Reply
Cancel
Reply
Offline
Martin Weidmann
over 7 years ago
Note: This was originally posted on 5th September 2012 at
http://forums.arm.com
You haven't said, but I'm guessing you are using Cortex-A9 MPCore - correct me if I guessed incorrectly.
So the nIRQ signals are the legacy interrupt signals. When the CPU interface is disabled (ICCICR.Enable=0) the nIRQ is connected directly to the core. All you need to generate an IRQ exception is clear CPSR.I and then assert the nIRQ signal (*).
When you enable the IC (ICCICR.Enable=1 & ICDDCR.Enable=1), the cores interrupts are driven by the IC. The nIRQ line no longer gets connected to the core directly, but becomes just another interrupt source for the IC (a PPI to be precise, with ID 31).
To take an interrupt connected via the IRQS signal you must enable and configure the IC. From your earlier post, you seem to programming all the right registers. Question is what are you programming them to? You could, for example, be enabling ID31 (the nIRQ ID) but not ID32 (the IRQS[0] ID).
On your question about vectors.... No, a Cortex-A9 core has only one IRQ vector.
* Remembering that nIRQ is active low. So to "assert" you actually take the signal low.
Cancel
Up
0
Down
Reply
Cancel
Children
No data
More questions in this forum
By title
By date
By reply count
By view count
By most asked
By votes
By quality
Descending
Ascending
All recent questions
Unread questions
Questions you've participated in
Questions you've asked
Unanswered questions
Answered questions
Questions with suggested answers
Questions with no replies
Suggested Answer
Positioning a function in a Position Independent Executable for ARMV8
0
5889
views
3
replies
Latest
1 month ago
by
Stephen Theobald
Answered
Link a pure binary file to image with scatter file
0
5845
views
3
replies
Latest
1 month ago
by
Ronan Synnott
Answered
Failed to read contents of Internal RAM L1-I_DATA in ARM DS
0
Arm Development Studio
Cache
Debug and Trace Services Layer (DTSL)
10093
views
23
replies
Latest
1 month ago
by
Boon Khai
Suggested Answer
DS-5 connect fail when cortex-r5 is in lock-step mode
0
8449
views
10
replies
Latest
2 months ago
by
Stuart Hirons
Suggested Answer
On Cortex-M4F microcontrollers: is fixed point math faster or floating point?
0
8118
views
10
replies
Latest
2 months ago
by
Ronan Synnott
<
>
View all questions in Arm Development Studio forum