US 12,217,048 B1
Separate firmware to fixed and removable storages
Lei Chang, Saratoga, CA (US); and Nicholas Cabi, San Jose, CA (US)
Assigned to Auradine, Inc., Santa Clara, CA (US)
Filed by Auradine, Inc., Santa Clara, CA (US)
Filed on Jun. 21, 2024, as Appl. No. 18/750,565.
Application 18/750,565 is a continuation of application No. 18/525,622, filed on Nov. 30, 2023, granted, now 12,026,505.
Application 18/525,622 is a continuation of application No. 18/370,192, filed on Sep. 19, 2023, granted, now 11,880,223, issued on Jan. 23, 2024.
Application 18/370,192 is a continuation of application No. 18/222,084, filed on Jul. 14, 2023, granted, now 11,797,295, issued on Oct. 24, 2023.
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 8/654 (2018.01); G06F 8/40 (2018.01)
CPC G06F 8/654 (2018.02) [G06F 8/40 (2013.01)] 21 Claims
OG exemplary drawing
 
1. A method for deploying firmware in embedded devices, comprising:
receiving, by an embedded device, an immutable firmware portion of specific firmware to be deployed with the embedded device, wherein the immutable firmware portion of the specific firmware is generated by a firmware generation system other than the embedded device from a first firmware source code portion;
receiving, by the embedded device, a mutable firmware portion of the specific firmware to be deployed with the embedded device, wherein the mutable firmware portion of the specific firmware is generated by the firmware generation system from a second firmware source code portion, wherein the first firmware source code portion and the second firmware source code portion are distinct from each other;
installing the immutable firmware portion of the specific firmware in one or more fixed storage drives of the embedded device;
installing the mutable firmware portion of the specific firmware in one or more swappable storage drives of the embedded device, wherein the one or more swappable storage derives is removably attached to the embedded device;
wherein the second firmware source code portion used for generating the mutable firmware portion is identified by the firmware generation system based at least in part on whether the mutable firmware portion generates runtime writes to persist runtime data absent from a release version of the received mutable firmware portion that is installed with the embedded device;
wherein the immutable firmware portion includes one or more executable files for kernel, loader and other embedded system services; wherein the mutable firmware portion includes one or more executable files for one or more embedded applications.