Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
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
TCM arbitration hazard: Considerations for Firmware
Jump...
Cancel
State
Not Answered
Locked
Locked
Replies
0 replies
Subscribers
347 subscribers
Views
1848 views
Users
0 members are here
Cortex-R
Cortex-R5
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
TCM arbitration hazard: Considerations for Firmware
c0deface
over 4 years ago
According to the ARM spec (ARM DDI 0460D section 8.4.4):
TCM arbitration
Each TCM port receives requests from the LSU, PFU, and AXI slave. In most cases, the LSU
has the highest priority, followed by the PFU, with the AXI slave having lowest priority.
When a higher-priority device is accessing a TCM port, an access from a lower-priority device
must stall.
When either the LSU or the AXI slave interface is performing a read-modify-write
operation on
a TCM port, various internal data hazards exist for either the AXI-slave interface
or the LSU.
In these cases,
additional stall cycles are generated
, beyond those normally
required for
arbitration.
Is there something special that the firmware should do for such hazard ?