WO2020113469A1

WO2020113469A1 - Power on self test method, power on self test device and mobile terminal

Info

Publication number: WO2020113469A1
Application number: PCT/CN2018/119377
Authority: WO
Inventors: 王立中
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2018-12-05
Filing date: 2018-12-05
Publication date: 2020-06-11
Also published as: CN112912855A

Abstract

The present invention relates to a power on self test method, a power on self test device, mobile terminal (5) and a computer readable storage medium, wherein the power on self test method comprises: detecting whether a preset identifier is present in a storage device (S101, S202); if so, acquiring a power on stage corresponding to the preset identifier (S102, S203); and determining that the power on stage corresponding to the preset identifier is not completed in the power on process. The method solves the problem in the prior art in which it is not possible to determine at which stage non-completion occurs in a power on process.

Description

Boot detection method, boot detection device and mobile terminal

Technical field

The present application belongs to the technical field of mobile terminals, and particularly relates to a boot detection method, a boot detection device, a mobile terminal, and a computer-readable storage medium.

Background technique

With the development and progress of communication technology, mobile terminals such as mobile phones and tablet computers have become important tools in people's lives. The mobile terminal often has a situation where the startup is not completed. In the prior art, when the startup of the mobile terminal is not completed, it cannot be judged at which stage in the startup process the startup is not completed.

Summary of the invention

The present application provides a boot detection method, a boot detection device, a mobile terminal, and a computer-readable storage medium to solve the problem that the prior art cannot determine at which stage in the boot process the boot is not completed.

The first aspect of the present application provides a boot detection method. The boot detection method includes:

Detect whether there is a preset mark in the storage device;

If the preset identifier exists in the storage device, obtain a start-up phase corresponding to the preset identifier;

It is determined that the startup phase corresponding to the preset identification is not completed during the startup process.

A second aspect of the present application provides a boot detection device, the boot detection device includes:

The identification detection module is used to detect whether a preset identification exists in the storage device;

A stage obtaining module, configured to obtain a start-up stage corresponding to the preset identifier if the preset identifier exists in the storage device;

The stage determination module is used to determine that the start-up stage corresponding to the preset identifier is not completed during the start-up process.

A third aspect of the present application provides a mobile terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, The steps of the method of the first aspect described above.

A fourth aspect of the present application provides a computer-readable storage medium storing a computer program, which when executed by a processor implements the steps of the method of the first aspect described above.

A fifth aspect of the present application provides a computer program product, the computer program product comprising a computer program, which when executed by one or more processors implements the steps of the method of the first aspect described above.

BRIEF DESCRIPTION

In order to more clearly explain the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only for the application In some embodiments, for those of ordinary skill in the art, without paying creative labor, other drawings may be obtained based on these drawings.

FIG. 1 is a schematic flowchart of an implementation of the boot detection method provided in Embodiment 1 of the present application;

2 is a schematic diagram of an implementation process of the boot detection method provided in Embodiment 2 of the present application;

3 is a schematic diagram of a boot detection device provided in Embodiment 3 of the present application;

4 is a schematic diagram of a mobile terminal provided in Embodiment 4 of the present application;

5 is a schematic diagram of a mobile terminal provided in Embodiment 5 of the present application.

detailed description

In the following description, for the purpose of illustration rather than limitation, specific details such as specific system structure and technology are proposed to thoroughly understand the embodiments of the present application. However, those skilled in the art should understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary details.

It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements, and/or components, but does not exclude one or more other features , Wholes, steps, operations, elements, components and/or their existence or addition.

In a specific implementation, the mobile terminals described in the embodiments of the present application include but are not limited to other portable devices such as mobile phones, laptop computers, or tablet computers with touch-sensitive surfaces (eg, touch screen displays and/or touch pads) . It should also be understood that, in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (eg, touch screen display and/or touch pad).

In the following discussion, a mobile terminal including a display and a touch-sensitive surface is described. However, it should be understood that the mobile terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.

The mobile terminal supports various applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk burning applications, spreadsheet applications, game applications, phones Apps, video conferencing apps, email apps, instant messaging apps, exercise support apps, photo management apps, digital camera apps, digital camera apps, web browsing apps, digital music player apps And/or digital video player applications.

Various applications that can be executed on the mobile terminal can use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal may be adjusted and/or changed between applications and/or within the corresponding applications. In this way, the common physical architecture of the terminal (eg, touch-sensitive surface) can support various applications with a user interface that is intuitive and transparent to the user.

It should be understood that the size of the sequence numbers of the steps in this embodiment does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In order to explain the above technical solutions of the present application, the following will be described by specific embodiments.

Example 1

Referring to FIG. 1, it is a schematic diagram of an implementation process of the boot detection method provided in Embodiment 1 of the present application. The boot detection method is applied to a mobile terminal. As shown in the figure, the boot detection method may include the following steps:

Step S101: Detect whether a preset identifier exists in the storage device.

In the embodiment of the present application, the preset identifier may refer to a preset identifier used to indicate that the startup is not completed. The mobile terminal usually includes multiple startup phases during the startup process, and a preset logo can be set for each startup phase, that is, a correspondence relationship between different startup phases and different preset logos is established, and different startup phases correspond to different preset logos, thereby According to the preset logo, determine the specific stage of incomplete booting.

Optionally, the startup stage includes a first startup stage, a second startup stage, a kernel kernel stage and an Android stage.

In the embodiment of the present application, the booting process may include four booting stages, which are a first booting stage, a second booting stage, a Kernel stage, and an Android stage. The four booting stages are sequentially executed during the booting process. Among them, the first startup stage is used to set up a secure environment, initialize the bus, double data rate (DDR) memory, clock, power management integrated circuit (Power Management IC, PMIC) and other drivers, and load the second startup stage; The second startup stage is used to initialize drivers such as PMIC, Universal Asynchronous Receiver/Transmitter (UART), and load Fastboot or Kernel; the Kernel stage provides functions such as file system, process management, and memory management; the Android stage provides Application, interface and other support.

Optionally, the first startup stage is an extensible boot loader (eXtensible Boot Loader, XBL) stage or a preloader program Preloader stage.

Optionally, the second startup stage is a unified extensible firmware interface (Unified Extensible Firmware Interface, UEFI) stage and a small kernel (Little Kernel, LK) stage.

In the embodiment of the present application, the mobile terminal uses different platforms, and the first startup stage and the second startup stage may be different. For example, when the mobile terminal uses the Qualcomm platform, the first startup stage may be the XBL stage, and the second startup stage may be UEFI phase; when the mobile terminal uses the MediaTek platform, the first startup phase may be the Preloader phase, and the second startup phase may be the LK phase.

Step S102, if the preset identifier exists in the storage device, acquire a start-up phase corresponding to the preset identifier.

In the embodiment of the present application, if the preset identifier exists in the storage device, it is determined that there is a situation in which the startup is not completed during the startup process, and the specific stage in which the startup is not completed can be obtained through the preset identifier; if If the preset identifier does not exist in the storage device, it is determined that there is no incomplete booting in the booting process, and there is no need to perform subsequent processes.

In step S103, it is determined that the startup phase corresponding to the preset identifier is not completed during the startup process.

Wherein, failing to complete the power-on phase corresponding to the preset logo may refer to a failure (eg, stuck) during the power-on phase corresponding to the preset logo, and the power-on corresponding to the preset logo cannot be executed Everything in the stage.

Exemplarily, the first startup phase corresponds to the preset logo 0x5A, the second startup phase corresponds to the preset logo 0x6B, the Kernel phase corresponds to the preset logo 0x7C, and the Android phase corresponds to the preset logo 0x8D. If 0x7C is detected in the storage device, then It indicates that the Kernel phase was not completed during the boot process.

In the embodiment of the present application, a preset logo indicating that the startup is not completed is set for each startup stage, and the preset logo is written into the storage device to detect whether the preset logo exists in the storage device. If there is a preset logo, it can be determined The startup phase corresponding to the preset logo is not completed, so that the uncompleted startup phase is quickly and accurately found according to the preset logo.

Example 2

Referring to FIG. 2, which is a schematic diagram of an implementation process of a power-on detection method provided in Embodiment 2 of the present application. The power-on detection method is applied to a mobile terminal. As shown in the figure, the power-on detection method may include the following steps:

Step S201: Monitor each startup stage during the startup process, and if it is detected that any startup stage is not completed, write a preset identifier corresponding to the startup stage in the storage device.

Optionally, the storage device may be an embedded multimedia memory card (Embedded Multi Media (eMMC) or universal flash memory (Universal Flash Storage, UFS).

Optionally, the monitoring of each startup stage during the startup process, and if it is detected that any startup stage is not completed, writing the preset identifier corresponding to the startup stage in the storage device includes:

Start the watchdog timer;

If it is detected that the watchdog timer times out during the first start-up phase, it is determined that the first start-up phase has not been completed during the boot process, and a first preset flag is written in the storage device;

If it is detected that the watchdog timer times out during the second startup phase, it is determined that the second startup phase has not been completed during the startup process, and a second preset flag is written in the storage device.

In the embodiment of the present application, when the first start-up phase is started, the watchdog timer is started. If the watchdog timer timeout is detected in the first start-up phase, it may be determined that the first start-up is not completed during the boot process Phase, because if the first start-up phase is successfully completed, the watchdog timer clear operation is performed and the watchdog timer does not time out. Similarly, if the first start-up phase is successfully completed during the boot process, the watchdog timer is cleared, the watchdog timer is reset to a preset time (for example, 20 seconds), and the second start-up phase is started. If the watchdog timer timeout is detected during the second start-up phase, it can be determined that the second start-up phase has not been completed during the boot process, because if the first start-up phase is successfully completed, the watchdog timer clear operation is performed. The watchdog timer will not time out.

In the embodiment of the present application, if the first startup stage is the XBL stage, the PMIC watchdog timer can be used for monitoring in the XBL stage, and if the second startup stage is the UEFI stage, the application processor can be used in the UEFI stage (Application Processor, AP) watchdog timer for monitoring; if the first start-up phase is the Preloader phase and the second start-up phase is the LK phase, the AP's watchdog timer can be used in both the Preloader and LK phases monitor.

Start the Kernel timer;

If it is detected that the Kernel timer expires during the Kernel stage, it is detected whether the first preset flag bit information exists;

If the first preset flag bit information does not exist, or the first preset flag bit information exists and the first preset flag bit information is not the first preset value, it is determined that the Describe the Kernel stage, and write a third preset identifier in the storage device;

If it is detected that the Kernel timer has expired in the Android stage, it is detected whether the second preset flag bit information exists; or a service Service is started in the Android stage, and after waking up the Service, it is detected whether the second preset flag bit exists information;

If the second preset flag bit information does not exist, or the second preset flag bit information exists and the second preset flag bit information is not the second preset value, it is determined that the Describe the Android stage, and write a fourth preset identifier in the storage device.

In the embodiment of the present application, the Kernel stage may be monitored using the Kernel timer. Specifically: if the second startup stage is successfully completed during the boot process, the watchdog timer clear operation is performed, and the watchdog timer resets the preset Set a time (for example, 20 seconds) to kick the dog (this watchdog timer can be used to monitor other programs), and start the Kernel timer, the Kernel timer is set with a timeout period (for example, 8 minutes), if in the Kernel stage It is detected that the Kernel timer times out (for example, after 8 minutes), and then it is detected whether the first preset flag bit information is present, and if the first preset flag bit information is not present, it is determined that the process is not completed during the boot process Kernel stage, and write a third preset flag in the storage device; or if the first preset flag bit information is present and the first preset flag bit information is not the first preset value, it is determined that The Kernel stage is not completed during the boot process; if the first preset flag bit information is present and the first preset flag bit information is the first preset value, it is determined that the Kernel stage is successfully completed during the boot process . The first preset flag bit information is used to indicate whether the Kernel stage is successfully completed, the first preset value is used to indicate the Kernel stage is successfully completed, and when the Kernel stage is successfully completed, the first preset flag is set Bit information, and set the first preset flag bit information to a first preset value, and the user can set the first preset value by himself, for example, 1 or TRUE.

In the embodiment of the present application, the Kernel timer can be used for monitoring in the Android stage. Specifically: if the Kernel stage is successfully completed during the startup process, the Android stage is started, and the Kernel timer is continued to be used. When the Kernel timer times out, it is detected whether there is second preset flag bit information. The Android stage can also start a Service during the execution of the Android stage to monitor the startup process of the Android stage. The Service is set with a sleep time (for example, 5 minutes). After the sleep time, the Service is woken up to detect whether there is a second Set the flag bit information. Wherein, the second preset flag bit information may be a sys.boot_completed flag, which is used to indicate whether the Android stage is successfully completed. The second preset value is used to indicate the successful completion of the Android stage, and when the successful completion of the Android stage is detected, the second preset flag bit information is set, and the second preset flag bit information is set to the second preset value , The user can set the second preset value, such as 1 or TRUE.

Optionally, when a preset identifier corresponding to the startup stage is written in the storage device, the embodiment of the present application further includes:

Record the current on-site log and send the on-site log to a preset server.

In the embodiment of the present application, when an unfinished startup phase is detected, a preset identifier corresponding to the startup phase (ie, the monitored uncompleted startup phase) may be written in the storage device before the mobile terminal restarts, In order to indicate which stage has not been completed, and record the current on-site log at the same time, store the on-site log to the storage device, after the mobile terminal is successfully turned on, return the on-site log to the preset server, which is convenient for R&D personnel to view the site Logs to analyze the reasons for the incomplete stage of the power-on phase to repair it. Wherein, the preset server may refer to a server of a mobile terminal operator. The current on-site log may refer to the environment information of the mobile terminal at the current moment, for example, some identification information at the current moment of the unfinished start-up phase, state information of the mobile terminal, etc. These information can analyze the cause of the uncompleted start-up phase.

Step S202: Detect whether a preset identifier exists in the storage device.

In the embodiment of the present application, this step is the same as or similar to step 101. For details, refer to the related description of step 101, and details are not described herein again.

Step S203, if the preset identifier exists in the storage device, obtain a start-up phase corresponding to the preset identifier.

In the embodiment of the present application, this step is the same as or similar to step 102. For details, refer to the related description of step 102, and details are not described herein again.

In step S204, it is determined that the startup phase corresponding to the preset identifier is not completed during the startup process.

In the embodiment of the present application, this step is the same as or similar to step 103. For details, refer to the related description of step 103, and details are not described herein again.

Example 3

Referring to FIG. 3, it is a power-on detection device provided in Embodiment 3 of the present application. The above power-on detection device may be integrated into a mobile terminal. For ease of description, only parts related to the embodiment of the present application are shown.

The boot detection device includes:

The identification detection module 31 is used to detect whether a preset identification exists in the storage device;

The stage obtaining module 32 is configured to obtain a start-up stage corresponding to the preset identifier if the preset identifier exists in the storage device;

The stage determination module 33 is configured to determine that the start-up stage corresponding to the preset identifier is not completed during the start-up process.

Optionally, the first startup stage is an extensible bootloader XBL stage or a preloader stage.

Optionally, the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.

Optionally, the startup detection device further includes:

The power-on monitoring module 34 is used to monitor each power-on phase during the power-on process. If any power-on phase is not completed, a preset identifier corresponding to the power-on phase is written in the storage device.

Optionally, the startup monitoring module 34 includes:

The first starting unit is used to start the watchdog timer;

The first determining unit is configured to determine that the first start-up phase is not completed during the start-up process if the watchdog timer times out during the first start-up phase, and write the first in the storage device Preset logo

The second determining unit is configured to, if the watchdog timer times out during the second startup phase, determine that the second startup phase has not been completed during the boot process, and write the second in the storage device Preset logo

The second start unit is used to start the Kernel timer;

A first detection unit, configured to detect whether the first preset flag bit information is present if the Kernel timer is detected to expire during the Kernel stage;

The third determining unit is configured to determine if the first preset flag bit information does not exist, or if the first preset flag bit information exists and the first preset flag bit information is not the first preset value The Kernel stage is not completed during the boot process, and a third preset logo is written in the storage device;

The second detection unit is configured to detect whether the second preset flag bit information is present if the Kernel timer is detected to expire in the Android stage; or to start a service Service in the Android stage and detect whether the service wakes up after the Service There is second preset flag bit information;

The fourth determining unit is configured to determine if the second preset flag bit information does not exist, or if the second preset flag bit information exists and the second preset flag bit information is not the second preset value The Android stage is not completed during the boot process, and a fourth preset logo is written in the storage device.

Optionally, the boot monitoring module 34 is also used to:

Record the current on-site log and send the on-site log to a preset server.

Optionally, the storage device is an embedded multimedia memory card eMMC or a universal flash storage UFS.

The boot detection device provided by the embodiment of the present application may be applied to the foregoing method embodiments 1 and 2, for details, refer to the descriptions of the above method embodiments 1 and 2, which will not be repeated here.

Example 4

4 is a schematic diagram of a mobile terminal provided in Embodiment 4 of the present application. As shown in the figure, the mobile terminal may include: one or more processors 401 (only one shown in the figure); one or more input devices 402 (only one shown in the figure), and one or more output devices 403 (Only one is shown in the figure) and the memory 404. The processor 401, the input device 402, the output device 403, and the memory 404 are connected via a bus 405. The memory 404 is used to store instructions, and the processor 401 is used to execute the instructions stored in the memory 404. among them:

The processor 401 is configured to detect whether a preset identifier exists in the storage device; if the preset identifier exists in the storage device, acquire a start-up phase corresponding to the preset identifier; determine that no Complete the start-up phase corresponding to the preset identification.

Optionally, the processor 401 is also used to:

Monitoring the startup phase during the startup process, and if it is detected that any startup phase is not completed during the startup process, a preset identifier corresponding to the startup phase is written in the storage device.

Optionally, the processor 401 is specifically used to:

Start the watchdog timer;

Optionally, the processor 401 is specifically used to:

Start the Kernel timer;

If it is detected that the Kernel timer times out in the Android stage, it detects whether there is second preset flag bit information; or in the Android stage, a service Service is started, and after waking up the Service, it is detected whether there is a second preset flag bit information;

Optionally, the processor 401 is also used to:

Record the current on-site log and send the on-site log to a preset server.

It should be understood that in the embodiment of the present application, the processor 401 may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP) , Application Specific Integrated Circuit (Application Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The input device 402 may include a touchpad, a fingerprint sensor (for collecting user fingerprint information and fingerprint direction information), a microphone, and a data receiving interface. The output device 403 may include a display (LCD, etc.), a speaker, a data transmission interface, and the like.

The memory 404 may include a read-only memory and a random access memory, and provide instructions and data to the processor 401. A portion of the memory 404 may also include non-volatile random access memory. For example, the memory 404 may also store device type information.

In a specific implementation, the processor 401, the input device 402, the output device 403, and the memory 404 described in the embodiments of the present application can execute the implementation described in the embodiment of the boot detection method provided by the embodiments of the present application, and can also be executed The implementation described in the boot detection device in Embodiment 3 will not be repeated here.

Example 5

5 is a schematic diagram of a mobile terminal provided in Embodiment 5 of the present application. As shown in FIG. 5, the mobile terminal 5 of this embodiment includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50. When the processor 50 executes the computer program 52, the steps in the above embodiments of each information processing method are implemented, for example, steps S101 to S103 shown in FIG. 1. Alternatively, when the processor 50 executes the computer program 52, the functions of each module/unit in the foregoing device embodiments are realized, for example, the functions of the modules 31 to 34 shown in FIG. 3.

Exemplarily, the computer program 52 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 51 and executed by the processor 50 to complete This application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions. The instruction segments are used to describe the execution process of the computer program 52 in the mobile terminal 5. For example, the computer program 52 may be divided into an identification detection module, a stage acquisition module, a stage determination module, and a start-up monitoring module. The specific functions of each module are as follows:

Optionally, the startup monitoring module is used to monitor each startup stage during the startup process, and if any startup stage is not completed, write a preset identifier corresponding to the startup stage in the storage device.

Optionally, the startup monitoring module includes:

The first starting unit is used to start the watchdog timer;

The second start unit is used to start the Kernel timer;

Optionally, the startup monitoring module is also used for:

Record the current on-site log and send the on-site log to a preset server.

The mobile terminal 5 may be a computing device such as a desktop computer, a notebook, a palmtop computer and a cloud server. The mobile terminal may include, but is not limited to, the processor 50 and the memory 51. Those skilled in the art may understand that FIG. 5 is only an example of the mobile terminal 5 and does not constitute a limitation on the mobile terminal 5, and may include more or fewer components than those illustrated, or a combination of certain components, or different components. For example, the mobile terminal may further include input and output devices, network access devices, buses, and the like.

The so-called processor 50 may be a central processing unit CPU or other general-purpose processors, digital signal processors DSP, application specific integrated circuits ASIC, ready-made programmable gate array FPGA or other programmable logic devices, discrete gates or transistor logic devices , Discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 51 may be an internal storage unit of the mobile terminal 5, such as a hard disk or a memory of the mobile terminal 5. The memory 51 may also be an external storage device of the mobile terminal 5, such as a plug-in hard disk equipped on the mobile terminal 5, a smart memory card (Smart) Media (SMC), and a secure digital (SD) Cards, flash cards, etc. Further, the memory 51 may also include both an internal storage unit of the mobile terminal 5 and an external storage device. The memory 51 is used to store the computer program and other programs and data required by the mobile terminal. The memory 51 can also be used to temporarily store data that has been or will be output.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, only the above-mentioned division of each functional unit and module is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated by different functional units, Module completion means that the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above integrated unit may use hardware It can also be implemented in the form of software functional units. In addition, the specific names of each functional unit and module are only for the purpose of distinguishing each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the above embodiments, the description of each embodiment has its own emphasis. For a part that is not detailed or recorded in an embodiment, you can refer to the related descriptions of other embodiments.

Those of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed device/mobile terminal may be implemented in other ways. For example, the device/mobile terminal embodiments described above are only schematic. For example, the division of the module or unit is only a logical function division, and in actual implementation, there may be another division manner, such as multiple units Or components can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or software functional unit.

If the integrated module/unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the present application can implement all or part of the processes in the methods of the above embodiments, and can also be completed by a computer program instructing relevant hardware. The computer program can be stored in a computer-readable storage medium. When the program is executed by the processor, the steps of the foregoing method embodiments may be implemented. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, and a read-only memory (Read-Only Memory, ROM) , Random Access Memory (Random Access Memory, RAM), electrical carrier signals, telecommunications signals and software distribution media, etc. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in jurisdictions. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media Does not include electrical carrier signals and telecommunications signals.

The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still implement the foregoing The technical solutions described in the examples are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application. Within the scope of protection of this application.

Claims

A startup detection method, characterized in that the startup detection method includes:

Detect whether there is a preset mark in the storage device;

If the preset identifier exists in the storage device, obtain a start-up phase corresponding to the preset identifier;

It is determined that the startup phase corresponding to the preset identification is not completed during the startup process.
The boot detection method according to claim 1, wherein the boot phase includes a first boot phase, a second boot phase, a kernel Kernel phase, and an Android Android phase.
The boot detection method according to claim 2, wherein the first startup stage is an extensible startup loader XBL stage or a preloader stage.
The boot detection method according to claim 2, wherein the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.
The boot detection method according to claim 2, wherein before detecting whether the preset identifier exists in the storage device, the method further comprises:

During the startup process, each startup stage is monitored, and if it is detected that any startup stage is not completed, a preset identifier corresponding to the startup stage is written in the storage device.
The boot detection method according to claim 5, wherein each boot phase is monitored during the boot process, and if it is detected that any boot phase is not completed, the storage device is written to correspond to the boot phase The preset logos include:

Start the watchdog timer;

If it is detected that the watchdog timer times out during the first start-up phase, it is determined that the first start-up phase has not been completed during the boot process, and a first preset flag is written in the storage device;

If it is detected that the watchdog timer times out during the second startup phase, it is determined that the second startup phase has not been completed during the startup process, and a second preset flag is written in the storage device.
The boot detection method according to claim 5, wherein each boot phase is monitored during the boot process, and if it is detected that any boot phase is not completed, the storage device is written to correspond to the boot phase The preset logos include:

Start the Kernel timer;

If it is detected that the Kernel timer expires during the Kernel stage, it is detected whether the first preset flag bit information exists;

If the first preset flag bit information does not exist, or the first preset flag bit information exists and the first preset flag bit information is not the first preset value, it is determined that the Describe the Kernel stage, and write a third preset identifier in the storage device;

If it is detected that the Kernel timer times out in the Android stage, it detects whether there is second preset flag bit information; or in the Android stage, a service Service is started, and after waking up the Service, it is detected whether there is a second preset flag bit information;

If the second preset flag bit information does not exist, or the second preset flag bit information exists and the second preset flag bit information is not the second preset value, it is determined that the Describe the Android stage, and write a fourth preset identifier in the storage device.
The boot detection method according to claim 5, wherein when writing a preset logo corresponding to the boot phase in the storage device, the method further comprises:

Record the current on-site log and send the on-site log to a preset server.
The boot detection method according to any one of claims 1 to 8, wherein the storage device is an embedded multimedia memory card eMMC or a universal flash memory UFS.
A startup detection device, characterized in that the startup detection device includes:

The identification detection module is used to detect whether a preset identification exists in the storage device;

A stage obtaining module, configured to obtain a start-up stage corresponding to the preset identifier if the preset identifier exists in the storage device;

The stage determination module is used to determine that the start-up stage corresponding to the preset identifier is not completed during the start-up process.
A mobile terminal, characterized in that it includes a memory, a processor, and a computer program stored in the memory and runable on the processor, wherein the processor is implemented as follows when executing the computer program step:

Detect whether there is a preset mark in the storage device;

If the preset identifier exists in the storage device, obtain a start-up phase corresponding to the preset identifier;

It is determined that the startup phase corresponding to the preset identification is not completed during the startup process.
The mobile terminal according to claim 11, wherein the power-on phase includes a first startup phase, a second startup phase, a kernel Kernel phase, and an Android Android phase.
The mobile terminal of claim 12, wherein the first startup stage is an extensible bootloader XBL stage or a preloader stage.
The mobile terminal of claim 12, wherein the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.
The mobile terminal of claim 12, wherein the processor further implements the following steps when executing the computer program:

Monitoring the startup phase during the startup process, if it is detected that any startup phase is not completed during the startup process, a preset identifier corresponding to the startup phase is written in the storage device.
The mobile terminal of claim 15, wherein the processor specifically implements the following steps when executing the computer program:

Start the watchdog timer;

If it is detected that the watchdog timer times out during the first start-up phase, it is determined that the first start-up phase has not been completed during the boot process, and a first preset flag is written in the storage device;

If it is detected that the watchdog timer times out during the second startup phase, it is determined that the second startup phase has not been completed during the startup process, and a second preset flag is written in the storage device.
The mobile terminal of claim 15, wherein the processor specifically implements the following steps when executing the computer program:

Start the Kernel timer;

If it is detected that the Kernel timer expires during the Kernel stage, it is detected whether the first preset flag bit information exists;

If the first preset flag bit information does not exist, or the first preset flag bit information exists and the first preset flag bit information is not the first preset value, it is determined that the Describe the Kernel stage, and write a third preset identifier in the storage device;

If it is detected that the Kernel timer times out in the Android stage, it detects whether there is second preset flag bit information; or in the Android stage, a service Service is started, and after waking up the Service, it is detected whether there is a second preset flag bit information;

If the second preset flag bit information does not exist, or the second preset flag bit information exists and the second preset flag bit information is not the second preset value, it is determined that the Describe the Android stage, and write a fourth preset identifier in the storage device.
The mobile terminal of claim 15, wherein the processor further implements the following steps when executing the computer program:

Record the current on-site log and send the on-site log to a preset server.
The mobile terminal according to any one of claims 11 to 18, wherein the storage device is an embedded multimedia memory card eMMC or a universal flash memory UFS.
A computer-readable storage medium storing a computer program, characterized in that when the computer program is executed by a processor, the steps of the power-on detection method according to any one of claims 1 to 9 are implemented .