Patent Application
20100268867
Embodiments of the present invention relate to firmware update. In particular, some relate to firmware updates over the air.
Firmware over the air (FOTA) describes a procedure for remotely updating software in a memory to which the device in normal operation has read-only access and not write access. Patches to existing software or new software can be downloaded to the read-only memory of a remote device via radio communications (over the air). This enables the updating of remote devices, such as mobile cellular telephones, without the need to bring the remote device to a service centre.
The updating of software on a device using FOTA may take a considerable amount of time and the device is unavailable for use during that time. This may be frustrating to a user, particularly if they have not initiated the FOTA update.
According to one embodiment of the invention there is provided a method comprising: storing data in a first memory that includes a first portion that has read-only access during a normal mode of operation; and during a update mode of operation: copying at least one data structure from the first memory to a second memory where it is available for use during the update mode; and updating data in the first portion of the first memory.
According to another embodiment of the invention there is provided a computer program comprising computer program instructions for: changing a mode of operation of a device from a normal mode of operation in which a first portion of a first memory has read-only access to a second mode of operation in which the first portion of the memory is updatable; and, during the update mode of operation, for enabling copying of at least one data structure from a first memory to a second memory and updating of data in the first portion of the first memory.
According to another embodiment of the invention there is provided an apparatus comprising: a first memory that includes a first portion for read-only access during a normal mode of operation; a second memory for storing data for use during an update mode of operation; and an update controller arrangement for controlling the transition from the normal mode to the update mode, for enabling the transfer of data for use during the update mode from the first memory to the second memory and for enabling updating of at least a part of the first portion of the first memory during the update mode.
For a better understanding of the present invention reference will now be made by way of example only to the accompanying drawings in which:
The electronic device 10 may be any suitable electronic device that enables the update of read-only data in a memory.
The input port 14 may include a radio receiver (and possibly a radio transmitter). The update of the read-only data may be achieved by receiving an update package or packages via the radio receiver or some other interface such as a mass storage interface, for example, a secure digital memory card or similar. As a non-limiting example, the device 10 may operate as a mobile cellular telephone or a module for operation in a mobile cellular telephone network and the update package(s) would be received from the mobile cellular telephone network.
The semi-permanent memory 20 has, in this example, a read-only section 30 for storing firmware i.e. software or files that are accessible to the device 10 on a read-only basis during a normal mode of operation.
The semi-permanent memory 20 has, in this example, a read/write section 32 for storing user data including software i.e. data that is accessible for reading and for modification during a normal mode of operation.
The memory access controller 22 controls access to the semi-permanent memory 20. In particular, it controls when data can be read from the memory 20 and the portions of the memory 20 to which data may be written.
The fast access memory 16 may be a random access type memory e.g. a RAM. It is typically used to cache data read from the semi-permanent memory 20 or data for writing to the semi-permanent memory 20. Although in the illustrated example, the fast access memory 16 is connected to the memory 20 and it access controller 22 via the processor(s) 12 in other embodiments direct memory access may be used.
In one embodiment the semi-permanent memory 20 is a NAND type flash memory. NAND flash memories cannot support execute-in-place. When executing software from NAND memories, memory contents must first be paged into the fast access memory 16 and executed there. A NAND type flash memory is accessed like a hard disk. It enables the rewriting of data quickly and repeatedly.
An schematic illustration of a semi-permanent memory 20 is illustrated in
The read-only section 30 comprises one or more read-only partitions 40 and the read/write section 32 comprises one or more read/write partitions 42.
The read-only partition(s) 40, in the example illustrated, include a boot-loader 401 for loading the operating system (OS) on booting-up the device 10, the core operating system (OS) image 402, and a read-only file system (ROFS) 403 which is mapped to drive Z. The read-only partitions 40, in a normal mode of operation, can be read but cannot be modified.
The read/write partition(s) 42, in the example illustrated, include a read/write file system such as a file allocation table (FAT) system for the storage of user data.
The operating system may be a Symbian operating system.
The operation of the device 10 during an update to the semi-permanent memory 20 is illustrated in
The method 50 comprises a series of sequential blocks that may be steps in a process or code portions in a computer program, such as OS image 402 or a separate program 70.
At block 51, an update package 15 is received at input port 14
At block 52, the processor 12 detects the receipt of an update package 15 and changes the mode of the device 10 from ‘normal’ to ‘update’.
At block 53, the processor 12 informs the memory access controller 22 that the update mode has been entered.
At block 54, the memory access controller 22 copies data structures 601, 602, 603 and 604 from the memory 20 to the fast access memory 16 so that they are available for use during the update procedure. The data structures 60 may, for example, be executable files from either the read-only section 30 of the semi-permanent memory 20 or from the read/write section 32 of the semi-permanent memory 32.
The identity of some or all of the data structures which are copied may be permanently predefined or may be variably predefined or a combination of permanently and variably predefined. For example, it may be specified that the data structures for executing specified key applications must be copied. For example, a user may be able to specify applications for which the associated data structures must be copied. ‘Pre-defined’ in this context means defined before the method 50 has started rather than as a part of the method.
The identity of some or all of the data structures which are copied may be defined in dependence upon the update package 15. If the update package 15 specifies an update to particular applications then the data structures 60 for those applications may be prevented from being copied. If the update package 15 specifies a particular section of the memory 20 then the data structures 60 for applications located in that section may be prevented from being copied.
In this way, a user may have access to useful applications such as those that provide for making and/or receiving calls, sending and/or receiving messages SMS, playing music etc. This may give the impression that the firmware update occurs as a background task.
At block 55, the memory controller 22 prevents further access to parts of the memory including an update area 62 in the read-only section 30 of the memory 20 to prevent automatic loading of data to the fast access memory 16.
At block 56, the memory controller 22 enables specific read/write access to the read-only section 30 of the memory 20, at only the update area 62 defined by the update package 15, by converting the status of the update area 62 temporarily from read-only to read/write. The memory controller 22 may continue to allow read/write access to read/write section(s) 32.
At update block 57, the content of the update package (possibly after processing) is then written to the appropriate sections of the memory 20 which will include the update area 62 of the RO section(s) 30 and may include RW section(s) 32.
At block 58, the method ends by re-booting the device 10.
During the method 50, at block 54, an update application for controlling the method 50 may be copied to the fast access memory 16. The update application logs the progress of the method 50. If the method is not complete because, for example, of powering off the device, on restarting the device the boot-up starts in the update mode at the point in the method where termination occurred.
The description refers to sections, portions and partitions of the memories. It should be understood that these are typically logically divisions of a physical memory but in some embodiments may be physical divisions.
The memory 20 stores computer program instructions 70 that control the operation of the electronic device 10 when loaded into the processor 12. The computer program instructions 70 provide the logic and routines that enables the electronic device to perform the methods illustrated in
The computer program instructions may arrive at the electronic device 10 via an electromagnetic carrier signal or be copied from a physical entity 72 such as a computer program product, a memory device or a record medium such as a CD-ROM or DVD.
Although embodiments of the present invention have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the invention as claimed. For example, a system may comprise more that one subsystem, where a subsystem has its own (physically or logically) processor and firmware in one or more memories. Examples of subsystems are: telephony subsystem, modem subsystem, Bluetooth subsystem, WLAN subsystem, digital camera subsystem, RFID subsystem etc. One subsystem, such as the one illustrated in
Whilst endeavoring in the foregoing specification to draw attention to those features of the invention believed to be of particular importance it should be understood that the Applicant claims protection in respect of any patentable feature or combination of features hereinbefore referred to and/or shown in the drawings whether or not particular emphasis has been placed thereon.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/IB2006/003872 | 9/29/2006 | WO | 00 | 6/23/2010 |
