METHOD AND APPARATUS FOR UPGRADING FIRMWARE IN AN EMBEDDED SYSTEM

Abstract: A method for upgrading firmware in an embedded system and a embedded system (110) provided with means for upgrading firmware received over a network (30) are disclosed. The method for upgrading firmware is performed from a client computer (10) to the embedded system (110) via a network connection by letting a virtual file system (122) of the embedded system (110) being shared with a client computer (10). The embedded system (110) is provided with means for upgrading firmware received over a network (30), and comprises a volatile memory (150), a persistent memory (160), a protocol stack (180) for communication over a network (30). Further it comprises a virtual file system (122), which is shareable with an operating system of a client computer (10) via the network (30), and a control means (128) for controlling a file intented for the virtual file system. Further the control means (128) comprises means for checking the characteristics of the file, and means for storing a file in the volatile memory.

Description: METHOD AND APPARATUS FOR UPGRADING FIRMWARE IN AN EMBEDDED SYSTEM Technical field of the invention The present invention relates to a method for upgrading firmware of an embedded system via a network connection. Further, the present invention relates to an embedded system provided with means for upgrading firmware received over a network, comprising; a volatile memory, a persistent memory, and a protocol stack for communication over a network. Background of the Invention The technology of data communication develops fast and the computer networks are expanding and consist of an increasing number of clients and servers. Users and owners of networks require that servers and the embedded systems thereof are up to date m accordance with the rapidly changing data communication technology. Further, an increasing part of the development of embedded systems is today performed as develop- ment of firmware. Because of the rapid development of data communication technologies and requirements of new functionality from users the firmware of an embedded system has to be upgraded frequently. Further, the use of computer networks is increasing, and today almost every company has a computer network of their own, or is at least connected to one. The increasing number of computer networks results m an increasing number of individuals responsible for the daily maintenance of networks. Many of those individuals are not specialised m computers or computer communications. Thus, the rapid development of computer communication technologies and products, and the increasing number of individuals responsible for the daily maintenance require that the firmware upgrade of the servers can be performed in a way that is easy and secure, in respect of low error probability. The upgrading of firmware is today commonly managed by connecting a computer direct to the embedded system. Further it is known to perform upgrading of firmware over the network which the server is connected to. A significant problem m upgrading the firmware of known embedded systems is that the individual performing the upgrade has to have detailed knowledge of the computer network and the embedded system and have to perform a number of rather complicated steps. Most individuals are not confident m performing said steps and are not confident in using all numerals and characteristics required to be input when performing the firmware upgrade. Further, the upgrading requires a specially designed program within the client to download the firmware upgrade to the embedded system. These aspects makes the operation of upgrading firmware of an embedded system difficult and time consuming for an individual, especially if the individual is not specially skilled m the art of computers and computer communications. In the known art an upgrade file is downloaded to the embedded system by means of a file transfer protocol. The download is performed with a special purpose program and the individual performing the download is required to specify, for example, where, in the form of a network address, the data is to be sent. Another common problem, when upgrading firmware m embedded systems, is the risk of communication failure during the firmware download. Such failure could render the embedded system inoperative, thus requiring considerate efforts to repair. US 5 812 857 discloses a method for upgrading a download code set, where an embedded system uses the same network drivers as when m normal operation. Further it describes a download where different portions of the code set are downloaded during different steps of the downloading operation. Some portions of the code set are downloaded to a flash memory via a volatile memory while some portions are downloaded directly to the flash memory. There is also described that a temporary down- loader, downloaded during an initial step and replaced by yet another downloader during a later step, is used during the operation of download. The described system and method is designed for minimising the time of executing code out of volatile memory to the persistent memory and is rather complicated. Summary of the Invention The object of the present invention is to provide a new and improved method for upgrading firmware m an embedded system and a new and improved embedded system, in respect of upgrading firmware. Another object of the invention is to provide a firmware upgrading method that is easy to use and that saves time. Yet another object of the invention is to provide a firmware upgrading method m which the probability of an erroneous upgrade is minimised. These objects, as well as other objects that will become apparent from the description below, are accomplished by a method according to claim 1 and 8 and by an embedded system according to claim 19. Preferred embodiments of the invention are disclosed m the dependent claims. Within the context of the invention the term embedded system denotes a special-purpose computer built into and integral to a server device. Wherein the server device can be, for example, a CD-server, a printer server, a file server, a communication server, etc. According to the invention, a virtual file system is used m the embedded system. This leads to the advantage that the individual starting the upgrade can be working m the volatile memory of the embedded system before it is written to the persistent memory. Thereby an error m the firmware upgrade file can be identified, e.g. by letting control means check the file, before the file replaces the firmware currently stored m the persistent memory. Such errors are generally a result of interruptions in network traffic or other network related errors . Brief Description of the Drawings Other features and advantages of the present invention will become apparent from the following detailed description of a presently preferred embodiment, with reference to the accompanying drawings . Fig. 1 is a schematic diagram of an environment of the embedded system of the invention. Fig. 2 is a schematic diagram of an embedded system and a client computer during an upgrade of firmware of the embedded system. Fig. 3 is a detailed view of a portion of the embedded system shown m Fig. 2 Fig. 4 is a diagram showing events according to the method of the invention. Detailed Description of a Presently Preferred Embodiment Referring to Fig. 1, an environment of the invention is shown where a client computer 10 and servers 100 are connected to a network 30. The servers 100 each provide a device 50 with means for communication with the client computer 10 over the network 30. The client computer 10 described herein could be any client computer of a plurality of client computers connected to the network 30. The servers 100 each comprise an embedded system 110 performing the processing of the servers 100. A firmware upgrade is started at the client computer 10 and is directed to one embedded system 110. A server 100, comprising the embedded system 110, enables devices 50 to be reached or shared via the network. The server 100 could be built in to a device 50, arrangement b, or could be external to a device 50, arrangement a . A device 50 can be any device that could be interesting to connect to a network. For example, it could be an industrial robot, a control unit or a gauge for a process or a peripheral device, such as a printer, a modem, a scanner, a fax machine, a photocopier or a multifunction peripheral. Now referring to Fig. 2, the embedded system 110 of the preferred embodiment comprises a file system 120, a volatile memory 150, a persistent memory 160, a central processing unit 170 (CPU) , at least one protocol stack 180 and a programmer 190. Within the file system 120 a virtual file system 122 (VFS) is implemented and in the virtual file system a directory for upgrading 126, hereinafter called "FLASH", is provided. In the preferred embodiment of the invention the FLiASH directory 126 is a subdirectory to a directory 124 called "SYSTEM" , which also comprises other resources . The volatile memory 150 is a memory that loses the information stored therein when the power to it is switched off and it is used to store temporary data. The persistent memory 160 is a reprogrammable memory where stored data is preserved even when the power to it is switched off. In the preferred embodiment the persistent memory 160 is a flash memory but could be any reprogrammable memory preserving data after the power has been switched of. The CPU 170 is processing the functions, protocols, etc of the embedded system. The protocol stack 180 contains the protocols for communica- tion over the network. The programmer 190, herein after called flash programmer 190, is a means for writing code into the persistent memory 160. The client computer 10 comprises an operating system having a file system 18 allowing mapping of resources 20 shared over the network 30. The server 100 related to the device 50 is mapped within the file system of the client computer. The server 100 is generally mapped m the file system 18 for other purposes than firmware upgrading. If, for example, the device 50 served by the server is a file storage device, the storage area is generally accessible from the client computer by the use of ordinary file handling commands of the operating system of the client computer 10. Thus, there is established a pointer from the file system 18 of the client computer 10 to a root directory of the file system 120 of the embedded system 110 of the server 100. Thereby, the subdirectories of the file system 120 of the embedded system 110 also are available within the file system 18 of the client computer 10. If the server 110 is not already mapped in the file system 18 of the client computer 10 for normal operation of the device 50, then the server 100 has to be mapped at the client computer 10 before performing the upgrading operation according to the invention. This arrangement results m the directories of the embedded system 110 being possible to handle within the file structure of the operating system of the client computer 10. Further, the directories of the embedded system 110 can be accessed as if they where directories of the client computer 10, using ordinary file handling commands . Referring now to Fig. 3, showing the FLASH directory 126 within the virtual file system 122 of the embedded system 110. There is a control means, realised by a data channel 128, associated with the FLASH directory 126. Hereinafter this data channel 128 is referred to as flash data channel 128. The flash data channel 128 is reset every time the FLASH directory 126 is accessed The flash channel is allocated a portion of the volatile memory 150 for storing data. The flash data channel 128 handles all data sent to the FLASH directory 126 and is specially designed to handle firmware upgrade files and to perform various control operations on the data received. To perform said control operations the flash data channel 128 comprises means for checking the characteristics of the file, namely first checking means 131, second checking means 132 and third checking means 133, and means 130 for storing data of a file m the volatile memory 150. Said checking and storing means are realised by program code related to the flash data channel 128 .The first checking means 131 checks if the file is a firmware upgrade file by checking for a "magic number", described below. The second checking means 132 checks if the file stored m the volatile memory 150 is intended for the product related to the embedded system 110. The third checking means 133 checks the checksum of the file to decide if there are any errors m the file. Further the flash data channel 128 provides a flash programmer 190 with the approved firmware upgrade files to have the firmware upgrade file written to the persistent memory 160. A more detailed description of the functions of the flash data channel is found below, m the description of the method. Now referring to Figs. 2 and 4, describing the preferred method for upgrading firmware . We presume that the server 100 has been mapped m the file system 18 of the client computer 10. Let us assume that an user is interested m upgrading the firmware of a server with a firmware upgrade file 24, which he has received from the manufacturer of the server 100 and has stored on the hard disk 22 of the client computer 10. It should be understood that the firmware upgrade file of course could be stored on any storage unit accessible from the client computer 10. The user then uses the ordinary file handling commands, for the present operating system, to copy or move the firmware upgrade file 24 to the FLASH directory. In the preferred embodiment the individual "drags and drops" 28 the firmware upgrade file 24 to the representation of the FLASH directory 26 within the client computer. The client computer 10 thereafter sends an instruction to the embedded system telling it to open a flash file, step 402, within the virtual file system 122 of the embedded system. Thereafter, the flash data channel is reset, step 404, and data of the firmware upgrade file 24 is received and stored, step 406, m the volatile memory 150. The flash data channel controls the data during reception, step 408, checking for an identifier m the form of "a magic number" corresponding to an identifier confirming that the data received belongs to a firmware upgrade file. The check, in step 408, for a magic number identifying the data as a firmware upgrade file, checks a predefined position m the data file for the "magic number" . Preferably the magic number is positioned at the beginning of the firmware upgrade file. If the magic number corresponding to a firmware upgrade file does not occur at the predefined position m step 408, then the data of the file does not belong to a firmware upgrade file. As a result thereof an error message is sent, step 422, to the client and the file transmission is terminated. If a magic number corresponding to a firmware upgrade file 24 is received, step 408, then the reception of data continues, steps 412, 414, until all data of the firmware upgrade file is stored m the volatile memory 150. When all data of a firmware upgrade file has been received the flash data cnannel controls the checksum, step 418, of the received file. If the checksum is not correct then the received file is corrupt. As a result thereof an error message is sent, step 422, to the client computer and the upgrading operation of the embedded system is terminated. If the checksum is correct then the flash data channel is checking, step 420, for a product identifier within the file telling what product the firmware upgrade file is intended for. If the identifier does not corre- spond to the server product then an error message is sent, step 422, to the client computer and the upgrading operation of the embedded system is terminated. If the product identifier is correct, then the flash programmer 190 is ordered to erase at least a portion of the memory and then write, step 424, the firmware upgrade file in the volatile memory 150 to the flash memory 160. When the firmware upgrade file has been written to the flash memory 160 the flash file is closed, which is indicated at the client computer in a similar way as when an ordinary file transfer has been completed.

Claims: CLAIMS 1. A method for upgrading firmware m an embedded system (110) from a client computer (10) via a network connection, comprising the steps of: sharing a virtual file system (122) of the embedded system (110) with the client computer (10) m such a way that the virtual file system (122) can be utilised within the operating system of the client computer (10) , sending data of a firmware upgrade file over the network (30) from the client computer (10) to the embedded system (110) as a result of the upgrade file being copied or moved (28) to a directory (26) , within the file system (18) of the client computer (10) , which directory (26) represents a link to the virtual file system (122) of the embedded system (110), receiving (406, 412) , from the client computer (10) , data of a firmware upgrade file at the virtual file system (122) of the embedded system (110) via the link, storing (406, 412) the data of the firmware upgrade file m a volatile memory (150) of the embedded system (110) connected to the virtual file system (122) , and writing (424) the firmware upgrade file from the volatile memory (150) of the embedded system (110) to a persistent memory (160) of the embedded system (110) . 2. Method according to claim 1, further comprising the step of controlling (408) if data received at the virtual file system (122) corresponds to a firmware upgrade file. 3. Method according to claim 2, further comprising, when the data received corresponds to a firmware upgrade file, the step of checking (420) if the firmware upgrade file stored m the volatile memory (150) is intended for the product type of the embedded system (110) . 4. Method according to claim 2 or 3 , further comprising, wnen the data received corresponds to a firmware upgrade file, the step of checking (418) the checksum of the received file. 5. Method according to any of claims 2-4, comprising the step of sending an error message (422) from the embedded system (110) to the client computer (10) when the data received does not correspond to a valid firmware upgrade file. 6. Method according to any of claims 1-5, wherein the protocols (180) used during the reception of the firmware upgrade file are the protocols (180) previously used by the embedded system (110) during the normal operation. 7. Method according to any of claims 1-6, wherein the received data of a firmware upgrade file is controlled within the embedded system by a data channel (128) of the virtual file system (122) . 8. A method for upgrading firmware of an embedded system (110) over a network connection, comprising the steps of : sharing a virtual file system (122) of the embedded system (110) with an external computer (10) via the network connection m such a way that the virtual file system (122) can be utilised by the operating system of the external computer (10) as if it was part of the file system of the external computer (10) , receiving (406) data of a firmware upgrade file at the virtual file system (122) of the embedded system (110) via the network connection. storing (406) the data of the firmware upgrade file in a volatile memory (150) connected to the virtual file system (122) , and writing (424) the firmware upgrade file from the volatile memory (150) to a persistent memory (160) . 9. Method according to claim 8, further comprising the step of controlling (408) if data received at the virtual file system (122) corresponds to a firmware upgrade file. 10. Method according to claim 9, further comprising, when the data received corresponds to a firmware upgrade file, the step of checking (420) if the stored firmware upgrade file is intended for the product type of the device (50) . 11. Method according to claim 9 or 10, further comprising, when the data received corresponds to a firmware upgrade file, the step of checking (418) the checksum of the received file. 12. Method according to claim 9, comprising the step of sending an error message (422) when the data received does not correspond to a firmware upgrade file. 13. Method according to claim 10, comprising the step of sending an error message (422) when the stored firmware upgrade file is not intended for the product type of the device (50) . 14. Method according to any of claims 8-13, comprising the step of erasing at least a portion of the persistent memory (160) after reception of a correct firmware upgrade file and before writing (424) said file to the persistent memory (160) . 15. Method according to any of claims 8-14, wherein the protocols (180) used during the reception of the firmware upgrade file are the protocols (180) previously used by the device (50) during the normal operation. 16. Method according to any of claims 8-15, wherein the received data of a firmware upgrade file is controlled by a data channel (128) of the virtual file system (122) . 17. Method according to any of claims 8-16, wherein the step of writing (424) the firmware upgrade file from the volatile memory (150) to the persistent memory (160) is preceded by all data of the firmware upgrade file being located m the volatile memory (150) . 18. Method according to any of claims 8-17, wherein the virtual file system (122) is mapped within a client computer (10) m such way that the virtual file system (122) can be utilised within the operating system of the client computer (10) . 19. An embedded system (110) provided with means for upgrading firmware received over a network (30) , compris- ing: a volatile memory (150) , a persistent memory (160) , a protocol stack (180) for communication over a network (30) , and a virtual file system (122) which is shareable with an operating system of a client computer (10) via the network (30), for upgrading said firmware. 20. A system (110) according to claim 19, further comprising a control means (128) for controlling a file intended for the virtual file system (122) , wherein the control means (128) comprises means (131, 132, 133) for checking the characteristics of the file, and means (130) for storing a file in the volatile memory (150) . 21. A system (110) according to claim 20, wherein the virtual file system (122) comprises an upgrading directory (126) and wherein the control means (128) is arranged to control a file intended for the upgrading directory (126) . 22. A system (110) according to claim 20 or 21, wherein a first means (131) for checking the characteristics of the file is arranged to check that the file is a firmware upgrade file. 23. A system (110) according to any one of claims 20-22, wherein a second means (132) for checking the characteristics of the file is arranged to check that a received firmware upgrade file is a firmware upgrade file intended for the product the embedded system (110) is representing. 24. A system (110) according to any one of claims 20-23, wherein a third means (133) for checking the characteristics of the file is arranged to check the checksum of a received firmware upgrade file. 25. A system (110) according to any one of claims 19-24, wherein a common protocol stack (180) for communication over the network (30) is used during normal operation and during download.

Inventors: STARVIK MIKAEL, STEN PER, STARVIK, MIKAEL, STEN, PER
Applicants: AXIS AB, STARVIK MIKAEL, STEN PER, STARVIK, MIKAEL, STEN, PER
Application year: 2000
Main classification: G06F9
IPC codes: G06F9, G06F11