Group-Based Debug Message Routing for Interdependent Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing debugging systems are limited in their ability to efficiently debug multiple interdependent system components simultaneously, often requiring lengthy debugging times and disrupting system setups, and are constrained by the involvement of host interfaces that consume system resources.
Innovation Solution
A debugging mechanism that supports cohesive debugging of multiple interdependent system components simultaneously, utilizing a Debug and Test System (DTS) with a debug controller and bridge to manage and route debug messages across groups of interconnected targets, employing Group Identifiers and Quality of Service parameters to optimize debugging operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing debugging systems debug multiple interdependent system components, then debugging coverage is improved, but debugging time increases significantly
Solution Approach 1:
The patent segments the debugging process by introducing a debug bridge that separates debug message routing from the host interface. The debug bridge divides debug traffic into different groups (e.g., first group to first debug target, second group to second debug target) and routes them independently. This segmentation allows parallel debugging of multiple interdependent components without requiring sequential access through a single host interface, thereby reducing total debugging time while maintaining comprehensive coverage.
2Ease of operation
If host interfaces are used for debugging, then system resource access is improved, but system resource consumption increases
Solution Approach 1:
The patent extracts the debugging function from the host interface by introducing a dedicated debug bridge. The debug bridge is specifically designed to handle debug message routing between debug targets and the debug and test system. This extraction allows the host interface to focus on its primary system resource management functions while the debug bridge handles debugging operations independently, reducing the burden on system resources and improving overall efficiency.
3Ease of operation
If system setup is disrupted for debugging, then debugging access is improved, but system stability deteriorates
Solution Approach 1:
The patent introduces a debug bridge as an intermediary component between the debug and test system and the interdependent system components. This debug bridge acts as a mediator that facilitates debugging access without requiring disruption to the existing system setup. The bridge intercepts and routes debug messages while allowing the original system architecture and component interactions to remain intact, thereby maintaining system stability while enabling comprehensive debugging capability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
For example, a debug target may include an interconnect interface; and a debug manager configured to cause the debug target to process a debug request message received from a Debug and Test System (DTS) via the interconnect interface. For example, the debug request message may include a group Identifier (ID) value and a debug request. For example, the debug manager may be configured to cause the debug target to execute the debug request, for example, based on a determination that the group ID value is to identify a group of debug targets including the debug target. For example, the debug manager may be configured to cause the debug target to send a debug response message via the interconnect interface, the debug response message including the group ID value and a debug response for the DTS.