CN116954674A - eMMC firmware upgrading method, firmware upgrading equipment and storage device - Google Patents
eMMC firmware upgrading method, firmware upgrading equipment and storage device Download PDFInfo
- Publication number
- CN116954674A CN116954674A CN202310779427.5A CN202310779427A CN116954674A CN 116954674 A CN116954674 A CN 116954674A CN 202310779427 A CN202310779427 A CN 202310779427A CN 116954674 A CN116954674 A CN 116954674A
- Authority
- CN
- China
- Prior art keywords
- firmware
- upgraded
- emmc
- android platform
- upgrading
- 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
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000005192 partition Methods 0.000 claims abstract description 55
- 238000010586 diagram Methods 0.000 description 9
- 238000012795 verification Methods 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses an eMMC firmware upgrading method, firmware upgrading equipment and a storage device, wherein the eMMC firmware upgrading method based on an android platform comprises the following steps: identifying the data size of firmware to be upgraded; if the data of the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area; after initializing the eMMC, reading the firmware to be upgraded in the boot area, and upgrading the firmware of the eMMC according to the firmware to be upgraded; if the data of the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in the guide area; after initializing the eMMC, executing an operation instruction of a boot area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and upgrading the firmware of the eMMC according to the firmware to be upgraded. Through the scheme, the reliability of eMMC firmware upgrading based on the android platform is improved.
Description
Technical Field
The application relates to the technical field of data storage, in particular to an eMMC firmware upgrading method, firmware upgrading equipment and a storage device based on an android platform.
Background
eMMC (Embedded Multi Media Card) is an embedded memory standard specification mainly aiming at products such as mobile phones, tablets and computers and is composed of an embedded memory solution, and is provided with an MMC (multimedia card) interface, a flash memory (nand-flash) and an eMMC controller. One significant advantage of eMMC is the integration of an eMMC controller in the package that provides a standard interface and manages flash memory so that the handset vendor can concentrate on other parts of the product development and shorten the time to market the product. More and more mobile devices employ eMMC as a storage unit.
At present, firmware software upgrading based on an android platform is basically performed in a boot zone (BootLoader), but the BootLoader space is very limited, generally 1M or 2M. However, when the firmware to be upgraded is large, the firmware cannot be stored in the BootLoader, so that firmware software upgrading based on the android platform is generally not feasible to place the firmware data to be upgraded in the BootLoader.
Disclosure of Invention
The application aims to provide an eMMC firmware upgrading method, firmware upgrading equipment and a storage device, so as to improve the reliability of eMMC firmware upgrading based on an android platform.
The application discloses an eMMC firmware upgrading method based on an android platform, which comprises the following steps:
identifying the data size of firmware to be upgraded;
if the data of the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area;
after initializing the eMMC, reading the firmware to be upgraded in the boot area, and upgrading the firmware of the eMMC according to the firmware to be upgraded;
if the data of the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in the guide area;
after initializing the eMMC, executing an operation instruction of a boot area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and upgrading the firmware of the eMMC according to the firmware to be upgraded.
Optionally, before the step of identifying the data size of the firmware to be upgraded, the method includes:
acquiring firmware information to be upgraded and firmware information of the eMMC;
comparing the firmware information to be upgraded with the firmware information to obtain a comparison result;
and if the comparison result is that the firmware information to be upgraded is inconsistent with the firmware information, executing the step of identifying the data size of the firmware to be upgraded.
Optionally, the read-only partition of the android platform includes a boot icon storage partition of the android platform.
Optionally, after the step of downloading and storing the firmware to be upgraded, the method further includes:
checking the integrity of the firmware to be upgraded;
if the firmware to be upgraded has the integrity, executing the next step; and if the firmware to be upgraded does not have the integrity, the firmware to be upgraded is downloaded again.
Optionally, after initializing the eMMC, executing an operation instruction of the boot area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and upgrading the firmware of the eMMC according to the firmware to be upgraded, including the following steps:
executing restarting operation, initializing eMMC, and entering a firmware upgrading mode;
executing an operation instruction of a guide area, reading the firmware to be upgraded in a read-only partition according to the operation instruction, and writing the firmware to be upgraded into a firmware storage area of the eMMC;
after the firmware upgrade is executed, the firmware upgrade mode is exited.
Optionally, the firmware information to be upgraded includes version information, file information or vendor code information.
Optionally, the firmware to be upgraded at least comprises a firmware upgrade file, and the firmware upgrade file is stored in a read-only partition of the android platform.
The application discloses firmware upgrading equipment of an eMMC (enhanced MMC) based on an android platform, which comprises the eMMC and a processor, wherein the processor is connected with the eMMC; the android platform is provided with a read-only partition; the processor is used for identifying the size of the firmware to be upgraded; if the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area; after initializing the eMMC, reading firmware to be upgraded in a boot area, and upgrading the firmware of the eMMC according to the firmware to be upgraded; if the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in a boot area; after initializing the eMMC, executing an operation instruction of the boot area, reading firmware to be upgraded in the read-only partition, and upgrading the firmware of the eMMC.
Optionally, the processor is configured to instruct the eMMC to enter or exit the FFU mode.
The application discloses a storage device for storing program data which can be executed to realize the eMMC firmware upgrading method.
According to the application, the firmware to be upgraded is stored in the boot area directly for eMMC firmware upgrading by distinguishing the larger firmware to be upgraded from the smaller firmware to be upgraded and storing the smaller firmware to be upgraded respectively, the larger firmware to be upgraded is stored in the read-only partition of the android platform, and when FFU upgrading is carried out, the firmware to be upgraded in the read-only partition is read through the pre-stored operation instructions in the boot area, so that FFU upgrading is carried out on the eMMC. The application has the advantages that the firmware data of the readable partition is read by setting the operation instruction in the boot area, and the problem of insufficient space for storing the firmware data in the boot area is solved. Secondly, the method avoids breaking the eMMC firmware upgrade in the multithread Cheng Hui of Kernel, avoids the multithread influence in Kernel, improves the reliability of the eMMC firmware upgrade scheme, and facilitates the quick firmware upgrade of the eMMC.
Drawings
The accompanying drawings, which are included to provide a further understanding of embodiments of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the principles of the application. It is evident that the figures in the following description are only some embodiments of the application, from which other figures can be obtained without inventive effort for a person skilled in the art. In the drawings:
fig. 1 is a schematic step diagram of an eMMC firmware upgrade method based on an android platform;
fig. 2 is a schematic step diagram of another eMMC firmware upgrade method based on the android platform of the present application;
FIG. 3 is a schematic step diagram of an eMMC firmware upgrade method based on an android platform according to the present application;
FIG. 4 is a schematic step diagram of an eMMC firmware upgrade method based on an android platform according to the present application;
fig. 5 is a schematic diagram of an eMMC firmware upgrade apparatus based on an android platform of the present application.
Detailed Description
It is to be understood that the terminology used herein, the specific structural and functional details disclosed are merely representative for the purpose of describing particular embodiments, but that the application may be embodied in many alternate forms and should not be construed as limited to only the embodiments set forth herein.
The application is described in detail below with reference to the attached drawings and alternative embodiments.
The firmware upgrading method is suitable for the eMMC firmware upgrading method of the android platform. In embedded operating systems, such as android platforms, a boot region (BootLoader) is run before the operating system kernel runs. The hardware device may be initialized and a memory space map established to bring the system's software and hardware environment to a proper state to prepare the correct environment for the final invocation of the operating system kernel. BootLoader is a small program that is the first program to run when the system is started, responsible for starting the operating system kernel. In Android (Android) devices, bootLoader is also responsible for executing tasks such as firmware upgrades and recovery systems. In an embedded system, there is usually no firmware program like BIOS (Basic Input Output System), so the loading start task of the whole system is completely completed by BootLoader. When the firmware is upgraded by the eMMC based on the android platform, the firmware to be upgraded needs to be written in at the stage.
It will be appreciated that the pilot zone typically has a space of 1 megameter (M) or 2M, with some pilot zones up to 4M. Although there is a 4M space, the bootloader size can only download 1M due to download tool limitations. And there is generally no continuous 512K space in the boot area to store the firmware to be upgraded of the eMMC, for example, the data of the fw.bin file used for firmware upgrade, when the data size of fw.bin is at least 512K, and continuous space is required for the data. For the boot sector, there is no way to place fw.bin directly in the boot sector in an array.
Referring to fig. 1, fig. 1 is a schematic step diagram of an eMMC firmware upgrade method based on an android platform.
In this regard, the application discloses an eMMC firmware upgrading method based on an android platform, which comprises the following steps:
s100: the data size of the firmware to be upgraded is identified.
The method mainly includes identifying whether data of firmware to be upgraded is larger than a preset value, wherein the preset value can be designed according to different data packets, for example, in a firmware upgrade file (fw. Bin) file, judging whether the fw. Bin file is larger than 512K, and executing the next step by taking 512K as the preset value.
S210: if the data of the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area;
s211: after initializing the eMMC, reading the firmware to be upgraded in the guide area, and performing FFU upgrade on the eMMC according to the firmware to be upgraded.
When the firmware to be upgraded meets the storage condition of the boot sector, that is, when the data size of the firmware to be upgraded is smaller than the space size of the boot sector, the firmware to be upgraded can be stored in the boot sector, and the firmware to be upgraded is directly read in the boot sector to be upgraded in the process of executing firmware upgrade (Field Firmware Updates, FFU upgrade).
S220: if the data of the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in the guide area;
s221: after initializing the eMMC, executing the operation instruction of the guide area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and performing FFU upgrading on the eMMC according to the firmware to be upgraded.
When the firmware to be upgraded is large, the firmware to be upgraded is stored in a read-only partition of the android platform in a temporary storage mode, wherein the read-only partition can only read the file and cannot modify the file, and the firmware to be upgraded is prevented from being modified. And more read-only partitions exist in the android platform, and in the storage process, the empty read-only partitions are selected for storage.
According to the application, the firmware to be upgraded is stored in the boot area directly for eMMC firmware upgrading by distinguishing the larger firmware to be upgraded from the smaller firmware to be upgraded and storing the smaller firmware to be upgraded respectively, the larger firmware to be upgraded is stored in the read-only partition of the android platform, and when FFU upgrading is carried out, the firmware to be upgraded in the read-only partition is read through the pre-stored operation instructions in the boot area, so that FFU upgrading is carried out on the eMMC. The application has the advantages that the firmware data of the readable partition is read by setting the operation instruction in the boot area, and the problem of insufficient space for storing the firmware data in the boot area is solved.
Moreover, because the kernel (kernel) is multi-threaded to operate, it is possible that many threads simultaneously issue requests to eMMC at the same time. And because eMMC is half duplex, the read and write must be performed separately, and the instructions are also packed. Thus, there are various possibilities, for example, it is possible that at the time of writing, the system may send a read command, interrupting the eMMC upgrade operation. For example, the command sent by eMMC is not as simple and convenient as bootloader configuration, and needs to configure host and core. The third kernel version has a firmware upgrade that can affect eMMC. Therefore, the method avoids breaking the eMMC firmware upgrade at the multithread Cheng Hui of Kernel, avoids the multithread influence in Kernel, improves the reliability of the eMMC firmware upgrade scheme, and facilitates the quick firmware upgrade of the eMMC.
Specifically, the firmware to be upgraded at least comprises an fw.bin file, and the fw.bin file is stored in a read-only partition of the android platform. It will be appreciated that the fw.bin file is a firmware bin file, and as mentioned above, the fw.bin file needs to be connected to a storage space greater than 512K, and in general, the boot area cannot be satisfied. Therefore, in this embodiment, the fw.bin file is stored in a read-only partition of the android platform, and the read-only partition, for example, a boot icon storage partition, is a logo partition, and the logo partition is used for storing a partition of the boot logo in the android platform.
Referring to fig. 2, fig. 2 is a schematic step diagram of another method for upgrading eMMC firmware based on the android platform according to the present application, and in step S210 or step S220, the step of downloading and storing the firmware to be upgraded includes:
s230: checking the integrity of the firmware to be upgraded;
s231: if the firmware to be upgraded has the integrity, executing the next step;
s232: and if the firmware to be upgraded does not have the integrity, the firmware to be upgraded is downloaded again. In this solution, considering that the firmware to be upgraded is stored in a readable partition or boot area, there may be a problem of file damage or loss. Therefore, after downloading and storing, a verification process of file integrity is needed, especially in a scheme of a read-only partition stored in an android platform, because more steps such as a partition mapping and a virtual partition storing process exist in the storing process, the problem that the file of firmware to be upgraded is lost or damaged is more easily caused.
In this verification step, checking the firmware to be upgraded, such as the version number of fw.bin file, flash ID, MID (vendor code), etc., may be further added to check again whether the firmware to be upgraded is the upgrade firmware required for the eMMC. It will be appreciated that, generally, in the process of obtaining the firmware to be upgraded, information such as the integrity or version information of the firmware to be upgraded mentioned above needs to be identified. It should be noted that this step may also be performed after eMMC initialization, and after CMD18 is sent to eMMC, the data of the firmware to be upgraded is read, so as to check whether the data integrity is correct.
Referring to fig. 3, fig. 3 is a schematic step diagram of another method for upgrading eMMC firmware based on an android platform according to the present application; specifically, the step of S100 is preceded by the steps of:
s101: and acquiring firmware information to be upgraded and firmware information of the eMMC.
The firmware to be upgraded, the firmware information and the like in the embodiment can be upgraded by an OTA, or obtained from the FOTA server, or read by a USB, or obtained by a wired manner, which is not limited herein, and generally speaking, the android platform can be directly upgraded by the OTA.
S102: comparing the firmware information to be upgraded with the firmware information to obtain a comparison result;
s103: and if the comparison result is that the firmware information to be upgraded is inconsistent with the firmware information, executing the step of identifying the data size of the firmware to be upgraded.
In the step of acquiring the firmware information to be upgraded of the eMMC, the information of the firmware to be upgraded of the eMMC is required to be compared, when the firmware information to be upgraded is consistent with the firmware information of the current eMMC, the information is not updated or has already been updated, and when the firmware information to be upgraded is inconsistent with the firmware information of the current eMMC, the information of the firmware to be upgraded is indicated to be upgradeable.
The firmware information may be file information, partial code information, version information, MID information (vendor code) of the eMMC firmware.
Through two checks, the embodiment reduces the problems that the firmware to be upgraded is interrupted due to online downloading or data is lost in the storage process as much as possible, and prevents the eMMC from being unable to normally operate due to firmware damage in the firmware upgrading process.
Referring to fig. 4, fig. 4 is a schematic step diagram of another method for upgrading eMMC firmware based on an android platform according to the present application; in step S211, specifically, the method includes:
s212: and executing a restarting operation, initializing the eMMC, and entering an FFU mode.
Wherein, FFU upgrade starts, through sending CMD6 to eMMC, gets into FFU mode.
S213: and executing an operation instruction of the guide area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and writing the firmware to be upgraded into the firmware storage area of the eMMC.
And writing the firmware to be upgraded in the read-only partition into a specific firmware position in the eMMC by sending CMD25 to the eMMC.
S214: after the FFU upgrade is performed, the FFU mode is exited.
Wherein, exiting the FFU mode is also by sending CMD6 to eMMC.
According to the embodiment, the firmware to be upgraded is temporarily stored in the read-only partition of the android platform, and the problem that the boot area cannot be stored due to space limitation is solved in a transit mode.
It can be understood that after the step of identifying the size of the firmware to be upgraded is performed, when the size of the firmware to be upgraded is smaller, the firmware to be upgraded is directly stored in the boot area, and after the eMMC is initialized later, the eMMC is also initialized, and then the data in the boot area is written into a specific position in the eMMC by sending CMD6 to the eMMC to enter an FFU mode.
It can be understood that the android platform writes the firmware to be upgraded into the eMMC according to the android partition table. When the Android system is initialized, the system reads BootLoader to dram operation from eMMC, and the application adds an operation instruction in BootLoader, and writes the firmware to be upgraded into a specific firmware position of eMMC when the boot zone works.
Referring to fig. 5, the application discloses an eMMC firmware upgrade device based on an android platform, wherein the firmware upgrade device 100 comprises an eMMC120 and a processor 110, and the processor is connected with the eMMC; the android platform is provided with a read-only partition; the processor is used for identifying the size of the firmware to be upgraded; if the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area; after initializing the eMMC, reading firmware to be upgraded in a boot area, and performing FFU upgrade on the eMMC according to the firmware to be upgraded; if the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in a boot area; after initializing the eMMC, executing an operation instruction of the boot area, reading firmware to be upgraded in the read-only partition, and performing FFU upgrade on the eMMC.
According to the application, the firmware to be upgraded is stored in the boot area directly for eMMC firmware upgrading by distinguishing the larger firmware to be upgraded from the smaller firmware to be upgraded and storing the smaller firmware to be upgraded respectively, the larger firmware to be upgraded is stored in the read-only partition of the android platform, and when FFU upgrading is carried out, the firmware to be upgraded in the read-only partition is read through the pre-stored operation instructions in the boot area, so that FFU upgrading is carried out on the eMMC. The application has the advantages that the firmware data of the readable partition is read by setting the operation instruction in the boot area, and the problem of insufficient space for storing the firmware data in the boot area is solved. Secondly, the method avoids breaking the eMMC firmware upgrade in the multithread Cheng Hui of Kernel, avoids the multithread influence in Kernel, improves the reliability of the eMMC firmware upgrade scheme, and facilitates the quick firmware upgrade of the eMMC.
The processor is configured to instruct the eMMC to enter or exit the FFU mode. The processor is used for acquiring firmware to be upgraded and information thereof through OTA, and when the firmware information of the eMMC is inconsistent with the firmware information to be upgraded, the processor instructs the eMMC to enter an FFU mode, reads the firmware to be upgraded from the read-only partition and writes the firmware to the specific firmware position of the eMMC in the FFU mode.
It is understood that the eMMC mentioned in the present application can enter the FFU mode, i.e., support the FFU mode.
The application also discloses a storage device for storing program data which can be executed to realize the eMMC firmware upgrading method of any one of the embodiments.
The foregoing is merely an embodiment of the present application, and is not intended to limit the scope of the present application, and all equivalent processes performed by the present specification and the accompanying drawings, or directly or indirectly applied to the related art, are within the scope of the present application.
It should be noted that, the inventive concept of the present application can form a very large number of embodiments, but the application documents are limited in space and cannot be listed one by one, so that on the premise of no conflict, the above-described embodiments or technical features can be arbitrarily combined to form new embodiments, and after the embodiments or technical features are combined, the original technical effects will be enhanced.
The above description of the application in connection with specific alternative embodiments is further detailed and it is not intended that the application be limited to the specific embodiments disclosed. It will be apparent to those skilled in the art that several simple deductions or substitutions may be made without departing from the spirit of the application, and these should be considered to be within the scope of the application.
Claims (10)
1. An eMMC firmware upgrading method based on an android platform is characterized by comprising the following steps:
identifying the data size of firmware to be upgraded;
if the data of the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area;
after initializing the eMMC, reading the firmware to be upgraded in the boot area, and upgrading the firmware of the eMMC according to the firmware to be upgraded;
if the data of the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in the guide area;
after initializing the eMMC, executing the operation instruction of the guide area, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and upgrading the firmware of the eMMC according to the firmware to be upgraded.
2. The eMMC firmware upgrade method according to claim 1, wherein the step of identifying the data size of the firmware to be upgraded is preceded by the step of:
acquiring firmware information to be upgraded and firmware information of the eMMC;
comparing the firmware information to be upgraded with the firmware information to obtain a comparison result;
and if the comparison result is that the firmware information to be upgraded is inconsistent with the firmware information, executing the step of identifying the data size of the firmware to be upgraded.
3. The android platform-based eMMC firmware upgrade method of claim 1, wherein the android platform read-only partition includes a boot icon storage partition of the android platform.
4. The eMMC firmware upgrade method based on the android platform of claim 1, further comprising, after the step of downloading and storing firmware to be upgraded:
checking the integrity of the firmware to be upgraded;
if the firmware to be upgraded has the integrity, executing the next step; and if the firmware to be upgraded does not have the integrity, the firmware to be upgraded is downloaded again.
5. The method for upgrading the eMMC firmware based on the android platform according to claim 1, wherein after initializing the eMMC, executing an operation instruction of a boot zone, reading the firmware to be upgraded in the read-only partition according to the operation instruction, and performing FFU upgrading on the eMMC according to the firmware to be upgraded, specifically comprising the following steps:
executing restarting operation, initializing eMMC, and entering a firmware upgrading mode;
executing an operation instruction of a guide area, reading the firmware to be upgraded in a read-only partition according to the operation instruction, and writing the firmware to be upgraded into a firmware storage area of the eMMC;
after the firmware upgrade is executed, the firmware upgrade mode is exited.
6. The eMMC firmware upgrade method based on the android platform of claim 2, wherein the firmware information to be upgraded includes version information, file information, or vendor code information.
7. The method for upgrading eMMC firmware based on the android platform as claimed in claim 2, wherein the firmware to be upgraded at least includes a firmware upgrade file, and the firmware upgrade file is stored in a read-only partition of the android platform.
8. The firmware upgrading device of the eMMC based on the android platform is characterized by comprising the eMMC and a processor, wherein the processor is connected with the eMMC; the android platform is provided with a read-only partition; the processor is used for identifying the size of the firmware to be upgraded;
if the firmware to be upgraded is smaller than the preset value, downloading and storing the firmware to be upgraded into a guide area; after initializing the eMMC, reading firmware to be upgraded in a boot area, and upgrading the firmware of the eMMC according to the firmware to be upgraded;
if the firmware to be upgraded is larger than the preset value, downloading and storing the firmware to be upgraded into a read-only partition of the android platform, and writing an instruction in a boot area; after initializing the eMMC, executing an operation instruction of the boot area, reading firmware to be upgraded in the read-only partition, and upgrading the firmware of the eMMC.
9. The android platform-based eMMC firmware upgrade apparatus of claim 8, wherein the processor is configured to instruct the eMMC to enter or exit FFU mode.
10. A storage device for storing program data executable to implement the eMMC firmware upgrade method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310779427.5A CN116954674A (en) | 2023-06-28 | 2023-06-28 | eMMC firmware upgrading method, firmware upgrading equipment and storage device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310779427.5A CN116954674A (en) | 2023-06-28 | 2023-06-28 | eMMC firmware upgrading method, firmware upgrading equipment and storage device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116954674A true CN116954674A (en) | 2023-10-27 |
Family
ID=88445403
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310779427.5A Pending CN116954674A (en) | 2023-06-28 | 2023-06-28 | eMMC firmware upgrading method, firmware upgrading equipment and storage device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116954674A (en) |
-
2023
- 2023-06-28 CN CN202310779427.5A patent/CN116954674A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101427755B1 (en) | Device and method for firmware upgrade using usb | |
| US7017004B1 (en) | System and method for updating contents of a flash ROM | |
| CN110597542B (en) | Software automatic OTA (over the air) upgrading method and device and electronic equipment | |
| WO2022007656A1 (en) | Bootloader software updating method and apparatus, embedded controller, and storage medium | |
| CN103970557B (en) | The method and storage device of storage device activation system | |
| KR101555210B1 (en) | Apparatus and method for downloadin contents using movinand in portable terminal | |
| US20060064576A1 (en) | Boot systems and methods | |
| US11042383B2 (en) | System and method for boot speed optimization using non-volatile dual in-line memory modules | |
| CN111813428A (en) | Method and device for upgrading terminal firmware, electronic equipment and storage medium | |
| CN111045713A (en) | Method, system and device for upgrading computer system | |
| US20070233750A1 (en) | Data control apparatus and method | |
| CN115951920A (en) | Mobile equipment upgrading method and device, storage unit and mobile equipment | |
| CN116954674A (en) | eMMC firmware upgrading method, firmware upgrading equipment and storage device | |
| CN114296764A (en) | System upgrading method and device, storage medium and electronic equipment | |
| CN111258617B (en) | Electronic equipment | |
| CN113010195B (en) | System upgrading method, storage medium and terminal equipment | |
| CN114625389A (en) | Embedded equipment upgrading method, embedded equipment and storage device | |
| US9081727B2 (en) | Method, apparatus and computer program for loading files during a boot-up process | |
| JP4735765B2 (en) | Linux program startup system | |
| KR101113342B1 (en) | Boot-loader version managing method for mobile communication terminal | |
| CN114090028A (en) | System upgrading method, electronic device and storage medium | |
| CN115904820A (en) | Recovery method and system for failed hard disk | |
| CN117369847A (en) | Method for upgrading firmware, electronic device and storage medium | |
| CN114281368A (en) | Installation method and device of operating system, computer equipment and storage medium | |
| CN117235707A (en) | Application program starting method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |