Vehicle Embedded Controller Reset Cause Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for determining the cause of resets in embedded controllers for vehicles are inadequate, as they often require additional costly debugging information and separate hardware, making it difficult to analyze reset causes effectively, which can impact vehicle safety and performance.
Innovation Solution
A method and embedded controller system that generates and analyzes logs during runtime to determine reset causes, using a sequence number generator, log collector, DMA controller, log analyzer, and log recorder to store analysis results in a non-volatile storage device, thereby identifying reset triggers and causes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If additional costly debugging information and separate hardware are used to determine reset causes, then measurement precision improves, but device complexity and cost increase
Solution Approach 1:
The embedded controller determines its own reset cause by analyzing logs generated during normal operation. The log collector continuously collects runtime information, and the log analyzer processes these logs to identify reset triggers, eliminating the need for external debugging hardware.
Solution Approach 2:
The system pre-collects and stores logs containing reset trigger information during normal runtime operations. When a reset occurs, the pre-collected logs are already available for immediate analysis, enabling rapid determination of the reset cause without requiring additional debugging equipment.
2Loss of information
If comprehensive log collection is performed during runtime, then information completeness improves, but loss of time for data processing increases
Solution Approach 1:
The log analyzer extracts only the specific reset trigger information needed from the collected logs, rather than processing entire log files. This selective extraction approach maintains information completeness while significantly reducing processing time.
Solution Approach 2:
Logs containing reset trigger information are collected and stored in advance during normal operation. When a reset occurs, the analysis is performed on pre-collected data rather than gathering information after the reset, eliminating time loss.
Data Source
AI summary
A method for determining a reset cause of an embedded controller for a vehicle includes: executing an embedded controller for the vehicle by a central processing unit (CPU) of the embedded controller; generating a log based on information related to reset of the embedded controller collected from the running embedded controller, and a sequence number generated by the running embedded controller by the embedded controller; determining cause information of a reset trigger by analyzing the log including the reset trigger log, and determining reset cause information of the embedded controller based on the cause information of the reset trigger by a log analyzer of the embedded controller; storing a cause analysis result log including the reset cause information in a cause analysis result buffer in response to the reset cause information by the embedded controller; and storing the cause analysis result log in a non-volatile storage device.