Secure Boot Storage Device Architecture for Fast Firmware Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing complexity of operating systems in electronic devices leads to excessive boot time due to the need to execute kernel and OS, which is exacerbated by the traditional method of reading the OS from a disk, resulting in inefficiencies in modern devices like smartphones and PDAs.
Innovation Solution
A semiconductor memory system with a storage device architecture that includes a host device and a storage device, utilizing a memory controller, OTP memory, boot ROM, and separate memory areas for secure booting and firmware updates, allowing for secure and efficient booting and firmware updates without relying on disk reads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the operating system is stored on a separate chip and equipped in the electronic device, then boot time is reduced, but device complexity increases
Solution Approach 1:
The patent divides the storage system into separate components: a first storage area (secure boot ROM) for storing boot code and a second storage area for storing the operating system. This segmentation allows the boot code to be executed from a dedicated secure area, reducing boot time while maintaining security. The boot ROM contains only essential boot code, separating it from the full OS, which resolves the contradiction by optimizing boot performance without significantly increasing overall device complexity.
2Adaptability or versatility
If firmware update is performed by reading from disk, then update capability is provided, but boot time increases and security is compromised
Solution Approach 1:
The patent implements preliminary action by pre-storing multiple firmware versions and their corresponding signatures in the first storage area before booting. The boot code retrieves and validates the appropriate firmware version during the boot process itself, rather than reading from disk after booting. This preliminary preparation enables fast firmware updates without increasing boot time, as the updated firmware is already available in the secure boot storage area.
Solution Approach 2:
The patent introduces an intermediary mechanism through the use of digital signatures and verification code. The boot code acts as an intermediary that validates firmware authenticity before execution, using cryptographic signatures stored in the secure boot ROM. This intermediary verification layer enables secure firmware updates from the first storage area without compromising security, while avoiding the need to read from slower disk storage during boot.
3Reliability
If secure booting is implemented with verification code, then security is enhanced, but device complexity increases
Solution Approach 1:
The patent merges the verification code and digital signature validation functionality directly into the boot code itself, which is stored in the secure boot ROM. Rather than adding separate verification modules, the security functions are integrated into the existing boot code structure. This merging approach enhances security through cryptographic verification while minimizing additional device complexity, as the security mechanisms are embedded within the already-necessary boot code.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A storage device is provided. The storage device includes a boot ROM that stores a plurality of public keys and a boot ROM image, an OTP memory that identifies a first public key among the plurality of public keys, a first memory including a first area that stores the plurality of public keys and a flash boot image different from the boot ROM image, and a second area that stores a first boot signature corresponding to the flash boot image, a second memory including a first firmware image including a first firmware signature, and a memory controller that receives a second firmware image including a second firmware signature and a second boot signature, receives a second public key among the plurality of public keys and the flash boot image based on the second firmware image being received, and writes the second boot signature in the second area of the first memory.