WO2020113469A1 - Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile - Google Patents

Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile Download PDF

Info

Publication number
WO2020113469A1
WO2020113469A1 PCT/CN2018/119377 CN2018119377W WO2020113469A1 WO 2020113469 A1 WO2020113469 A1 WO 2020113469A1 CN 2018119377 W CN2018119377 W CN 2018119377W WO 2020113469 A1 WO2020113469 A1 WO 2020113469A1
Authority
WO
WIPO (PCT)
Prior art keywords
preset
stage
startup
phase
storage device
Prior art date
Application number
PCT/CN2018/119377
Other languages
English (en)
Chinese (zh)
Inventor
王立中
Original Assignee
深圳市欢太科技有限公司
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市欢太科技有限公司, Oppo广东移动通信有限公司 filed Critical 深圳市欢太科技有限公司
Priority to PCT/CN2018/119377 priority Critical patent/WO2020113469A1/fr
Priority to CN201880098763.0A priority patent/CN112912855A/zh
Publication of WO2020113469A1 publication Critical patent/WO2020113469A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software

Definitions

  • 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.
  • 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:
  • 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.
  • 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.
  • FIG. 1 is a schematic flowchart of an implementation of the boot detection method provided in Embodiment 1 of the present application;
  • FIG. 2 is a schematic diagram of an implementation process of the boot detection method provided in Embodiment 2 of the present application;
  • FIG. 3 is a schematic diagram of a boot detection device provided in Embodiment 3 of the present application.
  • FIG. 4 is a schematic diagram of a mobile terminal provided in Embodiment 4 of the present application.
  • FIG. 5 is a schematic diagram of a mobile terminal provided in Embodiment 5 of the present application.
  • 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) .
  • 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).
  • a mobile terminal including a display and a touch-sensitive surface is described.
  • 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.
  • drawing 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.
  • the common physical architecture of the terminal eg, touch-sensitive surface
  • 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.
  • the boot detection method may include the following steps:
  • Step S101 Detect whether a preset identifier exists in the storage device.
  • 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.
  • the startup stage includes a first startup stage, a second startup stage, a kernel kernel stage and an Android stage.
  • 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.
  • 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.
  • the first startup stage is an extensible boot loader (eXtensible Boot Loader, XBL) stage or a preloader program Preloader stage.
  • extensible boot loader eXtensible Boot Loader, XBL
  • preloader program Preloader stage eXtensible Boot Loader
  • the second startup stage is a unified extensible firmware interface (Unified Extensible Firmware Interface, UEFI) stage and a small kernel (Little Kernel, LK) stage.
  • UEFI Unified Extensible Firmware Interface
  • LK Small Kernel
  • the mobile terminal uses different platforms, and the first startup stage and the second startup stage may be different.
  • the first startup stage may be the XBL stage, and the second startup stage may be UEFI phase;
  • 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.
  • 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.
  • step S103 it is determined that the startup phase corresponding to the preset identifier is not completed during the startup process.
  • 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.
  • 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
  • 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.
  • 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.
  • FIG. 2 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.
  • the storage device may be an embedded multimedia memory card (Embedded Multi Media (eMMC) or universal flash memory (Universal Flash Storage, UFS).
  • eMMC embedded Multi Media
  • UFS Universal Flash Storage
  • 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:
  • the watchdog timer 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.
  • a preset time for example, 20 seconds
  • 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.
  • the PMIC watchdog timer can be used for monitoring in the XBL 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.
  • AP Application Processor
  • 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:
  • 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;
  • the Kernel timer 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;
  • 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 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;
  • 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.
  • 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.
  • 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.
  • the embodiment of the present application further includes:
  • a preset identifier corresponding to the 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.
  • 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.
  • this step is the same as or similar to step 101.
  • steps 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.
  • this step is the same as or similar to step 102.
  • steps 102 For details, refer to the related description of step 102, and details are not described herein again.
  • step S204 it is determined that the startup phase corresponding to the preset identifier is not completed during the startup process.
  • this step is the same as or similar to step 103.
  • steps 103 For details, refer to the related description of step 103, and details are not described herein again.
  • 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.
  • 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.
  • the startup stage includes a first startup stage, a second startup stage, a kernel kernel stage and an Android stage.
  • the first startup stage is an extensible bootloader XBL stage or a preloader stage.
  • the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.
  • 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.
  • 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.
  • boot monitoring module 34 is also used to:
  • 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.
  • 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.
  • the startup stage includes a first startup stage, a second startup stage, a kernel kernel stage and an Android stage.
  • the first startup stage is an extensible bootloader XBL stage or a preloader stage.
  • the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.
  • processor 401 is also used to:
  • a preset identifier corresponding to the startup phase is written in the storage device.
  • the processor 401 is specifically used to:
  • the processor 401 is specifically used to:
  • 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;
  • 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;
  • 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.
  • processor 401 is also used to:
  • the storage device is an embedded multimedia memory card eMMC or a universal flash storage UFS.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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:
  • 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.
  • the startup stage includes a first startup stage, a second startup stage, a kernel kernel stage and an Android stage.
  • the first startup stage is an extensible bootloader XBL stage or a preloader stage.
  • the second startup stage is a unified extensible firmware interface UEFI stage and a small kernel LK stage.
  • 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.
  • the startup monitoring module 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.
  • the startup monitoring module is also used for:
  • the storage device is an embedded multimedia memory card eMMC or a universal flash storage UFS.
  • 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.
  • 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.
  • 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.
  • each functional unit and module is used as an example for illustration.
  • 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.
  • 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.
  • the disclosed device/mobile terminal may be implemented in other ways.
  • the device/mobile terminal embodiments described above are only schematic.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • electrical carrier signals telecommunications signals and software distribution media, etc.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé d'auto-test de mise sous tension, un dispositif d'auto-test de mise sous tension, un terminal mobile (5) et un support d'informations lisibles par ordinateur, le procédé d'auto-test de mise sous tension consiste : à détecter si un identifiant prédéfini est présent dans un dispositif de stockage (S101, S202) ; si tel est le cas, à acquérir un étage de mise sous tension correspondant à l'identifiant prédéfini (S102, S203) ; et à déterminer que l'étage de mise sous tension correspondant à l'identifiant prédéfini n'est pas achevée lors du processus de mise sous tension. Le procédé résout le problème de l'état de la technique selon lequel il n'est pas possible de déterminer à quel étage un procédé de mise sous tension échoue.
PCT/CN2018/119377 2018-12-05 2018-12-05 Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile WO2020113469A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/119377 WO2020113469A1 (fr) 2018-12-05 2018-12-05 Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile
CN201880098763.0A CN112912855A (zh) 2018-12-05 2018-12-05 开机检测方法、开机检测装置及移动终端

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/119377 WO2020113469A1 (fr) 2018-12-05 2018-12-05 Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile

Publications (1)

Publication Number Publication Date
WO2020113469A1 true WO2020113469A1 (fr) 2020-06-11

Family

ID=70974451

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/119377 WO2020113469A1 (fr) 2018-12-05 2018-12-05 Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile

Country Status (2)

Country Link
CN (1) CN112912855A (fr)
WO (1) WO2020113469A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114237378B (zh) * 2022-02-24 2022-07-12 荣耀终端有限公司 电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130132776A1 (en) * 2011-11-21 2013-05-23 Huawei Technologies Co., Ltd. Method for outputting power-on self test information, virtual machine manager, and processor
CN103761124A (zh) * 2014-01-06 2014-04-30 武汉烽火富华电气有限责任公司 用于保护测控装置的嵌入式Linux系统启动方法
CN103905603A (zh) * 2012-12-21 2014-07-02 上海晨兴希姆通电子科技有限公司 手机开机方法及手机开机系统
CN107145413A (zh) * 2017-04-21 2017-09-08 深圳市同泰怡信息技术有限公司 一种基于BMC的服务器BMC Post运行过程检测的固件开发方法
CN107704380A (zh) * 2017-07-26 2018-02-16 深圳天珑无线科技有限公司 移动终端调试方法、装置及存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104166561B (zh) * 2014-07-25 2017-11-07 深圳市大迈科技有限公司 电子设备系统启动方法和电子设备
CN106021006B (zh) * 2016-05-17 2019-03-26 Oppo广东移动通信有限公司 一种终端开机异常的处理方法及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130132776A1 (en) * 2011-11-21 2013-05-23 Huawei Technologies Co., Ltd. Method for outputting power-on self test information, virtual machine manager, and processor
CN103905603A (zh) * 2012-12-21 2014-07-02 上海晨兴希姆通电子科技有限公司 手机开机方法及手机开机系统
CN103761124A (zh) * 2014-01-06 2014-04-30 武汉烽火富华电气有限责任公司 用于保护测控装置的嵌入式Linux系统启动方法
CN107145413A (zh) * 2017-04-21 2017-09-08 深圳市同泰怡信息技术有限公司 一种基于BMC的服务器BMC Post运行过程检测的固件开发方法
CN107704380A (zh) * 2017-07-26 2018-02-16 深圳天珑无线科技有限公司 移动终端调试方法、装置及存储介质

Also Published As

Publication number Publication date
CN112912855A (zh) 2021-06-04

Similar Documents

Publication Publication Date Title
US8914653B2 (en) Method and system for providing hybrid-shutdown and fast startup processes
US10866623B2 (en) Information handling system and method to detect and recover from no power/no post failures
US8863109B2 (en) Updating secure pre-boot firmware in a computing system in real-time
CN107608693B (zh) 版本升级方法及终端设备
TWI465901B (zh) Method and system for verification of computerized systems for cloud testing and remote monitoring of integrated circuit devices
US20150186161A1 (en) Platform system, method for changing support hardware configuration of universal extensible firmware interface basic input output system and computer program product
WO2016074127A1 (fr) Dispositif informatique et procédé de démarrage de mémoire pour un dispositif informatique
CN104185836A (zh) 用于在系统改变之后验证计算设备的适当操作的方法和系统
US20160314002A1 (en) Caching unified extensible firmware interface (uefi) and/or other firmware instructions in a non-volatile memory of an information handling system (ihs)
CN103970560A (zh) 开机方法与电子装置
CN111581154B (zh) 用于管理数据库的电子设备和方法
US20130268744A1 (en) Method for detecting hardware
WO2020015203A1 (fr) Procédé et dispositif de récupération de système
CN107135462A (zh) Uefi 固件的蓝牙配对方法及其计算系统
TWI515557B (zh) 電腦系統與控制方法
US10115375B2 (en) Systems and methods for enabling a systems management interface with an alternate frame buffer
US20140365758A1 (en) Techniques for booting an information processing system
TWI310157B (en) Method for changing booting source of a computer system and related backuping/restoring method thereof
US11429723B2 (en) Multi-domain boot and runtime status code drift detection
WO2020113469A1 (fr) Procédé d'auto-test de mise sous tension, dispositif d'auto-test de mise sous tension et terminal mobile
US11467849B2 (en) Systems and methods for collecting deep operating system (OS) telemetry
TW202131170A (zh) 韌體損壞恢復技術
US20070162735A1 (en) Control chip for a computer boot procedure and related method
CN109104481B (zh) 文件完整性检测方法、文件完整性检测装置及终端设备
CN108520063B (zh) 事件日志的处理方法、装置及终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18942600

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19.10.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18942600

Country of ref document: EP

Kind code of ref document: A1