Multicore Vehicle Software Diagnosis via Shared Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software diagnosis systems for vehicles are costly, time-consuming, and require significant memory resources, often necessitating separate test benches and static test codes, which increase development costs and diagnosis time.
Innovation Solution
A system and method that utilize a shared memory to generate and verify data sets containing function and argument information across multiple cores in a multicore environment, allowing for real-time operation and verification of target software without a separate test bench or test code, thereby reducing memory usage and costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate test benches and static test codes are used for software diagnosis, then verification reliability is improved, but device complexity and cost increase
Solution Approach 1:
The patent merges the test bench functionality and test code storage into the target ECU itself by utilizing its internal memory resources. The diagnosis system combines the target software, test code, and data sets into a single integrated system, eliminating the need for separate external test benches and reducing overall device complexity while maintaining verification reliability.
Solution Approach 2:
The target ECU is designed to serve multiple functions: it executes the target software, stores test code, manages data sets, and performs verification operations. This multi-functionality eliminates the need for dedicated separate test equipment, reducing device complexity and cost while maintaining the ability to perform comprehensive software verification.
2Measurement precision
If separate test benches are used for software verification, then measurement precision is improved, but loss of time increases
Solution Approach 1:
By merging the test verification functionality into the target ECU's internal resources, the system eliminates the time required for data transfer and coordination between separate test benches and target systems. The integrated approach allows immediate execution of test codes and real-time verification, reducing diagnosis time while maintaining verification accuracy through systematic test code execution and result comparison.
3Manufacturing precision
If comprehensive test codes are stored externally, then manufacturing precision is improved, but use of energy and memory increases
Solution Approach 1:
The patent segments the test code and data sets into manageable portions that are sequentially loaded from external storage into the ECU's internal memory only when needed. This segmentation allows comprehensive test coverage to be achieved without permanently occupying large amounts of internal memory, as data is loaded, processed, and then discarded or reused as needed.
Solution Approach 2:
Test codes and data sets are prepared and organized in advance in external storage media. This preliminary preparation allows the ECU to load only the specific test data needed for current verification tasks, minimizing internal memory usage while ensuring comprehensive test coverage is available when required.
4Productivity
If multiple data sets are stored in shared memory, then productivity is improved, but use of energy and memory increases
Solution Approach 1:
The system implements periodic loading of data sets into shared memory based on verification needs rather than permanently storing all data sets. Data sets are loaded, processed for verification, and then discarded or archived, allowing the same memory resources to be reused for subsequent verification tasks. This periodic action enables efficient verification across multiple software versions while managing memory resources effectively.
Data Source
AI summary
A method of operating a system for diagnosing software for a vehicle according to the present invention includes: generating a plurality of data sets including a function and an argument related to a diagnosis of target software executed in each of the plurality of cores; sequentially outputting the plurality of data sets to a shared memory; operating the target software according to the data set of the shared memory; and verifying the operation result in a verifying core.