Autonomous Event Trace Module for Signaling Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In complex systems with multiple microcontroller-controlled devices, the increasing number of signaling events can lead to routing delays and complexity, requiring efficient methods to manage and trace these events without relying on system CPUs or DMA controllers.
Innovation Solution
A controller system with an event subsystem and trace module that receives, samples, and generates event trace records with timestamps, using multiplexers to route events and a mask module to identify unmasked events, enabling the generation of save commands and storage of event trace records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the number of devices in a system is increased, then the system functionality is improved, but the number of signaling events increases leading to routing delays and complexity
Solution Approach 1:
An autonomous event system is introduced as an intermediary layer between peripheral devices and the microcontroller. This event system includes event channels and multiplexers that automatically route signaling events between devices without requiring CPU or DMA controller intervention. The trace module further acts as an intermediary that captures and records events autonomously, reducing the complexity burden on the main system architecture.
Solution Approach 2:
The system architecture is segmented into distinct functional modules: peripheral devices, autonomous event system with multiplexers, trace module with sampling circuitry, and storage module. This segmentation allows each component to handle specific tasks independently, reducing overall routing complexity while maintaining system functionality.
2Reliability
If traditional CPU or DMA controllers are used to manage signaling events, then event management is achieved, but system complexity and execution time increase
Solution Approach 1:
The autonomous event system is designed to self-manage signaling events without external control. The multiplexers automatically route events based on predefined configurations, and the trace module autonomously samples and records events with timestamps. This self-service capability eliminates the need for CPU or DMA controller intervention, reducing control complexity while maintaining reliable event management.
Solution Approach 2:
The system performs preliminary actions by pre-configuring event channels and multiplexer routing paths before events occur. The trace module is pre-configured with sampling parameters and trigger conditions, allowing it to autonomously capture events without real-time control overhead. This preliminary setup reduces execution time and control complexity during actual event processing.
3Loss of information
If all signaling events are traced and stored, then complete event information is captured, but storage requirements and processing overhead increase
Solution Approach 1:
The trace module implements partial action by selectively tracing only specific signaling events based on configurable criteria. The mask module allows users to define which events should be captured and which can be ignored. This selective tracing approach maintains essential event information while significantly reducing storage requirements and processing overhead compared to tracing all events.
Solution Approach 2:
Different tracing configurations can be applied to different event channels or device groups. The system allows local customization of trace depth and detail based on the specific requirements of each peripheral device or event type, optimizing the balance between information completeness and storage efficiency for each local context.
Data Source
AI summary
Systems and methods for generating event trace records are described. One example system includes an event subsystem that receives signaling events generated by one or more associated peripheral devices. The system includes a trace module which is coupled to the event subsystem. The trace module receives the signaling events, samples the received signaling events, receives timestamps, and generates event trace records. Each event trace record includes the sampled signaling events and a respective timestamp indicative of the sampling time. The trace module can generate save commands, and deliver the event trace records and the save commands as outputs.