The Designer's Guide Community
Forum
Welcome, Guest. Please Login or Register. Please follow the Forum guidelines.
Apr 25th, 2024, 4:01am
Pages: 1
Send Topic Print
Universal Peripheral Bus Evolution (Read 2253 times)
sarangapani
New Member
*
Offline



Posts: 1
bangalore
Universal Peripheral Bus Evolution
Jun 13th, 2011, 1:34am
 
1. Master
1. Read related Inputs
1. rd_clk
2. rd_addr_ready
3. rd_data_valid
4. rd_data
5. rd_response (Kinda rd_strobe)
2. Read related Outputs
1. rd_addr
2. rd_addr_valid
3. rd_transaction_id
3. Write related Inputs
1. wr_clk
2. wr_addr_ready
3. wr_data_ready
4. wr_response
4. Write related outputs
1. wr_addr
2. wr_data
3. wr_addr_valid
4. wr_data_valid
5. wr_strobe
6. wr_transaction_id

Will all the above common port list will not be sufficient to have a Unified Peripheral Bus Protocol.

I guess almost all existing bus protocols resembles the same port list kind.

Then why cant be such Unified Peripheral Bus Protocol our Chip Industry follow, to avoid SOC hazzles.
Back to top
 
 
View Profile   IP Logged
Pages: 1
Send Topic Print
Copyright 2002-2024 Designer’s Guide Consulting, Inc. Designer’s Guide® is a registered trademark of Designer’s Guide Consulting, Inc. All rights reserved. Send comments or questions to editor@designers-guide.org. Consider submitting a paper or model.