WO2005085996A1 - Flash memory programming - Google Patents
Flash memory programming Download PDFInfo
- Publication number
- WO2005085996A1 WO2005085996A1 PCT/EP2005/000190 EP2005000190W WO2005085996A1 WO 2005085996 A1 WO2005085996 A1 WO 2005085996A1 EP 2005000190 W EP2005000190 W EP 2005000190W WO 2005085996 A1 WO2005085996 A1 WO 2005085996A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- memory
- updated
- program code
- module
- object module
- Prior art date
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1293—Printer information exchange with computer
- G06F3/1294—Status or feedback related to information exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/443—Optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
- G11C16/102—External programming circuits, e.g. EPROM programmers; In-circuit programming or reprogramming; EPROM emulators
Definitions
- This invention relates to the updating of program code stored in a memory, which memory comprises a plurality of memory sectors.
- Flash memory is a popular type of memory in electronic devices, because it allows multiple rewrites. However, the write operations are limited to entire memory sectors, so-called pages, at a time.
- a typical page size of current flash memories is 64 kbyte.
- an application where update times are of great concern is the over-the-air (OTA) update of mobile terminals.
- OTA over-the-air
- the modifications are generally referred to as delta-files.
- an update agent running on the mobile terminal applies the received modifications to the current image which is thereby transformed to the updated version.
- the terminal is not functional during the update process.
- even small updates of the source code of the software may cause a large portion of the flash pages to be updated, since changing even a single byte requires an entire page to be completely rewritten.
- the above prior art method requires information about the anticipated likelihood of changing the respective information components.
- the above prior art does not address the problem of reducing the number of required re-writes when updating program code in a memory with a plurality of memory sectors, without requiring information about the anticipated likelihood of future changes in the respective software components.
- a method for updating program code stored in a memory which memory comprises a plurality of memory sectors, the method comprising - transforming an updated input code into an updated program code version to be stored in a memory, which memory has stored thereon a current program code version occupying a first set of the memory sectors of the memory, wherein the updated program code version occupies a second set of memory sectors when stored in the memory; wherein the transforming further comprises - receiving a representation of the current program code version; and - performing at least one optimisation step adapted to decrease the number of memory sectors of the second set of memory sectors occupied by the updated code version that are different from the corresponding memory sectors of the first set of memory sectors occupied by the current program code version.
- the number of required re-writes is reduced.
- the above optimisation is based on information that is readily available to the updating process.
- the process is based on information about the currently installed version and the current update, whereas no information about the likelihood of any future updates is required.
- the representation of the current program code version comprises a current image of the first set of memory sectors and/or a map file description of the current image of the first set of memory sectors. Consequently, the representation comprises information about the layout of the program code components in the memory, thereby allowing the optimisation process to adapt the layout of the updated components as to reduce the differences between both versions.
- a code generation system comprises a compiler which compiles a source code and generates a number of object code modules, and a linker which generates the executable code.
- the linker resolves dependencies between the set of object code modules that constitute a software development project.
- the tasks of the linker generally include laying out the object modules in memory, i.e. assigning relative addresses to the different object modules in a corresponding address space. Hence, at the linker stage, the necessary information about the layout of the code in the memory space is available.
- the object module is typically represented as an object file in a low-level file format that is hardware and/or platform specific.
- the object file is generated by a compiler and serves as an input to the linker.
- An object module is typically relocatable and contains unresolved references.
- layout of the code in memory comprises the respective start or base addresses of the different object modules, i.e. their respective relative addresses within the address space occupied by the program code.
- the optimisation process is performed at the linker stage.
- the input code comprises a number of object modules and the transforming comprises linking the number of object modules.
- the optimisation process comprises determining the layout of said object modules in memory.
- the input code comprises at least one source code module; the transforming comprises - compiling the at least one source code module resulting in a number of object modules; and - linking the number of object modules; and performing at least one optimisation step comprises - generating feedback data during the linking step; and - re-compiling at least a subset of the source code modules based on the feedback data and resulting in a number of modified object modules; and - performing the linking step based on the number of modified object modules. Consequently, according to this embodiment, the linker generates feedback to the compiler stage causing the compiler to re-compile at least a part of the source code. This has the advantage that the linker controls the resulting set of object modules, thereby increasing the degrees of freedom of re-arranging object code modules by the linker.
- the transforming further comprises controlling the optimisation process by at least one optimisation parameter.
- the optimisation parameters determine one or more limitations for the optimisation process.
- one or more of the optimisation parameters may determine a maximum allowed increase in size caused by the optimisation process such as a maximum size of padding space allowed to be added by the optimisation process.
- at least one optimisation parameter may include a parameter determining a maximum allowed number of relays introduced by the optimisation process.
- determining the layout of said object modules in memory comprises - detecting an updated first object module having a different size than a corresponding first current object module, and an updated second object module equal to a corresponding second current object module, which updated second object module has a base address larger than the base address of the updated first object module; and - padding the detected updated first object module with a predetermined memory content of a predetermined padding size resulting in a padded updated first object module; wherein the padding size is selected to cause the base address of the updated second object module to be equal to the base address of the corresponding second current object module.
- determining the layout of said object modules in memory comprises - detecting an updated first object module that is larger than a corresponding first current object module; - moving a predetermined part of the updated first object module to a different memory sector resulting in a reduced updated first object module and a moved part of the updated first object module; - inserting a relay to the moved part of the updated first object module in the reduced first updated memory sector.
- the method further comprises generating a delta file representative of differences between the current program code version and the updated program code version.
- the resulting delta file includes the differences between the current and updated versions, i.e. the information required for the device to generate the updated version from the current version stored in the device and the delta file. It is an advantage of this embodiment, that the size of the file that needs to be uploaded to the device is reduced, thereby further reducing the time required to perform a software update.
- processing means comprises any circuit and/or device suitably adapted to perform the above functions.
- processing means comprises general- or special-purpose programmable microprocessors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Programmable Logic Arrays (PLA), Field Programmable Gate Arrays (FPGA), special purpose electronic circuits, etc., or a combination thereof.
- the program code means may be loaded in a memory, such as a RAM, from a storage medium or from another computer via a computer network.
- a memory such as a RAM
- the described features may be implemented by hardwired circuitry instead of software or in combination with software.
- the present invention can be implemented in different ways including the method described above and in the following, a data processing system, and further product means, each yielding one or more of the benefits and advantages described in connection with the first-mentioned method, and each having one or more preferred embodiments corresponding to the preferred embodiments described in connection with the first-mentioned method.
- the invention relates to a data processing system for updating program code stored in a memory, the memory comprising a plurality of memory sectors, the data processing system being suitably programmed to perform the steps of the method described above and in the following.
- the invention further relates to a computer program product comprising program code means adapted to cause a data processing system to perform the method described above and in the following, when said program code means are executed on the data processing system.
- the computer program product may be embodied as a computer-readable medium having stored thereon said program code means.
- the term electronic device comprises any device comprising a memory such as a flash memory for storing program code.
- Examples of such devices include portable radio communications equipment and other handheld or portable devices.
- portable radio communications equipment includes all equipment such as mobile telephones, pagers, communicators, i.e. electronic organisers, smart phones, personal digital assistants (PDAs), handheld computers, or the like.
- fig. 1 schematically shows a block diagram of an embodiment of a system for updating software in a mobile terminal
- fig. 2 schematically shows a block diagram of a mobile terminal according to an embodiment of the invention
- fig. 3 shows a block diagram of an embodiment of a software update process
- fig. 4 schematically illustrates the memory layout of a flash memory before and after a software update where the layout is optimised via an introduction of padding space;
- fig. 5 schematically illustrates the memory layout of a flash memory before and after a software update where the layout is optimised via an introduction of a relay
- fig. 6 shows a block diagram of another embodiment of a software update process
- Fig. 1 schematically shows a block diagram of an embodiment of a system for updating software in an electronic device such as a mobile terminal.
- the system comprises a mobile terminal 101 , e.g. a mobile telephone or the like, a software updating system 102, and a communications interface 103.
- the software updating system 102 may comprise a server computer having access to the communications network.
- the functionality of the server computer may be distributed among a plurality of computers, e.g. computers connected via a computer network, e.g. a local area network, a wide area network, an Internet, or the like.
- the software updating system 102 comprises an interface circuit 104 allowing the software updating system to communicate data via the communications interface 103.
- the interface circuit may comprise a serial port, a parallel port, a short range wireless communications interface, e.g. an infrared port, a Bluetooth transceiver, or the like.
- Further examples of interface circuits include a network card, a DSL modem, a gateway computer, or the like.
- the software updating system further comprises a processing unit 105, e.g. the CPU of a server computer, suitably programmed to control and perform the update process including the generation of the updated program code as described herein.
- the processing unit further comprises a version database 106 having stored therein memory images of at least a base version and an updated version of the software to be updated.
- the version database may further comprise additional information, e.g. a plurality of base versions and/or updated versions, e.g. for different models of mobile terminals, for different groups of customers, and/or the like.
- the communications interface 103 may be any suitable wired or wireless communications interface for communicating data between the software updating system 102 and the mobile terminal 101.
- the communication between the software updating system and the mobile terminal in connection with a software update may be performed via that cellular communications network, thereby avoiding the need for additional communications interfaces in the mobile terminal.
- the communication between the mobile terminal and the software updating system may involve more than one communications networks.
- the mobile phone may communicate via a base station and a cellular telecom network with a gateway system that, in turn, provides communication with the software updating system via the Internet.
- the mobile terminal in order to update software on the mobile terminal 101, e.g. the firmware or operating system of the mobile terminal, the mobile terminal connects to the software updating system 102.
- the software updating system may connect to the mobile terminal once an updated software version is available.
- the mobile terminal sends information to the software updating system about its current software version.
- the communication is performed via a suitable updating protocol, e.g. a protocol built on top of a TCI/IP protocol.
- the software updating system Based on the information received from the mobile terminal, the software updating system generates a dedicated updating message comprising updating instructions to the mobile terminal.
- the updating instructions include the images of the memory sectors to be rewritten.
- the updating instructions are generated such that they enable the mobile terminal to generate the updated software version from the existing version already stored in the mobile terminal and from additional information included in the updating instructions.
- the update process is initiated by an update agent running on the mobile terminal.
- the update agent controls the reception and verification of the delta file. Subsequently, the update agent causes the mobile terminal to be disconnected from the network and rebooted in a patch mode. In patch mode, the changes in the delta file are applied incrementally until the new memory image is complete.
- the generation of the delta file generation may schematically be illustrated by the following operations
- the actual generation of the new version may then be performed by the mobile terminal according to the following operation
- the delta file may be applied in-place, i.e. the changes are made by the mobile terminal on the existing image, thereby requiring little additional storage. Furthermore, since only the delta file needs to be loaded and since the delta file typically is considerably smaller than the new version, the loading time is reduced by the above method. Embodiments of the code generation process will be described in greater detail below.
- Fig. 2 schematically shows a block diagram of an electronic device such as a mobile terminal.
- the mobile terminal 101 comprises a communications block 210, a processing unit 211 , and s memory unit 212.
- the communications block 210 comprises circuitry and/or devices allowing radio-based communication of data via a cellular communications network.
- the communications block 210 comprises receiver circuitry and transmitter circuitry for receiving and transmitting data signals.
- the communications block may further comprise circuitry for suitably processing the signals, e.g. modulating, coding, amplifying, etc., the signals by suitable techniques well known in the art of radio communications.
- the mobile terminal further comprises a processing unit 211 , e.g. a suitably programmed microprocessor.
- the processing unit is adapted to determine the version of the software stored in the mobile terminal, to calculate checksums of the stored software, and to generate an updated version of the software upon receipt of corresponding update instructions.
- the memory unit 212 has stored thereon the software and/or other data in a predetermined version.
- the memory 212 may comprise the firmware of the mobile terminal that implements the basic functions of the mobile terminal when loaded into and executed by the processing unit 210.
- the firmware may further comprise an operating system allowing application software to be executed.
- the memory 212 may further have stored thereon application software providing additional functionality.
- the memory 212 is addressed using a suitable address space, thereby allowing the processing unit to access selected parts of the memory.
- the memory 212 may be logically or physically divided in a plurality of memory sectors.
- the memory 212 may comprise flash memory allowing data to be written in sectors of a predetermined size.
- the memory 212 is divided in a number of sectors of a predetermined size denoted P1 , P2, P3, ..., PN. However, it is understood that any other addressing of the memory may be used, instead. It is further understood that the updating process described herein may be applied to the entire memory 212, e.g. if the entire image of the flash memory of a mobile phone is to be updated, or to only predetermined parts of the memory, e.g. if one or more software applications are to be updated.
- Fig. 3 shows a block diagram of an embodiment of a software update process.
- the linker module 302 receives a number of object files 301. Each of the object files 301 is compiled by a compiler (not shown), wherein some or all of the object files may be compiled separately from each other.
- the linker module 302 combines the object modules into an absolute file 305 ready for execution.
- One of the tasks performed by the linker module 302 is the resolution of cross-references among separately compiled object modules and the assigning of final addresses to create a single executable program 305.
- the output 305 from the linker is a file that can directly be loaded into the flash memory.
- the output 305 will also be referred to as a build file.
- the linker module 302 further receives information about a previous build file 303, e.g. in the form of an image of the corresponding address space in a flash memory where the current build is stored.
- the linker 302 may also generate a text-file representation of the memory layout of the current build, a so-called map file.
- the map file may comprise a list of functions, the addresses assigned to them, their input parameters, etc.
- the information 303 about the previous build may comprise the corresponding map file of the previous build.
- the linker module receives both the map file and the memory image of the previous build.
- the linker module 302 is adapted to generate the memory image of the new build 305 such that the new image resembles the memory image of the previous build 303 as much as possible.
- the linker is adapted to perform a number of optimisation steps in order to reduce the differences between the memory images. Examples of such optimisation steps include:
- the linker module 302 further receives one or more optimisation parameters 304 for controlling the optimisation steps.
- the optimisation parameters may determine which optimisation steps the linker should perform.
- the optimisation parameters may determine a number of limitations or boundary conditions for one or more of the optimisation steps.
- the linker may be configured to reduce, preferably to minimize, the difference between the new build and the previous build within a number of limitations or boundary conditions determined by the optimisation parameters.
- Example of optimisation parameters include - a maximum bound on the allowed padding space that the linker is allowed to introduce, - a maximum number of relays that the linker is allowed to introduce. It is understood that, in some embodiments, one or more of the above optimisation parameters may be pre-set to predetermined default values.
- Fig. 4 schematically illustrates the memory layout of a flash memory before and after a software update where the layout is optimised via an introduction of padding space.
- Fig. 4a illustrates the structure of a part of the address space of a flash memory.
- the address space 401 is divided into a number of pages denoted P1 , P2, P3, P4, P5, P6, P7, and P8.
- the pages have a predetermined size S; in a typical conventional flash memory the page size is 64 kbyte.
- Fig. 4b illustrates an example of the memory layout of a program code version V1 , generally referred to by reference numeral 402, stored in the address space 401.
- the program code version in this example comprises five object modules designated A, B, C, D, and E.
- the object modules have different sizes and are sequentially arranged in the address space 401.
- This layout is also referred to as a monolith.
- Fig. 4c illustrates an updated version V2 of the program code, generally designated 403.
- the only change between version V1 and version V2 is the replacement of module A by module A', where the module A * is assumed to be larger than the previous module A as illustrated by the additional memory space 405 required for A'.
- the remaining modules B, C, D, and E are assumed to be unchanged, i.e. identical to the corresponding portion of version V1.
- reference numeral 406 in fig. 4c when sequentially arranging the updated version V2, the entire content of memory pages P1 through P7 need to be rewritten. Pages P1 , P2, and P3 need to be rewritten, because the content of module A has changed to A', and the remaining pages need to be rewritten because the location of the modules B, C, D, and E is changed between versions V1 and V2.
- Fig. 4d illustrates an optimised memory layout of the updated program version V2, generally designated 404.
- the linker has moved module B to the end of the monolith.
- the linker has inserted a padding space of unused memory 407 between modules A' and C.
- the size of the padding space 407 is determined as to allow the start address of module C in version V2 to be the same as in the previous version V1. Consequently, the memory image of modules C, D, and E is unchanged, assuming that they do not reference entities in module B, i.e. that no references are changed.
- the optimised updated version V2 to replace the previous version V1 , i.e.
- pages P1 , P2, P3, P7, and P8 need to be re-written, as illustrated by reference numeral 408.
- the remaining pages, i.e. pages P4, P5, and P6 need not be re-written.
- the layout may be optimised by merely adding a suitable padding space ensuring an unchanged base address of module B, i.e. without moving B.
- the above optimisation of the memory layout by adding a padding space reduces the number of necessary re-writes at the cost of an increased size of the memory image corresponding to the size of the additional padding space.
- this trade-off can be controlled by a optimisation parameter that determines the maximum size of padding space allowed to be inserted by the linker.
- the relocation of memory module B in the above example may induce changes in one or more of the modules C, D, and E, if they include references to functions in module B. Such references would be affected by a re-addressing of module B.
- Modules which no other functions in the unchanged modules refer to may be freely moved, while a movement of a module that is reference by an otherwise unchanged module increases the cost in terms of the number of required re-writes. Consequently, it is preferred that the linker is configured to determine the total effect/cost of the movement of an object module in order to determine whether and which modules to move.
- the determination of the layout of the object modules in memory comprises - detecting an updated first object module having a different size than a corresponding first current object module, and an updated second object module equal to a corresponding second current object module, which updated second object module has a base address larger than the base address of the updated first object module; and - padding the detected updated first object module with a predetermined memory content of a predetermined padding size resulting in a padded updated first object module; wherein the padding size is selected to cause the base address of the updated second object module to be equal to the base address of the corresponding second current object module.
- Fig. 5 schematically illustrates the memory layout of a flash memory before and after a software update where the layout is optimised via an introduction of a relay.
- Fig. 5a illustrates the structure of a part of the address space of a flash memory.
- the address space 501 is divided into a number of pages denoted P1 , P2, P3, P4, P5, P6, P7, and P8.
- the pages have a predetermined size S.
- Fig. 5b illustrates an example of the memory layout of a program code version V1 , generally referred to by reference numeral 502, stored in the address space 501.
- the program code version comprises five object modules designated A, B, C, D, and E.
- the object modules have different sizes and are sequentially arranged in the address space 501.
- Fig. 5c illustrates an updated version V2 of the program code, generally designated 503.
- the only change between version V1 and version V2 is that module A is replaced by module A', where the module A is assumed to be larger than the previous module A as illustrated by the additional memory space 505 required for A'.
- the remaining modules B, C, D, and E are assumed to be unchanged, i.e. identical to the corresponding portion of version V1.
- reference numeral 506 in fig. 5c when sequentially arranging the updated version V2, the entire content of memory pages P1 through P7 need to be rewritten.
- Pages P1 , P2, and P3 need to be rewritten, because the content of module A has changed to A', and the remaining pages need to be rewritten because the location of the modules B, C, D, and E is changed between versions V1 and V2.
- Fig. 5d illustrates an optimised memory layout of the updated program version V2, generally designated 504.
- the linker module may split up module A' into A and A 2 ', and move module A 2 ' to the end of the monolith and change the internal references in A-T to A 2 ' accordingly, i.e. by introducing a relay.
- the linker inserts a padding space 507 such that the start address of module B remains unchanged compared to the previous version V1. Consequently, the memory image of modules B, C, D, and E is unchanged.
- pages P1 , P2, P7, and P8 need to be re-written, as illustrated by reference numeral 508.
- the remaining pages, i.e. pages P3, P4, P5, and P6 need not be re-written.
- the determination of the layout of the object modules in memory comprises - detecting an updated first object module that is larger than a corresponding first current object module; - moving a predetermined part of the updated first object module to a different memory sector resulting in a reduced updated first object module and a moved part of the updated first object module; - inserting a relay to the moved part of the updated first object module in the reduced first updated memory sector.
- Fig. 6 shows a block diagram of another embodiment of a software update process. This embodiment is similar to the embodiment described in connection with fig. 3, where like reference numerals refer to the same components.
- the linker 302 further generates a feedback signal 608 to the compiler 606 that has generated the object files 301 from a corresponding set of source files 607.
- the feedback signal causes the compiler to re-compile one or more of the source files resulting in modified object files that are more suitable for the generation of the optimised memory layout by the linker.
- the linker 302 may request the compiler 606 to generate object modules A-i' and A 2 ' instead of A'.
- the feedback signal 608 may even include information about which functions to include in each of the sub- modules.
- a linker is disclosed that is configured to reduce the number of rewrites required when updating program code in a flash memory.
- the invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer.
- several of these means can be embodied by one and the same item of hardware, e.g. a suitably programmed microprocessor or computer, and/or one or more communications interfaces as described herein.
- a suitably programmed microprocessor or computer e.g. a microprocessor or computer, and/or one or more communications interfaces as described herein.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020067017293A KR101088192B1 (en) | 2004-02-27 | 2005-01-07 | A method and system for flash memory programming |
JP2007500074A JP4903686B2 (en) | 2004-02-27 | 2005-01-07 | Flash memory programming |
US10/598,332 US8255892B2 (en) | 2004-02-27 | 2005-01-07 | Flash memory programming |
HK07111197.1A HK1106036A1 (en) | 2004-02-27 | 2007-10-17 | Flash memory programming |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US54884104P | 2004-02-27 | 2004-02-27 | |
US60/548,841 | 2004-02-27 | ||
EP04388033.5 | 2004-05-11 | ||
EP04388033A EP1569102B1 (en) | 2004-02-27 | 2004-05-11 | Flash memory programming |
US57327504P | 2004-05-20 | 2004-05-20 | |
US60/573,275 | 2004-05-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005085996A1 true WO2005085996A1 (en) | 2005-09-15 |
Family
ID=34749073
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2005/000190 WO2005085996A1 (en) | 2004-02-27 | 2005-01-07 | Flash memory programming |
Country Status (9)
Country | Link |
---|---|
US (1) | US8255892B2 (en) |
EP (1) | EP1569102B1 (en) |
JP (1) | JP4903686B2 (en) |
KR (1) | KR101088192B1 (en) |
CN (1) | CN100449486C (en) |
AT (1) | ATE466334T1 (en) |
DE (1) | DE602004026822D1 (en) |
HK (1) | HK1106036A1 (en) |
WO (1) | WO2005085996A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007164242A (en) * | 2005-12-09 | 2007-06-28 | Nec Electronics Corp | Program rewrite data creating device, program and program rewrite data creating method |
US8539471B2 (en) | 2007-12-13 | 2013-09-17 | Telefonaktiebolaget L M Ericsson (Publ) | Updating firmware of an electronic device |
Families Citing this family (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8479189B2 (en) | 2000-11-17 | 2013-07-02 | Hewlett-Packard Development Company, L.P. | Pattern detection preprocessor in an electronic device update generation system |
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 |
US8555273B1 (en) | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
US7873956B2 (en) * | 2003-09-25 | 2011-01-18 | Pantech & Curitel Communications, Inc. | Communication terminal and communication network for partially updating software, software update method, and software creation device and method therefor |
US7694291B2 (en) * | 2004-04-06 | 2010-04-06 | Hewlett-Packard Development Company, L.P. | Build optimizer tool for efficient management of software builds for mobile devices |
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 |
JP4505265B2 (en) * | 2004-06-09 | 2010-07-21 | シスメックス株式会社 | Sample analyzer and external storage medium used for sample analyzer |
US8526940B1 (en) | 2004-08-17 | 2013-09-03 | Palm, Inc. | Centralized rules repository for smart phone customer care |
US7716661B2 (en) * | 2005-03-16 | 2010-05-11 | Microsoft Corporation | Embedded device update service |
TWI345175B (en) * | 2005-06-08 | 2011-07-11 | Winbond Electronics Corp | Method for updating firmware of memory card |
DE102005059319A1 (en) * | 2005-12-09 | 2007-06-14 | Robert Bosch Gmbh | File device operating method, involves storing data, which is stored on segment, and providing data for data conditions, where portion of data is converted, and converted data is stored on another segment during operation of device |
US7660558B2 (en) | 2005-12-31 | 2010-02-09 | Adobe Systems Incorporated | Interrupting and resuming a media player |
US7603113B2 (en) | 2005-12-31 | 2009-10-13 | Adobe Systems Incorporated | Using local codecs |
US20070156841A1 (en) * | 2005-12-31 | 2007-07-05 | Govind Balakrishnan | Platform independent user interface for a mobile device |
US20070157194A1 (en) * | 2005-12-31 | 2007-07-05 | Govind Balakrishnan | Post-deployment user interface update in a mobile device |
EP2025095A2 (en) | 2006-06-08 | 2009-02-18 | Hewlett-Packard Development Company, L.P. | Device management in a network |
EP2047420A4 (en) | 2006-07-27 | 2009-11-18 | Hewlett Packard Development Co | User experience and dependency management in a mobile device |
KR20080025957A (en) * | 2006-09-19 | 2008-03-24 | 삼성전자주식회사 | Apparatus and method for upgrading of software in portable terminal |
US20080117991A1 (en) * | 2006-11-21 | 2008-05-22 | Samsung Electronics Co., Ltd. | Partitioning Compression-Based Firmware Over the Air |
US20080119178A1 (en) * | 2006-11-21 | 2008-05-22 | Samsung Electronics Co., Ltd. | Allocating Compression-Based Firmware Over the Air |
US20130167024A1 (en) | 2006-12-05 | 2013-06-27 | Adobe Systems Incorporated | Embedded document within an application |
US7681009B2 (en) * | 2006-12-28 | 2010-03-16 | Motorola, Inc. | Dynamically updateable and moveable memory zones |
US7743339B1 (en) | 2007-02-01 | 2010-06-22 | Adobe Systems Incorporated | Rendering text in a brew device |
US8589779B2 (en) | 2007-03-08 | 2013-11-19 | Adobe Systems Incorporated | Event-sensitive content for mobile devices |
US8806439B1 (en) * | 2007-04-30 | 2014-08-12 | AT & T Intellectual Property II, LP | System and method for program stack security |
EP2012230A1 (en) * | 2007-07-05 | 2009-01-07 | Samsung Electronics Co., Ltd. | Partitioning compression-based firmware over the air |
US8312447B2 (en) * | 2008-09-25 | 2012-11-13 | Microsoft Corporation | Managing updates using compiler and linker information |
CN101686340A (en) * | 2008-09-26 | 2010-03-31 | 深圳市朗科科技股份有限公司 | Method and system for expanding function of image communication equipment |
WO2012057813A1 (en) * | 2010-10-28 | 2012-05-03 | Thomson Licensing | Method for non-volatile memory reallocation for information storage |
JP5660386B2 (en) * | 2011-05-26 | 2015-01-28 | 日本電気株式会社 | Memory allocation management device, memory allocation management method, memory allocation management program, and program creation system |
US9069966B2 (en) | 2011-10-11 | 2015-06-30 | International Business Machines Corporation | Code updates in processing systems |
JP2013218388A (en) * | 2012-04-05 | 2013-10-24 | Sharp Corp | Program update device, method, program, and recording medium |
US20140058532A1 (en) * | 2012-08-23 | 2014-02-27 | GM Global Technology Operations LLC | Method for partial flashing of ecus |
US9268552B1 (en) * | 2013-06-18 | 2016-02-23 | Ayla Networks, Inc. | Patching improvement for executables in memory constrained devices |
US10353793B2 (en) | 2014-11-05 | 2019-07-16 | Oracle International Corporation | Identifying improvements to memory usage of software programs |
US10275154B2 (en) | 2014-11-05 | 2019-04-30 | Oracle International Corporation | Building memory layouts in software programs |
US9552192B2 (en) * | 2014-11-05 | 2017-01-24 | Oracle International Corporation | Context-based generation of memory layouts in software programs |
US11329683B1 (en) * | 2015-06-05 | 2022-05-10 | Life365, Inc. | Device configured for functional diagnosis and updates |
US10162547B1 (en) * | 2015-09-16 | 2018-12-25 | Marvell International Ltd. | Memory expansion in a linking process |
US9792109B2 (en) * | 2015-09-30 | 2017-10-17 | Apple Inc. | Software updating |
WO2017158663A1 (en) * | 2016-03-15 | 2017-09-21 | パナソニックIpマネジメント株式会社 | Data generation apparatus, incorporated terminal, firmware update system, and data generation method |
CN109496301A (en) * | 2017-05-19 | 2019-03-19 | 深圳配天智能技术研究院有限公司 | Method, embedded device and its storage medium of file are managed in embedded system |
KR20210079601A (en) * | 2019-12-20 | 2021-06-30 | 주식회사 실리콘웍스 | Touch system and method for updating firmware |
FR3139216A1 (en) * | 2022-08-29 | 2024-03-01 | Stmicroelectronics (Rousset) Sas | Method for generating an update file and corresponding server device, update method and corresponding client device, update method and corresponding system. |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003009136A1 (en) * | 2001-07-16 | 2003-01-30 | Yuqing Ren | Embedded software update system |
WO2003025742A2 (en) * | 2001-09-17 | 2003-03-27 | Soma Networks, Inc. | Software update method, apparatus and system |
US6560703B1 (en) * | 2000-04-18 | 2003-05-06 | International Business Machines Corporation | Redundant updatable self-booting firmware |
WO2004095457A2 (en) * | 2003-04-11 | 2004-11-04 | Bitfone Coproration | Initialization and update of software and/or firmware in electronic devices |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH033036A (en) * | 1989-05-31 | 1991-01-09 | Nec Corp | Method for correcting load module |
EP0472812B1 (en) | 1990-08-28 | 1998-05-06 | Landis & Gyr Technology Innovation AG | Method to change an object code version of a first program stored in the computer of an appliance into an object code version of a second program which was derived by at least one change to the first program |
US5699275A (en) * | 1995-04-12 | 1997-12-16 | Highwaymaster Communications, Inc. | System and method for remote patching of operating code located in a mobile unit |
US6077315A (en) * | 1995-04-17 | 2000-06-20 | Ricoh Company Ltd. | Compiling system and method for partially reconfigurable computing |
US5920723A (en) * | 1997-02-05 | 1999-07-06 | Hewlett-Packard Company | Compiler with inter-modular procedure optimization |
US7409694B2 (en) * | 1998-09-09 | 2008-08-05 | Microsoft Corporation | Highly componentized system architecture with loadable virtual memory manager |
US6401182B1 (en) * | 1999-02-10 | 2002-06-04 | International Business Machines Corporation | Method and apparatus for memory management |
JP2000293366A (en) * | 1999-04-06 | 2000-10-20 | Mitsubishi Electric Corp | Method for updating module for set top box |
US20010047512A1 (en) * | 2000-03-23 | 2001-11-29 | Leland Szewerenko | Method and system for linking multiple processors having shared memory |
JP2001344109A (en) * | 2000-05-31 | 2001-12-14 | Sony Corp | Program generating method, program generating device, and memory medium |
CA2414281C (en) * | 2000-11-17 | 2009-06-02 | Bitfone Corporation | System and method for updating and distributing information |
JP2003108397A (en) * | 2001-09-27 | 2003-04-11 | Nec Eng Ltd | Firmware rewriting method |
EP2148334B1 (en) * | 2002-01-29 | 2011-11-09 | Agere Systems Inc. | Differential flash memory programming technique |
JP3801545B2 (en) * | 2002-08-02 | 2006-07-26 | 松下電器産業株式会社 | COMPILER PROGRAM, COMPILER DEVICE, AND COMPILING METHOD |
US7275242B2 (en) * | 2002-10-04 | 2007-09-25 | Hewlett-Packard Development Company, L.P. | System and method for optimizing a program |
JP4063076B2 (en) * | 2002-12-27 | 2008-03-19 | ソニー株式会社 | Optical recording method and optical recording apparatus |
US7089270B2 (en) * | 2003-06-20 | 2006-08-08 | Innopath Software | Processing software images for use in generating difference files |
-
2004
- 2004-05-11 DE DE602004026822T patent/DE602004026822D1/en active Active
- 2004-05-11 EP EP04388033A patent/EP1569102B1/en not_active Not-in-force
- 2004-05-11 AT AT04388033T patent/ATE466334T1/en not_active IP Right Cessation
-
2005
- 2005-01-07 KR KR1020067017293A patent/KR101088192B1/en active IP Right Grant
- 2005-01-07 US US10/598,332 patent/US8255892B2/en not_active Expired - Fee Related
- 2005-01-07 WO PCT/EP2005/000190 patent/WO2005085996A1/en active Application Filing
- 2005-01-07 JP JP2007500074A patent/JP4903686B2/en not_active Expired - Fee Related
- 2005-01-07 CN CNB2005800128201A patent/CN100449486C/en not_active Expired - Fee Related
-
2007
- 2007-10-17 HK HK07111197.1A patent/HK1106036A1/en not_active IP Right Cessation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6560703B1 (en) * | 2000-04-18 | 2003-05-06 | International Business Machines Corporation | Redundant updatable self-booting firmware |
WO2003009136A1 (en) * | 2001-07-16 | 2003-01-30 | Yuqing Ren | Embedded software update system |
WO2003025742A2 (en) * | 2001-09-17 | 2003-03-27 | Soma Networks, Inc. | Software update method, apparatus and system |
WO2004095457A2 (en) * | 2003-04-11 | 2004-11-04 | Bitfone Coproration | Initialization and update of software and/or firmware in electronic devices |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007164242A (en) * | 2005-12-09 | 2007-06-28 | Nec Electronics Corp | Program rewrite data creating device, program and program rewrite data creating method |
US8539471B2 (en) | 2007-12-13 | 2013-09-17 | Telefonaktiebolaget L M Ericsson (Publ) | Updating firmware of an electronic device |
Also Published As
Publication number | Publication date |
---|---|
KR101088192B1 (en) | 2011-11-30 |
ATE466334T1 (en) | 2010-05-15 |
CN100449486C (en) | 2009-01-07 |
DE602004026822D1 (en) | 2010-06-10 |
US8255892B2 (en) | 2012-08-28 |
JP2007524171A (en) | 2007-08-23 |
CN1954291A (en) | 2007-04-25 |
KR20060127161A (en) | 2006-12-11 |
JP4903686B2 (en) | 2012-03-28 |
EP1569102A1 (en) | 2005-08-31 |
US20070220504A1 (en) | 2007-09-20 |
HK1106036A1 (en) | 2008-02-29 |
EP1569102B1 (en) | 2010-04-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1569102B1 (en) | Flash memory programming | |
EP1755034B1 (en) | Object code generation for increasing the performance of delta files | |
US8539471B2 (en) | Updating firmware of an electronic device | |
US8296535B2 (en) | Generating incremental program updates | |
US7836444B2 (en) | Mobile communication terminal having embedded system for software download and method for software download | |
CN100416500C (en) | Methods and apparatus for generating upgraded software from initial software and software upgrade packages | |
US7673300B2 (en) | Segmented linker using spatial locality of reference for over-the-air software updates | |
US7657886B1 (en) | Mobile device with a MMU for faster firmware updates in a wireless network | |
US20070294686A1 (en) | Program upgrade system and method for ota-capable device | |
EP1755039B1 (en) | Feedback linker for increased delta performance | |
EP1956482A1 (en) | Generating delta updates for a processing device | |
KR20210041972A (en) | Apparatus for updating vehicle ECU software | |
EP2778910A1 (en) | Systems and methods to extend rom functionality | |
CN102073541B (en) | Data access method and mobile terminal | |
CN106648578A (en) | Desktop layout sharing method, sending terminal and receiving terminal | |
CN103501324A (en) | Theme packaging method and device as well as server | |
KR100585788B1 (en) | Method for upgrading system software in mobile telecommunication terminal equipment | |
KR100575780B1 (en) | Method for binary data update module executing by using ota | |
KR100622816B1 (en) | System software update method and system in mobile terminal | |
WO2005122439A1 (en) | Apparatus and method for efficient generation of delta files for over-the-air upgrades in a wireless network | |
CN111782227A (en) | Data processing method, device and equipment of assembly and storage medium | |
CN117527779A (en) | Method for issuing upgrade package, server, terminal and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2007500074 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020067017293 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1133/MUMNP/2006 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580012820.1 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 1020067017293 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10598332 Country of ref document: US Ref document number: 2007220504 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase | ||
WWP | Wipo information: published in national office |
Ref document number: 10598332 Country of ref document: US |