CN101539862A - Firmware update method and firmware framework - Google Patents
Firmware update method and firmware framework Download PDFInfo
- Publication number
- CN101539862A CN101539862A CN200810086747A CN200810086747A CN101539862A CN 101539862 A CN101539862 A CN 101539862A CN 200810086747 A CN200810086747 A CN 200810086747A CN 200810086747 A CN200810086747 A CN 200810086747A CN 101539862 A CN101539862 A CN 101539862A
- Authority
- CN
- China
- Prior art keywords
- report
- burning
- firmware
- usb
- output characteristic
- 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.)
- Pending
Links
Images
Abstract
The invention provides a firmware update method and a firmware framework. An application program calls a writing report request and a reading report request which are used for passing the load of a characteristic report and transferring commands or data of a humanistic interface device to complete a firmware updating program.
Description
Technical field
The present invention is relevant for USB (universal serial bus) (universal serial bus, USB) interface, especially relevant for a kind of humanization interface device (human interface device, (firmware) update method of firmware HID) and firmware framework of tool USB interface.
Background technology
Traditionally, main frame (host) has two kinds of embodiments if will carry out firmware update to a USB HID: first kind of mode is, the standard driver unloading (uninstall) that must earlier operating system (operating system) be provided, operating system scans the USB HID that this desire is upgraded firmware again, to carry out a bus enumeration (enumeration); Then, the driver that burning is used is installed, last, see through this burning and this USB HID is carried out all burning actions with driver.Utilize the benefit of this kind mode to be, this burning can be controlled this USB HID fully with driver, and transmits the read write command of burning by control type transmission (control transfer), interrupt-type transmission (interrupt transfer) or flood tide type transmission (bulk transfer).Yet in real work of part and application, this burning produces with having compatible problem between driver and personal computer (or operating system).
The second way mainly is that the standard USB HID driver that utilizes operating system to provide carries out the burning action, though this kind mode can be avoided compatible problem, if but the USB HID of this connection is mouse or keyboard, the control disposer (control handier) that then is used for controlling this USB HID can be stopped by some operating system (for example Windows XP and Windows Vista etc.).At this moment, program developer can only be declared (declare), and another does not belong to the interface of mouse and keyboard, and this is also meaning at least one end points (endpoint) and has been consumed.
On the other hand, for the firmware flow process of general USB HID, when normal mode of operation (generalworking mode) switched to burning pattern (in system programming mode), bus enumeration of recast be the reasons are as follows again.First: firmware operates when the burning pattern, and the main frame of connection need be installed another USB driver and carry out the burning action.Second: the employed transfer line of burning pattern (transfer pipe) can't and be deposited with the employed transfer line of normal mode of operation.A because hundreds of millisecond (millisecond) when bus enumeration of execution approximately costs, elongated the T.T. of whole burning firmware virtually, if still adopt this mode to upgrade firmware during volume production, then the bus enumeration time will occupy very big proportion in the whole renewal firmware time, significantly increases time cost.For addressing the above problem, therefore the present invention is proposed.
Summary of the invention
Because the problems referred to above, one of purpose of the present invention provides a kind of firmware update, can see through standard USB HID driver and come access one USB HID device, more this USB HID device can be switched to the burning pattern from normal mode of operation, and need not do the replacement of software or hardware.
For reaching above-mentioned purpose, firmware update of the present invention, be applied between a main frame (host) and the humanization interface device, this main frame has an application program and is connected to this humanization interface device through a universal sequential bus interface, this humanization interface device has one first firmware, the method includes the steps of: a setting up procedure, call out one via this application program and write report request (Set_Report), give this first firmware to transmit output characteristic report (feature report); One deciding step, according to this feature output report content that this first firmware receives, whether decision will switch to a burning pattern from a normal mode of operation; And, a burning step, after this first firmware switched to this burning pattern, this application program was called out this and is write the report request, and the loading in order to by this output characteristic report carries out burning to this humanization interface device.
The present invention also provides a kind of firmware update, be applied to a main frame, described main frame has an application program, described method comprises following steps: see through a universal sequential bus interface described main frame is connected to a humanization interface device, described humanization interface device has one first firmware; Carry out a burning pattern bus enumeration; And carry out burning, and call out one by described application program and write the report request, utilize the loading of output characteristic report, described humanization interface device is carried out burning.
Another purpose of the present invention provides a kind of firmware framework of USB device, comprise: a burning module, has one the one USB transfer function, and utilize a USB interface to realize a burning function, wherein, when receiving one when writing report request (Set_Report), carry out burning according to this content that writes one first report of report request; One common operational module, has one the 2nd USB transfer function, and utilize the 2nd USB transfer function to realize a specific products characteristic, wherein, when receiving a report content when equaling a default value, this common operational module is preserved a USB state and forbidden energy all and the irrelevant interruption of USB, and switches to this burning module; And a pattern judge module in order to according to a mode flag, determines to start this common operational module or this burning module.
Now the detailed description and the claim scope that cooperate following diagram, embodiment, will on address other purpose of the present invention and advantage and be specified in after.
Description of drawings
Fig. 1 shows the data stream between a main frame and the HID.
Fig. 2 is the process flow diagram of first embodiment of firmware update of the present invention.
Fig. 3 A and Fig. 3 B are the firmware process flow diagram of HID of the present invention.
Fig. 4 is the process flow diagram of second embodiment of firmware update of the present invention.
Fig. 5 A and Fig. 5 B are the firmware process flow diagram of USB device of the present invention.
Fig. 6 is the configuration diagram of an embodiment of firmware framework of the present invention.
Drawing reference numeral:
110 main frames, 111 application programs
112 standard USB HID drivers
120 humanization interface devices, 121 USB engines
122 firmwares, 130 USB interface
600 firmware frameworks, 610 pattern judge modules
620 burning modules, 630 common operational modules
Embodiment
Operating system system in this instructions illustrates as example that with windows XP firmware update only of the present invention also can be applicable to other operating system, as long as can support or meet the standard of USB.
Fig. 1 shows the data stream between a main frame and the HID.With reference to figure 1, the communication construction between relevant calculation machine host 110 and the HID 120 is divided into two layers in main frame 110: application program 111 and standard USB HID driver 112, in HID 120, also divide into two layers: USB engine 121 and firmware 122.Wherein, the actual executor of usb communication is driver 112 and USB engine 121, and they are responsible for setting up the transmission package, separate package and check communications protocol.
In the standard of existing USB, Set_Report and Get_Report all belong to the specific request of classification (class-specific request) instruction, and application program 111 is called out after the Set_Report instruction, is allowed to transmit one and reports to HID 120.And after application program 111 was called out the Get_Report instruction, HID 120 was allowed to transmit one by control type pipeline (control pipe) and reports to main frame 110.Report wherein has three kinds of kenels: input (input) report, output (output) report and feature (feature) report.
Characteristic of the present invention is the request that utilizes standard USB HID driver to provide or support: Set_Report (Feature) and Get_Report (Feature), in order between main frame 110 and HID 120, to transmit required burning program and the data of firmware update, as shown in Figure 1.In other words, the present invention utilizes above-mentioned two requests as one group of output/input channel, with the program downloaded and the data feature report that disguises oneself as, to carry out the firmware update action of HID, can successfully avoid the interception of operating systems such as Windows XP and WindowsVista, and extra driver need not be installed again, increased the convenience of firmware update greatly.
For the feature report that convenient application program 111 after a while can utilize Set_Report (Feature) and Get_Report (Feature) to be transmitted is smoothly come load module and relevant information, to carry out follow-up burning action, for HID 120, be standard and the agreement that meets USB, some relevant information (as the length of feature report etc.) are arranged, must declare report size (Report Size) project (item) and report count value (Report Count) project in unit (report descriptor) is described in report in advance, for example: the length of supposing the feature report equals 8 bytes (bytes), report that then the data in the size project must be declared as 8 with reporting the data in the count value project, just: Report Size (8), Report Count (8).According to this, connect in the performed bus enumeration of main frame 110 at HID 120 after a while, main frame 110 just can be obtained attribute and the function mode of HID 120, and application program 111 just can be called out Set_Report (Feature) and Get_Report (Feature) smoothly after a while.For avoiding confusion, when calling out Set_Report (feature), application program 111 is passed to the feature report of HID 120 by main frame 110, below be referred to as the output characteristic report.And application program 111 is back to the feature report of main frame 110 when calling out Get_Report (feature) by HID 120, below is referred to as the input feature vector report, as shown in Figure 1.On using, it is not necessarily identical with the length of input feature vector report that output characteristic is reported, also must describe in the unit in the HID report certainly and separately declare to differentiate now.
Fig. 2 is the process flow diagram of first embodiment of firmware update of the present invention.Fig. 3 A and Fig. 3 B are the firmware process flow diagram of HID of the present invention.
Before first embodiment of the invention begins to carry out, at first introduce present HID 120 residing states.What suppose HID 120 is a mouse, has connected main frame 110 and uses in (promptly in normal mode of operation) normal, so be the state (step S322, Fig. 3 A) that is in execution normal mode of operation USB program at present.Certainly, before entering step S322, the work that mode flag is judged (step S310, the initial value of mode flag MF are normal mode of operation), normal mode of operation initialization (step S320) and normal mode of operation bus enumeration (step S321) is crossed in the micro controller of HID 120 (figure does not show) executed.And normal mode of operation USB program has the USB transfer function among the step S322, and can utilize this USB transfer function to realize all characteristics of mouse, simultaneously, also can the response application program 111 standard request (standard request) of calling out and the specific request of classification.
Below, based on Fig. 2, Fig. 3 A and Fig. 3 B are auxilliary, and firmware update of the present invention is described.
Step S210: application program 111 is called out Set_Report (feature), to transmit the output characteristic report (supposing that length is 8 bytes) of certain content, starts whole firmware update program.After operating system is received this request, can see through declaration that USB HID driver 112 checks whether HID 120 have an output characteristic report with and the length of declaration whether correct.If success, because the output characteristic report is to see through control type transmission (Control Transfer) to transmit, operating system sees through the USB HID driver 112 of lower floor again, this request is sent to usb 1 30 in the setting stage (Setup Stage), then, with the default value of 8 bytes content as the output characteristic report, (Data Stage) is sent to usb 1 30 at data phase again.
Step S220:HID 120 receives aforementioned request and output characteristic report.
Whether step S230:HID 120 decisions switch to the burning pattern.Contrast Fig. 3 A, this moment, the micro controller (figure does not show) of HID 120 can judge whether to receive Set_Report (feature) request (step S323) continuously, and the output characteristic report content that receives whether correct (step S324).If all correct, then jump to step S240, otherwise, get back to step S220.
Step S240: switch to the burning pattern.Contrast Fig. 3 A, before entering the burning pattern from normal mode of operation, micro controller can be carried out the state initialization (step S325) of USB, and its content comprises: preserve all interruptions (interrupt) that have nothing to do with USB of the USB state enter before the burning pattern and forbidden energy (disable).Wherein, need the USB state of preservation to comprise: the length of output characteristic report, the length of input feature vector report, feature report identification code (report ID) are present in not, enabled status and time-out (halt) state, USB address and configuration state (configured state) or the like of each end points (endpoint).
The present invention is by preserving above-mentioned USB state, the micro controller of HID 120 can successfully enter the burning pattern from normal mode of operation under main frame 110 unwitting situations, the time of about several microseconds of only use (microsecond), also must re-execute burning pattern initialization (step S330) and burning pattern bus enumeration (step S340) compared to conventional practice, reduce the T.T. of whole firmware update greatly.
Step S250: carry out the burning action.The burning action here includes closes all burning orders of carrying out firmware update, for example: " obtaining firmware version ", " password comparison ", " switching working mode ", " removing flash memory (flash erase) ", " section is removed (sector erase) ", " sequencing (program) flash memory ", " reading flash memory " or the like burning order.Because 8 byte content of output characteristic report are responsible for decipher (just manufacturer defines voluntarily) by the USB engine 121 that receives, therefore, the content of each output characteristic report can optionally be inserted a burning order or a related data by application software 111.Application program 111 is according to the length of a firmware to be updated and the length (is 8 bytes in this hypothesis) of output characteristic report, but repeated call Set_Report (feature), by the loading of this output characteristic report, this firmware to be updated is loaded in the Nonvolatile memory (figure does not show) of HID 120.Otherwise during as if related data that will read HID 120 or state, then application program 111 is called out Get_Report (feature), and the loading by the input feature vector report passes back to data or state in the main frame 110.
Contrast Fig. 3 B, after normal mode of operation enters the burning pattern, micro controller begins to carry out burning pattern USB program (step S350), and this burning pattern USB program also has the USB transfer function, and can utilize usb 1 30 to realize firmware updating function.After micro controller is received Set_Report (feature) request (step S360), can go to capture the burning order of output characteristic report, judge whether to want sequencing firmware (step S362), if jump to step S364, to carry out the sequencing action; Otherwise, jump to step S366, to handle the burning order.After micro controller is received Get_Report (feature) request (step S370), can remove to judge whether to read itself data or state (step S372), if, jump to step S374, read to carry out data or state; Otherwise, jump to step S376, to respond request.In the burning process, micro controller can judge whether that the firmware update program finishes (step S380), if jump to step S382, to carry out USB unloading (step S382); Otherwise, get back to step S350, proceed burning.The USB unloading that above-mentioned steps S382 carried out mainly is the hardware USB function forbidden energy with HID 120, allows main frame 110 think that HID 120 has broken.Afterwards, micro controller is again with hardware USB function activation (enable), allow main frame 110 think that HID 120 has reconnected, micro controller just can be got back to normal mode of operation, re-execute a normal mode of operation initialization (step S320) and normal mode of operation bus enumeration (step S321), simultaneously, also finish whole firmware update program, the user can enjoy the firmware function of latest update.
Can see of the present invention two big advantages from above-mentioned whole firmware update process: first advantage is to save time, the present invention can significantly save replacement and the initialization of plug and software and the time of bus enumeration of hardware by directly switching to the burning pattern from normal mode of operation.Second convenience that advantage is to use, extra install driver, but just one-step installation is finished.
On the other hand, firmware update of the present invention not only can be applicable to the situation that HID 120 has been connected to main frame 110 and has entered normal mode of operation, can be applicable to the situation that HID 120 and main frame 110 are not connected as yet too.
Fig. 4 is the process flow diagram of second embodiment of firmware update of the present invention.Below with reference to Fig. 4 illustrate second embodiment of the invention the institute in steps.
Step S410: HID 120 is connected to main frame 110.
Step S420: firmware enters the burning pattern.Whether contrast Fig. 3 B can judgment model flag MF be burning pattern (step S310) after HID 120 starts.If, jumping to step S320, firmware enters the burning pattern and carries out burning pattern initial work.For example in the volume production stage, the predeterminable burning pattern that equals of above-mentioned pattern flag Invited-for MF is conveniently to be written into firmware.
Step S430: carry out burning pattern bus enumeration.As mentioned above, at this moment, HID 120 must be with the length of output characteristic report with the input feature vector report, declare that main frame 110 just can be obtained attribute and the function mode of HID 120 in report size (Report Size) project (item) and report count value (Report Count) project in unit (report descriptor) is described in report.
Step S440: carry out the burning action.According to the length of a firmware to be updated and the length of output characteristic report, but application program 111 repeated call Set_Report (feature), loading with by this output characteristic report imports burning order or related data into HID 120, and USB engine 121 is responsible for decipher again and is carried out it.Certainly, during as if data that will read HID 120 or state, application program 111 is called out Get_Report (feature), and the loading by the input feature vector report passes back to data or state in the main frame 110.Situation is discussed in above-mentioned steps S250 in detail, repeats no more here.
As mentioned above, utilize the firmware framework of Fig. 3 A and Fig. 3 B, when carrying out the burning action between main frame 110 and the HID 120, see through Get_Report (feature) and upload and down-transmitting data with two pipelines of Set_Report (feature), the control disposer that just can avoid controlling HID 120 is stopped by Windows XP.Note that when the firmware framework of Fig. 3 A and Fig. 3 B is applied in general USB device, with regard to the problem that does not have operating system to stop.Therefore, when between main frame 110 and general USB device (non-mouse and non-keyboard), carrying out the burning action, except this group pipeline that can see through Get_Report (feature) and Set_Report (feature), also can see through another group pipeline: promptly Get_Report (IN) uploads and down-transmitting data with Set_Report (OUT), shown in step S560, the S570 of step S523, the S524 of Fig. 5 A and Fig. 5 B.
Fig. 6 is the configuration diagram of an embodiment of firmware framework of the present invention.With reference to figure 6, firmware framework 600 of the present invention is applicable to all USB devices, comprises: a burning module 620, one a common operational module 630 and a pattern judge module 610.
After the start of USB device, the initial value of pattern judge module 610 meeting judgment model flag MF decides to start common operational module 630 or burning module 620; When supposing MF=W, pattern judge module 610 starts common operational module 630; And during MF=I, pattern judge module 610 starts burning modules 620.Burning module 620 has one the one USB transfer function, realizes a burning function in order to utilize a USB interface.After burning module 620 is activated, when receiving a Set_Report (feature) request or a Set_Report (OUT) request, promptly carry out burning according to the content of corresponding output characteristic report or output report; When receiving a Get_Report (feature) request or a Get_Report (IN) request, then, data or state are passed back in the main frame 110 by the loading of input feature vector report or input report.Dotted line among Fig. 6 is represented, might not switch back common operational module 630 after the burning action is finished, and decides on situation or demand fully.For example, in the volume production stage, just needn't the common operational module 630 of switchback; And if during for user online updating firmware, then need the common operational module 630 of switchback, use and go up facility more.
Common operational module 630 has one the 2nd USB transfer function, realizes a specific products characteristic (for example mouse or printer) in order to utilize the 2nd USB transfer function.After common operational module 630 is activated, when receiving a Set_Report (feature) request or a Set_Report (OUT) request, and the content of output characteristic report or output report is when equaling a default value, common operational module 630 is preserved present USB state and forbidden energy all and the irrelevant interruption of USB immediately, to switch to burning module 620.
The specific embodiment that is proposed in the detailed description of preferred embodiment is only in order to convenient explanation technology contents of the present invention, but not with narrow sense of the present invention be limited to the foregoing description, in the situation that does not exceed spirit of the present invention and claim scope, the many variations of being done is implemented, and all belongs to scope of the present invention.
Claims (27)
1. firmware update, be applied between a main frame and the humanization interface device, described main frame has an application program and is connected to described humanization interface device through a universal sequential bus interface, described humanization interface device has one first firmware, and described method comprises following steps:
One setting up procedure is called out one via described application program and is write the report request, reports to described first firmware to transmit an output characteristic;
One deciding step, according to the described feature output report content that described first firmware receives, whether decision will switch to a burning pattern from a normal mode of operation; And
One burning step, after described first firmware switched to described burning pattern, described application program was called out the described report request that writes, and the loading in order to by described output characteristic report carries out burning to described humanization interface device.
2. firmware update as claimed in claim 1, wherein said burning step more comprises:
According to the length of one second firmware and the length of described output characteristic report, described application program is called out the described report request that writes with a corresponding number of times, loading in order to by described output characteristic report is written into described second firmware in the described humanization interface device.
3. firmware update as claimed in claim 1, wherein said burning step more comprises:
Described application program sees through calling one and reads the report request, in order to the loading of reporting by a described input feature vector that reads the report request, with state or the data that return described humanization interface device.
4. firmware update as claimed in claim 3, the content of wherein said input feature vector report is data.
5. firmware update as claimed in claim 3 wherein more comprised following steps before described setting up procedure:
Carry out a normal mode of operation bus enumeration, in order to describe the length of the described input feature vector report of declaration in the unit in HID report.
6. firmware update as claimed in claim 5, wherein said execution in step more comprises:
According to the length of described input feature vector report, declare input feature vector report size project and input feature vector report count value project that described HID report description is first.
7. firmware update as claimed in claim 1 wherein more comprised following steps before described setting up procedure:
Carry out a normal mode of operation bus enumeration, in order to describe the length of the described output characteristic report of declaration in the unit in HID report.
8. firmware update as claimed in claim 7, wherein said execution in step more comprises:
According to the length of described output characteristic report, declare output characteristic report size project and output characteristic report count value project that described HID report description is first.
9. firmware update as claimed in claim 1, wherein said deciding step also comprises:
Before entering described burning pattern, described first firmware is preserved a USB state.
10. length, the feature report identification code that firmware update as claimed in claim 9, wherein said USB state comprise the length of described output characteristic report, the report of described input feature vector is present in not, the enabled status of each end points and halted state, USB address and configuration state one of them or its combination.
11. firmware update as claimed in claim 1, wherein said deciding step also comprises:
Before entering described burning pattern, the interruption that the described first firmware forbidden energy all and USB are irrelevant.
12. firmware update as claimed in claim 1, the content of wherein said output characteristic report comprise a burning order and data one of them or its combination, and described burning order is manufacturer's definition.
13. a firmware update is applied to a main frame, described main frame has an application program, and described method comprises following steps:
See through a universal sequential bus interface described main frame is connected to a humanization interface device, described humanization interface device has one first firmware;
Carry out a burning pattern bus enumeration; And
Carry out burning, call out one by described application program and write the report request, utilize the loading of output characteristic report, described humanization interface device is carried out burning.
14. firmware update as claimed in claim 13, wherein said burning step more comprises:
According to the length of one second firmware and the length of described output characteristic report, described application program is called out the described report request that writes with a corresponding number of times, loading in order to by described output characteristic report is written into described second firmware in the described humanization interface device.
15. firmware update as claimed in claim 13, wherein said burning step more comprises:
Described application program sees through calling one and reads the report request, and the loading that utilizes a described input feature vector that reads the report request to report is with state or the data that return described humanization interface device.
16. firmware update as claimed in claim 15, the content of wherein said input feature vector report is data.
17. firmware update as claimed in claim 15, the described burning pattern of wherein said execution bus enumeration step comprises:
Describe in the unit in HID report, declare the length of described input feature vector report.
18. firmware update as claimed in claim 17, wherein said announce step more comprises:
According to the length of described input feature vector report, declare input feature vector report size project and input feature vector report count value project that described HID report description is first.
19. firmware update as claimed in claim 13, the described burning pattern of wherein said execution bus enumeration step comprises:
Describe in the unit in HID report, declare the length of described output characteristic report.
20. firmware update as claimed in claim 19, wherein said announce step more comprises:
According to the length of described output characteristic report, declare output characteristic report size project and output characteristic report count value project that described HID report description is first.
21. firmware update as claimed in claim 13, the content of wherein said output characteristic report comprise a burning order and data one of them or its combination, and described burning order is manufacturer's definition.
22. the firmware framework of a USB device is characterized in that, the firmware framework of described USB device comprises:
One burning module has one the one USB transfer function, realizes a burning function in order to utilize a USB interface, wherein, writes when request report when receiving one, and described burning module carries out burning according to the described content that writes one first report of report request;
One common operational module, has one the 2nd USB transfer function, realize a specific products characteristic in order to utilize described the 2nd USB transfer function, wherein, when receiving a report content when equaling a default value, described common operational module is preserved a USB state and forbidden energy all and the irrelevant interruption of USB, and switches to described burning module; And
One pattern judge module in order to according to a mode flag, determines to start described common operational module or described burning module.
23. the firmware framework of USB device as claimed in claim 22 is characterized in that, described burning module more comprises:
Read when request report when receiving one, by the described loading that reads one second report of report request, with state or the data that return described USB device.
24. the firmware framework of USB device as claimed in claim 23 is characterized in that, described second is reported as an input feature vector report or an input report, and the content of described second report is data.
25. the firmware framework of USB device as claimed in claim 23, it is characterized in that length, the feature report identification code that described USB state comprises the length of described first report, described second report is present in not, the enabled status of each end points and halted state, USB address and configuration state one of them or its combination.
26. the firmware framework of USB device as claimed in claim 22 is characterized in that, described first is reported as an output characteristic report or an output report, and the content of described first report comprises a burning order and data one of them or its combination.
27. the firmware framework of USB device as claimed in claim 22 is characterized in that, described burning module can switch to described common operational module after finishing all burning actions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810086747A CN101539862A (en) | 2008-03-20 | 2008-03-20 | Firmware update method and firmware framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810086747A CN101539862A (en) | 2008-03-20 | 2008-03-20 | Firmware update method and firmware framework |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101539862A true CN101539862A (en) | 2009-09-23 |
Family
ID=41123064
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810086747A Pending CN101539862A (en) | 2008-03-20 | 2008-03-20 | Firmware update method and firmware framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101539862A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855149A (en) * | 2012-08-02 | 2013-01-02 | 福建伊时代信息科技股份有限公司 | Chip operating system update method, device and system |
| CN104683959A (en) * | 2013-11-27 | 2015-06-03 | 深圳市盛天龙视听科技有限公司 | Instant messaging type portable audio device and account number loading method thereof |
| CN101694642B (en) * | 2009-10-21 | 2015-07-22 | 中兴通讯股份有限公司 | Updating method of data card and device thereof |
| CN105808465A (en) * | 2016-03-04 | 2016-07-27 | 浙江大华技术股份有限公司 | Method and device for upgrading camera equipment |
| CN108280034A (en) * | 2018-01-30 | 2018-07-13 | 深圳市宏电技术股份有限公司 | A kind of Android system USB-HID apparatus self-adaptation method and devices |
| CN109002302A (en) * | 2017-05-25 | 2018-12-14 | 佛山市顺德区顺达电脑厂有限公司 | The firmware update of management engine |
| CN109656583A (en) * | 2018-12-28 | 2019-04-19 | 北京深思数盾科技股份有限公司 | Method for burning chip, host computer and chip burn-recording system |
| CN113467799A (en) * | 2020-03-31 | 2021-10-01 | 精工爱普生株式会社 | Update system, printing device, and program storage medium |
-
2008
- 2008-03-20 CN CN200810086747A patent/CN101539862A/en active Pending
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101694642B (en) * | 2009-10-21 | 2015-07-22 | 中兴通讯股份有限公司 | Updating method of data card and device thereof |
| CN102855149A (en) * | 2012-08-02 | 2013-01-02 | 福建伊时代信息科技股份有限公司 | Chip operating system update method, device and system |
| CN102855149B (en) * | 2012-08-02 | 2016-08-03 | 福建伊时代信息科技股份有限公司 | A kind of chip operating system upgrade method, device and system |
| CN104683959B (en) * | 2013-11-27 | 2018-09-18 | 深圳市盛天龙视听科技有限公司 | Instant messaging type portable audio and its account loading method |
| CN104683959A (en) * | 2013-11-27 | 2015-06-03 | 深圳市盛天龙视听科技有限公司 | Instant messaging type portable audio device and account number loading method thereof |
| CN105808465A (en) * | 2016-03-04 | 2016-07-27 | 浙江大华技术股份有限公司 | Method and device for upgrading camera equipment |
| CN105808465B (en) * | 2016-03-04 | 2018-12-07 | 浙江大华技术股份有限公司 | A kind of upgrade method and device of picture pick-up device |
| CN109002302A (en) * | 2017-05-25 | 2018-12-14 | 佛山市顺德区顺达电脑厂有限公司 | The firmware update of management engine |
| CN108280034A (en) * | 2018-01-30 | 2018-07-13 | 深圳市宏电技术股份有限公司 | A kind of Android system USB-HID apparatus self-adaptation method and devices |
| CN109656583A (en) * | 2018-12-28 | 2019-04-19 | 北京深思数盾科技股份有限公司 | Method for burning chip, host computer and chip burn-recording system |
| CN109656583B (en) * | 2018-12-28 | 2021-04-20 | 北京深思数盾科技股份有限公司 | Chip burning method, upper computer and chip burning system |
| CN113467799A (en) * | 2020-03-31 | 2021-10-01 | 精工爱普生株式会社 | Update system, printing device, and program storage medium |
| CN113467799B (en) * | 2020-03-31 | 2023-12-19 | 精工爱普生株式会社 | Update system, printing device, and program storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101539862A (en) | Firmware update method and firmware framework | |
| CN102473102B (en) | System and method for initiating a multi-environment operating system | |
| US10514930B2 (en) | Setting a startup parameter and controlling startup of a mainboard | |
| JP6554184B2 (en) | Soft processor based image signal source system and image signal processing method | |
| US5706410A (en) | Printing system having control language command and raster pixel image data processing capability | |
| US20060277325A1 (en) | Efficient data transmission system and method via direct memory access controller | |
| JP2001256170A (en) | Peripheral device and printer | |
| US7793004B2 (en) | Computer peripheral device implemented as optic storage device or/and removable disk by software emulation and implementing method thereof | |
| CN110119222A (en) | Touch-control module switching method, device, equipment and readable medium based on dual system | |
| US9553761B2 (en) | Dynamic server to server configuration and initialization | |
| CN100583049C (en) | Multi-nucleus processor sharing code segment patching method and apparatus | |
| TWI631442B (en) | Control device, data processing device, control system, control method, data processing method, control program, and data processing program | |
| CN101382875B (en) | Kvm switch identifying peripheral for computer and method thereof | |
| CN100576175C (en) | The parallel executing method and the system that are used for a plurality of kernels | |
| CN103777976A (en) | Single-chip microcomputer and on-line upgrading method and device thereof | |
| JP2006243988A (en) | Usb device, usb system and usb control program | |
| CN100462948C (en) | Computer peripheral device containing contents and method of outputting contents using the same | |
| CN113608769A (en) | Method based on parallel processing and self-upgrading of multiple single-chip microcomputers | |
| CN108182157B (en) | Method, BMC, device and storage medium for realizing heterogeneous hybrid memory | |
| CN100538673C (en) | The update method of embedded system and interface arrangement thereof and nonvolatile memory | |
| JP2008226111A (en) | Duplication controller system and operation system controller | |
| JP2003345638A5 (en) | ||
| CN102193745B (en) | Flash memory storage device, controller thereof and read-in management method | |
| CN100498736C (en) | Emulator and adaptation method for connecting emulator to target plate interface | |
| CN105589822A (en) | Data transmission method and device for human interface device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20090923 |