Partition Synchronization for Redundant MCU Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional non-MMU type MCU systems face challenges in performing redundant updates due to the inability to switch memory addresses, leading to differences in version images between partition areas that result in invalid execution images when copied across partitions.

Innovation Solution

A partition synchronization method that generates and utilizes synchronization information based on differences between redundant partition areas to synchronize images, allowing for the removal of differences from one partition's image using this information and copying it to another partition, thereby ensuring consistent and executable version images across both partitions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If conventional redundant update method is used in non-MMU type MCU, then update process is simple, but version images become invalid when copied across partitions due to address differences

Engineering Contradiction:
Improveupdate process simplicityVSAvoidexecution image validity
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent applies preliminary action by generating synchronization information before the update process. This synchronization information, which contains the difference between version images of different partitions, is prepared in advance and stored. During update, this pre-prepared synchronization information is used to correctly adjust the copied version image, preventing invalid execution images without complicating the actual update process.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If version images are copied across partitions without synchronization information, then update speed is fast, but execution images become invalid due to address mapping differences

Engineering Contradiction:
Improveupdate speedVSAvoidexecution image validity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent extracts only the necessary difference information between version images into separate synchronization information. Instead of copying entire version images or using complex address translation mechanisms, the system extracts minimal synchronization data that captures the essential differences. This extracted synchronization information is then applied during the copy process, maintaining fast update speed while ensuring execution image validity.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If synchronization information is generated and used to remove differences between partitions, then execution image validity is ensured, but update process complexity increases

Engineering Contradiction:
Improveexecution image validityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses copying by creating a standard version image in one partition and then copying it to another partition with the application of synchronization information. The synchronization information acts as a simple adjustment layer that accounts for address mapping differences. This copying approach with minimal adjustment is simpler than full address translation or regenerating version images, thus ensuring execution image validity without significantly increasing process complexity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250103319A1Partition synchronization method for redundant update and device for implementing same
Publication Date: 2025.03.27 HYUNDAI AUTOEVER
  • US20250103319A1 patent drawing
  • US20250103319A1 patent drawing
  • US20250103319A1 patent drawing

AI summary

A partition synchronization method in redundant update for updating a new version part in an execution controller operated redundantly with a first partition and a second partition includes generating first synchronization information and recording the first synchronization information along with a first new version part in one area of the first partition, and removing a difference from the first new version part using the first synchronization information and recording the difference-removed first new version part in one area of the second partition as a second new version part.