Software-Trace Message Sink Peripheral for SoC Timing Preservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In embedded software development for System on Chip (SoC) devices, the removal of trace instructions after development can alter the timing behavior of the software, leading to undesirable changes and potential introduction of new bugs, while retaining the software-trace message handling system consumes significant power, especially in battery-powered devices.
Innovation Solution
An integrated circuit device with a software-trace message sink peripheral and a hardware interconnect system that directs software-trace messages to the sink peripheral, mimicking the interconnect delay of the handling system, allowing for retention of trace code without the power-intensive handling system during non-debug modes, and configuring the delay to match the original timing behavior.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Use of energy by moving object
If trace instructions are removed from the software after development, then power consumption is reduced and the software runs faster, but the timing behavior of the software changes which can introduce bugs in timing-sensitive systems
Solution Approach 1:
The patent creates a simplified copy of the trace message handling functionality in the form of a sink peripheral that mimics the timing characteristics of the full handling system. This copy allows trace instructions to remain in the software without affecting timing behavior, while consuming minimal power since the sink peripheral is much simpler than the full handling system.
Solution Approach 2:
The patent changes the operational parameters of the trace message destination by switching from a full-featured handling system to a minimal sink peripheral that only maintains timing characteristics. The sink peripheral is configured to present the same interconnect delay as the original handling system, thereby maintaining timing parameters while reducing power consumption parameters.
2Reliability
If the software-trace message handling system is retained in the final product, then timing behavior is preserved, but power consumption increases significantly
Solution Approach 1:
Instead of retaining the full trace message handling system, the patent creates a simplified copy in the form of a sink peripheral that replicates only the essential timing characteristics. This copy consumes minimal power while preserving the timing behavior needed for timing-sensitive operations.
Solution Approach 2:
The patent replaces the expensive, power-intensive trace message handling system with a cheap, minimal sink peripheral that serves the same timing preservation function. The sink peripheral is a simplified, low-cost alternative that achieves the same timing preservation goal without the high power consumption of the original system.
3Reliability
If trace instructions are kept in the software, then timing behavior is maintained, but the software requires more processing time during execution
Solution Approach 1:
The patent creates a simplified copy of the trace handling functionality that allows trace instructions to remain in the software without significantly impacting execution speed. The sink peripheral processes trace messages with minimal overhead, preserving timing behavior while maintaining productivity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An integrated circuit device (100) has a processor (128), a software-trace message handling system (110), a software-trace message sink peripheral (122), and a hardware interconnect system (132). The interconnect system (132) is capable of directing software-trace messages from the processor (128) to the software-trace message handling system (110), and of directing software-trace messages from the processor (128) to the software-trace message sink peripheral (122). The software-trace message sink peripheral (122) can present an interconnect delay to the processor( 128), when receiving a software-trace message from the processor (128), that is equal to or substantially equal to an interconnect delay that the software-trace message handling system (110) would have presented to the processor (128) if the software-trace message handling system (110) were to have received the software-trace message.