Fabric Trace Hook for On-Chip System Fabric Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Debugging operations in system-on-chip (SoC) devices are complicated by the introduction of peer-to-peer transactions in PSF 2.0, which removes the system agent from the transaction path, making it difficult for debuggers to reach all entities on the SoC.
Innovation Solution
A fabric trace hook is embedded within the IOSF, featuring programmable triggering and capturing logic, timestamp capability, and a security feature to enable debugging of peer-to-peer transactions, operating in either lossy or lossless mode.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If peer-to-peer transactions are implemented in PSF 2.0 to enable direct communication between agents, then transaction efficiency and system performance are improved, but debugging capability and accessibility to all entities on the SoC deteriorate because the system agent is removed from the transaction path
Solution Approach 1:
A fabric trace hook is introduced as an intermediary component embedded within the IOSF to monitor and trace peer-to-peer transactions between agents. The trace hook captures transaction information without interfering with the direct peer-to-peer communication path, enabling debugging capabilities while maintaining transaction efficiency. The trace hook acts as a mediator that provides observability into transactions that would otherwise be inaccessible.
2Difficulty of detecting and measuring
If a trace hook is embedded within the IOSF to enable debugging of peer-to-peer transactions, then debugging capability is improved, but device complexity and implementation difficulty increase
Solution Approach 1:
The fabric trace hook is merged with the existing IOSF infrastructure, embedding the debugging functionality directly within the interconnect fabric rather than as a separate external component. This integration leverages existing fabric resources and pathways, reducing overall system complexity while maintaining comprehensive transaction tracing capability.
3Loss of information
If comprehensive transaction tracing is enabled to capture all fabric transactions for debugging purposes, then debugging information completeness is improved, but performance overhead and system resource consumption increase
Solution Approach 1:
The trace hook implementation uses local quality by allowing selective tracing of specific transaction types, sources, or destinations rather than uniformly tracing all transactions. This enables debugging focus on critical transaction paths while reducing overhead from tracing unrelated transactions, optimizing the balance between information completeness and performance overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A fabric trace hook is disclosed to enable debugging operations of agents operating in a peer-to-peer integrated on-chip system fabric. The fabric trace hook, embedded within the IOSF, includes programmable triggering and capturing logic, timestamp capability, and a security feature to disallow tracing of proprietary transactions. The fabric trace hook may operate in a lossy or lossless mode.