+

US9495146B2 - Host and method of upgrading connection manager of dongles - Google Patents

Host and method of upgrading connection manager of dongles Download PDF

Info

Publication number
US9495146B2
US9495146B2 US14/341,143 US201414341143A US9495146B2 US 9495146 B2 US9495146 B2 US 9495146B2 US 201414341143 A US201414341143 A US 201414341143A US 9495146 B2 US9495146 B2 US 9495146B2
Authority
US
United States
Prior art keywords
connection manager
dongle
version
upgrading
host
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.)
Expired - Fee Related, expires
Application number
US14/341,143
Other versions
US20150033003A1 (en
Inventor
Chung-Yu Hsiao
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hon Hai Precision Industry Co Ltd
Original Assignee
Hon Hai Precision Industry Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hon Hai Precision Industry Co Ltd filed Critical Hon Hai Precision Industry Co Ltd
Priority to US14/341,143 priority Critical patent/US9495146B2/en
Assigned to HON HAI PRECISION INDUSTRY CO., LTD. reassignment HON HAI PRECISION INDUSTRY CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HSIAO, CHUNG-YU
Publication of US20150033003A1 publication Critical patent/US20150033003A1/en
Application granted granted Critical
Publication of US9495146B2 publication Critical patent/US9495146B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G06F8/665—
    • 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
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/4068—Electrical coupling
    • 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
    • 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

Definitions

  • Embodiments of the present disclosure generally relate to upgrading firmware.
  • Dongles such as BLUETOOTH® dongles, USB (Universal Serial Bus) dongles, and television dongles, with different functions, are common today.
  • the dongles may need to be connected to a host for the execution of the functions.
  • the host may need to install a connection manager (hereinafter “CM”) for the dongles.
  • CM connection manager
  • the CM is saved in the dongle as a package and cannot be upgraded.
  • the host cannot install the newest version for the dongle and may have to upgrade the CM from the Internet.
  • the other host also cannot get the newer version from the dongle and may has also have to upgrade the CM from Internet.
  • FIG. 1 illustrates an application environment of a host device.
  • FIG. 2 is a block diagram of an embodiment of function modules of the host device.
  • FIG. 3 is a block diagram of a dongle.
  • FIG. 4 is a flowchart of an embodiment of a method of upgrading a CM of the dongle.
  • FIG. 5 is a flowchart of a second embodiment of a method of upgrading a CM of the dongle.
  • FIG. 6 is a flowchart of a third embodiment of a method of upgrading a CM of the dongle.
  • module refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language such as, for example, Java, C, or assembly.
  • One or more software instructions in the modules may be embedded in firmware such as in an erasable-programmable read-only memory (EPROM).
  • EPROM erasable-programmable read-only memory
  • the modules may comprise connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays and processors.
  • the modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of computer-readable medium or other computer storage device.
  • FIG. 1 illustrates an embodiment of an application environment of a host 10 .
  • the host 10 can connect to a dongle 20 and a network 30 .
  • the host 10 can upgrade a connection manager (CM) of the dongle 20 .
  • CM connection manager
  • the host 10 comprises a first CM 111 and a first version file 112 .
  • the first version file 112 corresponds to the first CM 111 .
  • the host 10 also includes a universal boot loader 113 (hereinafter “u-boot”) and a driver 114 .
  • the dongle 20 comprises a second CM 201 and a second version file 202 corresponding to the second CM 201 .
  • the first CM 111 is used to determine whether the second version file 202 of the dongle 20 matches the first version file 112 of the host 10 .
  • the first version file 112 is used to record version information of the first CM 111 , such as the version number and version type of the first CM 111 .
  • the second version file 202 is used to record version information of the second CM 201 .
  • the driver 114 can run the dongle 20 .
  • the u-boot 113 can be downloaded into the dongle 20 , so that the second version file 202 can be updated.
  • the host 10 can use the second CM 201 of the dongle 20 as the first CM 111 .
  • the host 10 can download an updated first CM 111 from the Internet 30 , and update the second CM 201 of the dongle 20 .
  • the other host can directly get the newer CM from the dongle 20 and does not need to download the newer CM from the Internet 30 .
  • the host 10 can be a desktop, a notebook, a tablet computer, or the like.
  • the dongle 20 can be a BLUETOOTH® dongle, a USB (Universal Serial Bus) dongle, a television dongle, or the like.
  • the host 10 comprises a storage system 11 , an updating module 12 , a reading module 13 , a version determining module 14 , a loading module 15 , and a processor 16 .
  • the modules 12 - 15 can comprise one or more software programs in the form of computerized codes stored in the storage system 11 .
  • the computerized codes include instructions executed by the processor 16 to provide functions for the modules 12 - 15 .
  • the upgrading module 12 upgrades the first CM 111 and the first version file 112 from the Internet 30 .
  • providers of the dongle 20 will periodically provide a new version of CM corresponding to the dongle 20 , so the first CM 111 and the first version file 112 periodically need to be upgraded.
  • the reading module 13 obtains the second version file 202 corresponding to the second CM 201 .
  • the dongle 20 has the second version file 202 and the second CM 201 , and the second version file 202 comprises version information of the second CM 201 .
  • the dongle 20 comprising the second CM 201 and the second version file 202 can be called CD-Less dongle.
  • the determining module 14 determines whether the upgraded first CM 111 is newer than the second CM 201 according to the upgraded first version file 112 and the second version file 201 .
  • the first version file 112 comprises version information of the first CM 111
  • the second version file 201 comprises version information of the second CM 201 , such as the respective version numbers and the version types of the first CM 111 and the second CM 201 .
  • the loading module 15 upgrades the second CM 201 on condition that the upgraded first CM 111 is newer than the second CM 201 .
  • the loading module 15 loads the u-boot 113 to the dongle 20 .
  • the dongle 20 stops running.
  • the second CM 201 can be upgraded.
  • the loading module 15 also generates an instruction to upgrade the second CM 201 , then the host 10 upgrades the second CM 201 according to the instruction.
  • the loading module 15 determines whether the first CM 111 is an engineer version which is offered to engineers according to the first version file 112 .
  • the upgrading instruction is to copy the first CM 111 to the dongle 20 , then the u-boot 113 of the dongle 20 copies the first CM 111 to the dongle 20 as the second CM 201 .
  • the upgrading instruction is to open a web page corresponding to the first CM 111 or the second CM 201 , then the user can upgrade parts of the second CM 201 selectively from the Internet 30 .
  • FIG. 4 is a flowchart of an embodiment of a method of upgrading CM of the dongle 20 .
  • the method is implemented in the application environment of FIG. 1 and executed by the host 10 .
  • an upgrading module upgrades a first CM and a first version file from the Internet.
  • a host has the first CM and the first version file.
  • a dongle comprises a second CM and a second version file. In the present embodiment, when the dongle is first connected to a host, the host can get the second CM from the dongle as the first CM.
  • a reading module obtains the second version file corresponding to the second CM from the dongle.
  • a determining module determines whether the upgraded first CM is newer than the second CM.
  • a loading module upgrades the second CM on condition that the upgraded first CM is newer than the second CM.
  • FIG. 5 is a flowchart of a second embodiment of a method of upgrading CM of the dongle.
  • the blocks 502 , 504 , and 506 are same as blocks 402 , 404 , and 406 , respectively.
  • the loading module downloads the u-boot to the dongle.
  • the u-boot can suspend the operation of the dongle.
  • the second CM can be upgraded.
  • the loading module generates an instruction to upgrade the second CM when the dongle stops running, then the host upgrades the second CM according to the instruction.
  • FIG. 6 is a flowchart of a third embodiment of a method of upgrading CM of the dongle.
  • the blocks 602 , 604 , 606 , and 608 are same as blocks 502 , 504 , 506 , and 508 , respectively.
  • the loading module determines whether the first CM is an engineer version which is offered to the engineers according to the first version file.
  • the first version file comprises the version type of the first CM.
  • the upgrading instruction is to copy the first CM, then the u-boot copies the first CM to the dongle as the second CM.
  • the upgrading instruction is to open web page corresponding to the first CM or the second CM, then the user can upgrade parts of the second CM selectively from the Internet.
  • the exemplary method of upgrading the connection manager of a dongle provides different ways to upgrade the connection manager of the dongle based on the version of the connection manager saved in the host.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

A host device with a function dongle includes a first connection manager and a first version file. The host upgrades the first connection manager and the first version file. The host gets a second version file which is saved in the dongle. The dongle includes a second connection manager corresponding to the second version file. The host determines whether the upgraded first connection manager is newer than the second connection manager according to the upgraded first version file and the second version file. The host upgrades the second connection manager if the upgraded first connection manager is newer than the second connection manager.

Description

FIELD
Embodiments of the present disclosure generally relate to upgrading firmware.
BACKGROUND
Dongles, such as BLUETOOTH® dongles, USB (Universal Serial Bus) dongles, and television dongles, with different functions, are common today. The dongles may need to be connected to a host for the execution of the functions. The host may need to install a connection manager (hereinafter “CM”) for the dongles. Currently, the CM is saved in the dongle as a package and cannot be upgraded. When there is a new version of the CM, the host cannot install the newest version for the dongle and may have to upgrade the CM from the Internet. Additionally, in this situation, when the dongle connects with another host, the other host also cannot get the newer version from the dongle and may has also have to upgrade the CM from Internet.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates an application environment of a host device.
FIG. 2 is a block diagram of an embodiment of function modules of the host device.
FIG. 3 is a block diagram of a dongle.
FIG. 4 is a flowchart of an embodiment of a method of upgrading a CM of the dongle.
FIG. 5 is a flowchart of a second embodiment of a method of upgrading a CM of the dongle.
FIG. 6 is a flowchart of a third embodiment of a method of upgrading a CM of the dongle.
 DETAILED DESCRIPTION
The embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references numerals indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references can mean “at least one.”
In general, the word “module” as used hereinafter refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language such as, for example, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware such as in an erasable-programmable read-only memory (EPROM). It will be appreciated that the modules may comprise connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays and processors. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of computer-readable medium or other computer storage device.
FIG. 1 illustrates an embodiment of an application environment of a host 10. In the present embodiment, the host 10 can connect to a dongle 20 and a network 30. According to a connection between the host 10 and the dongle 20, the host 10 can upgrade a connection manager (CM) of the dongle 20.
Referring to FIG. 2, the host 10 comprises a first CM 111 and a first version file 112. The first version file 112 corresponds to the first CM 111. The host 10 also includes a universal boot loader 113 (hereinafter “u-boot”) and a driver 114.
Referring to FIG. 3, the dongle 20 comprises a second CM 201 and a second version file 202 corresponding to the second CM 201. In the present embodiment, the first CM 111 is used to determine whether the second version file 202 of the dongle 20 matches the first version file 112 of the host 10. The first version file 112 is used to record version information of the first CM 111, such as the version number and version type of the first CM 111. Similarly, the second version file 202 is used to record version information of the second CM 201. In the present embodiment, once the dongle 20 is connected to the host 10 and the second version file 202 is determined as matching the first version file 112, the driver 114 can run the dongle 20. When the second version file 202 does not match the first version file 112, the u-boot 113 can be downloaded into the dongle 20, so that the second version file 202 can be updated.
In the present embodiment, if the host 10 does not have a CM corresponding to the dongle 20, the host 10 can use the second CM 201 of the dongle 20 as the first CM 111. When the CM 201 of the dongle 20 has a new version, the host 10 can download an updated first CM 111 from the Internet 30, and update the second CM 201 of the dongle 20. When the dongle 20 with the updated second CM 201 connects to another host, the other host can directly get the newer CM from the dongle 20 and does not need to download the newer CM from the Internet 30. In the present embodiment, the host 10 can be a desktop, a notebook, a tablet computer, or the like. The dongle 20 can be a BLUETOOTH® dongle, a USB (Universal Serial Bus) dongle, a television dongle, or the like.
As shown in FIG. 2, the host 10 comprises a storage system 11, an updating module 12, a reading module 13, a version determining module 14, a loading module 15, and a processor 16.
The modules 12-15 can comprise one or more software programs in the form of computerized codes stored in the storage system 11. The computerized codes include instructions executed by the processor 16 to provide functions for the modules 12-15.
The upgrading module 12 upgrades the first CM 111 and the first version file 112 from the Internet 30. In the present embodiment, providers of the dongle 20 will periodically provide a new version of CM corresponding to the dongle 20, so the first CM 111 and the first version file 112 periodically need to be upgraded.
The reading module 13 obtains the second version file 202 corresponding to the second CM 201. In the present embodiment, the dongle 20 has the second version file 202 and the second CM 201, and the second version file 202 comprises version information of the second CM 201. In the present embodiment, the dongle 20 comprising the second CM 201 and the second version file 202 can be called CD-Less dongle.
The determining module 14 determines whether the upgraded first CM 111 is newer than the second CM 201 according to the upgraded first version file 112 and the second version file 201. In the present embodiment, the first version file 112 comprises version information of the first CM 111, and the second version file 201 comprises version information of the second CM 201, such as the respective version numbers and the version types of the first CM 111 and the second CM 201.
The loading module 15 upgrades the second CM 201 on condition that the upgraded first CM 111 is newer than the second CM 201.
In the present embodiment, the loading module 15 loads the u-boot 113 to the dongle 20. When the u-boot 113 is executed, the dongle 20 stops running. When the dongle 20 stops running, the second CM 201 can be upgraded. In the present embodiment, the loading module 15 also generates an instruction to upgrade the second CM 201, then the host 10 upgrades the second CM 201 according to the instruction.
In the present embodiment, the loading module 15 determines whether the first CM 111 is an engineer version which is offered to engineers according to the first version file 112. When the first CM 111 is not an engineer version, the upgrading instruction is to copy the first CM 111 to the dongle 20, then the u-boot 113 of the dongle 20 copies the first CM 111 to the dongle 20 as the second CM 201.
In the present embodiment, when the first CM 111 is an engineer version, the upgrading instruction is to open a web page corresponding to the first CM 111 or the second CM 201, then the user can upgrade parts of the second CM 201 selectively from the Internet 30.
FIG. 4 is a flowchart of an embodiment of a method of upgrading CM of the dongle 20. In the embodiment, the method is implemented in the application environment of FIG. 1 and executed by the host 10.
In block 400, an upgrading module upgrades a first CM and a first version file from the Internet. In the present embodiment, a host has the first CM and the first version file. In addition, a dongle comprises a second CM and a second version file. In the present embodiment, when the dongle is first connected to a host, the host can get the second CM from the dongle as the first CM.
In block 402, a reading module obtains the second version file corresponding to the second CM from the dongle.
In block 404, a determining module determines whether the upgraded first CM is newer than the second CM.
In block 406, a loading module upgrades the second CM on condition that the upgraded first CM is newer than the second CM.
FIG. 5 is a flowchart of a second embodiment of a method of upgrading CM of the dongle. In FIG. 5, the blocks 502, 504, and 506 are same as blocks 402, 404, and 406, respectively.
In block 508, the loading module downloads the u-boot to the dongle. In the present embodiment, the u-boot can suspend the operation of the dongle. When the dongle stops running, the second CM can be upgraded.
In block 510, the loading module generates an instruction to upgrade the second CM when the dongle stops running, then the host upgrades the second CM according to the instruction.
FIG. 6 is a flowchart of a third embodiment of a method of upgrading CM of the dongle. In FIG. 6, the blocks 602, 604, 606, and 608 are same as blocks 502, 504,506, and 508, respectively.
In block 610, the loading module determines whether the first CM is an engineer version which is offered to the engineers according to the first version file. In the present embodiment, the first version file comprises the version type of the first CM.
In block 612, when the first CM is not the engineer version, the upgrading instruction is to copy the first CM, then the u-boot copies the first CM to the dongle as the second CM.
In block 614, when the first CM is the engineer version, the upgrading instruction is to open web page corresponding to the first CM or the second CM, then the user can upgrade parts of the second CM selectively from the Internet.
The exemplary method of upgrading the connection manager of a dongle provides different ways to upgrade the connection manager of the dongle based on the version of the connection manager saved in the host.
While various embodiments and methods have been described above, it should be understood that they have been presented by way of example only and not by way of limitation. Thus the breadth and scope of the present disclosure should not be limited by the above-described embodiments, and should be at least commensurate with the following claims and their equivalents.

Claims (8)

What is claimed is:
1. A host for connecting to a dongle, comprising at least one processor, a non-transitory storage system storing a first connection manager and one or more programs, and a first version file, wherein the one or more programs is executed by the at least one processor and comprises instructions for:
upgrading the first connection manager and the first version file;
obtaining a second version file which is saved in the dongle, wherein the dongle comprises a second connection manager corresponding to the second version file;
determining whether or not the upgraded first connection manager is newer than the second connection manager according to the upgraded first version file and the second version file;
downloading a universal boot loader to the dongle on condition that the upgraded first connection manager is newer than the second connection manager, wherein the universal boot loader is able to stop the dongle from running;
generating an instruction for upgrading the second connection manager when the dongle stops running; and
upgrading the second connection manager according to the instruction.
2. The host of claim 1, wherein generating an instruction of upgrading the second connection manager further bases on the determination about a version of the first connection manager.
3. The host of claim 2, wherein, when the version of the first connection manger is an engineer version, the instruction of upgrading the second connection manager is to open a web page corresponding to the second connection manager for upgrading parts of the second connection manager.
4. The host of claim 3, wherein, when the version of the first connection manger is not the engineer version, the instruction of upgrading the second connection manager is to copy the upgraded first connection manager to the dongle as the second connection manager.
5. A method of upgrading connection managers for a dongle, applied in a host comprising a first connection manager and a first version file, the method comprising:
upgrading the first connection manager and the first version file;
obtaining a second version file which is saved in the dongle, wherein the dongle comprises a second connection manager corresponding to the second version file;
determining whether or not the upgraded first connection manager is newer than the second connection manager according to the upgraded first version file and the second version file;
downloading a universal boot loader to the dongle on condition that the upgraded first connection manager is newer than the second connection manager, wherein the universal boot loader is able to stop the dongle from running;
generating an instruction for upgrading the second connection manager when the dongle stops running; and
upgrading the second connection manager according to the instruction.
6. The method of claim 5, wherein, generating an instruction of upgrading the second connection manager further bases on the determination about a version of the first connection manager.
7. The method of claim 6, wherein, when the version of the first connection manger is an engineer version, the instruction of upgrading the second connection manager is to open a web page corresponding to the second connection manager for upgrading parts of the second connection manager.
8. The method of claim 7, wherein, when the version of the first connection manger is not the engineer version, the instruction of upgrading the second connection manager is to copy the upgraded first connection manager to the dongle as the second connection manager.
US14/341,143 2013-07-29 2014-07-25 Host and method of upgrading connection manager of dongles Expired - Fee Related US9495146B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/341,143 US9495146B2 (en) 2013-07-29 2014-07-25 Host and method of upgrading connection manager of dongles

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
TW102127155A TWI486876B (en) 2013-07-29 2013-07-29 Host and method of upgrading connection manager of dongle
TW102127155 2013-07-29
US14/341,143 US9495146B2 (en) 2013-07-29 2014-07-25 Host and method of upgrading connection manager of dongles

Publications (2)

Publication Number Publication Date
US20150033003A1 US20150033003A1 (en) 2015-01-29
US9495146B2 true US9495146B2 (en) 2016-11-15

Family

ID=52391510

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/341,143 Expired - Fee Related US9495146B2 (en) 2013-07-29 2014-07-25 Host and method of upgrading connection manager of dongles

Country Status (2)

Country Link
US (1) US9495146B2 (en)
TW (1) TWI486876B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10395226B2 (en) * 2014-01-31 2019-08-27 Ncr Corporation Maintaining secure access to a self-service terminal (SST)
US10654244B2 (en) * 2016-10-14 2020-05-19 Gpcp Ip Holdings Llc Laminated multi-ply tissue products with improved softness and ply bonding
WO2021226880A1 (en) * 2020-05-13 2021-11-18 Arris Enterprises Llc Methods and systems for mass terminal device recovery

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040199911A1 (en) * 2003-04-04 2004-10-07 Incomm Technologies Co., Ltd. Apparatus and method for upgrading execution code of the portable memory device
CN1540497A (en) 2003-04-21 2004-10-27 矽成积体电路股份有限公司 Method for Updating Firmware Program of USB Device
US20050144612A1 (en) 2003-12-31 2005-06-30 Shin-Ping Wang Firmware updating method and application utilizing the same
US6990659B1 (en) * 1998-03-30 2006-01-24 Brother Kogyo Kabushiki Kaisha Device for rewriting software programs in peripheral devices connected to a network
US20060117312A1 (en) * 2004-11-29 2006-06-01 Jung-Soo Seo Device to serve software to a host device through a peripheral device and method thereof
US20060234632A1 (en) * 2005-04-18 2006-10-19 Zheng-Liang Lin Method of updating firmware using object push profile in the bluetooth object exchange protocol
US20060253620A1 (en) * 2005-05-06 2006-11-09 Kang Byung-Suk Data structure of flash memory having system area with variable size in which data can be updated, USB memory device having the flash memory, and method of controlling the system area
US20060282653A1 (en) 2005-06-08 2006-12-14 Ping-Ying Chu Method for updating frimware of memory card
TW200705227A (en) 2005-07-25 2007-02-01 Avision Inc Computer peripheral and method of updating files thereof
US20070169104A1 (en) * 2005-12-08 2007-07-19 Konica Minolta Business Technologies, Inc. Data processing apparatus
CN100514293C (en) 2007-09-05 2009-07-15 威盛电子股份有限公司 Firmware updating method
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
US20130179559A1 (en) * 2012-01-08 2013-07-11 Yi-Chieh Chen Control method for wireless communications device compatible with universal serial bus mass storage device class protocol

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6990659B1 (en) * 1998-03-30 2006-01-24 Brother Kogyo Kabushiki Kaisha Device for rewriting software programs in peripheral devices connected to a network
US20040199911A1 (en) * 2003-04-04 2004-10-07 Incomm Technologies Co., Ltd. Apparatus and method for upgrading execution code of the portable memory device
CN1540497A (en) 2003-04-21 2004-10-27 矽成积体电路股份有限公司 Method for Updating Firmware Program of USB Device
US20050144612A1 (en) 2003-12-31 2005-06-30 Shin-Ping Wang Firmware updating method and application utilizing the same
TW200521846A (en) 2003-12-31 2005-07-01 Asustek Comp Inc Firmware update processing method and application program
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
US20060117312A1 (en) * 2004-11-29 2006-06-01 Jung-Soo Seo Device to serve software to a host device through a peripheral device and method thereof
US20060234632A1 (en) * 2005-04-18 2006-10-19 Zheng-Liang Lin Method of updating firmware using object push profile in the bluetooth object exchange protocol
US20060253620A1 (en) * 2005-05-06 2006-11-09 Kang Byung-Suk Data structure of flash memory having system area with variable size in which data can be updated, USB memory device having the flash memory, and method of controlling the system area
US20060282653A1 (en) 2005-06-08 2006-12-14 Ping-Ying Chu Method for updating frimware of memory card
TW200705227A (en) 2005-07-25 2007-02-01 Avision Inc Computer peripheral and method of updating files thereof
US20070169104A1 (en) * 2005-12-08 2007-07-19 Konica Minolta Business Technologies, Inc. Data processing apparatus
CN100514293C (en) 2007-09-05 2009-07-15 威盛电子股份有限公司 Firmware updating method
US20130179559A1 (en) * 2012-01-08 2013-07-11 Yi-Chieh Chen Control method for wireless communications device compatible with universal serial bus mass storage device class protocol

Also Published As

Publication number Publication date
US20150033003A1 (en) 2015-01-29
TW201504945A (en) 2015-02-01
TWI486876B (en) 2015-06-01

Similar Documents

Publication Publication Date Title
US9507581B2 (en) Systems and methods of device firmware delivery for pre-boot updates
US9891939B2 (en) Application compatibility with library operating systems
US9027014B2 (en) Updating firmware compatibility data
US20140325496A1 (en) Apparatus and method for firmware upgrade using usb
US20170010884A1 (en) Systems And Methods To Securely Inject Binary Images And Code Into Firmware
US20110302572A1 (en) Embedded network device and firmware upgrading method
US10437580B2 (en) Software updating methods and systems
US10025587B2 (en) Method of bootup and installation, and computer system thereof
US9411605B2 (en) Device-less and system agnostic unified extensible firmware interface (UEFI) driver
CN109753299A (en) A system upgrade method, device and computer storage medium
AU2022202175B2 (en) Firmware publication of multiple binary images
KR102052776B1 (en) Installation engine and package format for parallelizable, reliable installations
US9672047B1 (en) Systems and methods for accessing a bootable partition on a serial peripheral interface device
US9495146B2 (en) Host and method of upgrading connection manager of dongles
US11983519B2 (en) Abort installation of firmware bundles
US7099967B2 (en) System and method for storing an image file in a computer system
US8458730B2 (en) Multi-level driver configuration
CN102298531B (en) Method for upgrading flash memory file system in embedded system
CN108196868B (en) BIOS (basic input output System) upgrading method and electronic equipment
US11755335B2 (en) Bios variable-based application deployments
CN109428936B (en) APP upgrade method, device, system, electronic device and storage medium
US20220334820A1 (en) System and method for intermediate software upgrades for information handling systems
CN110990041A (en) Bootloader upgrading method and bootloader upgrading system
US7103687B2 (en) System and method for providing an image file in a computer system
US10884763B2 (en) Loading new code in the initial program load path to reduce system restarts

Legal Events

Date Code Title Description
AS Assignment

Owner name: HON HAI PRECISION INDUSTRY CO., LTD., TAIWAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HSIAO, CHUNG-YU;REEL/FRAME:033394/0070

Effective date: 20140718

ZAAA Notice of allowance and fees due

Free format text: ORIGINAL CODE: NOA

ZAAB Notice of allowance mailed

Free format text: ORIGINAL CODE: MN/=.

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20241115

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载