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
PL031 verilog generation
Jump...
Cancel
State
Not Answered
Locked
Locked
Replies
2 replies
Subscribers
88 subscribers
Views
4443 views
Users
0 members are here
AMBA
PrimeCell High-Performance Matrix
primecell
pl301
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
PL031 verilog generation
nicolan nicolan
over 11 years ago
Note: This was originally posted on 19th February 2009 at
http://forums.arm.com
Pls, I need an answer to a blocking issue
I tried to generate a verilog code for PL031 connection matrix 2x3.
Unfortunely generated HSEL signal for each slave doesn't work properly.
In "AxiToAhbWrapper" output verilog file, in fact, following assign appears:
assign HSEL =1'b1;
and because this block is "copied" for all the master interface inside, then all "HSELx" signals are put high.
What's appens?!
regards
Nicola
Parents
0
Colin Campbell
over 11 years ago
Note: This was originally posted on 20th February 2009 at
http://forums.arm.com
Hi Nicola,
The PL301 (I assume this is what you meant) is usually IP licensed directly from ARM, so you would be much better sending your questions to them directly rather than using a more public forum such as this. Their support guys are probably best placed to support their own IP.
I would guess though that the answer to your questions is that this AHB port is designed to support just one AHB slave, hence the single HSEL output, and if there are no transfers coming to your slave, the HTRANS signal will probably be indicating IDLEs.
If each of your PL301 outputs are AHB ports, each would then have a single AHB HSEL signal, each driven permanently high, and the connected slaves would be permanently selected, using HTRANS to define when a transfer is occuring (all perfectly valid).
You can also specify that the AHB port appears as an AHB master, so no HSEL signal, and you then add your own external AHB decoder block, which will generate the HSEL outputs you want, and active only when you want.
But if you've got a support agreement for PL301 with ARM (or whoever you got the PL301 from), you would get a more definite answer using that channel.
JD
Cancel
Up
0
Down
Cancel
Reply
0
Colin Campbell
over 11 years ago
Note: This was originally posted on 20th February 2009 at
http://forums.arm.com
Hi Nicola,
The PL301 (I assume this is what you meant) is usually IP licensed directly from ARM, so you would be much better sending your questions to them directly rather than using a more public forum such as this. Their support guys are probably best placed to support their own IP.
I would guess though that the answer to your questions is that this AHB port is designed to support just one AHB slave, hence the single HSEL output, and if there are no transfers coming to your slave, the HTRANS signal will probably be indicating IDLEs.
If each of your PL301 outputs are AHB ports, each would then have a single AHB HSEL signal, each driven permanently high, and the connected slaves would be permanently selected, using HTRANS to define when a transfer is occuring (all perfectly valid).
You can also specify that the AHB port appears as an AHB master, so no HSEL signal, and you then add your own external AHB decoder block, which will generate the HSEL outputs you want, and active only when you want.
But if you've got a support agreement for PL301 with ARM (or whoever you got the PL301 from), you would get a more definite answer using that channel.
JD
Cancel
Up
0
Down
Cancel
Children
No data