CN115033267A

CN115033267A - Method for verifying equipment tree mirror image version and terminal equipment

Info

Publication number: CN115033267A
Application number: CN202110238984.7A
Authority: CN
Inventors: 穆超然; 朱永康
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-03-04
Filing date: 2021-03-04
Publication date: 2022-09-09

Abstract

The embodiment of the application relates to a method for verifying a device tree mirror image version, which comprises the following steps: and when the first version information in the main equipment tree image file is matched with the second version information in the overlay equipment tree image file, merging the main equipment tree image file and the overlay equipment tree image file, and starting an operating system of the terminal equipment. Before an operating system of the terminal equipment is started, version information in a main equipment tree image file and version information in a superposed equipment tree image file are acquired, and whether the version information of different image files is matched or not is compared. And when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file, starting the operating system of the terminal equipment. By comparing the version information in the image files, the problems of system failure and the like caused by adopting image files of different versions before the operating system is started are avoided.

Description

Method for verifying equipment tree mirror image version and terminal equipment

Technical Field

The present application relates to the field of operating systems, and in particular, to a method for verifying a Device Tree (DT) mirror version and a terminal device.

Background

DT is a data structure used to describe various hardware on the terminal device. For example, may include named nodes and attributes of the respective hardware. It is understood that the hardware can be understood as any physical device or apparatus on the terminal device, such as a hard disk, a mouse, a sound, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a baseband chip, and so on. The DT may be used by the operating system of the terminal device to support the use of various different hardware by the terminal device. In some examples, Linux kernels such as in android (android) support android devices using various hardware by using DTs.

Device Tree Source (DTS) files may be provided for hardware produced by different hardware providers, so that the DTS is compiled (compiler) into a device tree point (DTB) file used by a bootloader (bootloader) in an operating system. The DTB file is a binary file and is mainly used for bootloader to load corresponding hardware.

At present, because the DTB versions corresponding to different hardware devices may not be consistent with versions of a small kernel (LK) image or versions of other kernel (LK) images and system (system) images, the DTB versions may not be executed normally in a stage before the terminal device starts the operating system, and the terminal device may not start the operating system normally. This phase cannot be solved by repair (recovery) because it is a phase before the operating system is started. When the situation occurs, the terminal equipment of the user cannot be started for use, namely, the terminal equipment is commonly called as 'brick changing'.

Disclosure of Invention

The embodiment of the application provides a method for checking the version of a device tree image, and version information is compiled into a main device tree image file and a superposed device tree image file in a compiling stage. Before the terminal equipment prepares to start the operating system, the version information in the main equipment tree image file and the superimposed equipment tree image file is compared to determine whether the version information is matched, so that the terminal equipment can normally operate the operating system, and faults caused by different versions of the image files are avoided.

In a first aspect, a method for verifying a version of a device tree mirror image is provided, where the method is applied to a terminal device, and the method includes: acquiring a pre-stored main equipment tree image file and a pre-stored overlay equipment tree image file, wherein the main equipment tree image file comprises first version information, and the overlay equipment tree image file comprises second version information; when the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file; and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the superposed equipment tree image file. Before an operating system of the terminal equipment is started, version information in a main equipment tree image file and version information in a superposed equipment tree image file are acquired, and whether the version information of different image files is matched or not is compared. And when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file, starting the operating system of the terminal equipment. By comparing the version information in the image files, the problems of system failure and the like caused by adopting image files with different versions before starting the operating system are avoided.

In one possible embodiment, before obtaining the pre-stored primary device tree image file and the overlay device tree image file, the method further includes: generating mirror image version information; compiling the mirror image version information as first version information to a main equipment tree mirror image file; and compiling the mirror image version information as second version information to the superposed device tree mirror image file. According to the method and the device, the version information is compiled into different image files in the compiling stage, so that the terminal device can obtain the version information of the image files.

In one possible embodiment, the first version information includes: one or more of first terminal device platform information, first terminal device product information, first terminal device code branch information, and first creation time information; the second version information includes: one or more of second terminal device platform information, second terminal device product information, second terminal device code branch information, and second creation time information.

In one possible embodiment, when the first version information matches the second version information, merging the primary device tree image file and the overlay device tree image file includes: and when one or more groups of information in the first terminal equipment platform information and the second terminal equipment platform information, the first terminal equipment product information and the second terminal equipment product information, the first terminal equipment code branch information and the second terminal equipment code branch information, and the first terminal equipment code branch information and the second terminal equipment code branch information are the same, merging the main equipment tree image file and the superposed equipment tree image file.

In one possible embodiment, the method further comprises: when the first version information is not matched with the second version information, a backup superposition device tree mirror image file is obtained, wherein the backup superposition device tree mirror image file comprises third version information which is matched with the first version information; merging the main equipment tree mirror image file and the backup superposed equipment tree mirror image file; and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the backup superposed equipment tree image file. When the version information of the main equipment tree mirror image file is not matched with the version information of the superimposed equipment tree mirror image file, the superimposed equipment tree mirror image file matched with the version of the main equipment tree mirror image file can be adopted to replace the original superimposed equipment tree mirror image file so as to ensure that the terminal equipment can normally start the operating system, and the problems of system faults and the like caused by adopting mirror image files of different versions before the operating system is started are solved.

In one possible embodiment, before obtaining the backup overlay device tree image file, the method further includes: generating mirror image version information; and compiling the mirror image version information as third version information to the backup superposition device tree mirror image file. According to the method and the device, the version information is compiled into the backup superposition device tree image file in the compiling stage, so that the terminal device can acquire the version information of the image file.

In one possible embodiment, the third version information includes: one or more of third terminal device platform information, third terminal device product information, third terminal device code branch information, and third creation time information; the third version information is matched with the first version information, and comprises the following steps: and one or more groups of information in the third terminal equipment platform information and the first terminal equipment platform information, the third terminal equipment product information and the first terminal equipment product information, the third terminal equipment code branch information and the first terminal equipment code branch information, and the third terminal equipment code branch information and the first terminal equipment code branch information are the same.

In a second aspect, a terminal device for checking a version of a device tree image is provided, where the terminal device includes: the processor is used for being coupled with the memory and reading and executing the instructions stored in the memory; when the processor runs, executing the instruction, so that the processor is used for acquiring a pre-stored main equipment tree image file and a pre-stored overlay equipment tree image file, wherein the main equipment tree image file comprises first version information, and the overlay equipment tree image file comprises second version information; when the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file; and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the superposed equipment tree image file. Before an operating system of the terminal equipment is started, version information in a main equipment tree image file and version information in a superposed equipment tree image file are acquired, and whether the version information of different image files is matched or not is compared. And when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file, starting the operating system of the terminal equipment. By comparing the version information in the image files, the problems of system failure and the like caused by adopting image files of different versions before the operating system is started are avoided.

In one possible embodiment, the processor is further configured to: generating mirror image version information; compiling the mirror image version information as first version information to a main equipment tree mirror image file; and compiling the mirror image version information as second version information to the superposed device tree mirror image file. According to the method and the device, the version information is compiled into different image files in the compiling stage, so that the terminal device can obtain the version information of the image files.

In one possible embodiment, the processor is further configured to: and when one or more groups of information in the first terminal equipment platform information and the second terminal equipment platform information, the first terminal equipment product information and the second terminal equipment product information, the first terminal equipment code branch information and the second terminal equipment code branch information, and the first terminal equipment code branch information and the second terminal equipment code branch information are the same, merging the main equipment tree image file and the superposed equipment tree image file.

In one possible embodiment, the processor is further configured to: when the first version information is not matched with the second version information, a backup superposition device tree mirror image file is obtained, wherein the backup superposition device tree mirror image file comprises third version information which is matched with the first version information; merging the main equipment tree mirror image file and the backup superposed equipment tree mirror image file; and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the backup superposed equipment tree image file. When the version information of the main equipment tree mirror image file is not matched with the version information of the superimposed equipment tree mirror image file, the superimposed equipment tree mirror image file matched with the version of the main equipment tree mirror image file can be adopted to replace the original superimposed equipment tree mirror image file so as to ensure that the terminal equipment can normally start the operating system, and the problems of system faults and the like caused by adopting mirror image files of different versions before the operating system is started are solved.

In one possible embodiment, the processor is further configured to: generating mirror image version information; and compiling the mirror image version information as third version information to the backup superposition device tree mirror image file. According to the method and the device, the version information is compiled into the backup superposition device tree image file in the compiling stage, so that the terminal device can acquire the version information of the image file.

In one possible embodiment, the third version information includes: one or more of third terminal device platform information, third terminal device product information, third terminal device code branch information, and third creation time information; the processor is further configured to: and one or more groups of information in the third terminal equipment platform information and the first terminal equipment platform information, the third terminal equipment product information and the first terminal equipment product information, the third terminal equipment code branch information and the first terminal equipment code branch information, and the third terminal equipment code branch information and the first terminal equipment code branch information are the same.

In a third aspect, there is provided a computer readable storage medium having stored therein instructions that, when executed on a terminal, cause the terminal to perform the method of any one of the first aspect.

In a fourth aspect, there is provided a computer device containing instructions which, when run on a terminal, cause the terminal to perform the method of any one of the first aspects.

The application discloses a method for verifying version of equipment tree mirror image and terminal equipment. And when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file, starting an operating system of the terminal equipment. When the version information of the main device tree mirror image file and the version information of the overlay device tree mirror image file are not matched, a backup overlay device tree mirror image file matched with the version of the main device tree mirror image file can be adopted to replace the original overlay device tree mirror image file. The terminal equipment can normally start the operating system, and the problems of system failure and the like caused by adopting mirror image files of different versions before the operating system is started are avoided.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

FIG. 2 is a diagram of an initialized operating system runtime environment;

fig. 3 is a flowchart of a method for checking a version of a device tree mirror image according to an embodiment of the present application;

fig. 4 is a flowchart of another method for checking a version of a device tree mirror image according to an embodiment of the present application;

fig. 5 is a flowchart of another method for checking a version of a device tree mirror image according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a mirror head alignment provided in an embodiment of the present application;

fig. 7 is a flowchart of a method for checking a version of a device tree mirror image according to an embodiment of the present application;

FIG. 8 is a flowchart of a terminal device initializing an operating system runtime environment;

fig. 9 is a flowchart of an operating environment for verifying and initializing a version of a device tree image according to an embodiment of the present disclosure;

fig. 10 is a schematic diagram illustrating compilation of an image file according to an embodiment of the present application;

fig. 11 is a schematic operational diagram of a terminal device according to an embodiment of the present application;

fig. 12 is a schematic diagram of a terminal device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The method and the device are mainly applied to scenes before the terminal equipment starts the operating system. Such as shown in fig. 1, when a user is ready to turn on a terminal device, such as a cell phone. After the user presses the power-on key, the terminal device needs to initialize various hardware devices, such as a CPU, a GPU, and the like, on the terminal device through a Boot Loader (BL). Meanwhile, a memory space mapping chart can be established so as to bring the software and hardware environment of the terminal equipment operating system to a proper state to prepare a correct environment for finally calling the operating system kernel. In some examples, the BL may also be referred to as a boot subsystem.

However, since a power failure may occur during the process of updating the system by the user or the update may be interrupted due to some accident. At this time, part of the files in the system are updated, and part of the files are not updated. This will result in file version inconsistencies in the system. Since the operation of the operating system requires a correct operation environment, when the BL is initialized, the initialization of the operation environment of the operating system fails due to the inconsistency of the versions of the partial files. This will directly result in the terminal device not being able to start the operating system. Just as in fig. 1, first, the terminal device is initializing the operating environment of the operating system before starting the operating system, and when the initialization of the operating environment fails, the terminal device enters the state shown by second, that is, cannot enter the operating system. At this time, the terminal device cannot normally be started up, and since the terminal device does not enter the operating system at this time, the terminal device cannot be recovered through corresponding operations in the system. For example, the factory-restored settings in the terminal device settings cannot be used for modification.

FIG. 2 is a diagram of an initialized operating system runtime environment.

As shown in fig. 2, a schematic diagram of the terminal device initializing the operating system environment through the BL before starting the operating system under normal conditions is shown. When the user starts the terminal device by a power-on button of the terminal device, S201 is executed, and after the terminal device is powered on, the terminal device jumps to a boot code (code) in a boot-only memory (ROM) and executes the boot code. By executing the boot code S201, a pre-loader (per-loader) in the ROM is loaded into an Internal Static Random Access Memory (ISRAM), i.e., S202. S203, after the per-loader is loaded in the ISRAM, the LK image in the ROM may be loaded to a Dynamic Random Access Memory (DRAM), i.e., S203 and S204. After the LK image is loaded to the DRAM, the per-loader may also load a kernel and a virtual memory (ramdisk) stored in the ROM into the DRAM, respectively, for example, S205. After the LK image loaded into the DRAM is compiled, S206 may be executed to compile the kernel loaded into the DRAM. When kernel compilation in DRAM is complete, S207 compilation of ramdisk may be performed. Thereby completing the initialization operation of the operating system operating environment of the terminal device.

When the LK images and kernel are compiled in the DRAM, a Device Tree Overlay (DTO) is usually used to dynamically overlay the special DT of the terminal device. Wherein the DTO may be used to overlay other device information on the basis of the primary DTB in the DT. So that the BL can maintain a system on chip (SoC) DT. In some examples, the DTO may also be referred to as a superimposed device tree. Typically, SoC DT is a master device tree, and its compiled DTB file can be denoted with DTB in common suffix, which can be called DTB mirror. And DTO is an overlay device tree, and the compiled DTB file thereof is usually indicated by dtbo as a suffix, which may be called a dtbo mirror image, to distinguish the compiled DTB file of the main device tree. It is understood that in fig. 2 when the LK image is compiled, the dtb image may also be referred to as the LK image. While the dtb mirror may be referred to as the kernel mirror when compiling the kernel mirror. Obviously, the process of compiling the LK image, that is, compiling the DTS of the LK and the DTS of the device tree overlay into the LK image and the dtbo image, and performing a merging process. And for the process of compiling the kernel image, compiling the DTS of the kernel and the DTS of the device tree superposition layer into the kernel image and the dtbo image, and merging the kernel image and the DTS of the device tree superposition layer. Due to the adoption of the DTO, nodes corresponding to corresponding hardware equipment can be superposed in the DT, and the attributes in any node in the equipment tree are changed.

Basic configuration information for supporting the operation of the operating system is stored in both the DT and the DTO, and in order to ensure that the operating system code can be reused, a designer of the operating system abstracts the logic of the operating system code and decouples the code logic and the configuration. And the configuration is independently stored in the partition corresponding to the dtb mirror image and the dtbo mirror image. Obviously, the above-described approach may result in a lot of visible gains in the optimization of the code structure. But at the same time there are some problems. For example, if some abnormality occurs during the upgrade of the operating system of the mobile phone, which results in the upgrade failure, the dtb image and the dtbo image may be mismatched. But at present, the terminal device does not find the problem of mismatch between the dtb image and the dtbo image before starting the operating system. Therefore, the terminal device cannot be turned on by the attempt. The reason is that the dtb mirror image and the dtbo mirror image are not matched with each other, so that the environment suitable for running of the operating system cannot be initialized, and the operating system cannot normally run due to an error in accessing configuration information during execution. For the user, the terminal device cannot be normally powered on and cannot normally enter the operating system. Such problems occur when images such as LK images, kernel images, and system (system) images are dtb images. Of course, since the terminal device cannot enter the boot operating system, the user cannot solve the above problem by recovery or recovery.

Some of the more common scenarios may be an android (integrated circuit) chip issued by the Media Tek (MTK). Of course, similar problems exist for IC chips based on other operating systems released by other manufacturers.

Therefore, the present application provides a method for checking version of device tree mirror, which obtains version information in a main device tree mirror file and a superimposed device tree mirror file before starting an operating system of a terminal device, and compares whether version information of different mirror files is matched. And starting the operating system of the terminal equipment when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file. And when the version information of the main equipment tree image file is not matched with the version information of the superposed equipment tree image file, replacing the original superposed equipment tree image file with a backup superposed equipment tree image file matched with the version of the main equipment tree image file. The terminal equipment can normally start the operating system, and the problems of system failure and the like caused by adopting mirror image files of different versions before the operating system is started are avoided.

The following describes technical solutions in the embodiments of the present application in detail with reference to the drawings in the embodiments of the present application.

Fig. 3 is a flowchart of a method for checking a version of a device tree mirror image according to an embodiment of the present application.

As shown in fig. 3, the present application provides a method for checking a version of a device tree image, which can be applied to a terminal device. The terminal device related to the present application may be a mobile phone, a Personal Computer (PC), a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR) device, a Virtual Reality (VR) device, an Artificial Intelligence (AI) device, a wearable device, a vehicle-mounted device, a smart television, a smart home device, and/or a smart city device, and the specific type of the terminal device is not particularly limited in the present application.

The method may comprise the steps of:

s301, acquiring a pre-stored main device tree image file and a pre-stored overlay device tree image file.

Before starting an operating system, the terminal device first acquires a pre-stored main device tree image file and a superposed device tree image file.

In one example, the primary device tree image file and the overlay device tree image file may be stored in a ROM of the terminal device, such as the ROM shown in fig. 2. The master device tree image file may include first version information, and the overlay device tree image file may include second version information. It is to be understood that the first version information is used to describe a version of the master device tree image file and the second version information is used to describe a version of the overlay device tree image file.

For the master tree image file, in some examples, it may be the aforementioned LK image, kernel image, system image, etc., i.e., the file suffix of.dtb after being compiled into a binary file. And the overlay device tree image file may be, in some examples, a file that is compiled into a binary file followed by a.dtbo suffix.

S302, when the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file.

After acquiring the first version information of the master device tree image file and the second version information of the overlay device tree image file in S301, the terminal device may compare the first version information with the second version information. If the first version information matches the second version information, the master device tree image file and the overlay device tree image file may be merged (merge).

In one example, the first version information and the second version information may be collectively referred to as version information or fingerprint information (fingerprint). It will be appreciated that the fingerprint is used to uniquely identify the information corresponding to the current DT configuration version of the image file. In some examples, the finger print may be stored as a field in a different image file. The fingerprint field may include one or more of platform information (platform), product information (product), branch information (branch) and build time information (build) of the terminal device. In some examples, the fingerprint field may further include other information that may be used to indicate the version of the image file, and the application is not limited herein. The finger print field may be such as shown in table 1,

platform

product

branch

buildtime

TABLE 1

It is to be understood that table 1 shows only one possible constituent structure of the finger print. Of course, there may be more or less information, and the arrangement order of the information in the finger print field may also be adjusted according to the actual situation, which is not limited in this application.

In one example, the terminal device acquires in S301 that the primary device tree image file and the overlay device tree image file are the dtb image and the dtbo image that have been compiled. Obviously, the obtained main device tree image file and the overlay device tree image file are compiled files. And the fingerprint field may uniquely identify the version information of the current device tree image file in compiled state. Therefore, the terminal device needs to determine a fingerprint field of the primary device tree image file, which may be referred to as a first fingerprint field or first version information; and the terminal device needs to determine a fingerprint field of the overlay device tree image file, which may be referred to as a second fingerprint field or second version information. And comparing whether the fingerprint fields of different image files match. I.e. whether the first version information and the second version information match.

It is understood that the information contained in the first fingerprint field may be referred to as first terminal device platform information, first terminal device product information, first terminal device code branch information, and first creation time information; the information contained in the second finger print field may be referred to as second terminal device platform information, second terminal device product information, second terminal device code branch information, and second creation time information.

In one example, it may be determined whether one or more of the platform, product, branch, and build in different image files are the same as a basis for matching. For example, the first version information and the second version information may be considered to match by determining that the first finger print field is the same as any one of the platform, product, branch, or build in the second finger print field. Of course, the product and the build may also be selected to be the same, that is, the first version information and the second version information are considered to match. Or, when the platform, product, branch and build in the first fingerprint field and the second fingerprint field are the same, the first version information and the second version information are considered to match. It is understood that the present application merely illustrates a few examples, and that any number of information in the finger print field may be selected for comparison to determine whether the first version information matches the second version information.

And when the terminal equipment determines that the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file.

And S303, starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the superposed equipment tree image file.

The terminal device starts the operating system on the terminal device by using the master device tree image file and the overlay device tree image file combined in S302. It can be understood that, when it is determined that the fingerprint fields of the primary device tree image file and the overlay device tree image file match, it may be determined that the system crash is not caused after the primary device tree image file and the overlay device tree image file are merged, and it may be ensured that the environment where the terminal device is initialized is a normal environment. Therefore, the terminal device can start the operating system in a normal environment after the main device tree image file and the overlay device tree image file are combined.

Fig. 4 is a flowchart of another method for checking versions of device tree images according to an embodiment of the present disclosure.

As shown in fig. 4, the present application further provides another flowchart of a method for checking a version of a device tree image. After S301, when the first version information does not match the second version information, the method may further include the steps of:

s401, when the first version information is not matched with the second version information, obtaining a backup superposition device tree mirror image file.

When the terminal device determines that the first version information is not matched with the second version information, the backup overlay device tree image file can be obtained.

In one example, the backup overlay device tree image file may be a backup image file pre-stored in the terminal device and used for merging with the main device tree image file when the overlay device tree image file is not available. In most cases, the method can be used for terminal equipment to perform recovery or recovery. For example, the backup overlay device tree image file may be a dtbo image file for recovery, i.e., recovery _ dtbo. For another example, the backup overlay device tree image file may also be a dtbo image file for an erecovery, i.e., erecovery _ dtbo. It can be understood that, when the main device tree image file and the overlay device tree image file of the terminal device cannot start the operating system due to different versions, the backup overlay device tree image file and the main device tree image file may be merged, so that a user may enter the operating system to perform recovery or optimization.

The backup overlay device tree image file may include third version information. The third version information matches the first version information. In one example, the fingeprint field of the backup overlay device tree image file may be referred to as a third fingeprint field or third version information. It is to be understood that the information contained in the third fingerprint field may be referred to as third terminal device platform information, third terminal device product information, third terminal device code branch information, and third creation time information. For the third version information matching the first version information, it may be: and one or more groups of information in the third terminal equipment platform information and the first terminal equipment platform information, the third terminal equipment product information and the first terminal equipment product information, the third terminal equipment code branch information and the first terminal equipment code branch information, and the third terminal equipment code branch information and the first terminal equipment code branch information are the same. Specifically, reference may be made to corresponding description in S302, where the first version information is matched with the second version information, and details are not described herein again.

S402, merging the main equipment tree mirror image file and the backup superposed equipment tree mirror image file.

And the terminal device merges the backup overlay device tree image file acquired in the step S401 with the main device tree image file.

And S403, starting the operating system of the terminal equipment by using the combined main equipment tree image file and the backup superposed equipment tree image file.

The terminal device starts the operating system on the terminal device by using the main device tree image file and the backup overlay device tree image file merged in S402.

Fig. 5 is a flowchart of another method for checking a version of a device tree image according to an embodiment of the present application.

As shown in fig. 5, the present application further provides a flowchart of another method for checking a version of a device tree image. Before S301, the primary device tree image file and the overlay device tree image file often need to be compiled (built). Therefore, when the primary device tree image file and the overlay device tree image file are compiled, the fingerprint field may be saved in the primary device tree image file and the overlay device tree image file, and before S301, the method may further include the following steps:

s501, generating mirror image version information.

The terminal equipment can generate mirror image version information in the compiling process. It is to be understood that the image version information may be a fingerprint field.

S502, compiling the mirror image version information as first version information to a main equipment tree mirror image file; and compiling the mirror image version information as second version information to the superposition device tree mirror image file.

The terminal device compiles the finger print field generated in S501 into the primary device tree image file and the overlay device tree image file. It can be understood that the fingerprint field compiled into the primary device tree image file is the first fingerprint field; and compiling the second fingerprint field into the fingerprint field in the overlay device tree image file. The process of compiling the fingerprint field into the image file can also be understood as a process of writing the fingerprint field into the image file.

In one example, the first finger print field may be saved to a header in the primary device tree image file. For example, a fingerprint field is newly added in the image header of the primary device tree image file to store the version information of the image file. As shown in fig. 6, for example, the original mirror header contains: magic is used to represent the magic of the mirror identification. It will be appreciated that magic numbers are typically numerical constants or strings that are not interpreted, and may also be referred to as magic values. Most files have a fixed content of the first few bytes, e.g. intentionally padded, or otherwise. Obviously, the content of the first few bytes of the file is magic number, and the terminal device can determine the type of each file according to the content of the few bytes. Total _ size is used to indicate the total size of the image file, header _ size is used to indicate the image header size, and DT _ entry _ size is used to indicate the size of each DT entry in the device tree. It can be understood that, for the primary device number image file or the overlay device tree image file, the structures are identical, and each DT image file contains one or more DT entries for recording the DT image file contents. DT _ entry _ count is used to indicate the number of DT entries in the image file. DT _ entries _ offset is used to indicate the offset of the DT entry in the image file, page _ size is used to indicate the size of the image single page, and version is used to describe the structural version of the image file.

The mirror image is described. And for a new mirror image header, namely the mirror image header of the mirror image file in the application, a fingerprint field is added. Obviously, the new image header added with the finger print field will contain the version information of the image file. So as to identify whether the different image files are matched or not subsequently. In another example, the second finger print field may also be saved to the header of the overlay device tree image file as shown in FIG. 6.

In other examples, the fingerprint field may also be saved to any other location in the image file, and the present application is not limited herein.

It will be appreciated that version is used to represent a version of the image file's overall structure. For example, the mirror structure of different versions is completely different. The version described in the fingerprint field related in the present application can be distinguished from different versions obtained by modifying some parameters under the same version structure version. It is obvious that the fingerprint field is more fine-grained than version for partitioning the image file version.

It is understood that the mirror header shown in fig. 6 can be used for dtb mirror as well as dtbo mirror.

After S502 is performed, S301 in fig. 3 may be performed.

Fig. 7 is a flowchart of a method for checking a version of a device tree image according to another embodiment of the present disclosure.

As shown in fig. 7, the present application further provides a flowchart of another method for checking a version of a device tree mirror. It is understood that the terminal device may also obtain the backup overlay device tree image file when the versions of the primary device tree image file and the overlay device tree image file do not match. Therefore, the terminal device also needs to compile the fingerprint field into the backup overlay device tree image file in the compiling stage. Therefore, after S501, the method may also include the steps of:

and S701, compiling the mirror image version information serving as third version information to the backup overlay device tree mirror image file.

The terminal device compiles the fingerprint field generated in S501 into the backup overlay device tree image file. It is understood that the fingerprint field compiled into the backup overlay device tree image file is the third fingerprint field described above. The position of the third fingerprint field in the backup overlay device tree image file may refer to corresponding description of the first fingerprint field or the second fingerprint field in S502, which is not described herein again.

After S701 is performed, S301 in fig. 3 may be performed.

According to the method for verifying the version of the equipment tree mirror image, before the operating system of the terminal equipment is started, the version information in the main equipment tree mirror image file and the version information in the superposed equipment tree mirror image file are obtained, and whether the version information of different mirror image files is matched or not is compared. And when the version information of the main equipment tree image file is matched with the version information of the superposed equipment tree image file, starting the operating system of the terminal equipment. And when the version information of the main equipment tree mirror image file is not matched with the version information of the superposed equipment tree mirror image file, acquiring a backup superposed equipment tree mirror image file to replace the original superposed equipment tree mirror image file. The terminal equipment can still normally start the operating system, and the problems of system failure, breakdown and the like caused by adopting different versions of mirror image files before the operating system is started are avoided.

Fig. 8 is a flowchart of a terminal device initializing an operating system operating environment.

As shown in fig. 8, a flowchart of a terminal device initializing an operating system runtime environment is provided. In the process, because the version information does not exist in the image file, when the image versions do not match, the system is crashed. It is understood that fig. 8 is described with the LK image as the master tree image file. In the embodiment illustrated in FIG. 8, the master tree image file may be lk _ main _ dtb. Of course, in other examples, the master device tree image file may also be a kernel image, a system image, and the like, and the present application is not limited thereto. The method may comprise the steps of:

s801, load lk _ main _ dtb, dtbo.

Before the operating system is operated by the terminal equipment, the operating system operation environment needs to be initialized, so that the LK image and the superposed equipment tree image files namely LK _ main _ dtb and dtbo need to be loaded firstly.

S802, merge lk _ main _ dtb with dtbo.

The terminal device merges the lk _ main _ dtb and dtbo loaded in S801. For subsequent booting of the operating system.

And S803, judging whether the combination is successful.

If the merging is successful, S804 is executed, and if the merging is failed, S805 is executed.

S804, a Liquid Crystal Display (LCD) is driven to obtain configuration information, and the terminal equipment identifies that the configuration is not matched with the logic.

The terminal device normally acquires configuration information of hardware by the LCD driver, and executes logic in lk _ main _ dtb and dtbo. But since the versions of lk _ main _ dtb and dtbo do not match, the corresponding parameters in the running logic do not match with the configuration information acquired by the LCD driver. This execution results in S806.

And S805, merging the backup with the lk _ main _ dtb by using recovery _ dtbo or recovery _ dtbo as a backup.

If the terminal device determines in S803 that lk _ main _ dtb and dtbo are not merged successfully, it selects recovery _ dtbo or recovery _ dtbo as backup dtbo to merge with lk _ main _ dtb, and executes S804.

S806, the operating system crashes.

Since the corresponding parameters in the operation logic in S804 are not matched with the configuration information acquired by the LCD driver, the terminal device cannot operate the operating system directly. To the user, the terminal device will appear to be unable to power on, i.e. "brick change".

Obviously, in the current scheme, because the image file does not contain version information, when the versions of the image files are not matched, the user cannot enter the system for repair, and the user experience is seriously affected. And even cause serious economic loss.

Therefore, the version information is added to the image file, so that the backup image file can be found and loaded in time when the image file versions are not matched, the normal operation of the operating system of the terminal equipment is guaranteed, or a user can enter the operating system to further repair the terminal equipment.

Fig. 9 is a flowchart of an operating environment for verifying and initializing a version of a device tree image according to an embodiment of the present application.

FIG. 9 is a flowchart illustrating a device tree image version check initialization operating system operating environment after adding version information to an image file. Similar to fig. 8, the LK image is still used as the main device tree image file in this embodiment for description, and the main device tree image file may be LK _ main _ dtb. Of course, in other examples, the master device tree image file may also be a kernel image, a system image, and the like, and the present application is not limited thereto.

The method may comprise the steps of:

s901, loading lk _ main _ dtb and dtbo.

And the terminal equipment loads the LK mirror image and the superposed equipment tree mirror image files namely LK _ main _ dtb and dtbo. And determines the finger print fields in lk _ main _ dtb, dtbo, i.e., the first finger print field and the second finger print field.

S902, judging whether the finger print field is matched

The terminal device determines whether one or more pieces of information in the first finger print field and the second finger print field match. If the matching is successful, executing S903; if not, go to step S904.

S903, merge lk _ main _ dtb and dtbo.

The terminal device merges the lk _ main _ dtb and dtbo loaded in S901. For subsequent booting of the operating system.

And S904, merging the duplicate _ dtbo or duplicate _ dtbo serving as a backup with the lk _ main _ dtb.

If the terminal device determines in S903 that the fingerprint fields do not match, it selects recovery _ dtbo or recovery _ dtbo as the backup dtbo to merge with lk _ main _ dtb, and then executes S903. It will be appreciated that the recovery _ dtbo or fingerprint field in recovery _ dtbo in S904 matches the fingerprint field in lk _ main _ dtb.

S905, the operating system is started normally, and is guided to enter repair or recovery.

If dtbo merged with lk _ main _ dtb in S903 is the backup device tree image file, the operating system of the terminal device may start normally. If the dtbo merged with the lk _ main _ dtb in the S903 is recovery _ dtbo, the operating system of the terminal device is booted and then is guided to recover for repair. If the dtbo merged with the lk _ main _ dtb in the S903 is an overlap _ dtbo, the operating system of the terminal device is booted to enter overlap for recovery.

The difference is that the recovery intelligence adopts a local configuration file to repair, and the ereco can download the latest configuration file through a network, so that the latest configuration file is adopted to repair the terminal equipment. The specific repair process may refer to the existing method, which is not described herein.

It can be understood that, for the method shown in fig. 9, specific implementation processes thereof may refer to fig. 3 to fig. 7, which are not described herein again.

Fig. 10 is a schematic view of compiling an image file according to an embodiment of the present application.

As shown in fig. 10, in the compiling stage, the terminal device generates a finger print field and writes the content of the field into the image header of the overlay device tree image file and the primary device tree image file. In some examples, the files may all be written into the image header of the image file, or stored as a fingerprint variable in any optional location in the image file, which is not limited herein.

Of course, in other examples, in order to ensure that when the primary device tree image file and the overlay device tree image file cannot be merged, a backup overlay device tree image file may replace the overlay device tree image file to be merged with the primary device tree image file. Therefore, in the compiling stage, the terminal device can also write the fingerprint field into the image header of the backup overlay device tree image file, or store the fingerprint field as a fingerprint variable in any optional position in the image file.

It can be understood that, the specific implementation process thereof may refer to the corresponding descriptions in fig. 5 to fig. 7, and is not described herein again.

The compiling stages described in fig. 5 to fig. 7 and fig. 10 may be performed before the terminal device leaves the factory, or before the operating system is released.

Fig. 11 is a schematic view of operation of a terminal device according to an embodiment of the present application.

As shown in fig. 11, in the running (running) phase, the terminal device obtains the fingerprint field in the primary device tree image file and the overlay device tree image file for comparison. Therefore, when the versions are different, the backup superposed device tree image file can be adopted to replace the superposed device tree image file in time and is merged with the main device tree image file. So that the user can enter the operating system to repair.

It can be understood that, the specific implementation process thereof may refer to the corresponding descriptions in fig. 3 to fig. 9, which are not described herein again.

The present application provides a terminal device 1200, where the terminal device 1200 may include: a processor 1201, a memory 1202, and a bus 1203. The processor 1201 and the memory 1202 in the terminal apparatus 1200 may establish communication connection through the bus 1203. It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the terminal device 1200. Terminal device 1200 may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 1201 may be an advanced reduced instruction set (ARM) processor, an X86, a microprocessor without an internal interlocking pipeline (MIPS), or other architectures. The processor 1201 may include one or more processing units, such as: an Application Processor (AP), a modem processor, a GPU, an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor and/or a neural-Network Processing Unit (NPU), etc. Wherein, the different processing units may be independent devices or may be integrated in one or more processors.

A memory may also be provided within the processor 1202 for storing instructions and data. In some embodiments, memory 1202 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 1201. If the processor 1210 needs to reuse the instruction or data, it may be called directly from memory. Avoiding repeated accesses reduces the latency of the processor 1201 and thus improves the efficiency of the system. In one example, the storage 1202 may include a memory in which an operating system, image files, and the like may be stored. The memory 1202 may also include a secondary memory or be referred to as an external memory, such as may be a non-removable memory or a removable memory card, or the like.

Wherein the internal memory may be used to store computer executable program code, the executable program code comprising instructions. The internal memory may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one of a magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 1201 executes various functional applications of the apparatus 1200 and data processing by executing instructions stored in the memory.

The apparatus 1200 provided in this application may implement any function of the terminal device in the examples described in fig. 3 to fig. 11, and the specific implementation manner may refer to the corresponding descriptions in fig. 3 to fig. 11, which is not described herein again.

In some embodiments, the present application further provides a manner of determining infringement, for example, by parsing the DT image file using a script, it is determined whether the parsed content of the image file includes version information, such as a fingerprint field.

Before the operating system of the terminal equipment is started, version information in the main equipment tree image file and the superposed equipment tree image file is obtained, and whether the version information of different image files is matched or not is compared. One type of operating system operational failure caused by configuration and code logic mismatches is addressed. And when the version information of the main equipment tree image file is not matched with the version information of the superposed equipment tree image file, the backup superposed equipment tree image file matched with the version of the main equipment tree image file can be adopted to replace the original superposed equipment tree image file. And loading backup configuration data in time to ensure normal operation of the system or repair system faults. The problem of non-startup caused by inconsistent DT configuration versions is solved.

It will be further appreciated by those of ordinary skill in the art that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described in a functional generic sense in the foregoing description for the purpose of clearly illustrating the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by a program, and the program may be stored in a computer-readable storage medium, where the storage medium is a non-transitory medium, such as a random access memory, a read only memory, a flash memory, a hard disk, a solid state disk, a magnetic tape (magnetic tape), a floppy disk (floppy disk), an optical disk (optical disk), and any combination thereof.

The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for checking a device tree mirror version is characterized in that the method is applied to a terminal device, and comprises the following steps:

acquiring a pre-stored main equipment tree image file and a pre-stored overlay equipment tree image file, wherein the main equipment tree image file comprises first version information, and the overlay equipment tree image file comprises second version information;

when the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file;

and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the superposed equipment tree image file.

2. The method of claim 1, wherein prior to obtaining the pre-stored primary device tree image file and overlay device tree image file, the method further comprises:

generating mirror image version information;

compiling the mirror image version information as the first version information to the main equipment tree mirror image file; and the number of the first and second groups,

and compiling the mirror image version information serving as the second version information to the superposed equipment tree mirror image file.

3. The method of claim 1 or 2, wherein the first version information comprises: one or more of first terminal device platform information, first terminal device product information, first terminal device code branch information, and first creation time information;

the second version information includes: one or more of second terminal device platform information, second terminal device product information, second terminal device code branch information, and second creation time information.

4. The method of claim 3, wherein merging the primary device tree image file with the overlay device tree image file when the first version information matches the second version information comprises:

and when one or more groups of information in the first terminal equipment platform information and the second terminal equipment platform information, the first terminal equipment product information and the second terminal equipment product information, the first terminal equipment code branch information and the second terminal equipment code branch information, and the first terminal equipment code branch information and the second terminal equipment code branch information are the same, merging the main equipment tree image file and the superposition equipment tree image file.

5. The method of any one of claims 1-4, further comprising:

when the first version information is not matched with the second version information, a backup superposition device tree mirror image file is obtained, wherein the backup superposition device tree mirror image file comprises third version information, and the third version information is matched with the first version information;

merging the main equipment tree mirror image file and the backup superposed equipment tree mirror image file;

and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the backup superposed equipment tree image file.

6. The method of claim 5, wherein prior to obtaining the backup overlay device tree image file, the method further comprises:

generating mirror image version information;

and compiling the image version information as the third version information to the backup overlay device tree image file.

7. The method of claim 5 or 6, wherein the third version information comprises: one or more of third terminal device platform information, third terminal device product information, third terminal device code branch information, and third creation time information;

the third version information is matched with the first version information, and includes:

one or more groups of information in the third terminal equipment platform information and the first terminal equipment platform information, the third terminal equipment product information and the first terminal equipment product information, the third terminal equipment code branch information and the first terminal equipment code branch information, and the third terminal equipment code branch information and the first terminal equipment code branch information are the same.

8. A terminal device for verifying a device tree mirror version, the terminal device comprising:

the processor is used for being coupled with the memory and reading and executing the instructions stored in the memory;

when the processor runs, the instruction is executed, so that the processor is used for acquiring a pre-stored main equipment tree image file and a pre-stored overlay equipment tree image file, wherein the main equipment tree image file comprises first version information, and the overlay equipment tree image file comprises second version information; when the first version information is matched with the second version information, merging the main equipment tree image file and the superposed equipment tree image file; and starting the operating system of the terminal equipment by adopting the combined main equipment tree image file and the superposed equipment tree image file.

9. The terminal device of claim 8, wherein the processor is further configured to:

generating mirror image version information;

and compiling the image version information as the second version information to the superposed device tree image file.

10. The method of claim 8 or 9, wherein the first version information comprises: one or more of first terminal device platform information, first terminal device product information, first terminal device code branch information, and first creation time information;

11. The terminal device of claim 10, wherein the processor is further configured to:

and when one or more groups of information in the first terminal equipment platform information and the second terminal equipment platform information, the first terminal equipment product information and the second terminal equipment product information, the first terminal equipment code branch information and the second terminal equipment code branch information, and the first terminal equipment code branch information and the second terminal equipment code branch information are the same, merging the main equipment tree mirror image file and the superposed equipment tree mirror image file.

12. The terminal device of any of claims 8-11, wherein the processor is further configured to:

merging the main equipment tree mirror image file and the backup overlay equipment tree mirror image file;

13. The terminal device of claim 12, wherein the processor is further configured to:

generating mirror image version information;

14. The terminal device according to claim 12 or 13, wherein the third version information includes: one or more of third terminal device platform information, third terminal device product information, third terminal device code branch information, and third creation time information;

the processor is further configured to:

15. A computer-readable storage medium having instructions stored thereon, which, when run on a terminal, cause the terminal to perform the method of any one of claims 1-7.

16. A computer device comprising instructions which, when run on a terminal, cause the terminal to perform the method of any one of claims 1-7.