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
SoC Design and Simulation forum
Confusion over AMBA AHB hsize[] signal definition
Jump...
Cancel
State
Not Answered
Locked
Locked
Replies
4 replies
Subscribers
88 subscribers
Views
10647 views
Users
0 members are here
AMBA
Bus Architecture
AHB
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
Confusion over AMBA AHB hsize[] signal definition
davemac2 davemac2
over 11 years ago
Note: This was originally posted on 26th February 2008 at
http://forums.arm.com
After reading the AMBA AHB spec rev 2, I am still confused over the relationship of the HSIZE[2:0] signal and the implemented bus width on an interface. If an AHB bus is implemented using 32 bit write and read data buses, I would think this would imply that hsize[2] is essentially unused and always '0' since data transfer width on this bus can only be a byte, half word, or word. Yet, I see interface signal specifications on various 32 bit bus AHB designs where hsize[2] seems to be used and is not optimized out even after synthesis?? My understanding of HSIZE[] and HBURST[] signals is that HBURST[] determines the number of data transfer beats on the bus for a burst transaction whereas HSIZE determines the data width of each transfer. The spec. seems to be vague on this with no examples.
dave mc
Parents
0
Colin Campbell
over 11 years ago
Note: This was originally posted on 21st July 2008 at
http://forums.arm.com
Hemamth,
Just to correct your reply, if you are using data bus widths of up to 32 (3'b010) or 64 bits (3'b011) wide then HSIZE[1:0] would be sufficient, so it is only once you go above that level when the HSIZE[2] bit would be required.
JD
Cancel
Up
0
Down
Cancel
Reply
0
Colin Campbell
over 11 years ago
Note: This was originally posted on 21st July 2008 at
http://forums.arm.com
Hemamth,
Just to correct your reply, if you are using data bus widths of up to 32 (3'b010) or 64 bits (3'b011) wide then HSIZE[1:0] would be sufficient, so it is only once you go above that level when the HSIZE[2] bit would be required.
JD
Cancel
Up
0
Down
Cancel
Children
No data