Die-to-Die Link Configuration via Sideband Debug Path
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing die-to-die communication systems face challenges in debugging and troubleshooting when the high-speed link fails or the primary die is unable to access configuration data from the secondary die, leading to system instability and inability to configure the high-speed link.
Innovation Solution
Implementing a sideband link alongside the high-speed link to enable access to the secondary die for control and status data, allowing debugging and troubleshooting operations by receiving control and status data from the secondary die through the sideband link, even in failure scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a high-speed link is used for die-to-die communication, then data transfer speed and bandwidth are improved, but the ability to debug and troubleshoot the link is worsened when configuration failures occur
Solution Approach 1:
A sideband link is introduced as an intermediary communication channel between the primary and secondary dies. This sideband link operates independently from the high-speed link and carries configuration commands and status data. When the high-speed link fails to configure properly, the sideband link serves as a mediator to transmit debugging information and control data, enabling troubleshooting without relying on the failed high-speed connection.
2Productivity
If the primary die uses the high-speed link to access configuration data from the secondary die, then configuration speed is improved, but system stability is worsened when the link fails
Solution Approach 1:
The sideband link is established beforehand as a backup communication path. It is specifically designed to carry control and status data independently of the high-speed link. When configuration failures occur on the high-speed link, the sideband link provides a pre-prepared cushioning mechanism that maintains system stability by allowing the primary die to still access configuration data and status information through the alternative path.
3Device complexity
If only a high-speed link is implemented between dies, then device complexity is reduced, but the ability to perform debugging operations is worsened
Solution Approach 1:
The communication infrastructure is segmented into two distinct functional channels: a high-speed link for data transfer and a sideband link for control and debugging operations. This segmentation separates the debugging functionality from the high-speed data path, allowing troubleshooting operations to be performed through the sideband link without interfering with or complicating the high-speed link structure.
Data Source
AI summary
A first device includes first circuitry to communicate with a second device over a first die-to-die (D2D) link, second circuitry to communicate with the second device over a second D2D link, and a link controller comprising logic to send first configuration data to the second device over the first D2D link. Responsive to determining that the first configuration data failed to configure the second device, the link controller comprises logic to send second configuration data to the second device over the second D2D link.