Remote Memory Check via Debug File Symbol Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory check technologies, such as in-circuit emulators, lack flexibility and are not suitable for remote debugging operations, as they require direct connection to a motherboard and can only analyze data within the emulator itself, limiting their applicability and efficiency.
Innovation Solution
A memory check method and system that generates a debug file from source code with symbol information, allowing for remote analysis of memory data from a memory storage device, enabling automatic analysis and presentation of firmware status through an application program interface, with the ability to update firmware codes based on user adjustments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If an in-circuit emulator is used to retrieve and analyze memory data, then the memory storage device can be accessed through a communication port of the motherboard, but the device requires direct connection to the motherboard and lacks flexibility for remote debugging operations
Solution Approach 1:
The patent introduces a host system as an intermediary component between the memory storage device and the analysis tool. The host system includes a processor that generates debug files from source code and automatically analyzes memory data, eliminating the need for direct physical connection between the emulator and the analysis tool. This mediator enables remote debugging operations while maintaining analysis capability.
Solution Approach 2:
The patent creates a debug file that contains symbol information copied from the source code. This debug file serves as a representation of the original source code, allowing the system to analyze memory data against the symbol information without requiring the actual source code or direct connection to the development environment. This copying approach enables flexible remote analysis.
2Adaptability or versatility
If an in-circuit emulator is used to analyze memory data, then the data can be retrieved from the memory storage device, but the analysis can only be performed by the in-circuit emulator itself, limiting flexibility
Solution Approach 1:
The patent segments the debugging system into separate functional components: the host system that generates debug files from source code, the component that retrieves memory data from the storage device, and the processor that automatically analyzes the memory data against the debug file. This segmentation allows each component to perform its specific function independently, enabling flexible analysis without requiring a monolithic in-circuit emulator system.
Solution Approach 2:
The host system performs self-service by automatically generating the debug file from the source code and using it to analyze the memory data. The processor automatically compares the memory data with the symbol information in the debug file and presents the analysis results. This automated self-service approach eliminates the need for manual intervention and enables flexible analysis across different platforms.
3Productivity
If symbol information from source code is incorporated into a debug file for automatic analysis, then work efficiency in performing firmware checks is increased, but additional processing steps are required to generate the debug file
Solution Approach 1:
The patent applies preliminary action by generating the debug file containing symbol information from the source code before the actual firmware checking process begins. The host system processes the source code and creates the debug file in advance, so that when memory data needs to be analyzed, the symbol information is already prepared and readily available. This preliminary preparation significantly speeds up the subsequent firmware checking and analysis operations.
Data Source
AI summary
A memory check method, a memory check device and a memory check system are disclosed. The method includes the following. A debug file is generated according to a source code, where the debug file carries symbol information related to a description message in the source code. Memory data generated by a memory storage device in execution of a firmware is received. The debug file is loaded to automatically analyze the memory data. In addition, an analysis result is presented by an application program interface, where the analysis result reflects a status of the firmware with assistance of the symbol information.