CA2307908A1 - A method and apparatus for downloading software into an embedded-system - Google Patents
A method and apparatus for downloading software into an embedded-system Download PDFInfo
- Publication number
- CA2307908A1 CA2307908A1 CA002307908A CA2307908A CA2307908A1 CA 2307908 A1 CA2307908 A1 CA 2307908A1 CA 002307908 A CA002307908 A CA 002307908A CA 2307908 A CA2307908 A CA 2307908A CA 2307908 A1 CA2307908 A1 CA 2307908A1
- Authority
- CA
- Canada
- Prior art keywords
- initialization
- memory
- embedded system
- data
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
Abstract
Metliod for upgrading operating software and/or initialization program versions of an embedded system by using a single non-volatile memory.
The non-volatile memory comprises a write-protected area containing an original initialization and download operation program version, and an unprotected area containing an upgradable initialization and download operation program version. Upon initialization, the upgradable, or the original version, of the initialization and download operation program version is copied into a second memory and/or into a memory location. The embedded system is operated from the second memory and/or memory location, enabling the downloading of the new operating software and/or initialization program versions and programming the unprotected area with the downloaded versions.
The non-volatile memory comprises a write-protected area containing an original initialization and download operation program version, and an unprotected area containing an upgradable initialization and download operation program version. Upon initialization, the upgradable, or the original version, of the initialization and download operation program version is copied into a second memory and/or into a memory location. The embedded system is operated from the second memory and/or memory location, enabling the downloading of the new operating software and/or initialization program versions and programming the unprotected area with the downloaded versions.
Description
~ 5856/US/99 A METHOD AND APPARATUS FOR DOWNLOADING SOFTWARE
INTO AN EMBEDDED-SYSTEM
Field of the Invention The present invention relates to the field of embedded systems. More particularly, the invention relates to an effective method and apparatus for upgrading software versions which are used to control the operation of embedded systems, by downloading new software versions, on-board and using a fail-safe procedure, into a single non-volatile memory of an embedded system.
Background of the Invention Embedded systems are widely used in industry and in office and consumer products. Actually, embedded systems include almost any device, which employs a microprocessor and/or a microcontroller and is not directed only to general-purpose computation. The control system is "embedded" into the device and is an integral part of it. Such devices are used to control, monitor or assist the operation of machinery and equipment of many types. For example, telephones, and many other electronic devices are operated and controlled by a firmware, which is a specific software that is stored in (or "burned" into) a memory of the electronic device, and is constantly called by a controller and/ or a processing unit which normally operates the device.
In many devices, the firmware is linked to a database, which is also stored in the same or in another memory, and contains necessary information, required for proper operation of the device. Normally, the device contains a specific Printed Circuit Board (PCB), on which the controller or the processing unit, and the required linked memories are assembled (normally soldered). This PCB structure is widely used, since it saves space and is cost effective in mass-production. Original versions of the ssssiusiss ._ - 2 -firmware and the contents of the database, are initially downloaded into the memory of the device by the manufacturer, before delivery to the customer, and in conjunction with a processor or a controller, serve as an operating system of the device.
In many cases, improvements in the features of the device are desired as time progresses, due to customer demands, and new features are offered by the manufacturer who continues with research and development activity in order to improve the capability of the device. Such improvements may be implemented by upgrading the firmware and/or the contents of the database in the device, from time to time, with a new version. This upgrade requires downloading of the new version, and overwriting (programming) the memory cells which contain the preceding firmware and database version. Upgrading may be carried out in the field, by a technician, or by a data source such as a Personal Computer (PC), via a data communication link which is connected to the device, so as to eliminate the need of returning the device to the manufacturer for upgrading. In addition, it is highly desired to enable an on-board upgrade, i.e., to eliminate disassembly of the upgradeable components (e.g. memory devices) from the PCB.
Most of the embedded systems employ an initialization process, known as a "boot" operation, in which a basic software or specific instructions are loaded from a boot sector (a sector represents a unit of storage space) of a memory, until the system is brought into its normal operation mode.
Booting capability should be sustained even when the download process has failed, or the downloaded firmware version is corrupted for any reason, so as to enable another download and programming process.
Therefore, boot instructions should be stored and recovered safely whenever a failure in the downloading or the programming process occurs.
A typical known solution is to store the boot instructions in a Read Only 585s/US/99 Memory (R,OM), which is non-volatile (i.e., it retains its stored data with no need for power supply) and is write protected. However, even though a ROM has a relatively high density, it is not upgradeable and should be operated with additional reprogrammable non-volatile memories to enable the stored firmware version to be overwritten. Therefore, this solution is not flexible or cost effective since more than one non-volatile memory is required, which also consumes precious PCB area and the boot sector can not be upgraded. Moreover, initial programming of a ROM is relatively time consuming, and is cost-effective mostly in mass production.
US Patent 5,666,293 discloses a method for upgrading the operating system software of terminal devices by downloading new versions through a broadcast channel. Upgrading is carried out by performing a cyclic broadcast of a packetized data file, which contains the operating system, which is captured and stored by the terminal devices. However, the operating system upgrade routine is stored in a ROM which is operated alone or with combination with a write protected sector of a Non-Volatile Random Access Memory (T~J~RAM). In addition, booting up the operating system, which is stored in the NVRAM, is carried out by a loader program, which is stored in a ROM and is not upgradeable.
US Patent 5,647,986 discloses an automated apparatus for wastewater treatment, which is controlled by a controller. The controller includes a combination of a flash memory and a boot memory, with remote programming capability. The flash memory stores the operating program of the apparatus and the boot memory contains a boot code, which is required to handle basic communication and reprogramming of the flash memory. The controller establishes a connection with a central computer from which a new operating program is downloaded, and receives a command to erase the contents of the flash memory. After the contents of the latter have been erased, the controller begins to reprogram the flash memory with data that is transmitted from the central computer. After the programming is completed, the controller reboots the processing unit of the apparatus and the apparatus starts to operate according to the updated operating program. However, this apparatus has no backup or reboot capability in the event of a failure during download and/or programming process and requires a separate non-upgradable boot memory.
The art has not yet provided satisfactory solutions to the problem of on-board downloading new software and boot versions into a single non-volatile memory of an embedded system, using a fail-safe procedure, that also allows for upgrading of the download control program.
It is an object of the present invention to provide a method and apparatus for downloading new software and boot versions into the memory of an embedded system, using a fail-safe procedure.
It is another object of the present invention to provide a method and apparatus for downloading new software and boot versions into the memory of an embedded system, which is carried out on-board and in the field.
It is a further object of the present invention to provide a method and apparatus for ,downloading new software and boot versions into the memory of an embedded system, which employs a single non-volatile memory component.
Other objects and advantages of the invention will become apparent as the description proceeds.
w CA 02307908 2000-OS-09 Summary of the Invention The invention is directed to a method for field upgrading of an operating software and/or initialization program version of an embedded-system. A
single non-volatile memory component, such as a flash memory, is divided into a write-protected area and an unprotected area. The unprotected area is used to store downloaded software versions. The hardware write protected area in the flash memory is used to store an original version of the initialization and download program, and may be programmed only by relatively high voltage which is not available in the field. The original protected initialization and download program functions as a backup program, which is used to perform a new downloading process whenever a current downloading process fails. The write-protected area eliminates the need for additional non-volatile memory, such as a ROM.
Preferably, the last valid version of the initialization and download program, which is stored in the flash memory, is copied into a volatile memory, such as a RAM, and the embedded-system is operated from the RAM. This enables the downloading process of a new initialization program and operating software version during normal operation of the embedded-system. Preferably, at the initialization process, the initialization and download program is copied into the RAM and the embedded-system is operated from the RAM to perform initialization and downloading functions, if desired. Alternatively, all or part of the system functions may . be duplicated and operated from the RAM to allow additional functionality during the upgrade process.
Downloading is carried out via a data receiving input into the embedded-system. The downloaded data is verified and if found valid, is programmed into the unprotected area of the flash memory. Alternatively, in order to be upgraded, the flash memory may first be erased, and the data is stored directly into the unprotected area of the flash memory. If a downloading process is disrupted by an unrecoverable error, it may be completed after activating the original initialization process from the write protected areas of the flash memory, or an updated initialization process from the unprotected areas of the flash memory. The downloading and programming process is restarted from the beginning, or alternatively continued from the detection point of tIze data error. After programming, the system is rebooted and the updated initialization process stored in the unprotected area of the flash memory is activated, copied into the RAM
and the embedded-system is operated by the new operating software version. Alternatively, all or part of the operating software may be copied into, and subsequently run from, the RAM.
Preferably, downloading of a new version is carried out in the field by a data source, such as a PC, which is connected to the data receiving input of the embedded system, or from a remote data source by transmitting data groups from the remote source over a data link into the data receiving input of the embedded system.
The invention is also directed to an embedded system having in field and on-board upgrading capability of its operating software and/or initialization program version without affecting its normal operation. The embedded system comprises - a single non-volatile memory component containing a write protected area for storing an original initialization and download program of the embedded system and an unprotected area for storing at least updated version of the initialization and download program;
- a volatile memory for storing initialization programs and/or operating software versions of the embedded-system, which enables simultaneous operation and reprogramming of new versions;
- a control circuitry for controlling the initialization process and the operation of the embedded-system, for copying the contents of the non-. 5856/US/99 volatile memory into the volatile memory and for downloading, verifying and programming new versions of said operating software and/or said initialization program; and - a data receiving input for downloading software and/or said initialization program versions.
Brief Description of the Drawings The above and other characteristics and advantages of the invention will be better understood through the following illustrative and non-limitative detailed description of preferred embodiments thereof, with reference to the appended drawings, wherein:
- Fig. 1 is a block diagram of a software upgradable embedded system with a single non-volatile memory, according to a preferred embodiment of the invention;
- Fig. 2 schematically illustrates the memory arrangement of the embedded system of Fig. 1, according to a preferred embodiment of the invention;
- Fig. 3 is a flow chart of the status word of a non-volatile memory system, according to a preferred embodiment of the invention; and - Fig. 4 is a flow chart of the embedded-system operation, according to a preferred embodiment of the invention.
Detailed Description of Preferred Embodiments Fig. 1 is a block diagram of a software upgradable embedded system with a single non-volatile memory component, according to a preferred embodiment of the invention. The embedded system 10 is controlled by a controller 11, which is linked to a flash memory 12 and a Random Access Memory (R.AM) 13 and operates the system functions according to an operating software which is stored in the flash memory 12. The flash memory 12 is the only non-volatile memory which is required for storing the operating software and/or other desired instructions. The RAM 13 is a _g_ volatile memory which is used for temporary storage of the initialization and download program, and enables the controller 11 to operate the system 10 during download mode, using the latest software version which is copied from the flash memory 12 into the RAM 13, each time the system is initialized. In an alternative embodiment, some or all of the operating program may also be copied into RAM 13 so as to allow additional functionality during the download process. For example, in a smart telephone, part of the telephone operating control program that allows for dialing, ringing type of the phone for incoming calls, and other basic functions may be copied into RAM 13, allowing this functionality during a download. It is also possible to copy the entire operating program into RAM 13, allowing for complete operation during a download, in which case all software will be run from the RAM. The main advantage of a flash memory is that it is a non-volatile high-density device, whose contents can be easily modified "in-system", i.e., without the need for disassembly.
System 10 is connected to a data source via a communication link 14, through which new program versions may be downloaded into the flash memory 12 and/or the RAM 13. The controller 11 controls data flow.
Therefore, downloading and programming of a new software and firmware version into system 10 may be carried out via the link 14, typically by connecting a programming device (e.g., a computer) to the link 14. Thus, upgrades can be carried out in the field, and distributed on CD-ROMs or over the Internet. For example, system 10 may be a smart telephone, which may be programmed by downloading new software versions from an attached PC, via a serial (e.g., an RS-232) connection, which serves as the data communication link 14. During normal operation of the system 10, each time when the system 10 is turned on, a boot process is started according to instruction which are stored in the flash memory 12 and copied into the R,AM 13. After the boot process, the system 10 is brought to its normal operation mode and the controller 11 controls the system ssssiusis9 functions, following the program stored in RAM 13 and/or flash memory 12. Normally, the original (first) software version is programmed into the flash memory 12 by the manufacturer, and is updated from time to time by updating in the field new (and advanced) versions which improve the functionality of the system 10 and/or offers new features to the user.
However, for several reasons, sometimes the downloading process disrupted, or a part of the new software version is corrupted (e.g., due to unrecoverable errors which occur during the data transfer through the communication link 14). Since downloading and programming involve data erasing of the preceding software version from the memory, a situation where the flash memory contains only the corrupted or incomplete software version should be eliminated. It is therefore extremely important to keep the boot procedure protected and available for reuse, so as to enable a new boot process and a following downloading and programming operation. In another preferred embodiment, it is desireable to provide a memory arrangement which simultaneously enables the system 10 to operate at some level of functionality according to the current software version, and to program the system 10 with a new software version (i.e., the operation of the system 10 is not completely stopped while programming it with the new software version). RAM 13 is used to store part or the entire current software version required for operation, while the flash memory 12 is programmed. At a minimum, RAM 13 is used to store and operate the downloading program. In addition, it is . desired to allow upgrading of the boot and download procedures themselves. Current flash memory technology does not allow for the same memory component to be simultaneously accessed while being programmed in any sector.
Fig. 2 schematically illustrates the memory arrangement of the embedded system of Fig. 1, according to a preferred embodiment of the invention.
The storage space of the flash memory 12 is divided into a plurality of ssssivsis9 - to -sectors, also known as segments (minimum three sectors). Two sectors are used to store the boot program, and the other sectors are used to store the current version of the operation software, which may have been upgraded by a download operation. One boot sector 20 in the flash memory contains the original boot program as programmed by the manufacturer, and is hardware protected. The hardware protection may be accomplished, for example, by requiring a relatively high voltage, which is not available in the field to enable a write function. As a result, the system 10 has a protected boot sector that can not be upgraded in the field. The other boot sector 21, which is not write protected, is also initially programmed with the original boot program, and may be upgraded with new versions. A flag, appended at the end of the sector, is used as a status flag for each accessible sector 21 and 22 of the flash memory 12. Referring to Fig. 3, we find a state diagram of the status flag. The flag is programmed at the factory in the "valid" state. The first step in the update process involves resetting this flag to "erase process". Once this is set, the update process can begin, which entails erasing the current program. After the erase procedure is completed the flag is reset to the "erased" state. After a sector is programmed, and verified, the flag is again restored to the "valid" state.
During the download process, a CRC (Cyclic Redundancy Code) is appended by the remote data source (of new software/boot versions) to each block of data that is transmitted to the system 10 over the link 14.
The controller 11 applies the same CRC calculation to the received data and compares the result, which has been appended to the data block before transmission. If the results agree, it is an indication that the data block has been received successfully, i.e., without data errors, and is a correct copy. If the results do not agree, a request is transmitted over the communication line 14 to resend the data block and the block is then resent by the remote data source. This procedure is well known to a person who is skilled in the art. Once a logical sector has been properly received, b8b6/US/99 as indicated by a valid CRC code, the sector is programmed by the upgrade program being run. The data is then read from the stored sector, and again confirmed, following which the status flag at the end of the sector is set to "valid".
According to a preferred embodiment ofthe invention, this dual boot sector arrangement (of a write protected and an accessible sectors) in the flash memory 12 enables reboot operation whenever the downloading process is disrupted, by using the original boot program, stored in the write protected boot sector 20, or an updated boot program, using the contents of accessible boot sector 21 if a correct copy exists, as indicated by the status flag. If the flag is valid, the updated boot program is copied into a memory segment 23 (a boot segment) in the RAM 13, which is used to boot the system 10 whenever the system is restarted, such as after downloading and programming of the flash memory 12. If the flag of boot sector 21 was not valid, then the original, hardware protected version of the boot program is copied into memory segment 23. The RAM 13 comprises additional segments 24, into which downloaded data blocks may be copied for.temporary storage, if desired. The system 10 is operated and controlled by the controller 11 by using the (copied) boot program which is stored in the RAM 13 and the software which is stored in the flash memory 12.
Thus, whenever the system starts up, on of the two boot segments, 20 or 21, is copied into segment 23 in the RAM 13. The program is thus always operated from the same address space, irrespective of which code versions are used.
Fig. 4 is a flow chart of the embedded-system operation, according to a preferred embodiment of the invention. The program starts from sector 20 of the flash memory. At the first step 401, the validity of the software stored in sector 21 is checked, by checking its status flag, which is stored at the end in the same sector. If found valid, at the next step 402, the ssss~rsiss content of sector 21 is copied into segment 23 in the RAM 13. If found invalid, at the next step 403, the content of segment 20 is copied into sector 23 in the RAM 13. At the next step 404, the operating address of the controller 11 is transferred to (operate from) sector 23. The program, which is copied into sector 23, at least allows the controller 11 to operate the downlink 14 and to update the flashmemory 12.
According to another preferred embodiment of the invention, one or more sectors 22 of the flash memory 12 are also copied into the RAM 13. In this case, the controller 11 operates that section of the program from the RAM
13, rather than from the flash memory 12. This allows additional functionality during downloading, since the program can not run from same addresses, being updated. In current practice, during updating, software can not be run from the flash memory 12 at all, and therefore, only software copied into RAM 13 is functional.
Sectors 22 in the flash memory 12, together with the boot sector 23 in the RAM 13 are used to generate a software version. The original software version is programmed into the sectors 22 of the hash memory by the manufacturer. During operation, if the last version of the boot program (the original boot program in the first operation) is found to be valid, it is copied from the unprotected boot sector 21 into the boot segment 23, and the last software version (the original software version in the first operation) is used from sectors 22 to allow the controller 11 to operate the system 10 from the RAM 13, and the flash memory 12.
The boot program may also be updated by transmitting a new boot data block and programming the unprotected boot sector 21 with the received boot data block. The protected boot sector 20 contains the original boot program as a backup. When the system 10 initializes, the controller 11 selects the boot program which is used for initialization by first checking the validity of the last boot program version which is stored in the boot sector 21. If the status code of the received (new) boot data block is found valid, the last boot program is copied from sector 21 into the boot segment 23 of the R,AM 13, and the initialization process continues from the RAM
13 according to the last (updated) boot program version. If the status code of sector 21, indicates that the received (new) boot data block is not valid, the original boot program is copied from sector 20 into the boot segment 23 of the RAM 13, and the initialization process continues from the RAM 13 according to the original boot program version, and a new downloading and programming process is enabled. Therefore, by using dual boot sectors in the flash memory 12, the downloading and programming process is fail-safe. According to a preferred embodiment of the invention, if the status code of sector 21 indicates that the received (new) boot data block is not valid, in addition to copying the original boot program from sector 20 into the boot sector 23 of the RAM 13, additional logical segments from sectors 22 are copied into RAM 24 to allow for additional functionality. Each sector is only loaded if it's status word indicates that it is valid. The operating program must be so designed so as to allow independent functionality from each logical segment, so that some additional valid segments will be able to operate in the absence of others that are not valid.
According to a preferred embodiment of the invention, the downloading and programming operations which are described above, and are carried out by transmitting updated data blocks from a remote source over the communication link, may also be carried out similarly in the field and on-board, by a technician or a user who connects the data source, such as a PC, to a suitable input in the system 10 or to the data link input (e.g., a serial RS-232 port).
The above examples and description have of course been provided only for the purpose of illustrations, and are not intended to limit the invention in any vvay. As will be appreciated by the skilled person, the invention can be carried out in a great variety of ways, using a micro-controller or a microprocessor to control the operation of the embedded system, employing more than one technique from those described above, such as using a wireless data communication link for downloading upgraded software versions, implementing the embedded system on a monolithic circuitry, using other volatile and non-volatile memory types, other than a flash memory and/or a RAM, all without exceeding the scope of the invention.
INTO AN EMBEDDED-SYSTEM
Field of the Invention The present invention relates to the field of embedded systems. More particularly, the invention relates to an effective method and apparatus for upgrading software versions which are used to control the operation of embedded systems, by downloading new software versions, on-board and using a fail-safe procedure, into a single non-volatile memory of an embedded system.
Background of the Invention Embedded systems are widely used in industry and in office and consumer products. Actually, embedded systems include almost any device, which employs a microprocessor and/or a microcontroller and is not directed only to general-purpose computation. The control system is "embedded" into the device and is an integral part of it. Such devices are used to control, monitor or assist the operation of machinery and equipment of many types. For example, telephones, and many other electronic devices are operated and controlled by a firmware, which is a specific software that is stored in (or "burned" into) a memory of the electronic device, and is constantly called by a controller and/ or a processing unit which normally operates the device.
In many devices, the firmware is linked to a database, which is also stored in the same or in another memory, and contains necessary information, required for proper operation of the device. Normally, the device contains a specific Printed Circuit Board (PCB), on which the controller or the processing unit, and the required linked memories are assembled (normally soldered). This PCB structure is widely used, since it saves space and is cost effective in mass-production. Original versions of the ssssiusiss ._ - 2 -firmware and the contents of the database, are initially downloaded into the memory of the device by the manufacturer, before delivery to the customer, and in conjunction with a processor or a controller, serve as an operating system of the device.
In many cases, improvements in the features of the device are desired as time progresses, due to customer demands, and new features are offered by the manufacturer who continues with research and development activity in order to improve the capability of the device. Such improvements may be implemented by upgrading the firmware and/or the contents of the database in the device, from time to time, with a new version. This upgrade requires downloading of the new version, and overwriting (programming) the memory cells which contain the preceding firmware and database version. Upgrading may be carried out in the field, by a technician, or by a data source such as a Personal Computer (PC), via a data communication link which is connected to the device, so as to eliminate the need of returning the device to the manufacturer for upgrading. In addition, it is highly desired to enable an on-board upgrade, i.e., to eliminate disassembly of the upgradeable components (e.g. memory devices) from the PCB.
Most of the embedded systems employ an initialization process, known as a "boot" operation, in which a basic software or specific instructions are loaded from a boot sector (a sector represents a unit of storage space) of a memory, until the system is brought into its normal operation mode.
Booting capability should be sustained even when the download process has failed, or the downloaded firmware version is corrupted for any reason, so as to enable another download and programming process.
Therefore, boot instructions should be stored and recovered safely whenever a failure in the downloading or the programming process occurs.
A typical known solution is to store the boot instructions in a Read Only 585s/US/99 Memory (R,OM), which is non-volatile (i.e., it retains its stored data with no need for power supply) and is write protected. However, even though a ROM has a relatively high density, it is not upgradeable and should be operated with additional reprogrammable non-volatile memories to enable the stored firmware version to be overwritten. Therefore, this solution is not flexible or cost effective since more than one non-volatile memory is required, which also consumes precious PCB area and the boot sector can not be upgraded. Moreover, initial programming of a ROM is relatively time consuming, and is cost-effective mostly in mass production.
US Patent 5,666,293 discloses a method for upgrading the operating system software of terminal devices by downloading new versions through a broadcast channel. Upgrading is carried out by performing a cyclic broadcast of a packetized data file, which contains the operating system, which is captured and stored by the terminal devices. However, the operating system upgrade routine is stored in a ROM which is operated alone or with combination with a write protected sector of a Non-Volatile Random Access Memory (T~J~RAM). In addition, booting up the operating system, which is stored in the NVRAM, is carried out by a loader program, which is stored in a ROM and is not upgradeable.
US Patent 5,647,986 discloses an automated apparatus for wastewater treatment, which is controlled by a controller. The controller includes a combination of a flash memory and a boot memory, with remote programming capability. The flash memory stores the operating program of the apparatus and the boot memory contains a boot code, which is required to handle basic communication and reprogramming of the flash memory. The controller establishes a connection with a central computer from which a new operating program is downloaded, and receives a command to erase the contents of the flash memory. After the contents of the latter have been erased, the controller begins to reprogram the flash memory with data that is transmitted from the central computer. After the programming is completed, the controller reboots the processing unit of the apparatus and the apparatus starts to operate according to the updated operating program. However, this apparatus has no backup or reboot capability in the event of a failure during download and/or programming process and requires a separate non-upgradable boot memory.
The art has not yet provided satisfactory solutions to the problem of on-board downloading new software and boot versions into a single non-volatile memory of an embedded system, using a fail-safe procedure, that also allows for upgrading of the download control program.
It is an object of the present invention to provide a method and apparatus for downloading new software and boot versions into the memory of an embedded system, using a fail-safe procedure.
It is another object of the present invention to provide a method and apparatus for downloading new software and boot versions into the memory of an embedded system, which is carried out on-board and in the field.
It is a further object of the present invention to provide a method and apparatus for ,downloading new software and boot versions into the memory of an embedded system, which employs a single non-volatile memory component.
Other objects and advantages of the invention will become apparent as the description proceeds.
w CA 02307908 2000-OS-09 Summary of the Invention The invention is directed to a method for field upgrading of an operating software and/or initialization program version of an embedded-system. A
single non-volatile memory component, such as a flash memory, is divided into a write-protected area and an unprotected area. The unprotected area is used to store downloaded software versions. The hardware write protected area in the flash memory is used to store an original version of the initialization and download program, and may be programmed only by relatively high voltage which is not available in the field. The original protected initialization and download program functions as a backup program, which is used to perform a new downloading process whenever a current downloading process fails. The write-protected area eliminates the need for additional non-volatile memory, such as a ROM.
Preferably, the last valid version of the initialization and download program, which is stored in the flash memory, is copied into a volatile memory, such as a RAM, and the embedded-system is operated from the RAM. This enables the downloading process of a new initialization program and operating software version during normal operation of the embedded-system. Preferably, at the initialization process, the initialization and download program is copied into the RAM and the embedded-system is operated from the RAM to perform initialization and downloading functions, if desired. Alternatively, all or part of the system functions may . be duplicated and operated from the RAM to allow additional functionality during the upgrade process.
Downloading is carried out via a data receiving input into the embedded-system. The downloaded data is verified and if found valid, is programmed into the unprotected area of the flash memory. Alternatively, in order to be upgraded, the flash memory may first be erased, and the data is stored directly into the unprotected area of the flash memory. If a downloading process is disrupted by an unrecoverable error, it may be completed after activating the original initialization process from the write protected areas of the flash memory, or an updated initialization process from the unprotected areas of the flash memory. The downloading and programming process is restarted from the beginning, or alternatively continued from the detection point of tIze data error. After programming, the system is rebooted and the updated initialization process stored in the unprotected area of the flash memory is activated, copied into the RAM
and the embedded-system is operated by the new operating software version. Alternatively, all or part of the operating software may be copied into, and subsequently run from, the RAM.
Preferably, downloading of a new version is carried out in the field by a data source, such as a PC, which is connected to the data receiving input of the embedded system, or from a remote data source by transmitting data groups from the remote source over a data link into the data receiving input of the embedded system.
The invention is also directed to an embedded system having in field and on-board upgrading capability of its operating software and/or initialization program version without affecting its normal operation. The embedded system comprises - a single non-volatile memory component containing a write protected area for storing an original initialization and download program of the embedded system and an unprotected area for storing at least updated version of the initialization and download program;
- a volatile memory for storing initialization programs and/or operating software versions of the embedded-system, which enables simultaneous operation and reprogramming of new versions;
- a control circuitry for controlling the initialization process and the operation of the embedded-system, for copying the contents of the non-. 5856/US/99 volatile memory into the volatile memory and for downloading, verifying and programming new versions of said operating software and/or said initialization program; and - a data receiving input for downloading software and/or said initialization program versions.
Brief Description of the Drawings The above and other characteristics and advantages of the invention will be better understood through the following illustrative and non-limitative detailed description of preferred embodiments thereof, with reference to the appended drawings, wherein:
- Fig. 1 is a block diagram of a software upgradable embedded system with a single non-volatile memory, according to a preferred embodiment of the invention;
- Fig. 2 schematically illustrates the memory arrangement of the embedded system of Fig. 1, according to a preferred embodiment of the invention;
- Fig. 3 is a flow chart of the status word of a non-volatile memory system, according to a preferred embodiment of the invention; and - Fig. 4 is a flow chart of the embedded-system operation, according to a preferred embodiment of the invention.
Detailed Description of Preferred Embodiments Fig. 1 is a block diagram of a software upgradable embedded system with a single non-volatile memory component, according to a preferred embodiment of the invention. The embedded system 10 is controlled by a controller 11, which is linked to a flash memory 12 and a Random Access Memory (R.AM) 13 and operates the system functions according to an operating software which is stored in the flash memory 12. The flash memory 12 is the only non-volatile memory which is required for storing the operating software and/or other desired instructions. The RAM 13 is a _g_ volatile memory which is used for temporary storage of the initialization and download program, and enables the controller 11 to operate the system 10 during download mode, using the latest software version which is copied from the flash memory 12 into the RAM 13, each time the system is initialized. In an alternative embodiment, some or all of the operating program may also be copied into RAM 13 so as to allow additional functionality during the download process. For example, in a smart telephone, part of the telephone operating control program that allows for dialing, ringing type of the phone for incoming calls, and other basic functions may be copied into RAM 13, allowing this functionality during a download. It is also possible to copy the entire operating program into RAM 13, allowing for complete operation during a download, in which case all software will be run from the RAM. The main advantage of a flash memory is that it is a non-volatile high-density device, whose contents can be easily modified "in-system", i.e., without the need for disassembly.
System 10 is connected to a data source via a communication link 14, through which new program versions may be downloaded into the flash memory 12 and/or the RAM 13. The controller 11 controls data flow.
Therefore, downloading and programming of a new software and firmware version into system 10 may be carried out via the link 14, typically by connecting a programming device (e.g., a computer) to the link 14. Thus, upgrades can be carried out in the field, and distributed on CD-ROMs or over the Internet. For example, system 10 may be a smart telephone, which may be programmed by downloading new software versions from an attached PC, via a serial (e.g., an RS-232) connection, which serves as the data communication link 14. During normal operation of the system 10, each time when the system 10 is turned on, a boot process is started according to instruction which are stored in the flash memory 12 and copied into the R,AM 13. After the boot process, the system 10 is brought to its normal operation mode and the controller 11 controls the system ssssiusis9 functions, following the program stored in RAM 13 and/or flash memory 12. Normally, the original (first) software version is programmed into the flash memory 12 by the manufacturer, and is updated from time to time by updating in the field new (and advanced) versions which improve the functionality of the system 10 and/or offers new features to the user.
However, for several reasons, sometimes the downloading process disrupted, or a part of the new software version is corrupted (e.g., due to unrecoverable errors which occur during the data transfer through the communication link 14). Since downloading and programming involve data erasing of the preceding software version from the memory, a situation where the flash memory contains only the corrupted or incomplete software version should be eliminated. It is therefore extremely important to keep the boot procedure protected and available for reuse, so as to enable a new boot process and a following downloading and programming operation. In another preferred embodiment, it is desireable to provide a memory arrangement which simultaneously enables the system 10 to operate at some level of functionality according to the current software version, and to program the system 10 with a new software version (i.e., the operation of the system 10 is not completely stopped while programming it with the new software version). RAM 13 is used to store part or the entire current software version required for operation, while the flash memory 12 is programmed. At a minimum, RAM 13 is used to store and operate the downloading program. In addition, it is . desired to allow upgrading of the boot and download procedures themselves. Current flash memory technology does not allow for the same memory component to be simultaneously accessed while being programmed in any sector.
Fig. 2 schematically illustrates the memory arrangement of the embedded system of Fig. 1, according to a preferred embodiment of the invention.
The storage space of the flash memory 12 is divided into a plurality of ssssivsis9 - to -sectors, also known as segments (minimum three sectors). Two sectors are used to store the boot program, and the other sectors are used to store the current version of the operation software, which may have been upgraded by a download operation. One boot sector 20 in the flash memory contains the original boot program as programmed by the manufacturer, and is hardware protected. The hardware protection may be accomplished, for example, by requiring a relatively high voltage, which is not available in the field to enable a write function. As a result, the system 10 has a protected boot sector that can not be upgraded in the field. The other boot sector 21, which is not write protected, is also initially programmed with the original boot program, and may be upgraded with new versions. A flag, appended at the end of the sector, is used as a status flag for each accessible sector 21 and 22 of the flash memory 12. Referring to Fig. 3, we find a state diagram of the status flag. The flag is programmed at the factory in the "valid" state. The first step in the update process involves resetting this flag to "erase process". Once this is set, the update process can begin, which entails erasing the current program. After the erase procedure is completed the flag is reset to the "erased" state. After a sector is programmed, and verified, the flag is again restored to the "valid" state.
During the download process, a CRC (Cyclic Redundancy Code) is appended by the remote data source (of new software/boot versions) to each block of data that is transmitted to the system 10 over the link 14.
The controller 11 applies the same CRC calculation to the received data and compares the result, which has been appended to the data block before transmission. If the results agree, it is an indication that the data block has been received successfully, i.e., without data errors, and is a correct copy. If the results do not agree, a request is transmitted over the communication line 14 to resend the data block and the block is then resent by the remote data source. This procedure is well known to a person who is skilled in the art. Once a logical sector has been properly received, b8b6/US/99 as indicated by a valid CRC code, the sector is programmed by the upgrade program being run. The data is then read from the stored sector, and again confirmed, following which the status flag at the end of the sector is set to "valid".
According to a preferred embodiment ofthe invention, this dual boot sector arrangement (of a write protected and an accessible sectors) in the flash memory 12 enables reboot operation whenever the downloading process is disrupted, by using the original boot program, stored in the write protected boot sector 20, or an updated boot program, using the contents of accessible boot sector 21 if a correct copy exists, as indicated by the status flag. If the flag is valid, the updated boot program is copied into a memory segment 23 (a boot segment) in the RAM 13, which is used to boot the system 10 whenever the system is restarted, such as after downloading and programming of the flash memory 12. If the flag of boot sector 21 was not valid, then the original, hardware protected version of the boot program is copied into memory segment 23. The RAM 13 comprises additional segments 24, into which downloaded data blocks may be copied for.temporary storage, if desired. The system 10 is operated and controlled by the controller 11 by using the (copied) boot program which is stored in the RAM 13 and the software which is stored in the flash memory 12.
Thus, whenever the system starts up, on of the two boot segments, 20 or 21, is copied into segment 23 in the RAM 13. The program is thus always operated from the same address space, irrespective of which code versions are used.
Fig. 4 is a flow chart of the embedded-system operation, according to a preferred embodiment of the invention. The program starts from sector 20 of the flash memory. At the first step 401, the validity of the software stored in sector 21 is checked, by checking its status flag, which is stored at the end in the same sector. If found valid, at the next step 402, the ssss~rsiss content of sector 21 is copied into segment 23 in the RAM 13. If found invalid, at the next step 403, the content of segment 20 is copied into sector 23 in the RAM 13. At the next step 404, the operating address of the controller 11 is transferred to (operate from) sector 23. The program, which is copied into sector 23, at least allows the controller 11 to operate the downlink 14 and to update the flashmemory 12.
According to another preferred embodiment of the invention, one or more sectors 22 of the flash memory 12 are also copied into the RAM 13. In this case, the controller 11 operates that section of the program from the RAM
13, rather than from the flash memory 12. This allows additional functionality during downloading, since the program can not run from same addresses, being updated. In current practice, during updating, software can not be run from the flash memory 12 at all, and therefore, only software copied into RAM 13 is functional.
Sectors 22 in the flash memory 12, together with the boot sector 23 in the RAM 13 are used to generate a software version. The original software version is programmed into the sectors 22 of the hash memory by the manufacturer. During operation, if the last version of the boot program (the original boot program in the first operation) is found to be valid, it is copied from the unprotected boot sector 21 into the boot segment 23, and the last software version (the original software version in the first operation) is used from sectors 22 to allow the controller 11 to operate the system 10 from the RAM 13, and the flash memory 12.
The boot program may also be updated by transmitting a new boot data block and programming the unprotected boot sector 21 with the received boot data block. The protected boot sector 20 contains the original boot program as a backup. When the system 10 initializes, the controller 11 selects the boot program which is used for initialization by first checking the validity of the last boot program version which is stored in the boot sector 21. If the status code of the received (new) boot data block is found valid, the last boot program is copied from sector 21 into the boot segment 23 of the R,AM 13, and the initialization process continues from the RAM
13 according to the last (updated) boot program version. If the status code of sector 21, indicates that the received (new) boot data block is not valid, the original boot program is copied from sector 20 into the boot segment 23 of the RAM 13, and the initialization process continues from the RAM 13 according to the original boot program version, and a new downloading and programming process is enabled. Therefore, by using dual boot sectors in the flash memory 12, the downloading and programming process is fail-safe. According to a preferred embodiment of the invention, if the status code of sector 21 indicates that the received (new) boot data block is not valid, in addition to copying the original boot program from sector 20 into the boot sector 23 of the RAM 13, additional logical segments from sectors 22 are copied into RAM 24 to allow for additional functionality. Each sector is only loaded if it's status word indicates that it is valid. The operating program must be so designed so as to allow independent functionality from each logical segment, so that some additional valid segments will be able to operate in the absence of others that are not valid.
According to a preferred embodiment of the invention, the downloading and programming operations which are described above, and are carried out by transmitting updated data blocks from a remote source over the communication link, may also be carried out similarly in the field and on-board, by a technician or a user who connects the data source, such as a PC, to a suitable input in the system 10 or to the data link input (e.g., a serial RS-232 port).
The above examples and description have of course been provided only for the purpose of illustrations, and are not intended to limit the invention in any vvay. As will be appreciated by the skilled person, the invention can be carried out in a great variety of ways, using a micro-controller or a microprocessor to control the operation of the embedded system, employing more than one technique from those described above, such as using a wireless data communication link for downloading upgraded software versions, implementing the embedded system on a monolithic circuitry, using other volatile and non-volatile memory types, other than a flash memory and/or a RAM, all without exceeding the scope of the invention.
Claims (23)
1. A method for upgrading operating software and/or initialization program versions of an embedded system, comprising:
a) providing a programmable, non-volatile first memory having at least one write-protected area containing an original initialization and download operation program version, and at least one unprotected area containing at least an upgradable initialization and download operation program version;
b) upon initialization, copying at least said upgradable, or the original version of said initialization and download operation program version, into a second memory and/or into a memory location;
c) operating said embedded system from said second memory and/or from said memory location; and d) enabling downloading of new operating software and/or initialization program versions and programming said unprotected area with said downloaded versions.
a) providing a programmable, non-volatile first memory having at least one write-protected area containing an original initialization and download operation program version, and at least one unprotected area containing at least an upgradable initialization and download operation program version;
b) upon initialization, copying at least said upgradable, or the original version of said initialization and download operation program version, into a second memory and/or into a memory location;
c) operating said embedded system from said second memory and/or from said memory location; and d) enabling downloading of new operating software and/or initialization program versions and programming said unprotected area with said downloaded versions.
2. A method according to claim 1, wherein said second memory is physically separated from said first memory.
3. A method according to claim 1, wherein the downloading of a new version is carried out by using a portable data source connected to the data-receiving input of the embedded system.
4. A method according to claim 1, wherein the downloading of a new version is carried out from a remote data source by transmitting data groups from said source over a data link into the data-receiving input of the embedded system.
5. A method according to claim 4, wherein the data link is a wireless link.
6. A method according to claim 1, wherein the non-volatile memory is a flash memory.
7. A method according to claim 2, wherein the second memory is a volatile memory.
8. A method according to claim 1, wherein the arrival of disrupted downloaded data is detected by checking a data status code.
9. A method according to claim 1, wherein upon initialization, performing the following steps:
a) checking a status code in theunprotected area;
b) if said status code indicates a valid initialization and download operation program version, copying said program version into a second memory and/or into a memory location; and c) if said status code does not indicate a valid initialization and download operation program version, copying said original initialization and download operation program version into a second memory and/or into a memory location.
a) checking a status code in theunprotected area;
b) if said status code indicates a valid initialization and download operation program version, copying said program version into a second memory and/or into a memory location; and c) if said status code does not indicate a valid initialization and download operation program version, copying said original initialization and download operation program version into a second memory and/or into a memory location.
10. A method according to claim 2, wherein the write-protected and unprotected areas are sectors of a single flash memory.
11. A method according to claim 1, wherein the embedded system is a telephone.
12. A method according to claim 1, wherein the embedded system is a telecommunication system.
13. Embedded system having upgrading capability for its operating software and/or initialization program version, comprising:
a) a single non-volatile memory having at least one write-protected area for storing an original initialization and download program version of said embedded system and at least one unprotected area for storing an upgradable initialization and download program version of said embedded-system;
b) at least a second memory and/or memory location, for storing initialization and download program version of said embedded-system;
c) control circuitry for controlling the initialization process and the operation of said embedded system for at least copying the contents of said original initialization and download program or said upgradable initialization and download program version into said second memory and/or memory location and for at least downloading and programming of new initialization and/or download program versions; and d) a data receiving input for downloading software and/or said initialization program versions.
a) a single non-volatile memory having at least one write-protected area for storing an original initialization and download program version of said embedded system and at least one unprotected area for storing an upgradable initialization and download program version of said embedded-system;
b) at least a second memory and/or memory location, for storing initialization and download program version of said embedded-system;
c) control circuitry for controlling the initialization process and the operation of said embedded system for at least copying the contents of said original initialization and download program or said upgradable initialization and download program version into said second memory and/or memory location and for at least downloading and programming of new initialization and/or download program versions; and d) a data receiving input for downloading software and/or said initialization program versions.
14. Embedded system according to claim 13, in which said second memory is physically separated from said first memory.
15. Embedded system according to claim 13, into which new versions are downloaded by using a data source, connected to its data receiving input.
16. Embedded system according to claim 13, having a data communication link for receiving and downloading of data new versions, transmitted by a data source.
17. Embedded system according to claim 13, wherein the data communication link is a wireless link.
18. Embedded system according to claim 13, in which the non-volatile memory is a flash memory.
19. Embedded system according to claim 13, in which the second memory is a volatile memory.
20. Embedded system according to claim 13, in which the control circuitry operates at least according to the following steps:
a) upon initialization, checking a status word in said unprotected area;
b) if said status word indicates a valid initialization and download operation program version, copying the program version into a second memory and/or into a memory location; and c) if said status word does not indicate a valid initialization and download operation program version, copying said original initialization and download operation program version into a second memory and/or into a memory location.
a) upon initialization, checking a status word in said unprotected area;
b) if said status word indicates a valid initialization and download operation program version, copying the program version into a second memory and/or into a memory location; and c) if said status word does not indicate a valid initialization and download operation program version, copying said original initialization and download operation program version into a second memory and/or into a memory location.
21. Embedded system according to claim 13, in which the original initialization program is used whenever the data status word does not indicate the upgradable initialization and download program version is valid.
22. Embedded system according to claim 13, being a telephone.
23. Embedded system according to claim 13, being a telecommunication system.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
IL12994799A IL129947A (en) | 1999-05-13 | 1999-05-13 | Method and apparatus for downloading software into an embedded system |
IL129947 | 1999-05-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2307908A1 true CA2307908A1 (en) | 2000-11-13 |
Family
ID=11072800
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002307908A Abandoned CA2307908A1 (en) | 1999-05-13 | 2000-05-09 | A method and apparatus for downloading software into an embedded-system |
Country Status (5)
Country | Link |
---|---|
US (1) | US6615404B1 (en) |
EP (1) | EP1052571A3 (en) |
JP (1) | JP2000357095A (en) |
CA (1) | CA2307908A1 (en) |
IL (1) | IL129947A (en) |
Families Citing this family (167)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
PL351957A1 (en) * | 1999-06-03 | 2003-07-14 | Igt Reno Nev | Method of and apparatus for implementation of a system for transferring software downloaded from network |
US8033913B2 (en) * | 1999-06-03 | 2011-10-11 | Igt | Gaming machine update and mass storage management |
KR100322006B1 (en) * | 1999-06-09 | 2002-02-06 | 윤종용 | Program upgrading apparatus and method for a firmware board |
US8625270B2 (en) | 1999-08-04 | 2014-01-07 | Super Talent Technology, Corp. | USB flash drive with deploying and retracting functionalities using retractable cover/cap |
US20070292009A1 (en) * | 1999-08-04 | 2007-12-20 | Super Talent Electronics, Inc. | Press/Push USB Flash Drive With Deploying And Retracting Functionalities With Elasticity Material And Fingerprint Verification Capability |
US8102662B2 (en) | 2007-07-05 | 2012-01-24 | Super Talent Electronics, Inc. | USB package with bistable sliding mechanism |
US8141240B2 (en) | 1999-08-04 | 2012-03-27 | Super Talent Electronics, Inc. | Manufacturing method for micro-SD flash memory card |
US7830666B2 (en) | 2000-01-06 | 2010-11-09 | Super Talent Electronics, Inc. | Manufacturing process for single-chip MMC/SD flash memory device with molded asymmetric circuit board |
US7383362B2 (en) * | 2003-12-02 | 2008-06-03 | Super Talent Electronics, Inc. | Single-chip multi-media card/secure digital (MMC/SD) controller reading power-on boot code from integrated flash memory for user storage |
US7103684B2 (en) * | 2003-12-02 | 2006-09-05 | Super Talent Electronics, Inc. | Single-chip USB controller reading power-on boot code from integrated flash memory for user storage |
US7447037B2 (en) * | 1999-08-04 | 2008-11-04 | Super Talent Electronics, Inc. | Single chip USB packages by various assembly methods |
US7877542B2 (en) * | 2000-01-06 | 2011-01-25 | Super Talent Electronics, Inc. | High integration of intelligent non-volatile memory device |
US7535719B2 (en) * | 1999-08-04 | 2009-05-19 | Super Talent Electronics, Inc. | Single chip USB packages with contact-pins cover |
US7466556B2 (en) * | 1999-08-04 | 2008-12-16 | Super Talent Electronics, Inc. | Single chip USB packages with swivel cover |
US7872871B2 (en) * | 2000-01-06 | 2011-01-18 | Super Talent Electronics, Inc. | Molding methods to manufacture single-chip chip-on-board USB device |
JP2001051851A (en) * | 1999-08-17 | 2001-02-23 | Nec Corp | System and method for program modification of portable electronic equipment |
US6668375B1 (en) * | 1999-12-15 | 2003-12-23 | Pitney Bowes Inc. | Method and system for providing build-to-order software applications |
US6854009B1 (en) * | 1999-12-22 | 2005-02-08 | Tacit Networks, Inc. | Networked computer system |
US20080320209A1 (en) * | 2000-01-06 | 2008-12-25 | Super Talent Electronics, Inc. | High Performance and Endurance Non-volatile Memory Based Storage Systems |
US7535088B2 (en) * | 2000-01-06 | 2009-05-19 | Super Talent Electronics, Inc. | Secure-digital (SD) flash card with slanted asymmetric circuit board |
US20080286990A1 (en) * | 2003-12-02 | 2008-11-20 | Super Talent Electronics, Inc. | Direct Package Mold Process For Single Chip SD Flash Cards |
US7428605B2 (en) * | 2000-01-06 | 2008-09-23 | Super Talent Electronics Inc. | Symmetric USB device with metal-tube plastic-plug shell with USB plug centered and integrated with circuit board substrate |
JP2002094639A (en) * | 2000-09-13 | 2002-03-29 | Nec Access Technica Ltd | Mobile telephone, and method of rewriting software used for it, and storage medium having stored its control program |
US7805720B2 (en) | 2003-04-11 | 2010-09-28 | Flexiworld Technologies, Inc. | Autorun for integrated circuit memory component |
US11467856B2 (en) | 2002-12-12 | 2022-10-11 | Flexiworld Technologies, Inc. | Portable USB device for internet access service |
US11204729B2 (en) | 2000-11-01 | 2021-12-21 | Flexiworld Technologies, Inc. | Internet based digital content services for pervasively providing protected digital content to smart devices based on having subscribed to the digital content service |
US7409685B2 (en) | 2002-04-12 | 2008-08-05 | Hewlett-Packard Development Company, L.P. | Initialization and update of software and/or firmware in electronic devices |
US7401320B2 (en) | 2000-11-17 | 2008-07-15 | Hewlett-Packard Development Company, L.P. | Operator network that routes customer care calls based on subscriber/device profile and CSR skill set |
US20030182414A1 (en) * | 2003-05-13 | 2003-09-25 | O'neill Patrick J. | System and method for updating and distributing information |
US8479189B2 (en) | 2000-11-17 | 2013-07-02 | Hewlett-Packard Development Company, L.P. | Pattern detection preprocessor in an electronic device update generation system |
AU2002226948A1 (en) | 2000-11-20 | 2002-06-03 | Flexiworld Technologies, Inc. | Tobile and pervasive output components |
US6886160B1 (en) * | 2000-11-29 | 2005-04-26 | Hyung Sup Lee | Distribution of mainframe data in the PC environment |
JP2002175194A (en) * | 2000-12-07 | 2002-06-21 | Ricoh Co Ltd | Program downloading system, program downloading device, image forming device, program downloading method, and computer-readable recording medium with program for executing the method recorded thereon |
US7055148B2 (en) * | 2000-12-07 | 2006-05-30 | Hewlett-Packard Development Company, L.P. | System and method for updating firmware |
US6804798B2 (en) * | 2001-03-30 | 2004-10-12 | Hewlett-Packard Development Company, L.P. | System and method for setting new values for configuration parameters on a device |
JP4120180B2 (en) * | 2001-05-08 | 2008-07-16 | ティアック株式会社 | Program processing apparatus, program version upgrade method and program version upgrade program therefor |
EP1271348A1 (en) * | 2001-06-28 | 2003-01-02 | Siemens Aktiengesellschaft | Method for online transformation of mass data |
KR100440950B1 (en) | 2001-06-30 | 2004-07-21 | 삼성전자주식회사 | Method for upgrading software in network environment and network device thereof |
US7386653B2 (en) * | 2001-08-06 | 2008-06-10 | Sandisk Il Ltd | Flash memory arrangement |
US6504131B1 (en) * | 2001-09-19 | 2003-01-07 | Illinois Tool Works Inc. | Welding-type power supply with boot loader |
GB2380018A (en) * | 2001-09-21 | 2003-03-26 | Hewlett Packard Co | Reprogramming electronic apparatus having non-volatile memory |
KR20030032257A (en) * | 2001-10-17 | 2003-04-26 | 삼성전자주식회사 | Method for upgrading program and apparatus therefor |
US7319991B2 (en) * | 2001-12-11 | 2008-01-15 | International Business Machines Corporation | Computerized cost estimate system and method |
US7409435B1 (en) * | 2002-02-28 | 2008-08-05 | Sprint Communications Company L.P. | Integrated services hub binary file trial run process |
US7017004B1 (en) * | 2002-03-29 | 2006-03-21 | Microsoft Corporation | System and method for updating contents of a flash ROM |
KR100774857B1 (en) * | 2002-04-01 | 2007-11-08 | 가부시키가이샤 엔티티 도코모 | Communication terminal software updating method, communication terminal, and software updating method |
US7089549B2 (en) | 2002-04-01 | 2006-08-08 | International Business Machines Corp. | Updating flash memory |
US6925467B2 (en) * | 2002-05-13 | 2005-08-02 | Innopath Software, Inc. | Byte-level file differencing and updating algorithms |
GB0212318D0 (en) * | 2002-05-28 | 2002-07-10 | Symbian Ltd | Tamper evident removable media storing executable code |
EP1372068A3 (en) * | 2002-06-11 | 2006-02-08 | Seiko Epson Corporation | System, method and program for rewriting a flash memory |
AU2003242930A1 (en) * | 2002-06-28 | 2004-01-19 | Koninklijke Philips Electronics N.V. | Software download into a receiver |
US7367027B1 (en) * | 2002-08-22 | 2008-04-29 | Hewlett-Packard Development Company, L.P. | System for generating efficient and compact update packages |
DE10240584A1 (en) * | 2002-08-28 | 2004-03-11 | Pilz Gmbh & Co. | Safety control system for fault protected operation of critical process such as occurs in machine system operation |
US7096311B2 (en) | 2002-09-30 | 2006-08-22 | Innopath Software, Inc. | Updating electronic files using byte-level file differencing and updating algorithms |
US6836657B2 (en) * | 2002-11-12 | 2004-12-28 | Innopath Software, Inc. | Upgrading of electronic files including automatic recovery from failures and errors occurring during the upgrade |
US7363540B2 (en) | 2002-10-22 | 2008-04-22 | Microsoft Corporation | Transaction-safe FAT file system improvements |
US7174420B2 (en) * | 2002-10-22 | 2007-02-06 | Microsoft Corporation | Transaction-safe FAT file system |
US7320010B2 (en) * | 2002-11-18 | 2008-01-15 | Innopath Software, Inc. | Controlling updates of electronic files |
US20040098361A1 (en) * | 2002-11-18 | 2004-05-20 | Luosheng Peng | Managing electronic file updates on client devices |
US7007049B2 (en) | 2002-11-18 | 2006-02-28 | Innopath Software, Inc. | Device memory management during electronic file updating |
US7003534B2 (en) | 2002-11-18 | 2006-02-21 | Innopath Software, Inc. | Generating difference files using module information of embedded software components |
US7844734B2 (en) * | 2002-11-18 | 2010-11-30 | Innopath Software, Inc. | Dynamic addressing (DA) using a centralized DA manager |
US20040098716A1 (en) * | 2002-11-19 | 2004-05-20 | Lin Cheng-Chung | Detecting system and method |
US7099884B2 (en) | 2002-12-06 | 2006-08-29 | Innopath Software | System and method for data compression and decompression |
WO2004055638A2 (en) | 2002-12-12 | 2004-07-01 | Flexiworld Technologies, Inc. | Wireless communication between computing devices |
JP2004199277A (en) * | 2002-12-17 | 2004-07-15 | Fujitsu Ltd | Bios redundancy management method, data processor, and storage system |
US20040230965A1 (en) * | 2003-02-28 | 2004-11-18 | Harri Okkonen | Mobile handset network that facilitates interaction between a generic intelligent responsive agent and a service broker server |
US7171606B2 (en) * | 2003-03-25 | 2007-01-30 | Wegener Communications, Inc. | Software download control system, apparatus and method |
US7975147B1 (en) | 2003-03-31 | 2011-07-05 | Hewlett-Packard Development Company, L.P. | Electronic device network supporting enciphering and deciphering and update generation in electronic devices |
US7089414B2 (en) * | 2003-04-10 | 2006-08-08 | International Business Machines Corporation | Method and apparatus for updating a microcode image in a memory |
US7463610B2 (en) * | 2003-05-15 | 2008-12-09 | Samsung Electronics Co., Ltd. | System and method for providing an online software upgrade |
US20040243284A1 (en) * | 2003-05-28 | 2004-12-02 | Caterpillar Inc. | Methods and systems for modifying flash files |
US7356577B2 (en) * | 2003-06-12 | 2008-04-08 | Samsung Electronics Co., Ltd. | System and method for providing an online software upgrade in load sharing servers |
JP3906825B2 (en) * | 2003-06-17 | 2007-04-18 | 日本電気株式会社 | Computer system, computer system activation method and program |
US7810088B2 (en) | 2003-06-20 | 2010-10-05 | Samsung Electronics Co., Ltd. | Apparatus and method for performing a fail-safe over-the-air software update in a mobile station |
US7089270B2 (en) * | 2003-06-20 | 2006-08-08 | Innopath Software | Processing software images for use in generating difference files |
EP1636700A1 (en) * | 2003-06-24 | 2006-03-22 | Bayerische Motoren Werke Aktiengesellschaft | Method for booting up a software in the boot sector of a programmable read-only memory |
US7206411B2 (en) | 2003-06-25 | 2007-04-17 | Wegener Communications, Inc. | Rapid decryption of data by key synchronization and indexing |
US7343443B1 (en) * | 2003-07-08 | 2008-03-11 | Hewlett-Packard Development Company, L.P. | Updated package generation based on analysis of bank dependency |
US20050010576A1 (en) * | 2003-07-09 | 2005-01-13 | Liwei Ren | File differencing and updating engines |
US20050010870A1 (en) * | 2003-07-09 | 2005-01-13 | Jinsheng Gu | Post-processing algorithm for byte-level file differencing |
US7031972B2 (en) * | 2003-07-21 | 2006-04-18 | Innopath Software, Inc. | Algorithms for block-level code alignment of software binary files |
US20050020308A1 (en) * | 2003-07-23 | 2005-01-27 | David Lai | Dynamically binding Subscriber Identity Modules (SIMs)/User Identity Modules (UIMs) with portable communication devices |
US7886093B1 (en) | 2003-07-31 | 2011-02-08 | Hewlett-Packard Development Company, L.P. | Electronic device network supporting compression and decompression in electronic devices |
JP4517607B2 (en) * | 2003-09-01 | 2010-08-04 | ソニー株式会社 | Electronic device and method for updating the program |
KR101003888B1 (en) | 2003-09-03 | 2010-12-30 | 휴렛-팩커드 디벨롭먼트 컴퍼니, 엘.피. | Tri-phase boot process in electronic devices |
US8555273B1 (en) | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
WO2005040988A2 (en) * | 2003-10-23 | 2005-05-06 | Innopath Software, Inc. | Dynamic addressing (da) using a centralized da manager |
KR100547809B1 (en) | 2003-10-31 | 2006-01-31 | 삼성전자주식회사 | Mobile communication terminal with embedded system for software download and software download method |
US7440286B2 (en) * | 2005-04-21 | 2008-10-21 | Super Talent Electronics, Inc. | Extended USB dual-personality card reader |
US8998620B2 (en) * | 2003-12-02 | 2015-04-07 | Super Talent Technology, Corp. | Molding method for COB-EUSB devices and metal housing package |
US7872873B2 (en) | 2003-12-02 | 2011-01-18 | Super Talent Electronics, Inc. | Extended COB-USB with dual-personality contacts |
US8102657B2 (en) | 2003-12-02 | 2012-01-24 | Super Talent Electronics, Inc. | Single shot molding method for COB USB/EUSB devices with contact pad ribs |
US7869219B2 (en) * | 2004-01-20 | 2011-01-11 | Super Talent Electronics, Inc. | Flash drive with spring-loaded retractable connector |
US7546596B2 (en) * | 2004-03-29 | 2009-06-09 | International Business Machines Corporation | Non-disruptive method, system and program product for overlaying a first software module with a second software module |
US7904895B1 (en) | 2004-04-21 | 2011-03-08 | Hewlett-Packard Develpment Company, L.P. | Firmware update in electronic devices employing update agent in a flash memory card |
US7543118B1 (en) | 2004-05-07 | 2009-06-02 | Hewlett-Packard Development Company, L.P. | Multiple variance platform for the management of mobile devices |
KR20050044837A (en) * | 2004-06-08 | 2005-05-13 | 삼성전자주식회사 | Mobile communication terminal and method for processing communication_function during the outputting of digital_broadcasting_data |
US20080195817A1 (en) * | 2004-07-08 | 2008-08-14 | Super Talent Electronics, Inc. | SD Flash Memory Card Manufacturing Using Rigid-Flex PCB |
US8526940B1 (en) | 2004-08-17 | 2013-09-03 | Palm, Inc. | Centralized rules repository for smart phone customer care |
US7516451B2 (en) * | 2004-08-31 | 2009-04-07 | Innopath Software, Inc. | Maintaining mobile device electronic files including using difference files when upgrading |
US20060084464A1 (en) * | 2004-09-30 | 2006-04-20 | Macronix International Co., Ltd. | Apparatus and method for firmware download in a mobile audio platform |
US7634258B2 (en) * | 2004-11-22 | 2009-12-15 | Motorola, Inc. | System and method for over-the-air update of wireless communication devices |
US20060120191A1 (en) * | 2004-12-06 | 2006-06-08 | Mediatek Incorporation | Systems and methods for optical drive operation |
US8606830B2 (en) | 2004-12-17 | 2013-12-10 | Microsoft Corporation | Contiguous file allocation in an extensible file system |
US8321439B2 (en) | 2004-12-17 | 2012-11-27 | Microsoft Corporation | Quick filename lookup using name hash |
US7873596B2 (en) | 2006-05-23 | 2011-01-18 | Microsoft Corporation | Extending cluster allocations in an extensible file system |
US9639554B2 (en) | 2004-12-17 | 2017-05-02 | Microsoft Technology Licensing, Llc | Extensible file system |
FR2881912A1 (en) * | 2005-02-07 | 2006-08-11 | France Telecom | METHOD FOR DISPLAYING TEXT MESSAGES, TERMINAL AND PROGRAM FOR IMPLEMENTING THE METHOD |
JP4764056B2 (en) * | 2005-04-14 | 2011-08-31 | キヤノン株式会社 | Image processing apparatus, control program update method, and program |
DE602005015689D1 (en) * | 2005-06-10 | 2009-09-10 | Sony Ericsson Mobile Comm Ab | Processor-controlled device with different operating modes |
US7418590B2 (en) * | 2005-07-14 | 2008-08-26 | Dell Products L.P. | Information handling system for storing basic input output system configurations |
DE102005050288A1 (en) * | 2005-10-14 | 2007-04-19 | Siemens Ag | System for implementing software updates in embedded systems and a method for doing so |
TWI275029B (en) * | 2005-11-18 | 2007-03-01 | Hon Hai Prec Ind Co Ltd | An embedded system and method for processing data thereof |
US20070277028A1 (en) * | 2006-05-26 | 2007-11-29 | Jamey Cates | Method and system for recovery from reprogramming failures in nonvolatile memory |
EP2025095A2 (en) | 2006-06-08 | 2009-02-18 | Hewlett-Packard Development Company, L.P. | Device management in a network |
DE102006028797A1 (en) * | 2006-06-23 | 2007-12-27 | Khs Ag | Replaceable drive system |
US9726392B2 (en) * | 2006-06-29 | 2017-08-08 | Honeywell International Inc. | Generic user interface system |
US8418128B2 (en) * | 2006-06-29 | 2013-04-09 | Honeywell International Inc. | Graphical language compiler system |
US7738972B2 (en) * | 2006-06-29 | 2010-06-15 | Honeywell International Inc. | Modular shared-memory resource stage driver system for flexible resource linking in an energy conversion system |
US8112162B2 (en) * | 2006-06-29 | 2012-02-07 | Honeywell International Inc. | System level function block engine |
FR2903791B1 (en) * | 2006-07-13 | 2008-10-17 | Airbus France Sas | METHOD FOR DOWNLOADING A SOFTWARE MODULE. |
WO2008014454A2 (en) | 2006-07-27 | 2008-01-31 | Hewlett-Packard Development Company, L.P. | User experience and dependency management in a mobile device |
US8224888B2 (en) * | 2006-11-14 | 2012-07-17 | Honeywell International Inc. | Public variable interface system |
US7990724B2 (en) | 2006-12-19 | 2011-08-02 | Juhasz Paul R | Mobile motherboard |
CA2637480A1 (en) * | 2006-12-19 | 2008-06-26 | Halliburton Energy Services, Inc. | Secure firmware updates in embedded systems |
US7613738B2 (en) * | 2007-01-16 | 2009-11-03 | Microsoft Corporation | FAT directory structure for use in transaction safe file system |
US7747664B2 (en) | 2007-01-16 | 2010-06-29 | Microsoft Corporation | Storage system format for transaction safe file system |
US8254134B2 (en) * | 2007-05-03 | 2012-08-28 | Super Talent Electronics, Inc. | Molded memory card with write protection switch assembly |
US7822963B2 (en) * | 2007-06-05 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Remote computer operating system upgrade |
US7850468B2 (en) | 2007-06-28 | 2010-12-14 | Super Talent Electronics, Inc. | Lipstick-type USB device |
US8102658B2 (en) * | 2007-07-05 | 2012-01-24 | Super Talent Electronics, Inc. | Micro-SD to secure digital adaptor card and manufacturing method |
US7944702B2 (en) | 2007-08-27 | 2011-05-17 | Super Talent Electronics, Inc. | Press-push flash drive apparatus with metal tubular casing and snap-coupled plastic sleeve |
US8650306B2 (en) * | 2007-10-24 | 2014-02-11 | Honeywell International Inc. | Interoperable network programmable controller generation system |
US8241047B2 (en) * | 2007-10-30 | 2012-08-14 | Super Talent Electronics, Inc. | Flash drive with spring-loaded swivel connector |
US9122553B2 (en) * | 2007-12-01 | 2015-09-01 | Sony Corporation | Synchronous bus download of TV software update |
US8116083B2 (en) * | 2007-12-04 | 2012-02-14 | Super Talent Electronics, Inc. | Lipstick-type USB device with tubular housing |
JP5272414B2 (en) * | 2008-01-18 | 2013-08-28 | 富士通セミコンダクター株式会社 | Information processing system and firmware execution method |
US8219595B2 (en) * | 2008-02-14 | 2012-07-10 | Hewlett-Packard Development Company, L.P. | System and method for efficient remote data access for server management |
US9488992B2 (en) * | 2008-10-16 | 2016-11-08 | Honeywell International Inc. | Wall module configuration tool |
CN101477471B (en) * | 2009-01-07 | 2014-04-30 | 杭州海康威视数字技术股份有限公司 | Embedded system firmware on-line upgrading method |
TW201027324A (en) * | 2009-01-14 | 2010-07-16 | Giga Byte Tech Co Ltd | Embedded electronic device free from being stuck in update failure and method of making the same |
EP2427845B1 (en) * | 2009-05-04 | 2020-01-01 | Nokia Solutions and Networks Oy | Mechanism for updating software |
US8190574B2 (en) | 2010-03-02 | 2012-05-29 | Storagecraft Technology Corporation | Systems, methods, and computer-readable media for backup and restoration of computer information |
EP2378417A1 (en) * | 2010-04-16 | 2011-10-19 | Accenture Global Services Limited | Extending the functionality of an embedded system |
US8646072B1 (en) * | 2011-02-08 | 2014-02-04 | Symantec Corporation | Detecting misuse of trusted seals |
US8538588B2 (en) | 2011-02-28 | 2013-09-17 | Honeywell International Inc. | Method and apparatus for configuring scheduling on a wall module |
KR20120109800A (en) * | 2011-03-28 | 2012-10-09 | 삼성전자주식회사 | Data update method based on a firmware on the air and portable device supporting the same |
US8943330B2 (en) * | 2011-05-10 | 2015-01-27 | Qualcomm Incorporated | Apparatus and method for hardware-based secure data processing using buffer memory address range rules |
CN103176806B (en) * | 2011-12-21 | 2017-08-18 | 富泰华工业(深圳)有限公司 | Programming system and burning control method |
US20130166893A1 (en) * | 2011-12-23 | 2013-06-27 | Sandisk Technologies Inc. | Auxiliary card initialization routine |
JP5886099B2 (en) * | 2012-03-21 | 2016-03-16 | 日立オートモティブシステムズ株式会社 | Electronic control unit for automobile |
TWI502507B (en) * | 2013-01-22 | 2015-10-01 | Wistron Corp | Method of updating battery firmware, portable electronics device and rechargeable battery module |
US9910660B2 (en) * | 2013-08-05 | 2018-03-06 | Harman International Industries, Incorporated | Operating system replacement for in-vehicle computing system |
US8886933B1 (en) * | 2013-12-17 | 2014-11-11 | Google Inc. | Streamlined provisioning and configuration of computing devices |
US9940048B2 (en) | 2014-02-26 | 2018-04-10 | Macronix International Co., Ltd. | Nonvolatile memory data protection using nonvolatile protection codes and volatile protection codes |
US9582262B2 (en) | 2014-06-16 | 2017-02-28 | Wipro Limited | Systems and methods for installing upgraded software on electronic devices |
US9920944B2 (en) | 2015-03-19 | 2018-03-20 | Honeywell International Inc. | Wall module display modification and sharing |
US9858231B2 (en) | 2015-06-22 | 2018-01-02 | Google Llc | Operating system card for multiple devices |
EP3724757B1 (en) * | 2017-12-13 | 2023-06-28 | Absolute Software Corporation | Firmware publication of multiple binary images |
JP2020087293A (en) * | 2018-11-30 | 2020-06-04 | キヤノン株式会社 | Information processing apparatus and control method of information processing apparatus |
US11150890B2 (en) * | 2019-09-12 | 2021-10-19 | International Business Machines Corporation | File system synchronization-based updating |
CN112685053A (en) * | 2019-10-18 | 2021-04-20 | 航天科工惯性技术有限公司 | Remote upgrading control method for single chip microcomputer program |
CN111488168B (en) * | 2019-12-25 | 2023-09-12 | 湖北航天飞行器研究所 | Weapon system control software safety upgrading method based on boot secondary loading |
US11237838B2 (en) * | 2020-01-02 | 2022-02-01 | Western Digital Technologies, Inc. | Storage system and method for enabling a direct accessible boot block in a memory die |
CN112181454B (en) * | 2020-09-21 | 2023-04-07 | 西安微电子技术研究所 | Remote upgrading system and method for unattended equipment |
JP2022071954A (en) * | 2020-10-29 | 2022-05-17 | キヤノン株式会社 | Information processing device, information processing method, and program |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5535355A (en) * | 1989-04-06 | 1996-07-09 | Kabushiki Kaisha Toshiba | Controller for a storage device which allows either prestored or user defined firmware to be executed |
DE69034191T2 (en) * | 1989-04-13 | 2005-11-24 | Sandisk Corp., Sunnyvale | EEPROM system with multi-chip block erasure |
GB2251323B (en) * | 1990-12-31 | 1994-10-12 | Intel Corp | Disk emulation for a non-volatile semiconductor memory |
GB2251324B (en) * | 1990-12-31 | 1995-05-10 | Intel Corp | File structure for a non-volatile semiconductor memory |
IT1254937B (en) * | 1991-05-06 | 1995-10-11 | DYNAMIC UPDATE OF NON-VOLATILE MEMORY IN A COMPUTER SYSTEM | |
US5388267A (en) * | 1991-05-29 | 1995-02-07 | Dell Usa, L.P. | Method and apparatus for updating and restoring system BIOS functions while maintaining BIOS integrity |
US5473775A (en) * | 1991-10-11 | 1995-12-05 | Kabushiki Kaisha Toshiba | Personal computer using flash memory as BIOS-ROM |
US5870520A (en) * | 1992-12-23 | 1999-02-09 | Packard Bell Nec | Flash disaster recovery ROM and utility to reprogram multiple ROMS |
US5522076A (en) * | 1993-05-13 | 1996-05-28 | Kabushiki Kaisha Toshiba | Computer system having BIOS (basic input/output system)-ROM (Read Only Memory) writing function |
US5452339A (en) * | 1994-02-09 | 1995-09-19 | Harris Corporation | Local/remote modification of electronically alterable operating system firmware resident in redundant flash memory of remote unit for testing/conditioning subscriber line circuits |
US6148441A (en) * | 1994-04-06 | 2000-11-14 | Dell Usa, L.P. | Method for reprogramming flash ROM in a personal computer implementing an EISA bus system |
US5666293A (en) * | 1994-05-27 | 1997-09-09 | Bell Atlantic Network Services, Inc. | Downloading operating system software through a broadcast channel |
US5654746A (en) * | 1994-12-01 | 1997-08-05 | Scientific-Atlanta, Inc. | Secure authorization and control method and apparatus for a game delivery service |
US5647986A (en) | 1994-12-02 | 1997-07-15 | Nawathe; Dilip | Apparatus and process for distributed treatment of wastewater |
US5568641A (en) * | 1995-01-18 | 1996-10-22 | Hewlett-Packard Company | Powerfail durable flash EEPROM upgrade |
US5748940A (en) * | 1995-08-17 | 1998-05-05 | Compaq Computer Corporation | Secure updating of non-volatile memory |
US5812883A (en) * | 1995-11-22 | 1998-09-22 | Mitsubishi Chemical America, Inc. | System for reading and storing formatting information after formatting a first storage medium and using the stored formatting information to format a second storage medium |
US5701492A (en) * | 1996-03-29 | 1997-12-23 | Canon Kabushiki Kaisha | Fail-safe flashing of EPROM |
US5940074A (en) * | 1996-06-03 | 1999-08-17 | Webtv Networks, Inc. | Remote upgrade of software over a network |
US6023620A (en) * | 1997-02-26 | 2000-02-08 | Telefonaktiebolaget Lm Ecrisson | Method for downloading control software to a cellular telephone |
US6135651A (en) * | 1997-05-29 | 2000-10-24 | Cirrus Logic, Inc. | Patching apparatus and method for upgrading modem software code |
US5966301A (en) * | 1997-06-13 | 1999-10-12 | Allen-Bradley Company, Llc | Redundant processor controller providing upgrade recovery |
GB9713094D0 (en) * | 1997-06-21 | 1997-08-27 | Philips Electronics Nv | Optical disc drive |
US6055632A (en) * | 1997-09-25 | 2000-04-25 | Allen-Bradley Company, Llc | Method and apparatus for transferring firmware to a non-volatile memory of a programmable controller system |
US6185678B1 (en) * | 1997-10-02 | 2001-02-06 | Trustees Of The University Of Pennsylvania | Secure and reliable bootstrap architecture |
US6035423A (en) * | 1997-12-31 | 2000-03-07 | Network Associates, Inc. | Method and system for providing automated updating and upgrading of antivirus applications using a computer network |
US6308265B1 (en) * | 1998-09-30 | 2001-10-23 | Phoenix Technologies Ltd. | Protection of boot block code while allowing write accesses to the boot block |
US6385721B1 (en) * | 1999-01-22 | 2002-05-07 | Hewlett-Packard Company | Computer with bootable hibernation partition |
-
1999
- 1999-05-13 IL IL12994799A patent/IL129947A/en not_active IP Right Cessation
- 1999-05-18 US US09/313,609 patent/US6615404B1/en not_active Expired - Fee Related
-
2000
- 2000-05-05 EP EP00303809A patent/EP1052571A3/en not_active Ceased
- 2000-05-09 CA CA002307908A patent/CA2307908A1/en not_active Abandoned
- 2000-05-15 JP JP2000142053A patent/JP2000357095A/en active Pending
Also Published As
Publication number | Publication date |
---|---|
JP2000357095A (en) | 2000-12-26 |
EP1052571A3 (en) | 2005-01-19 |
US6615404B1 (en) | 2003-09-02 |
IL129947A0 (en) | 2000-02-29 |
IL129947A (en) | 2003-06-24 |
EP1052571A2 (en) | 2000-11-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6615404B1 (en) | Method and apparatus for downloading software into an embedded-system | |
US6681390B2 (en) | Upgrade of a program | |
US8539471B2 (en) | Updating firmware of an electronic device | |
US6275931B1 (en) | Method and apparatus for upgrading firmware boot and main codes in a programmable memory | |
US7275153B2 (en) | Booting and boot code update system using boot strapper code to select between a loader and a duplicate backup loader | |
EP1142309B1 (en) | Method and apparatus for operating system downloads in a set-top box environment | |
US5987605A (en) | Methods and apparatus for dual-boot memory selection, update, and recovery in a programmable device | |
US7206971B2 (en) | Selectable and updatable computer boot memory | |
US8181007B2 (en) | Electronic device and method for secure operating system update in embedded system | |
EP1087294B1 (en) | Method and apparatus of remotely updating firmware of a communication device | |
US7971199B1 (en) | Mobile device with a self-updating update agent in a wireless network | |
KR100440950B1 (en) | Method for upgrading software in network environment and network device thereof | |
EP1639468B1 (en) | Network equipment and a method for monitoring the start up of a such an equipment | |
US7017038B1 (en) | Method and system to provide first boot to a CPU system | |
US20080098388A1 (en) | Safe Flashing | |
US6772364B1 (en) | Fault tolerant field updating with alternation of memory areas | |
JP2005284902A (en) | Terminal device, control method and control program thereof, host device, control method and control program thereof, and method, system, and program for remote updating | |
KR20010007066A (en) | A method and apparatus for downloading software into an embedded system | |
KR100422928B1 (en) | apparatus and method for booting in data processing system | |
KR20070060448A (en) | Device and method for upgradin system using two step bootloader | |
JP2003122575A (en) | Information processing unit | |
JPH10287001A (en) | Data rewriting device | |
CN117632162A (en) | Software upgrading system and method | |
JP2005228225A (en) | Memory card adaptor | |
JPH0793145A (en) | Remote changing system for program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued |