Peripheral Device Firmware Update via Segmented Memory Blocks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for updating firmware in peripheral devices are cumbersome, inconvenient, and risk rendering the device inoperable, often requiring significant user interaction and limiting mobility, with potential for permanent damage if not performed correctly.

Innovation Solution

A system and method for automatically updating firmware in peripheral devices, such as protective cases for electronic devices, using communication circuitry and processors to manage memory blocks, allowing seamless updates without requiring the device to be operated during the process and ensuring that only one memory block is updated at a time to prevent errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If conventional firmware update methods are used, then firmware can be updated, but the process is cumbersome and requires significant user interaction

Engineering Contradiction:
Improvefirmware update automationVSAvoiduser interaction requirement
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The peripheral device autonomously manages the firmware update process by detecting available updates, downloading them to a non-active memory block, verifying integrity, and automatically switching to the updated firmware without requiring user intervention. The device serves itself by monitoring its own firmware status and executing updates independently.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by downloading and verifying the firmware update image before actually installing it. The update is prepared in advance in a non-active memory block, and only after verification succeeds does the system proceed with the installation, ensuring readiness and safety before the actual update occurs.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If firmware update is performed without automation, then control over the process is maintained, but the risk of rendering the device inoperable increases

Engineering Contradiction:
Improvedevice operability during updateVSAvoidmemory block management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The firmware storage memory is segmented into multiple blocks, with at least one active memory block for current firmware execution and at least one non-active memory block for storing update images. This segmentation isolates the update process from the active execution environment, allowing updates to be prepared and verified without affecting the currently running firmware, thus maintaining device operability throughout the update process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system provides beforehand cushioning by maintaining a backup active memory block that can be quickly switched to if the update fails. The non-active memory block serves as a cushioning storage area where the update image is prepared and verified before installation, preventing potential failures from immediately rendering the device inoperable.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Productivity

If multiple memory blocks are updated simultaneously, then update speed increases, but the risk of errors and device malfunction increases

Engineering Contradiction:
Improveupdate speedVSAvoidupdate error rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The firmware storage memory is segmented into multiple blocks, with at least one active memory block for current firmware execution and at least one non-active memory block for storing update images. This segmentation isolates the update process from the active execution environment, allowing updates to be prepared and verified without affecting the currently running firmware, thus maintaining device operability throughout the update process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by downloading and verifying the firmware update image before actually installing it. The update is prepared in advance in a non-active memory block, and only after verification succeeds does the system proceed with the installation, ensuring readiness and safety before the actual update occurs.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9513900B2Peripheral device and method for updating firmware thereof
Publication Date: 2016.12.06 OTTER PRODUCTS LLC
  • US9513900B2 patent drawing
  • US9513900B2 patent drawing
  • US9513900B2 patent drawing

AI summary

A protective cover for an electronic device includes a memory configured to store at least an active firmware image and another firmware image, and circuitry configured to execute instructions provided in the firmware image. The circuitry receives commands and a firmware image included from the electronic device. The circuitry determines whether the firmware is targeted to a non-active block of the memory and if so, writes the firmware image to the non-active memory block.