CN110413230A - A kind of embedded system construction method and storage medium - Google Patents
A kind of embedded system construction method and storage medium Download PDFInfo
- Publication number
- CN110413230A CN110413230A CN201910628547.9A CN201910628547A CN110413230A CN 110413230 A CN110413230 A CN 110413230A CN 201910628547 A CN201910628547 A CN 201910628547A CN 110413230 A CN110413230 A CN 110413230A
- Authority
- CN
- China
- Prior art keywords
- partition
- file
- user
- script
- disk
- 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.)
- Granted
Links
- 238000003860 storage Methods 0.000 title claims abstract description 17
- 238000010276 construction Methods 0.000 title claims abstract description 8
- 238000005192 partition Methods 0.000 claims abstract description 174
- 238000000034 method Methods 0.000 claims description 15
- 101100226364 Arabidopsis thaliana EXT1 gene Proteins 0.000 claims description 3
- 238000001514 detection method Methods 0.000 abstract 1
- 230000007613 environmental effect Effects 0.000 abstract 1
- 238000005516 engineering process Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000007689 inspection Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
Classifications
-
- 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
-
- 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
- G06F3/0674—Disk device
- G06F3/0676—Magnetic disk device
-
- 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/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of embedded system construction method and storage mediums, disk is divided into four areas, after disk partition file system is by carry and detection, the automatic perform script file of Ramdisk file system can also load the customized starting configuration script of the user in second disk subregion and execute.In the customized starting script of the user of the second subregion of execution, the library file of second subregion is mounted to below the library directory of Ramdisk root file system, and the relevant configurations such as environmental variance for increasing system executing application needs, the application program for finally loading third subregion execute.The user application of third subregion is written and read the data in magnetic disk in the 4th subregion.The present invention can ensure system reliability service, even if system can also resume operation automatically in starting next time in the case where system power-off illegally, substantially increase the dynamic configuration and flexibility of whole system.
Description
Technical Field
The present invention relates to embedded systems, and more particularly, to a method for constructing an embedded system and a storage medium.
Background
Embedded systems are increasingly used in a wide range of applications, including many areas of human life, such as digital communications, information appliances, aerospace, industrial process control, engineering machinery control, and military electronics. The embedded technology is more and more closely related to the aspects of daily life of people, and the integration trend of consumer electronics, computers and communication is more and more obvious, so that the embedded technology is an important component in the field of computers.
The embedded system is based on computer technology and has available software and hardware, and is suitable for application system with strict function, reliability, cost, volume and power consumption constraints.
Embedded systems are generally composed of embedded software and hardware, and the software is tightly integrated with the hardware. The hardware takes an embedded microprocessor as a core, and integrates a memory and input and output equipment special for the system; the software comprises initialization codes and drivers, an embedded operating system, application programs and the like, and the software is organically combined together to form system-specific integrated software.
In the using process of the embedded system, a user may illegally power off the embedded system at any time, so that certain measures need to be taken to ensure that the embedded system can stably and reliably operate. The existing conventional processing mode for the embedded system adopting Emmc storage is as follows: forbidding forced power failure of embedded equipment, such as mobile phone equipment, so that a battery cannot be forcibly disassembled, and when a system battery is exhausted, the power failure is processed through a certain shutdown process; in other embedded devices, the root file system may run directly in the disk, and all read-write operations operate the disk, so that the possibility of disk damage is greatly increased under the condition of illegal power failure, and under the condition of disk damage, certain measures are required to be adopted to repair or isolate the damaged disk.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide an embedded system construction method and a storage medium for overcoming the defects in the prior art, so that the constructed system can stably and reliably operate, a root file system is operated in a memory, the system operation speed is increased, the controllability of the system is ensured, and even if the system is powered on illegally to cause errors of the disk file system, the next system can automatically repair the disk file system.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows: an embedded system construction method comprises the following steps:
preparing a storage medium for system startup in advance, wherein the storage medium comprises four partitions, and a first partition is used for a boot file for system startup; the second partition is used for storing library files and starting configuration files; the third partition is used for storing an executable file of a user and a corresponding configuration file; the fourth partition is used for storing data read and written by user application;
when the system is booted, loading a system kernel mirror image and a Ramdisk memory file system from a first partition to a memory for operation;
the starting configuration script in the Ramdisk memory file system automatically mounts the second, third and fourth partitions to subdirectories of the root file system, and then executes the user-defined starting script in the loaded second partition;
a second partition user self-defined starting script links the library file compiled by the user to a Ramsisk library file directory;
the second partition user self-defined starting script starts the executable application program of the third partition;
the third partition may execute the application to store or read the service data to or from the fourth partition.
The first partition is in a Fat file system format; the second partition, the third partition and the fourth partition are all in the Ext4 file system format. The three mounted disk partitions are the Ext4 file system, and the system can automatically detect and recover when being powered on and started, so that the stability and reliability of the system after being started are ensured.
The first partition, the second partition and the third partition are read-only partitions; the fourth partition is a readable and writable partition.
When the system is guided, the specific implementation process from the loading of the system in the first partition to the running of the memory comprises the following steps: copying an initial boot file of the system into an SD card or programming the initial boot file into Qspi, and after the system is powered on again, booting the system from the SD card or the Qspi to execute; and copying the boot file in the U disk into the first partition of Emmc.
After the system loads the boot file from the first partition, the first partition is not mounted in the file system, so that after the system is started, the first partition is hidden, a user cannot perform any operation on the partition, and even under the condition of illegal power failure, the file system of the first partition cannot be damaged.
The method comprises the steps that when a Ramdisk memory file system is automatically mounted to the second, third and fourth partitions of a disk, the Ramdisk file firstly mounts the second, third and fourth partitions to a root file system in an EXT4 disk file system format, and disk inspection and repair are carried out on each partition. The root file system is based on Ramdisk, reading and writing of the root file system are carried out in the memory, and Emmc disk partitions cannot be operated, so that after illegal power failure, no influence is caused on the disks. The root file system is based on Ramdisk, and the whole root file system runs in the memory, so that the running speed of the system is very high. The root file system is based on the Ramdisk, and the operation of the root file system can be automatically restored after the system is powered on next time, so that the whole file system can be completely controlled by a user who operates the read-write operation of the service data, and when the user upgrades the file system, only the Ramdisk mirror image file needs to be upgraded without worrying about the damage of the original disk file data in the file system.
When the system is started, the user-defined configuration file of the second partition is embedded into the starting script of the Ramdisk root file system to run, and the user can modify the starting configuration file only by re-mounting the partition into a read-write state without re-modifying and packaging the whole Ramdisk mirror image, so that the flexibility of the system is greatly improved.
When the user self-defined starting script of the second partition is executed, the library file of the second partition is soft-linked to the root file system, the environment variable required by application execution is initialized, and finally the user application program of the third partition is loaded for execution.
The library file compiled by the user is used for mounting the library file directory of the Ramdisk root file system in a soft link mode, so that the size of a Ramdisk mirror image is greatly reduced, the user can also dynamically add and delete the library file compiled by the user, the starting speed of the system is increased, and the dynamic configuration and flexibility of the system are also increased.
And mounting the second partition and the third partition in a read-only mode, so that the file system cannot perform write operation on the two partitions, thereby protecting the two disk partitions, and only when a user upgrades the library files or the application programs of the two partitions, the two partitions are mounted again in a read-write mode.
And after the third partition executable application program stores the service data into the fourth partition or reads the data from the fourth partition, the system is powered on again, the initial boot file is executed from Emmc, and then the kernel and the Ramdisk file system are loaded for execution.
The application program reads and writes the fourth partition, all user data are stored in the partition, when the partition is automatically powered on and started, the error of the partition can be self-checked and recovered, if a disk file system is damaged due to error in the reading and writing process, the partition can be independently processed, the situation that the system cannot be normally started and the application program cannot be started and executed is avoided, when a user upgrades, the user does not need to pay attention to a user service data disk, and only files of the previous partitions need to be upgraded, so that system files, configuration files and service data in the system files are separated, and the system is easier to maintain.
Correspondingly, the invention also provides an embedded system storage medium which comprises four partitions, wherein the first partition is used for a boot file of system startup; the second partition is used for storing library files and starting configuration files; the third partition is used for storing an executable file of a user and a corresponding configuration file; the fourth partition is used for storing data read and written by user application; wherein,
loading the system from the first partition to a memory for running when the system is booted;
mounting the second, third and fourth partitions under subdirectories of a Ramdisk memory file system;
after the second partition is loaded, a starting configuration script in the Ramdisk guides a user-defined starting script in the second partition to run;
a second partition user self-defined starting script links the library file compiled by the user to a Ramsisk library file directory;
the second partition user self-defined starting script starts the executable application program of the third partition;
the third partition may execute the application to store or read the service data to or from the fourth partition.
The first partition is in a Fat file system format; the second partition, the third partition and the fourth partition are all in the Ext4 file system format.
The first partition, the second partition and the third partition are read-only partitions; the fourth partition is a readable and writable partition.
Compared with the prior art, the invention has the beneficial effects that: the method can ensure that the system runs quickly, stably and reliably, is simple, convenient, quick and reliable, and only needs to prepare the boot file, the Ramdisk file system, the library file and the configuration file in advance and automatically store all the files prepared in advance into each corresponding partition of Emmc through the script file defined by a user. After the system is powered off and rebooted, the system can be quickly loaded into the memory for operation, and the stability and reliability of the system can be ensured. The method can ensure that the system can automatically recover operation when the system is started next time even under the condition of illegal power failure of the system, the user-defined starting configuration file is embedded into the starting configuration script of the Ramdisk root file system for execution, and the library file compiled by the user is linked to the library directory of the Ramdisk root file system, so that the dynamic configuration and the flexibility of the whole system are greatly improved.
Drawings
FIG. 1 is a storage media partition for system boot.
Fig. 2 is a flow chart of constructing a stable and reliable embedded system.
FIG. 3 is a flow chart of the embedded system after the system is built.
Detailed Description
As shown in fig. 1, in order to construct a stable and reliable embedded system, when constructing an embedded system, the distribution of a system boot storage medium needs to be considered in advance: dividing a storage medium for system startup into four partitions (the size of each partition can be determined according to the size of a file stored in each partition), wherein the first partition is used for storing a boot file during system startup, the second partition is used for storing a library file compiled by a user (such as a Qt library file and an OpenCV library file) and a custom startup configuration file (such as an autostart script. After the system is started, the first partition is hidden for a common user, only the last three partitions are shown, the first three partitions are read-only partitions, and only the last partition can be subjected to read-write operation.
The method for constructing the stable and reliable embedded system comprises the following steps:
1, copying an initial boot file of a system to an SD (secure digital) card through a PC (personal computer) or burning the initial boot file into a Qspi through a Jtag tool, so that the system is booted and executed from the SD card or the Qspi;
step 2, inserting the U disk storing other files such as a boot file, a mirror image, a start configuration file, a library file and the like into the system;
step 3, restarting the system;
step 4, after the system is powered on, firstly, the initial boot file is guided from the SD card or the Qspi to be executed; reading a Linux kernel and a Ramdisk file system from the U disk by the initial boot file, executing, and successfully entering the file system after the execution is finished; in a file system, an Emmc disk is formatted according to a disk partition of FIG. 1 by a system command; after the partitions are formatted, copying other files such as boot files, kernels, Ramdisk file system images, library files and the like in the U disk to each corresponding disk partition of Emmc (comprising steps 5 and 6);
after a file system is configured in a/etc/fstab file of a Ramdisk mirror image, a partition in an Ext4 format is automatically mounted in a root file system, the error of the file system is checked and recovered, and a call for a second partition starting script file is embedded in a starting automatic execution script file/etc/init.d/rcS of the file system, so that when a user needs to modify the system starting configuration, the system can be realized by modifying a configuration file of a second partition, and because a rcS file in the root file system can be automatically restored to factory configuration after the system is powered off;
step 5, copying the library file in the U disk and the user-defined starting configuration file to a second partition of the disk;
in the user-defined configuration file, the library file of the partition is softly linked to a library file directory of a Ramdisk root file system, the relevant environment variable for starting an application program is configured, and finally the application program of a third partition is configured to be automatically executed when the system is started;
step 6, copying the application program and the related configuration file in the USB flash disk to a third partition, and performing read-write operation on data in a fourth partition when the application program is executed;
and 7, restarting the system after power failure, so that the system boots the initial boot file, the kernel and the file system from the first disk partition of Emmc, and initializing the whole system according to the steps of FIG. 3.
According to step 4, the Ramdisk file firstly mounts the second, third and fourth partitions under the root file system in the format of EXT4 disk file system, and performs disk inspection and repair on each partition;
after the file system is started, the start script file is executed rcS, so that the user-defined start script file in the third partition is executed, as described in step 4;
when the user-defined script of the second partition is executed, softly linking the library file of the partition to the root file system, initializing the environment variables required by application execution, and finally loading the user application program of the third partition for execution;
and 6, performing read-write operation on the data in the fourth partition by the user application of the third partition.
After the file system is started, the first partition cannot be mounted, is hidden for common users, and only shows the last three partitions. The first three partitions relate to boot files, configuration, libraries and executable programs of the system, a user cannot modify the boot files, and the first three partitions can be operated only during upgrading, so that the safety and the stability of the system are guaranteed.
And the Emmc disk partition and the copying of the U disk file to the disk partition corresponding to the Emmc can be performed manually or automatically through a script file.
The invention can quickly construct a stable and reliable embedded system, and can automatically recover the file system when the system is started next time even if the file system makes mistakes or the system is illegally powered off in the system execution process, thereby ensuring the stable and reliable operation of the system.
Claims (10)
1. A method for constructing an embedded system is characterized by comprising the following steps:
preparing a storage medium for system startup in advance, wherein the storage medium comprises four partitions, and a first partition is used for a boot file for system startup; the second partition is used for storing library files and starting configuration files; the third partition is used for storing an executable file of a user and a corresponding configuration file; the fourth partition is used for storing data read and written by user application;
when the system is guided, loading the system from the first partition to the memory for operation;
the starting configuration script in the Ramdisk memory file system automatically mounts the second, third and fourth partitions to subdirectories of the root file system, and then executes the user-defined starting script in the loaded second partition;
a second partition user self-defined starting script links the library file compiled by the user to a Ramsisk library file directory;
the second partition user self-defined starting script starts the executable application program of the third partition;
the third partition may execute the application to store or read the service data to or from the fourth partition.
2. The embedded system construction method according to claim 1, wherein the first partition is in a Fat file system format; the second partition, the third partition and the fourth partition are all in the Ext4 file system format.
3. The embedded system construction method according to claim 1, wherein the first partition, the second partition, and the third partition are read-only partitions; the fourth partition is a readable and writable partition.
4. The method for constructing an embedded system according to claim 1, wherein the specific implementation process from loading the system in the first partition to running the memory during system boot includes: copying an initial boot file of the system into an SD card or programming the initial boot file into Qspi, and after the system is powered on again, booting the system from the SD card or the Qspi to execute; and copying the boot file in the U disk into the first partition of Emmc.
5. The embedded system construction method according to claim 4, wherein the Ramdisk memory file system is automatically mounted to the second, third, and fourth partitions of the disk, the Ramdisk file first mounts the second, third, and fourth partitions to the root file system in the EXT4 disk file system format, and performs disk checking and repairing on each partition.
6. The embedded system building method according to claim 4, wherein the user-defined startup script of the second partition, when executed, soft-links the library file of the second partition to the root file system, initializes environment variables required for application execution, and finally loads the user application program of the third partition for execution.
7. The embedded system building method according to claim 1, wherein the third partition executable application stores the service data in the fourth partition or reads the data from the fourth partition, and then the system is powered up again, executes the initial boot file from Emmc, and then loads the kernel and the Ramdisk file system for execution.
8. An embedded system storage medium, comprising: the first partition is used for booting a boot file of the system; the second partition is used for storing library files and starting configuration files; the third partition is used for storing an executable file of a user and a corresponding configuration file; the fourth partition is used for storing data read and written by user application; wherein,
loading the system from the first partition to a memory for running when the system is booted;
the starting configuration script in the Ramdisk memory file system automatically mounts the second, third and fourth partitions to subdirectories of the root file system, and then executes the user-defined starting script in the loaded second partition;
a second partition user self-defined starting script links the library file compiled by the user to a Ramsisk library file directory;
the second partition user self-defined starting script starts the executable application program of the third partition;
the third partition may execute the application to store or read the service data to or from the fourth partition.
9. The embedded system storage medium of claim 8, wherein the first partition is in a Fat file system format; the second partition, the third partition and the fourth partition are all in the Ext4 file system format.
10. The embedded system storage medium of claim 8, wherein the first partition, the second partition, and the third partition are read-only partitions; the fourth partition is a readable and writable partition.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910628547.9A CN110413230B (en) | 2019-07-12 | 2019-07-12 | Embedded system construction method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910628547.9A CN110413230B (en) | 2019-07-12 | 2019-07-12 | Embedded system construction method and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110413230A true CN110413230A (en) | 2019-11-05 |
| CN110413230B CN110413230B (en) | 2023-01-06 |
Family
ID=68361218
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910628547.9A Active CN110413230B (en) | 2019-07-12 | 2019-07-12 | Embedded system construction method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110413230B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111176665A (en) * | 2019-12-26 | 2020-05-19 | 晶晨半导体（深圳）有限公司 | Method and device for manufacturing high-capacity emmc mirror image |
| CN113778760A (en) * | 2021-11-11 | 2021-12-10 | 麒麟软件有限公司 | Key data self-destruction and automatic restoration method and device based on embedded system |
| CN113918228A (en) * | 2021-09-15 | 2022-01-11 | 成都安恒信息技术有限公司 | Memory file system starting method based on multi-CPU architecture |
| CN113986124A (en) * | 2021-10-25 | 2022-01-28 | 深信服科技股份有限公司 | User configuration file access method, device, equipment and medium |
| CN114063913A (en) * | 2021-11-03 | 2022-02-18 | 东风汽车集团股份有限公司 | EMMC partition storage method and structure |
| CN114124684A (en) * | 2021-10-22 | 2022-03-01 | 杭州依赛通信有限公司 | Method for realizing zero-contact full-automatic network element deployment by using USB flash disk |
| CN114356443A (en) * | 2021-12-23 | 2022-04-15 | 常州新途软件有限公司 | The management method based on the multi-partition of the instrument |
| CN115344546A (en) * | 2022-09-02 | 2022-11-15 | 深圳软牛科技有限公司 | Method for realizing memory file system and related device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5666540A (en) * | 1993-07-26 | 1997-09-09 | International Business Machines Corporation | Information processing system |
| JP2003150428A (en) * | 2001-11-08 | 2003-05-23 | Fujitsu Ltd | File system that enables repair of defective files |
| CN101477482A (en) * | 2008-10-14 | 2009-07-08 | 深圳市共进电子有限公司 | Method for recovering flash memory data at power-off of built-in Linux system |
| CN102262543A (en) * | 2010-05-25 | 2011-11-30 | 上海中标软件有限公司 | Power-failure resistant method for starting Linux system |
| CN102262568A (en) * | 2010-05-25 | 2011-11-30 | 上海中标软件有限公司 | Power-down prevention Linux system startup method |
| CN103106091A (en) * | 2013-01-31 | 2013-05-15 | 深圳市开立科技有限公司 | Start-up system and method of operating system based on removable storage media |
| CN106843940A (en) * | 2016-12-30 | 2017-06-13 | 长沙湘计海盾科技有限公司 | A kind of fast updating method of embedded system |
-
2019
- 2019-07-12 CN CN201910628547.9A patent/CN110413230B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5666540A (en) * | 1993-07-26 | 1997-09-09 | International Business Machines Corporation | Information processing system |
| JP2003150428A (en) * | 2001-11-08 | 2003-05-23 | Fujitsu Ltd | File system that enables repair of defective files |
| CN101477482A (en) * | 2008-10-14 | 2009-07-08 | 深圳市共进电子有限公司 | Method for recovering flash memory data at power-off of built-in Linux system |
| CN102262543A (en) * | 2010-05-25 | 2011-11-30 | 上海中标软件有限公司 | Power-failure resistant method for starting Linux system |
| CN102262568A (en) * | 2010-05-25 | 2011-11-30 | 上海中标软件有限公司 | Power-down prevention Linux system startup method |
| CN103106091A (en) * | 2013-01-31 | 2013-05-15 | 深圳市开立科技有限公司 | Start-up system and method of operating system based on removable storage media |
| CN106843940A (en) * | 2016-12-30 | 2017-06-13 | 长沙湘计海盾科技有限公司 | A kind of fast updating method of embedded system |
Non-Patent Citations (1)
| Title |
|---|
| 田超: "基于ARM嵌入式系统上的SD卡驱动程序及文件系统的研究和开发", 《中国优秀硕士学位论文全文数据库》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111176665A (en) * | 2019-12-26 | 2020-05-19 | 晶晨半导体（深圳）有限公司 | Method and device for manufacturing high-capacity emmc mirror image |
| CN111176665B (en) * | 2019-12-26 | 2024-02-09 | 晶晨半导体（深圳）有限公司 | High-capacity emmc mirror image manufacturing method and device |
| CN113918228B (en) * | 2021-09-15 | 2023-10-13 | 成都安恒信息技术有限公司 | Memory file system starting method based on multi-CPU architecture |
| CN113918228A (en) * | 2021-09-15 | 2022-01-11 | 成都安恒信息技术有限公司 | Memory file system starting method based on multi-CPU architecture |
| CN114124684B (en) * | 2021-10-22 | 2024-04-19 | 杭州依赛通信有限公司 | Method for realizing zero-contact full-automatic deployment of network elements by using USB flash disk |
| CN114124684A (en) * | 2021-10-22 | 2022-03-01 | 杭州依赛通信有限公司 | Method for realizing zero-contact full-automatic network element deployment by using USB flash disk |
| CN113986124A (en) * | 2021-10-25 | 2022-01-28 | 深信服科技股份有限公司 | User configuration file access method, device, equipment and medium |
| CN113986124B (en) * | 2021-10-25 | 2024-02-23 | 深信服科技股份有限公司 | User configuration file access method, device, equipment and medium |
| CN114063913A (en) * | 2021-11-03 | 2022-02-18 | 东风汽车集团股份有限公司 | EMMC partition storage method and structure |
| CN113778760B (en) * | 2021-11-11 | 2022-03-11 | 麒麟软件有限公司 | Key data self-destruction and automatic restoration method and device based on embedded system |
| CN113778760A (en) * | 2021-11-11 | 2021-12-10 | 麒麟软件有限公司 | Key data self-destruction and automatic restoration method and device based on embedded system |
| CN114356443A (en) * | 2021-12-23 | 2022-04-15 | 常州新途软件有限公司 | The management method based on the multi-partition of the instrument |
| CN115344546A (en) * | 2022-09-02 | 2022-11-15 | 深圳软牛科技有限公司 | Method for realizing memory file system and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110413230B (en) | 2023-01-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110413230B (en) | Embedded system construction method and storage medium | |
| KR101856284B1 (en) | Backing up firmware during initialization of device | |
| US9703635B2 (en) | Method, computer program, and computer for restoring set of variables | |
| US20110302572A1 (en) | Embedded network device and firmware upgrading method | |
| CN101021797A (en) | Repairing and staging method for software of embedded system | |
| EP3769224B1 (en) | Configurable recovery states | |
| CN104123153A (en) | Apparatus and method for firmware upgrade using USB | |
| CN102135893A (en) | Method for integrating operating system on BIOS (Basic Input Output System) chip and starting operating system on server | |
| US10521218B2 (en) | Enhanced techniques for updating software | |
| CN102141923B (en) | Memory file system loading method and device | |
| CN104424047A (en) | NVRAM data recovery method and NVRAM data recovery device | |
| CN113238819B (en) | Dynamic loading method and system of drive file suitable for U-Boot | |
| US10204011B1 (en) | Techniques for partially restarting a computing device in response to a configuration change | |
| CN100395713C (en) | Method and module for automatically repairing basic input output system element | |
| US20060190933A1 (en) | Method and apparatus for quickly developing an embedded operating system through utilizing an automated building framework | |
| CN102135923A (en) | Method for integrating operating system into BIOS (Basic Input/Output System) chip and method for starting operating system | |
| CN100476745C (en) | Method for realizing automatic fault tolerance of image file in Linux operating system boot process | |
| CN113778485A (en) | System operation method, device, electronic chip and storage medium of electronic chip | |
| CN105630523A (en) | Computer BIOS data recovery system and method | |
| CN112463240B (en) | Method for restarting access to WinPE | |
| CN100361075C (en) | Method and device for rapidly developing embedded system by applying automatic compiling framework | |
| CN111868698A (en) | Free space direct connection | |
| CN115421762A (en) | BMC (baseboard management controller) firmware upgrading method, device, equipment and medium | |
| Tyler | XDA Developers' Android Hacker's Toolkit: The Complete Guide to Rooting, ROMs and Theming | |
| KR101420026B1 (en) | A method, apparatus and computer program for loading files during a boot-up process |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |