Bus Bridge Translating Module Bus to AXI Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy local control network (LCN) chassis-based systems that use the module bus communication protocol are becoming obsolete due to manufacturers discontinuing support, and newer devices supporting modern protocols like the advanced extensible interface (AXI) bus are unable to communicate with them, leading to a communication barrier.
Innovation Solution
A bus interface device with programmable logic, such as a gate array or FPGA, is used to bridge between the module bus and AXI bus, receiving and buffering read/write requests to translate them into conforming requests for either protocol, enabling communication between legacy and modern systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a bus interface device buffers and translates read/write requests between module bus and AXI bus protocols, then compatibility between legacy and modern systems is improved, but device complexity increases
Solution Approach 1:
The bus interface device serves as an intermediary component between the module bus and AXI bus, translating requests from one protocol to the other. The device includes a request buffer that temporarily stores incoming requests, allowing translation to occur without real-time synchronization requirements between the two different bus protocols, thus enabling compatibility while managing complexity through buffered asynchronous operation
Solution Approach 2:
The bus interface device changes protocol parameters by translating read/write requests between two different bus protocols (module bus and AXI bus). The translation process modifies request format, timing, and protocol-specific parameters to make them conform to the target protocol, enabling legacy devices to communicate with modern systems despite parameter differences
2Manufacturing precision
If the bus interface device buffers read/write requests, then translation accuracy is improved, but loss of time increases
Solution Approach 1:
The bus interface device performs preliminary buffering of read/write requests before translation occurs. By capturing and storing incoming requests in a buffer first, the device can translate them at its own pace without being constrained by real-time protocol synchronization requirements, ensuring accurate translation while managing time delays through asynchronous operation
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A method for bus bridging includes providing a bus interface device (110) that is coupled between at least one module bus (132) and at least one advanced extensible interface (AXI) bus (162) for translating bus requests between the module bus and the AXI bus. The bus interface device includes logic (114). The logic is configured to receive (304, 354) a read/write (R/W) request that is one of a module bus protocol R/W request and an AXI bus protocol R/W request and to buffer (306, 356) the R/W request to provide a buffered R/W request. The logic translates (310) the buffered R/W request to a first AXI protocol conforming request if the buffered R/W request is the module bus protocol R/W request and translates (360) the buffered R/W request to a first module bus protocol conforming request if the buffered R/W request is the AXI bus protocol R/W request. The translated requests are transmitted (312, 362) to their respective bus.