Event Logger for Embedded Software Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Embedded software development faces challenges in debugging due to resource constraints and the need for cost-effective solutions that do not require computationally intensive debugger systems, especially in environments like flight systems where size and resource consumption are critical.
Innovation Solution
An event logger is implemented as a software component that writes data values to a memory partition in response to specific events, including an identifier and parameters, and ceases logging when a predefined stop identifier is matched, allowing for efficient data capture and error analysis without the need for extensive debugging systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a debugger or debugging tool is used to test and debug embedded software, then debugging capability is improved, but resource consumption and system complexity increase
Solution Approach 1:
The patent extracts the essential debugging function from a complex debugger system and implements it as a lightweight event logger within the embedded application. The event logger captures only necessary runtime information (events, parameters, timestamps) without requiring the full debugger infrastructure, thus providing debugging capability while minimizing system complexity and resource consumption.
Solution Approach 2:
The patent creates a simplified copy of the debugging function by implementing an event logger that mirrors essential debugging capabilities (data capture, event tracking) without replicating the entire debugger system. This allows the embedded system to maintain debugging functionality while using minimal resources.
2Loss of information
If an event log continuously writes data values to memory, then data capture completeness is improved, but memory resources are consumed and critical information may be overwritten
Solution Approach 1:
The patent applies preliminary action by pre-defining stop identifiers and conditions before runtime. When these predefined conditions are met during execution, the event logger automatically ceases logging, preventing overwriting of critical information and preserving memory resources without requiring continuous monitoring or dynamic allocation.
Solution Approach 2:
The patent changes the operational state of the event logger by introducing a stop condition parameter. When the event identifier matches the predefined stop identifier, the logging parameter transitions from active to inactive, dynamically controlling memory usage based on runtime conditions while ensuring critical data is preserved.
3Measurement precision
If computationally intensive debugger systems are used for error analysis, then debugging precision is improved, but resource consumption and cost increase
Solution Approach 1:
The patent replaces expensive, resource-intensive debugger systems with a lightweight, disposable event logger implementation. The event logger uses minimal memory and processing resources to capture essential debugging information, providing adequate debugging precision for embedded systems while dramatically reducing resource consumption and cost.
Data Source
AI summary
An application can executes a plurality of tasks and responds to interrupts. The application can include an event logger that writes data values to an event log stored in an assigned partition of memory in response to a call to the event logger, wherein the call includes an identifier of an event and parameters corresponding to the data values, and the event logger ceases further writing to the event log in response to the identifier of the event matching a predefined stop identifier.