CN109857468B - Method and system for supporting multiple DTBs in single Linux system mirror image - Google Patents
Method and system for supporting multiple DTBs in single Linux system mirror image Download PDFInfo
- Publication number
- CN109857468B CN109857468B CN201910008920.0A CN201910008920A CN109857468B CN 109857468 B CN109857468 B CN 109857468B CN 201910008920 A CN201910008920 A CN 201910008920A CN 109857468 B CN109857468 B CN 109857468B
- Authority
- CN
- China
- Prior art keywords
- dtb
- file
- linux system
- files
- image
- 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.)
- Active
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for supporting multiple DTBs in a single Linux system mirror image, which relate to the technical field of computer communication. When a bootstrap program boots a system, a plurality of products use the same Linux system mirror image file, and load the corresponding DTB file through the corresponding strategy, so that the aim of supporting a plurality of different DTB files in the same Linux system mirror image is fulfilled, and the aim of uniformly using one Linux system mirror image by a plurality of products is fulfilled.
Description
Technical Field
The invention relates to the technical field of computer communication, in particular to a method and a system for supporting multiple DTBs (dynamic time slots) in a single Linux system mirror image.
Background
A Device tree (Device tree) is a set of rules used in the Linux system to describe the ownership of hardware, and describes the parameters of target hardware in a tree data structure; DTS (device tree syntax) is a device tree source file and adopts a text format; the dtb (device tree blob) is a binary file compiled from a DTS file and is programmed into the storage medium. Dtc (device tree builder) is a small tool responsible for converting DTS into dtb (device tree blob). When the Linux system is started, a boot program (such as Uboot and boot loader) reads a DTB file into a memory before starting the Linux system mirror image, jumps to the Linux system mirror image to execute, and transmits a DTB starting address to the Linux system mirror image. The Linux system mirror image can analyze the whole equipment tree according to the DTB structure through the initial address to complete the initialization of the hardware drive. The introduction of the device tree reduces the change of system mirror images required for supporting new hardware, improves code reuse, accelerates the development of Linux support packages, and enables a single Linux system mirror image to support a plurality of systems.
In Linux product development, an operating system Image (OS Image) generated by a product is usually packaged by three files: a system image file (uinmage or zmmage), a DTB file and a root file system file (RootFS). Due to the difference of the device tree files, the packaging files of each product are different, namely, a company still has to maintain a set of Linux system images for each product. This is uneconomical both from a product development point of view and from a product maintenance point of view.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a method and a system for supporting multiple DTBs in a single Linux system mirror image, so as to support multiple different DTB files in the same Linux system mirror image.
In a first aspect, a method for supporting multiple DTBs in a single Linux system image is provided, including:
integrating a plurality of different DTB files into a DTB integrated file, packaging the DTB integrated file and Linux system mirror images containing all product drivers in the same Linux system mirror image version into a Linux system mirror image file;
when the bootstrap program is started, the DTB file corresponding to each product is loaded by modifying the bootstrap program code.
According to the first aspect, in a first implementation manner of the first aspect, the integrating the multiple different DTB files into one DTB integration file specifically includes the following steps:
compiling DTB files of a plurality of products by using a DTC tool;
filling each generated DTB file into a file with a set size by using a script tool, or specifying the size of the DTB file to be the set size when the DTB file is generated by using the DTC tool;
and combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
According to the first aspect, in a second implementation manner of the first aspect, the packaging the DTB integration file and the Linux system image images including all product drivers in the same Linux system image version into a Linux system image file specifically includes the following steps:
and packaging the DTB integration file, the Linux system mirror images containing all product drivers in the same Linux system mirror image version and the root file system into a Linux system mirror image file by using an mkimage tool.
According to the first aspect, in a third implementation manner of the first aspect, when the bootstrap program is started, the step of loading the DTB file corresponding to each product by modifying the bootstrap program code specifically includes the following steps:
judging whether a product identification mechanism is provided;
if yes, modifying the bootstrap code, and jumping to a corresponding code branch through a product identification mechanism to automatically load a DTB (data transfer bus) file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
According to a third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the loading the DTB file corresponding to each product by setting the environment variable specifically includes the following steps:
setting the environment variables as: UBoot > fdt addrDTB _ BASE + m filter size, wherein:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
In a second aspect, a system for supporting multiple DTBs in a single Linux system image is provided, comprising:
the file integration module is used for integrating a plurality of different DTB files into one DTB integration file;
the image packaging module is used for packaging the DTB integration file and the Linux system image images containing all product drivers under the same Linux system image version into a Linux system image file;
and the file loading module is used for loading the DTB files corresponding to the products by modifying the codes of the bootstrap program when the bootstrap program is started.
According to the second aspect, in a first implementation manner of the second aspect, the integrating module integrates a plurality of different DTB files into one DTB integration file, and specifically includes the following steps:
compiling DTB files of a plurality of products by using a DTC tool;
filling each generated DTB file into a file with a set size by using a script tool, or specifying the size of the DTB file to be the set size when the DTB file is generated by using the DTC tool;
and combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
According to a second aspect, in a second implementation manner of the second aspect, the image packaging module packages the DTB integration file and the Linux system image images including all product drivers in the same Linux system image version into a Linux system image file, which specifically includes the following steps:
and packaging the DTB integration file, the Linux system mirror images containing all product drivers in the same Linux system mirror image version and the root file system into a Linux system mirror image file by using an mkimage tool.
According to the second aspect, in a third implementation manner of the second aspect, the loading module loads the DTB file corresponding to each product by modifying the boot program code when the boot program is started, and specifically includes the following steps:
judging whether a product identification mechanism is provided;
if yes, modifying the bootstrap code, and jumping to a corresponding code branch through a product identification mechanism to automatically load a DTB (data transfer bus) file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
According to a third implementation manner of the second aspect, in a fourth implementation manner of the second aspect, the loading module loads the DTB file corresponding to each product by setting an environment variable, and specifically includes the following steps:
setting the environment variables as: UBoot > fdt addr DTB _ BASE + m filter size, where:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
Compared with the prior art, the invention has the advantages that:
the invention integrates a plurality of different DTB files into a unified DTB integrated file, and packs the integrated DTB integrated file and the Linux system mirror image containing all product drivers in the same Linux system mirror image version into the Linux system mirror image file. When a bootstrap program boots a system, a plurality of products use the same Linux system mirror image file, and load the corresponding DTB file through the corresponding strategy, so that the aim of supporting a plurality of different DTB files in the same Linux system mirror image is fulfilled, and the aim of uniformly using one Linux system mirror image by a plurality of products is fulfilled.
Drawings
FIG. 1 is a schematic flow chart illustrating a DTB integration file generation method for supporting multiple DTBs in a single Linux system image according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a method for generating a Linux system image file that supports multiple DTBs in a single Linux system image according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating loading of a DTB file corresponding to each product by modifying a boot code according to the method for supporting multiple DTBs in a single Linux system image in an embodiment of the present invention.
Detailed Description
Description of terms:
UBoot: the Universal Boot Loader is an open source code item that complies with the terms of GPL (GNU General Public License, an abbreviation of GNU General Public License informal Chinese translation). The role of UBoot is system guidance. The source code catalog and compiling form of the UBoot are similar to the mirror image of a Linux system, in fact, many UBoot source codes are formed by simplifying corresponding Linux system mirror source programs, especially drivers of some devices, and this can be reflected from the annotation of the UBoot source codes. The UBoot not only supports the boot of an embedded Linux system, but also supports embedded operating systems such as NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS, android and the like. The target operating systems to be supported at present are OpenBSD, NetBSD, FreeBSD,4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, LynxOS, pSOS, QNX, RTEMS, ARTOS, android. This is a layer of meaning of Universal in the UBoot, and the other layer of meaning is that the UBoot can support not only a processor of PowerPC (Performance Optimization With Enhanced RISC-Performance Computing, sometimes abbreviated as PPC, which is a central processing unit of a reduced instruction set architecture) series, but also a plurality of processors of common series such as MIPS, x86, ARM, NIOS, XScale, and the like. These two features are the development goals of the UBoot project, namely, supporting as many embedded processors and embedded operating systems as possible. As far as the current point of view, UBoot supports most abundantly the PowerPC series processor and most perfectly the Linux.
mkimege tool: tools under the tools/directories of the UBoot source code that can be used to make various bootable image files that are uncompressed or compressed. When an mkimage creates an image file, a header of 0x40 bytes is added in front of the original executable image file, and information specified by parameters is recorded, so that the UBoot can identify which CPU architecture the image is for, which OS, which type in the loaded memory, where the entry point is in the memory, and what the name of the image is.
FPGA: the Field-Programmable gate array is a product further developed on the basis of Programmable devices such as PAL (Phase alternation Line, meaning Phase-alternating Line), GAL (a Device designed by Lattice on the basis of PAL, that is, a general array Logic Device), CPLD (Complex Programmable Logic Device, a Device developed from PAL and GAL devices), and the like. The circuit is a semi-custom circuit in the field of Application Specific Integrated Circuits (ASIC), not only overcomes the defects of the custom circuit, but also overcomes the defect that the number of gate circuits of the original programmable device is limited.
A dial switch: the dial switch has many kinds, and the main principle is binary combination, each bit has two kinds of combinations of 0 and 1, so there are 2 combinations in 4 powers, namely 16 combinations, and the MCU (Microcontroller Unit) recognizes the combination and then makes different responses.
Image: image is objcopy processed system Image code containing only binary data, which is not already in elf format, but the system Image in this format has not yet been compressed. Objcopy is a GNU (GNU is Not Unix, an abbreviation, and is a free operating system) use utility, and Objcopy functions to copy the contents of one object file into another object file, that is, an object file in one format can be converted into an object file in another format. By using binary as the output target, an original binary file can be generated, essentially all symbols and relocation information will be discarded, leaving only binary data.
zImage: zmima is a compressed image file commonly used by ARM (Advanced RISC Machines, a RISC microprocessor) Linux, and is formed by compressing uncompressed system images (vmlinux) plus decompression codes, and the command format is # make zmima. It is applicable to the case of small system images, which exist for backward compatibility.
The present invention will be described in further detail with reference to the accompanying drawings and examples.
Example 1:
referring to fig. 1, an embodiment of the present invention provides a method for supporting multiple DTBs in a single Linux system image, including:
integrating a plurality of different DTB files into a DTB integrated file (namely DEV. DTB in figure 1), and packaging the DTB integrated file and Linux system mirror images containing all product drivers under the same Linux system mirror image version into a Linux system mirror image file (namely Linux. kernel. image in figure 1);
when the boot program (Uboot or bootloader, etc.) is started, the DTB file corresponding to each product is loaded by modifying the boot program code.
The invention integrates a plurality of different DTB files into a unified DTB integrated file, and packs the integrated DTB integrated file and the Linux system mirror image containing all product drivers in the same Linux system mirror image version into the Linux system mirror image file. When a bootstrap program boots a system, a plurality of products use the same Linux system mirror image file, and load the corresponding DTB file through the corresponding strategy, so that the aim of supporting a plurality of different DTB files in the same Linux system mirror image is fulfilled, and the aim of uniformly using one Linux system mirror image by a plurality of products is fulfilled.
Example 2:
on the basis of embodiment 1, referring to fig. 2, the integrating of multiple different DTB files into one DTB integrated file specifically includes the following steps:
compiling DTB files of a plurality of products by using a DTC tool;
each DTB file generated is filled into a file of a set size using a scripting tool.
And combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
Because a common storage medium such as a flash generally uses n × 32 kbytes as a sector unit, and considering that a DTB file is generally not larger than 50 kbytes, a script tool is used to fill each generated DTB file into a file with a size of 64 kbytes, or a DTC tool is used to designate the size of the DTB file as 64 kbytes when the DTB file is generated;
when a script tool is used to fill each generated DTB file into a file with the size of 64K, the actual size of the device tree file can be obtained from the self-contained attribute of the file, the remaining filling content is 0 or 1, and finally, characters such as a product feature code, MD5 and the like can be added, and the user can define the actual size of the device tree file. The filler content and the device tree file can be viewed as 2 non-interfering files.
The padding size is not limited to 64KB, which is only an empirical or suggested value. The main reasons for using 64KB have several reasons:
1. DTB files are typically smaller than 30KB, 64KB already being very large. Of course very large files do exist, it is also possible to use values larger than 64 KB.
2. The DTB file is stored in a storage device such as a NOR flash, a NAND flash. Since the NOR flash usually uses RAW mode (without file system) to access files, the size of one sector of the current NOR flash is 64KB or 128KB, so that the use of multiple of 64KB is reasonable; meanwhile, since many devices have a NOR flash of 512KB, if the manufacturer uses a NOR flash of 512KB to store Uboot images and multiple DTB files at the same time for cost saving, then using 64KB is a relatively reasonable setting. The NAND flash is generally large and has a file system, so that the limitation does not exist.
Combining the above two points, NOR flash has a slower access speed due to the slower reading speed of larger files, so the minimum 64KB comparison efficiency is used.
The method for packaging the DTB integration file and the Linux system mirror images of all product drivers under the same Linux system mirror image version into the Linux system mirror image file specifically comprises the following steps:
and packaging the DTB integration file, the Linux system image images (uImage or zImage) containing all product drivers under the same Linux system image version and the root file system into a Linux system image file by using an mkimage tool.
Example 3:
on the basis of embodiment 1, referring to fig. 3, when the bootstrap program is started, the step of loading the DTB file corresponding to each product by modifying the bootstrap program code specifically includes the following steps:
judging whether a product identification mechanism (FPGA identification or dial switch identification and the like) is provided;
the FPGA identification process comprises the following steps: the designated register of the FPGA is stored with a pre-embedded product identification code. When the bootstrap program is started, the CPU accesses a designated register of the FPGA through a designated interface (Local Bus or SPI and the like) communicated with the FPGA, reads a product identification code, and loads a corresponding DTB file according to the identification code.
The identification process of the dial switch comprises the following steps: the dip switch may be equivalent to a set of resistors that can change settings, with a product corresponding to a set of fixed resistance values, i.e., a fixed dip switch preset value. When the bootstrap program is started, the CPU reads the preset value of the dial switch through a specific interface (generally GPIO) to obtain a product identification code, and loads a corresponding DTB file according to the identification code.
If yes, modifying the bootstrap code, and jumping to a corresponding code branch through a product identification mechanism to automatically load a DTB (data transfer bus) file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
The loading of the DTB files corresponding to the products by setting the environment variables specifically comprises the following steps:
setting the environment variables as: UBoot > fdt addr DTB _ BASE + m filter size, where:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
For example, when the set size of the DTB file is 64kb, the environment variables are set as: UBoot > fdt addr DTB _ BASE + m 0x 10000.
Example 4:
the embodiment of the invention discloses a system for supporting multiple DTBs in a single Linux system mirror image, which comprises:
the file integration module is used for integrating a plurality of different DTB files into one DTB integration file;
the image packaging module is used for packaging the DTB integration file and the Linux system image images containing all product drivers under the same Linux system image version into a Linux system image file;
and the file loading module is used for loading the DTB files corresponding to the products by modifying the codes of the bootstrap program when the bootstrap program is started.
Example 5:
on the basis of embodiment 4, the file integration module integrates a plurality of different DTB files into one DTB integration file, and specifically includes the following steps:
the DTB files for a plurality of products are generated using the DTC tool compilation.
Filling each generated DTB file into a file with a set size by using a script tool, or specifying the size of the DTB file to be the set size when the DTB file is generated by using the DTC tool;
and combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
The image packaging module packages the DTB integration file and the Linux system image images containing all product drivers in the same Linux system image version into a Linux system image file, and specifically comprises the following steps:
and packaging the DTB integration file, the Linux system mirror images containing all product drivers in the same Linux system mirror image version and the root file system into a Linux system mirror image file by using an mkimage tool.
Example 6:
on the basis of embodiment 4, when the boot program is started, the file loading module loads the DTB file corresponding to each product by modifying the boot program code, and specifically includes the following steps:
judging whether a product identification mechanism (FPGA identification or dial switch identification and the like) is provided;
if yes, modifying the bootstrap code, and jumping to a corresponding code branch through a product identification mechanism to automatically load a DTB (data transfer bus) file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
The file loading module loads the DTB files corresponding to the products by setting the environment variables, and specifically comprises the following steps:
setting the environment variables as: UBoot > fdt addr DTB _ BASE + m filter size, where:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
For example, when the set size of the DTB file is 64kb, the environment variables are set as: UBoot > fdt addr DTB _ BASE + m 0x 10000.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (8)
1. A method for supporting multiple DTBs in a single Linux system image, comprising:
integrating a plurality of different DTB files into a DTB integrated file, packaging the DTB integrated file and Linux system mirror images containing all product drivers in the same Linux system mirror image version into a Linux system mirror image file;
when the bootstrap program is started, loading DTB files corresponding to products by modifying the bootstrap program codes;
the method specifically comprises the following steps of loading the DTB files corresponding to the products by setting environment variables:
setting the environment variables as: UBoot > fdt addr DTB _ BASE + m filter size, where:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
2. The method of claim 1, wherein the method for supporting multiple DTBs in a single Linux system image comprises: the integrating of the plurality of different DTB files into one DTB integrated file specifically comprises the following steps:
compiling DTB files of a plurality of products by using a DTC tool;
filling each generated DTB file into a file with a set size by using a script tool, or specifying the size of the DTB file to be the set size when the DTB file is generated by using the DTC tool;
and combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
3. The method of claim 1, wherein the method for supporting multiple DTBs in a single Linux system image comprises: the method for packaging the DTB integration file and the Linux system mirror images of all product drivers under the same Linux system mirror image version into the Linux system mirror image file specifically comprises the following steps:
and packaging the DTB integration file, the Linux system mirror image containing all product drivers in the same Linux system mirror image version and the root file system into a Linux system mirror image file by using an mkimage tool.
4. The method of claim 1, wherein the method for supporting multiple DTBs in a single Linux system image comprises: when the bootstrap program is started, the DTB file corresponding to each product is loaded by modifying the bootstrap program code, and the method specifically comprises the following steps:
judging whether a product identification mechanism is provided;
if yes, modifying the bootstrap code, jumping to a corresponding code branch through a product identification mechanism, and automatically loading a DTB file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
5. A system for supporting multiple DTBs in a single Linux system image, comprising:
the file integration module is used for integrating a plurality of different DTB files into one DTB integration file;
the image packaging module is used for packaging the DTB integration file and the Linux system image images containing all product drivers under the same Linux system image version into a Linux system image file;
the file loading module is used for loading the DTB files corresponding to the products by modifying the codes of the bootstrap program when the bootstrap program is started;
the file loading module loads the DTB files corresponding to the products by setting the environment variables, and specifically comprises the following steps:
setting the environment variables as: UBoot > fdt addr DTB _ BASE + m filter size, where:
fdt addr DTB _ BASE is a DTB loading BASE address, m is a serial number of a specified DTB file needing to be loaded, and the file size is the set size of the DTB file.
6. The system of claim 5, wherein the system supports multiple DTBs in a single Linux system image, wherein: the file integration module integrates a plurality of different DTB files into one DTB integration file, and specifically comprises the following steps:
compiling DTB files of a plurality of products by using a DTC tool;
filling each generated DTB file into a file with a set size by using a script tool, or specifying the size of the DTB file to be the set size when the DTB file is generated by using the DTC tool;
and combining a plurality of DTB files with set sizes into a DTB integrated file with n set sizes by using a script, wherein n is the total number of the DTB files.
7. The system of claim 5, wherein the system supports multiple DTBs in a single Linux system image, wherein: the image packaging module packages the DTB integration file and the Linux system image images containing all product drivers in the same Linux system image version into a Linux system image file, and specifically comprises the following steps:
and packaging the DTB integration file, the Linux system mirror image containing all product drivers in the same Linux system mirror image version and the root file system into a Linux system mirror image file by using an mkimage tool.
8. The system of claim 5, wherein the system supports multiple DTBs in a single Linux system image, wherein: when the file loading module bootstrap program is started, the DTB file corresponding to each product is loaded by modifying the bootstrap program code, and the method specifically comprises the following steps:
judging whether a product identification mechanism is provided;
if yes, modifying the bootstrap code, jumping to a corresponding code branch through a product identification mechanism, and automatically loading a DTB file corresponding to each product; and if not, loading the DTB files corresponding to the products by setting the environment variables.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910008920.0A CN109857468B (en) | 2019-01-04 | 2019-01-04 | Method and system for supporting multiple DTBs in single Linux system mirror image |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910008920.0A CN109857468B (en) | 2019-01-04 | 2019-01-04 | Method and system for supporting multiple DTBs in single Linux system mirror image |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109857468A CN109857468A (en) | 2019-06-07 |
| CN109857468B true CN109857468B (en) | 2022-03-01 |
Family
ID=66894038
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910008920.0A Active CN109857468B (en) | 2019-01-04 | 2019-01-04 | Method and system for supporting multiple DTBs in single Linux system mirror image |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109857468B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209059B (en) * | 2020-01-14 | 2023-03-03 | 中国北方车辆研究所 | Embedded software multi-version control system and method |
| CN112000382B (en) * | 2020-08-26 | 2023-10-13 | 绿盟科技集团股份有限公司 | Linux system starting method and device and readable storage medium |
| CN112559079A (en) * | 2020-12-22 | 2021-03-26 | 新华三大数据技术有限公司 | Data source connection driving self-adaptive loading method and device and electronic equipment |
| CN115866049B (en) * | 2023-02-22 | 2023-05-16 | 中国兵器装备集团自动化研究所有限公司 | HongMong system access interconnection device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541572A (en) * | 2010-12-08 | 2012-07-04 | 中兴通讯股份有限公司 | Method, system and device for realizing guide of operating system kernel |
| CN106569802A (en) * | 2016-10-17 | 2017-04-19 | 汉柏科技有限公司 | Manufacturing method and manufacturing device of ISO installation mirror images of firewalls |
| CN106951257A (en) * | 2017-03-24 | 2017-07-14 | 济南浪潮高新科技投资发展有限公司 | A kind of implementation method for starting WinCE with Uboot_CDROM |
| CN107632828A (en) * | 2016-07-18 | 2018-01-26 | 迈普通信技术股份有限公司 | More dts files support method, compilation device and embedded device |
| CN108170480A (en) * | 2017-12-25 | 2018-06-15 | 北京康拓科技有限公司 | A kind of startup method based on u-boot guiding μ C/OS operating systems |
Family Cites Families (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5379165A (en) * | 1993-03-19 | 1995-01-03 | Tandberg Data A/S | Method and apparatus for improving the accuracy of a tape servo track seek algorithm by using longitudinally correlated waveforms of lateral tape movement unique to each tape cassette |
| CN1274126C (en) * | 2002-07-15 | 2006-09-06 | 威盛电子股份有限公司 | Method of controlling radio network access via wired network access interface |
| CN101639782A (en) * | 2009-07-14 | 2010-02-03 | 上海市共进通信技术有限公司 | System bootloading method based on embedded operating system |
| CN102135908B (en) * | 2010-01-25 | 2013-01-23 | 研祥智能科技股份有限公司 | Method, device and computer system for switching operating system |
| CN103035264B (en) * | 2011-09-29 | 2015-07-08 | 凌阳科技股份有限公司 | Data recovery device and method |
| CN103123586A (en) * | 2011-11-17 | 2013-05-29 | 英业达股份有限公司 | Upgrade device based on Linux embedded operating system and method |
| CN103455345A (en) * | 2013-08-15 | 2013-12-18 | 京信通信系统（中国）有限公司 | Method and device for compressing and guiding mirror image file of embedded operation system |
| US20150074015A1 (en) * | 2013-09-12 | 2015-03-12 | SPEX Certiprep | System and method for disseminating a certified analysis for reference materials |
| CN103853557A (en) * | 2014-03-05 | 2014-06-11 | 中南大学 | Method for starting WinCE by utilizing Uboot network |
| CN104185023B (en) * | 2014-09-16 | 2017-02-15 | 上海通途半导体科技有限公司 | Automatic detecting method and device for three-dimensional video format |
| CN104791113B (en) * | 2015-03-20 | 2017-06-13 | 武汉理工大学 | Engine automatic start-stop Intellective method for triggering and system based on traveling road conditions |
| CN105159714B (en) * | 2015-09-02 | 2019-06-21 | 福州瑞芯微电子股份有限公司 | A kind of PMIC initial method and electronic equipment |
| CN105407140B (en) * | 2015-10-23 | 2018-08-17 | 上海比林电子科技有限公司 | A kind of computing resource virtual method of networking test system |
| CN106598780A (en) * | 2016-11-22 | 2017-04-26 | 深圳中科讯联科技股份有限公司 | System backup and recovery method and device |
| CN107562483A (en) * | 2017-07-26 | 2018-01-09 | 博为科技有限公司 | A kind of method and device of carry guiding file system |
| CN107577477B (en) * | 2017-09-06 | 2021-09-14 | 武汉虹信科技发展有限责任公司 | DTB file-based multi-platform software version self-adaption method and system |
| CN107729091A (en) * | 2017-11-30 | 2018-02-23 | 天津光电通信技术有限公司 | Embedded system platform and linux kernel associated documents generation method based on Zynq |
-
2019
- 2019-01-04 CN CN201910008920.0A patent/CN109857468B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541572A (en) * | 2010-12-08 | 2012-07-04 | 中兴通讯股份有限公司 | Method, system and device for realizing guide of operating system kernel |
| CN107632828A (en) * | 2016-07-18 | 2018-01-26 | 迈普通信技术股份有限公司 | More dts files support method, compilation device and embedded device |
| CN106569802A (en) * | 2016-10-17 | 2017-04-19 | 汉柏科技有限公司 | Manufacturing method and manufacturing device of ISO installation mirror images of firewalls |
| CN106951257A (en) * | 2017-03-24 | 2017-07-14 | 济南浪潮高新科技投资发展有限公司 | A kind of implementation method for starting WinCE with Uboot_CDROM |
| CN108170480A (en) * | 2017-12-25 | 2018-06-15 | 北京康拓科技有限公司 | A kind of startup method based on u-boot guiding μ C/OS operating systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109857468A (en) | 2019-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109857468B (en) | Method and system for supporting multiple DTBs in single Linux system mirror image | |
| CN109062617B (en) | Application method of platform supporting multiple types of equipment and mobile terminal | |
| CN106775723B (en) | Android platform-based system firmware customization method and Android device | |
| CN107632828B (en) | Multi-dts file supporting method, compiling device and embedded equipment | |
| CN111078229A (en) | Application processing method and device, storage medium and electronic equipment | |
| JPH02214994A (en) | Ic card | |
| CN114816417B (en) | Cross compiling method, device, computing equipment and storage medium | |
| CN114398145A (en) | Method for operating non-root Linux by Jailhouse based on X86 platform | |
| CN111985055A (en) | Model packaging method and device and electronic equipment | |
| CN113703926A (en) | Android container creation method and device | |
| US6175935B1 (en) | Software debugging method and recording medium to which debugging program has been recorded | |
| CN112631684A (en) | Executable program running method and device, electronic equipment and computer storage medium | |
| CN110704113B (en) | Starting method and system based on FPGA platform and development board device | |
| CN114756290A (en) | Operating system installation method, device and readable storage medium | |
| CN114756296A (en) | Read-write mounting starting method and device, storage medium and electronic equipment | |
| US10310870B2 (en) | Method for creating a revised application by adding code functionality to an existing application executable | |
| US20060074931A1 (en) | Configuring a shared library to accommodate relocatable data in a pervasive device | |
| CN116954752A (en) | Differentiated system configuration and loading method and device and computer equipment | |
| CN110597514A (en) | Program issuing system under VxWorks | |
| CN112148377B (en) | Method and device for preventing SSD from abnormal power failure in EFI Shell environment | |
| CN111273940B (en) | Method and device for uploading program file to code warehouse | |
| CN113157329A (en) | Method, system, server and storage medium for starting application | |
| CN113672238B (en) | Operation method, device and equipment based on real-time operating system modularized management | |
| CN117075960B (en) | Program reconstruction method, application cross-platform migration method, device and computing equipment | |
| CN116301908B (en) | Buildroot local compiling method and system based on Shenwei architecture |
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 |