Vehicle ECU Update Circuit With Hardwired Packet Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional electronic control units (ECUs) in vehicles face increased processing load and operational disruptions when receiving software updates, as the bootloader module handles data packets, affecting normal CPU operation during software updates.

Innovation Solution

Incorporating a hardware component with hardwired logic that encodes a predefined communication protocol to receive and store software program data packets, offloading this functionality from the processing unit, thereby reducing processing load and maintaining normal operation during updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the bootloader or CPU handles data packets for software updates, then the software update function is achieved, but the processing load of the CPU increases and normal operation is affected

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidCPU processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system is divided into two independent parts: a hardware component with hardwired logic dedicated to receiving and storing software update data packets, and a processing unit (CPU) that handles normal operational tasks. This segmentation allows the CPU to remain unloaded during update operations while the hardware component independently manages data reception and storage via the memory interface.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A dedicated hardware component acts as an intermediary between the communication network and the CPU. This intermediary receives data packets through the network interface, processes them according to the encoded communication protocol, and stores them in non-volatile memory through the memory interface, thereby shielding the CPU from processing load during update operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Duration of action of stationary object

If the CPU executes the previous software version while receiving update data, then continuous operation is maintained, but the processing load increases and may cause operational disruptions

Engineering Contradiction:
Improvecontinuous operation durationVSAvoidoperational stability
Core Design Contradiction:
Duration of action of stationary objectVSReliability

Solution Approach 1:

By separating the software update reception function into a dedicated hardware component, the CPU can continuously execute the previous software version without interruption or increased processing load. The hardware component independently handles all update-related operations, ensuring operational stability while maintaining continuous service.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The hardware component with hardwired logic performs self-service for receiving and storing software update data packets. It independently manages the entire update data reception process through its encoded communication protocol, without requiring CPU intervention, thus allowing the CPU to maintain normal operational continuity without additional processing burden.

Inventive Principle:
Principle #25Self-service

3Productivity

If a hardware component with hardwired logic is introduced to receive and store software updates, then the processing load on the CPU is reduced, but the device complexity increases

Engineering Contradiction:
ImproveCPU processing efficiencyVSAvoidelectronic circuit complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The software update reception functionality is extracted from the CPU and implemented as a separate hardware component with hardwired logic. This extracted component handles all data packet reception and storage operations independently, reducing the CPU's processing load while adding a dedicated functional unit that simplifies the overall system architecture by clearly separating concerns.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The software-based bootloader approach is replaced with a hardware-based solution featuring hardwired logic that encodes the communication protocol directly in hardware. This substitution eliminates the need for CPU software execution during update reception, reducing processing load and improving determinism, while the hardware implementation provides reliable and efficient data handling.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If the hardwired logic encodes the communication protocol in hardware, then the update process becomes more deterministic and robust, but the manufacturing complexity increases

Engineering Contradiction:
Improveupdate process robustnessVSAvoidhardware component manufacturing
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The communication protocol processing is implemented in hardwired logic rather than software, providing deterministic and robust update operations. While this increases manufacturing complexity compared to software-only solutions, it eliminates runtime processing variability and ensures reliable protocol handling. The hardware implementation can be integrated into standard electronic control unit manufacturing processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The hardware component with hardwired logic is designed as a universal solution that can be integrated into various electronic control units for software updates. By encoding the communication protocol in hardware, the same component design can serve multiple applications and vehicle models, amortizing the manufacturing complexity across large production volumes and different product lines.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP4290369A1Electronic circuit for a vehicle
Publication Date: 2023.12.13 VALEO INTERNAL AUTOMOTIVE SOFTWARE EGYPT A LLC
  • EP4290369A1 patent drawingFigure 1~2
  • EP4290369A1 patent drawing
  • EP4290369A1 patent drawing

AI summary

An electronic circuit (3) for a vehicle (1) comprises a network interface (7) for connecting the electronic circuit (3) to a communication network and a hardware component (6) with a hardwired logic to receive at least one data packet representing a software program from the communication network via the network interface (7) according to a predefined communication protocol. The electronic circuit (3) comprises a memory interface (13) connected to the hardware component (6), wherein the hardware component (6) is adapted to store the software program to a non-volatile memory (8) via the memory interface (13), and a processing unit (5), which is configured to read the non-volatile memory (8) and to execute the software program.