AXI to OPB Bridge Protocol Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing data interaction between the Advanced extensible Interface (AXI) bus and the On-chip Peripheral Bus (OPB) requires redesign and verification, which is time-consuming and labor-intensive, reducing project development efficiency.
Innovation Solution
A method and apparatus that involve receiving AXI write data, storing it in an AXI write cache, performing timing conversion from the AXI bus protocol to the OPB protocol, and exporting the converted data to the OPB, while also handling read operations through a similar caching and conversion process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data interaction between AXI bus and OPB is performed using existing methods, then data transfer functionality is achieved, but redesign and verification work is required which consumes time and labor
Solution Approach 1:
The patent creates a bridge device that copies and adapts the AXI bus protocol to the OPB protocol, allowing existing IP components designed for one protocol to interact with components designed for another protocol without redesign. The bridge device implements protocol conversion by copying data and control signals from the AXI bus and transforming them into OPB protocol format, thereby eliminating the need for redesign and verification of individual IP components.
Solution Approach 2:
The bridge device serves as an intermediary between the AXI bus and OPB, mediating data interaction by receiving data from one bus protocol and transmitting it through protocol conversion to the other bus protocol. This intermediary approach allows existing IP components to remain unchanged while enabling seamless data interaction, thus reducing development time and labor costs.
2Reliability
If data interaction between AXI bus and OPB is performed using existing methods, then data transfer functionality is achieved, but redesign and verification work reduces project development efficiency
Solution Approach 1:
The bridge device provides universal protocol conversion capability that enables multiple IP components from different protocol families to interact through a single standardized interface. By implementing multi-functional protocol adaptation, the bridge device allows existing IP components to be reused across different bus protocols without modification, thereby improving project development efficiency and reducing redundant verification work.
Solution Approach 2:
The bridge device copies and adapts protocol signals and data between AXI and OPB, enabling universal compatibility. This copying mechanism allows the same IP component to be instantiated multiple times with different protocol requirements, enhancing productivity by eliminating the need for protocol-specific redesign and verification.
3Adaptability or versatility
If protocol conversion is implemented between AXI and OPB, then compatibility is improved, but device complexity increases
Solution Approach 1:
The bridge device implements protocol conversion by acting as an intermediary that translates AXI bus protocol signals into OPB protocol signals and vice versa. This intermediary approach improves protocol compatibility while containing complexity within the bridge device itself, allowing the connected IP components to remain simple and unchanged.
Solution Approach 2:
The bridge device segments the protocol conversion function into distinct modules for address translation, data transfer, and control signal conversion. This segmentation improves adaptability to different protocol requirements while managing device complexity through modular design, making the system more maintainable and easier to verify.
Data Source
AI summary
Disclosed are a method and apparatus for writing data from an Advanced extensible Interface (AXI) bus to an On-chip Peripheral Bus (OPB), a method and apparatus for reading the data from the AXI bus to the OPB, an electronic device and a non-transitory computer readable storage medium. The method for writing the data includes the following steps: receiving AXI write data sent by the AXI bus (S101); storing the AXI write data into an AXI write cache (S102); performing timing conversion from an AXI bus protocol to an OPB protocol on the AXI write data to obtain OPB write data (S103); and exporting the OPB write data from the AXI write cache to the OPB (S104). By applying the method for writing the data, data interaction between the AXI bus and the OPB is completed, the cost is reduced, and the project development efficiency is improved.