Partitioned Memory Firmware for Independent Diagnostic Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional memory systems, updating diagnostic firmware requires updating the entire firmware, which is costly and time-consuming, especially in industries like military, satellite, and automotive where firmware verification is extensive.
Innovation Solution
The firmware is partitioned into core firmware and diagnostic firmware, with each stored in separate slots, allowing only one to be active at a time. This enables updates to diagnostic firmware without affecting the core firmware, thus reducing verification costs and ensuring safety and reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the entire firmware is updated to improve diagnostic capabilities, then the diagnostic functionality is improved, but the verification cost and time increase significantly
Solution Approach 1:
The firmware is segmented into two independent parts: core firmware and diagnostic firmware. Each part can be updated separately, allowing diagnostic capabilities to be improved without requiring verification of the entire firmware. This segmentation enables independent update cycles for different firmware components, significantly reducing verification time and cost.
Solution Approach 2:
The diagnostic firmware is extracted as a separate, independent component from the core firmware. This extracted diagnostic firmware can be updated, tested, and verified independently, removing it from the costly and time-consuming entire-firmware verification process while maintaining its functionality within the memory subsystem.
2Adaptability or versatility
If the entire firmware is updated to improve diagnostic capabilities, then the diagnostic functionality is improved, but the reliability risk increases
Solution Approach 1:
Segmenting firmware into core and diagnostic parts isolates the risk of updates. Changes to diagnostic firmware cannot affect core firmware reliability, as they are independent. This segmentation ensures that even if diagnostic firmware updates introduce issues, the core firmware remains unaffected and reliable.
Solution Approach 2:
The system prepares for potential update risks by maintaining separate firmware slots and enabling independent verification. This beforehand preparation allows the system to cushion against reliability risks by preventing faulty diagnostic updates from compromising core firmware functionality.
3Adaptability or versatility
If the entire firmware is updated to improve diagnostic capabilities, then the diagnostic functionality is improved, but the manufacturing cost increases
Solution Approach 1:
Segmenting firmware into independent core and diagnostic components allows separate manufacturing and verification processes. Diagnostic firmware can be manufactured and verified independently at lower cost, without requiring the expensive and time-consuming entire-firmware verification process.
Solution Approach 2:
Instead of performing complete firmware verification (excessive action), the system performs only the necessary partial verification on the diagnostic firmware component alone. This partial action approach reduces manufacturing costs while still ensuring diagnostic functionality integrity.
Data Source
AI summary
Methods, systems, and apparatuses include receiving, by a memory subsystem, an activate command for firmware of the memory subsystem, where the firmware includes a core firmware subportion and a diagnostic firmware subportion, content of the diagnostic firmware subportion differs from content of the core firmware subportion, and the diagnostic firmware subportion and the core firmware subportion execute independently of one another. The core firmware subportion is activated causing the memory subsystem to operate using the core firmware subportion in response to the received activate command. The diagnostic firmware subportion is deactivated preventing the memory subsystem from operating using the diagnostic firmware subportion in response to the received activate command.


