Master-Slave MCU Firmware Boot via Shared Flash Chip

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex systems with multiple MCUs, the traditional method of using separate Flash chips for each MCU results in resource wastage, increased circuit complexity, and higher costs due to underutilization of storage space.

Innovation Solution

A firmware boot implementation method where one MCU acts as a master and the others as slaves, with the master MCU connected to a Flash chip, allowing it to power on, read firmware data, and distribute it to the slave MCUs, maximizing resource utilization and reducing costs by sharing a single Flash chip.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each MCU is mounted with a separate Flash chip, then each MCU can independently access firmware, but the system experiences resource waste, increased circuit complexity, and higher costs

Engineering Contradiction:
Improvefirmware access reliabilityVSAvoidcircuit complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple slave MCUs share a single Flash chip through the master MCU, merging what would traditionally be separate storage resources into a shared resource pool. The master MCU acts as an intermediary that manages firmware distribution to multiple slaves, reducing the total number of Flash chips needed while maintaining reliable firmware access for all MCUs

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The master MCU serves multiple functions: it boots from the Flash chip like a traditional MCU, and simultaneously acts as a firmware distributor to multiple slave MCUs. This multi-functionality allows a single Flash chip to serve multiple MCUs, reducing circuit complexity while maintaining system reliability

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

2Reliability

If each MCU is mounted with a separate Flash chip, then each MCU has dedicated storage, but the storage space utilization is low and costs increase

Engineering Contradiction:
Improvefirmware storage reliabilityVSAvoidstorage space waste
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent merges multiple dedicated Flash chip resources into a single shared Flash chip that serves multiple MCUs. The master MCU manages firmware distribution to slave MCUs, ensuring that storage space is efficiently utilized across the system while maintaining reliable firmware availability for all MCUs

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single Flash chip performs multiple functions by serving the master MCU directly and serving multiple slave MCUs through the master MCU's firmware distribution mechanism. This universal usage maximizes storage space utilization while maintaining firmware storage reliability

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

3Ease of operation

If each MCU is mounted with a separate Flash chip, then firmware can be loaded independently, but the system cost increases

Engineering Contradiction:
Improvefirmware loading independenceVSAvoidnumber of Flash chips
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent combines multiple Flash chip components into a single shared Flash chip that serves the entire MCU system. The master MCU manages firmware distribution to slave MCUs, reducing the quantity of Flash chips needed while maintaining the ability to load firmware independently for each MCU through the shared resource

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11231936B2Firmware boot implementation method based on flash chip simulation connected to a master microcontroller unit (MCU) and slave MCU
Publication Date: 2022.01.25 YEALINK (XIAMEN) NETWORK TECHNOLOGY CO LTD
  • US11231936B2 patent drawing
  • US11231936B2 patent drawing
  • US11231936B2 patent drawing

AI summary

The embodiments of the present disclosure disclose a firmware boot implementation method based on Flash chip simulation, the method comprising: when there are at least two MCUs, one of the MCUs is selected as a master MCU and each remaining MCU is as slave MCU which is connected with the master MCU respectively, and the master MCU is connected with a Flash chip; when the master MCU is started, the master MCU is started by reading firmware data in the Flash chip; when the slave MCU is started, the master MCU controls the slave MCU to be powered on, and the slave MCU sends a request for reading the firmware data to the master MCU; the master MCU transmits the request to the Flash chip, and transmits the firmware data returned by the Flash chip to the slave MCU, so as to start the slave MCU.