CN111538670A - U-Boot debugging method and system - Google Patents
U-Boot debugging method and system Download PDFInfo
- Publication number
- CN111538670A CN111538670A CN202010358038.1A CN202010358038A CN111538670A CN 111538670 A CN111538670 A CN 111538670A CN 202010358038 A CN202010358038 A CN 202010358038A CN 111538670 A CN111538670 A CN 111538670A
- Authority
- CN
- China
- Prior art keywords
- boot
- printing
- memory
- debug
- opened
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000015654 memory Effects 0.000 claims abstract description 83
- 230000008569 process Effects 0.000 claims description 14
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 5
- 230000002093 peripheral effect Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
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
- G06F11/362—Software debugging
Abstract
The invention discloses a method and a system for debugging U-Boot, relating to the field of equipment debugging, wherein the method comprises the steps of writing mark data into a memory of a CPU (Central processing Unit), wherein the mark data is used for marking whether debug printing is opened or not, and the memory is a cache memory or a random access memory; when the U-Boot is powered on and started, the U-Boot reads the marking data in the memory; and determining whether debug macro printing is opened or not based on the marking data read by the U-Boot. By printing the log information, a plurality of sets of codes do not need to be compiled again, and the engineering development difficulty of developers is effectively reduced.
Description
Technical Field
The invention relates to the field of equipment debugging, in particular to a U-Boot debugging method and a U-Boot debugging system.
Background
The U-Boot (Universal Boot Loader) is used for starting the equipment to run, is responsible for initializing a serial port, a memory and a peripheral interface and preparing for loading kernel software subsequently, and can print some information in the starting process and analyze the running state of the equipment according to the information.
The U-Boot is used as a Boot software, and various hardware drivers, such as a Serial port, an i2c bus, a memory, a qspi (queue Serial Interface), a spi (Serial Peripheral Interface), a network port, and a pci (personal computer extended bus) Interface, are initialized during the Boot process. If the hardware equipment is normal, starting the U-Boot normally; if the U-Boot is abnormally started, it is indicated that some equipment is abnormal, for example, a memory is abnormal, the U-Boot is jammed, at the moment, the U-Boot is required to display more printing logs, the DEBUG macro in a common.h file needs to be defined when the log information is printed by the U-Boot, so that the U-Boot needs to be recompiled, two sets of uboot codes need to be provided under the condition, the U-Boot is used in one set of formal engineering, the U-Boot is used when a problem location problem occurs, and the development difficulty of multiple sets of codes greatly increases the engineering development difficulty of developers.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a U-Boot debugging method and a system, which can effectively reduce the engineering development difficulty of developers by printing log information without recompiling a plurality of sets of codes.
In order to achieve the above purpose, the invention provides a U-Boot debugging method, which comprises the following steps:
writing mark data in a memory of a CPU, wherein the mark data is used for indicating whether debug printing is opened or not, and the memory is a cache memory or a random access memory;
when the U-Boot is powered on and started, the U-Boot reads the marking data in the memory;
and determining whether debug macro printing is opened or not based on the marking data read by the U-Boot.
On the basis of the technical scheme, the writing of the mark data in the memory of the CPU specifically comprises the following steps:
initializing a QSPI Flash memory, and writing the mark data into the QSPI Flash memory;
and the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
On the basis of the technical scheme, the QSPI Flash memory is NOR Flash, Nand Flash, SD card or eMMC.
On the basis of the technical scheme, whether debug macro printing is opened or not is determined based on the marking data read by the U-Boot, and the specific steps comprise: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
On the basis of the above technical solution, before the judgment of the tag data read by the U-Boot, the method further includes: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed.
The invention provides a U-Boot debugging system, comprising:
the writing module is used for writing mark data in a memory of the CPU, and the mark data is used for indicating whether debug printing is opened or not;
the reading module is used for driving the U-Boot to read the marking data in the memory when the U-Boot is powered on and started;
and the execution module is used for determining whether debug macro printing is opened or not based on the marking data read by the U-Boot.
On the basis of the technical scheme, the writing module writes mark data in a memory of the CPU, and the specific process comprises the following steps:
initializing a QSPI Flash memory, and writing the mark data into the QSPI Flash memory;
and the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
On the basis of the technical scheme, the QSPI Flash memory is NOR Flash, Nand Flash, SD card or eMMC.
On the basis of the technical scheme, the execution module determines whether debug macro printing is opened or not based on the marking data read by the U-Boot, and the specific process comprises the following steps: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
On the basis of the above technical solution, before the judgment of the tag data read by the U-Boot, the method further includes: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed.
Compared with the prior art, the invention has the advantages that: the method comprises the steps of writing mark data written in a QSPI Flash memory into a memory of a CPU, reading the mark data in the memory by a U-Boot, determining whether to open debug macro printing based on the read mark data by the U-Boot, writing the mark data into a storage medium, and determining whether to open debug macro printing by the subsequent U-Boot only by reading the mark data written in the storage medium in the starting process, so as to print log information without recompiling multiple sets of codes, thereby effectively reducing the engineering development difficulty of developers.
Drawings
Fig. 1 is a flowchart of a U-Boot debugging method in an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The embodiment of the invention provides a U-Boot debugging method, which is characterized in that mark data are written in a storage medium, and the subsequent U-Boot can determine whether debug macro printing is opened or not to print log information by only reading the mark data written in the storage medium in the starting process. The embodiment of the invention also correspondingly provides a U-Boot debugging system.
Referring to fig. 1, a U-Boot debugging method provided in an embodiment of the present invention includes:
s1: writing label data in a memory of a Central Processing Unit (CPU), the label data indicating whether debug printing is turned on. In the embodiment of the invention, the memory is a cache memory or a random access memory. The write-in operation of the marking data can be executed in a software mode, in the early preparation work, after the U-Boot is powered on and started, the software code is responsible for writing the marking data into the memory, and in the early stage after the U-Boot is powered on, when the relevant software module can read the relevant external equipment after the relevant software is started, for example, after the flash software driving module can work, the marking data can be written into the memory.
Normally, there is a section of RAM (Random Access Memory) or CACHE (Memory) inside the CPU, for example, there is a section of CACHE inside the chip of the ls-series ARM architecture of nxp company, which stores part of Boot code and data during the U-Boot process, and since the address of the CPU of the ARM architecture is directly mapped, the U-Boot can Access the CACHE during the Boot process. Of course, the method of the embodiment of the present invention is also applicable to CPUs with architectures such as MIPS, PPC, X86, and the like.
S2: when the U-Boot is powered on and started, the U-Boot reads the marking data in the memory;
s3: and determining whether debug macro printing is opened or not based on the marking data read by the U-Boot. The method specifically comprises the following steps: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
Of course, whether to open debug macro printing may also be determined according to the external hardware interface configuration information. The external hardware Interface configuration information may be input data of a serial port, configuration of a GPIO (General-purpose input/output), contents of a memory Device of an I2C (Inter-Integrated Circuit/SPI (serial peripheral Interface) Interface, an external CPLD (complex Programmable Logic Device) storage register, and Interface information of an external FPGA (Field Programmable Gate Array) storage register.
According to the U-Boot debugging method, the marking data written in the QSPI Flash memory is written into the memory of the CPU, then the marking data in the memory is read by the U-Boot, whether debug macro printing is opened or not is determined based on the marking data read by the U-Boot, the marking data is written in the storage medium, and whether debug macro printing is opened or not can be determined by reading the marking data written in the storage medium in the starting process of the subsequent U-Boot without recompiling a plurality of sets of codes, so that the engineering development difficulty of developers is effectively reduced, the debug macro printing is conveniently opened, and the problem of positioning of software personnel and hardware personnel is facilitated.
Optionally, on the basis of the embodiment corresponding to fig. 1, in a first optional embodiment of the U-Boot debugging method provided in the embodiment of the present invention, the writing of the flag data in the memory of the CPU includes:
s101: initializing a QSPI (queue SPI, a queue serial peripheral interface protocol) Flash (memory chip), and writing the mark data into a QSPI Flash memory, and certainly, writing the mark data into other external memories; in the initial stage of the U-Boot startup, the storage medium is initialized, here, the QSPI Flash memory is initialized.
The QSPI Flash memory is NOR Flash, Nand Flash, SD card (Secure digital card) or eMMC. NOR Flash is a non-volatile Flash technology created by Intel in 1988. The Nand-Flash is one of Flash memories, and a nonlinear macro-unit mode is adopted in the Nand-Flash memory, so that a cheap and effective solution is provided for realizing a solid-state large-capacity memory. The Nand-flash has the advantages of large capacity, high rewriting speed and the like, is suitable for storing a large amount of data, and is widely applied in the industry. The emmc (embedded Multi media card) is an embedded memory standard specification established by the MMC association and mainly used for products such as mobile phones and tablet computers. The eMMC integrates a controller in the package, provides standard interfaces, and manages the flash memory.
S102: and the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
Before judging the marking data read by the U-Boot, the method further comprises the following steps: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information (log information) is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed. Specifically, a debug macro printing definition may be added to the common header file of the U-Boot, and the debug macro printing definition may be added to the common header file of the U-Boot, and corresponds to the tag data, where the corresponding code is:
# define DEBUG (0)/. Add DEBUG Macro Definitions >
#ifdef DEBUG
# define _ DEBUG (1 ═ CACHE address stored data)/# specify _ DEBUG macro ×
。。。
#endif
If the storage data of the memory is equal to 1, the debug macro printing is opened, and if the storage data of the memory is not equal to 1, the debug macro printing is not opened.
In the U-Boot debugging method of the embodiment of the present invention, the U-Boot reads the tag data written in the QSPI Flash memory or other external storage devices, and writes the read tag data in the memory of the CPU, where the corresponding codes are:
CACHE address store data read _ DEV (); // reading the tag from an external device.
The U-Boot debugging system provided by the embodiment of the invention comprises a writing module, a reading module and an execution module.
The writing module is used for writing mark data in a memory of the CPU, and the mark data is used for marking whether debug printing is opened or not; the reading module is used for driving the U-Boot to read the marking data in the memory when the U-Boot is powered on and started; and the execution module is used for determining whether debug macro printing is opened or not based on the marking data read by the U-Boot.
The writing module writes mark data in a memory of the CPU, and the specific process comprises the following steps:
initializing a QSPI Flash memory, and writing the mark data into the QSPI Flash memory; the QSPI Flash memory is NOR Flash, Nand Flash, SD card or eMMC.
And the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
Optionally, on the basis of the embodiment corresponding to the U-Boot debugging system, in a first optional embodiment of the U-Boot debugging system provided in the embodiment of the present invention, the execution module determines whether to open debug macro printing based on tag data read by the U-Boot, and the specific process includes: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
Before judging the marking data read by the U-Boot, the method further comprises the following steps: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed.
According to the U-Boot debugging system, the marking data written in the QSPI Flash memory is written in the memory of the CPU, then the marking data in the memory is read by the U-Boot, whether debug macro printing is opened or not is determined based on the marking data read by the U-Boot, the marking data is written in the storage medium, and whether debug macro printing is opened or not can be determined by reading the marking data written in the storage medium in the starting process of the subsequent U-Boot without recompiling a plurality of sets of codes, so that the engineering development difficulty of developers is effectively reduced, the debug macro printing is conveniently opened, and the problem of positioning of software personnel and hardware personnel is facilitated.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A U-Boot debugging method is characterized by comprising the following steps:
writing mark data in a memory of a CPU, wherein the mark data is used for indicating whether debug printing is opened or not, and the memory is a cache memory or a random access memory;
when the U-Boot is powered on and started, the U-Boot reads the marking data in the memory;
and determining whether debug macro printing is opened or not based on the marking data read by the U-Boot.
2. A U-Boot debugging method according to claim 1, characterized by: the writing of the mark data in the memory of the CPU specifically comprises the following steps:
initializing a QSPI Flash memory, and writing the mark data into the QSPI Flash memory;
and the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
3. A U-Boot debugging method according to claim 2, characterized by: the QSPI Flash memory is NOR Flash, Nand Flash, SD card or eMMC.
4. The U-Boot debugging method according to claim 1, wherein the step of determining whether to open debug macro printing based on the tag data read by the U-Boot comprises: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
5. A U-Boot debugging method according to claim 4, wherein before determining the flag data read by the U-Boot, the method further comprises: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed.
6. A U-Boot debugging system, comprising:
the writing module is used for writing mark data in a memory of the CPU, and the mark data is used for indicating whether debug printing is opened or not;
the reading module is used for driving the U-Boot to read the marking data in the memory when the U-Boot is powered on and started;
and the execution module is used for determining whether debug macro printing is opened or not based on the marking data read by the U-Boot.
7. The U-Boot debugging system of claim 6, wherein: the writing module writes mark data in a memory of the CPU, and the specific process comprises the following steps:
initializing a QSPI Flash memory, and writing the mark data into the QSPI Flash memory;
and the U-Boot reads the mark data written in the QSPI Flash memory and writes the read mark data into a memory of the CPU.
8. The U-Boot debugging system of claim 7, wherein: the QSPI Flash memory is NOR Flash, Nand Flash, SD card or eMMC.
9. The U-Boot debugging system of claim 6, wherein the execution module determines whether to open debug macro printing based on the tag data read by the U-Boot, and the specific process comprises: judging the marking data read by the U-Boot, and when the marking data is that debug macro printing is opened, opening debug macro printing to print log information; and when the marking data is that the debug macro printing is not opened, closing the debug macro printing.
10. The U-Boot debugging system according to claim 9, further comprising, before determining the flag data read by the U-Boot: adding a debug macro printing definition in the U-Boot, wherein the debug macro printing definition corresponds to the marking data, when the marking data is that debug macro printing is opened, the debug macro printing is opened, log information is printed, and when the marking data is that debug macro printing is not opened, the debug macro printing is closed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010358038.1A CN111538670A (en) | 2020-04-29 | 2020-04-29 | U-Boot debugging method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010358038.1A CN111538670A (en) | 2020-04-29 | 2020-04-29 | U-Boot debugging method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111538670A true CN111538670A (en) | 2020-08-14 |
Family
ID=71978918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010358038.1A Pending CN111538670A (en) | 2020-04-29 | 2020-04-29 | U-Boot debugging method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111538670A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508621A (en) * | 2011-10-20 | 2012-06-20 | 珠海全志科技股份有限公司 | Debugging printing method and device independent of serial port on embedded system |
| CN102541572A (en) * | 2010-12-08 | 2012-07-04 | 中兴通讯股份有限公司 | Method, system and device for realizing guide of operating system kernel |
| CN103678214A (en) * | 2013-11-29 | 2014-03-26 | 青岛海信电器股份有限公司 | Method for redirecting system console and display equipment |
| WO2015154538A1 (en) * | 2014-07-08 | 2015-10-15 | 中兴通讯股份有限公司 | Memory booting method and device |
| CN105260315A (en) * | 2015-11-13 | 2016-01-20 | 上海斐讯数据通信技术有限公司 | Method for debugging log in embedded system process |
| CN108363661A (en) * | 2018-01-04 | 2018-08-03 | 郑州云海信息技术有限公司 | A kind of output implementation method by all kinds of means of application layer code Debugging message |
| CN110135130A (en) * | 2019-04-25 | 2019-08-16 | 武汉虹信通信技术有限责任公司 | A kind of embedded device software tamper-resistant method and system |
| CN110442387A (en) * | 2019-07-02 | 2019-11-12 | 湖北亿咖通科技有限公司 | A kind of the parameter adaptive method, apparatus and automobile of onboard system |
-
2020
- 2020-04-29 CN CN202010358038.1A patent/CN111538670A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541572A (en) * | 2010-12-08 | 2012-07-04 | 中兴通讯股份有限公司 | Method, system and device for realizing guide of operating system kernel |
| CN102508621A (en) * | 2011-10-20 | 2012-06-20 | 珠海全志科技股份有限公司 | Debugging printing method and device independent of serial port on embedded system |
| CN103678214A (en) * | 2013-11-29 | 2014-03-26 | 青岛海信电器股份有限公司 | Method for redirecting system console and display equipment |
| WO2015154538A1 (en) * | 2014-07-08 | 2015-10-15 | 中兴通讯股份有限公司 | Memory booting method and device |
| CN105260315A (en) * | 2015-11-13 | 2016-01-20 | 上海斐讯数据通信技术有限公司 | Method for debugging log in embedded system process |
| CN108363661A (en) * | 2018-01-04 | 2018-08-03 | 郑州云海信息技术有限公司 | A kind of output implementation method by all kinds of means of application layer code Debugging message |
| CN110135130A (en) * | 2019-04-25 | 2019-08-16 | 武汉虹信通信技术有限责任公司 | A kind of embedded device software tamper-resistant method and system |
| CN110442387A (en) * | 2019-07-02 | 2019-11-12 | 湖北亿咖通科技有限公司 | A kind of the parameter adaptive method, apparatus and automobile of onboard system |
Non-Patent Citations (5)
| Title |
|---|
| OUCAIJUN: "C语言：类似linux内核的分等级DEBUG宏（打印宏）", 《HTTPS://WWW.CNBLOGS.COM/MYLINUX/P/5906576.HTML》 * |
| WEIXIN_34087503: ""u-boot 2011.09 开启debug 调试"", 《HTTPS://BLOG.CSDN.NET/WEIXIN_34087503/ARTICLE/DETAILS/85823960》 * |
| 施荣华: "检查和修改寄存器内容的", 《计算机硬件技术基础》 * |
| 王茂才: "debug相关命令介绍", 《计算机病毒实验教程》 * |
| 虚生: "u-boot中debug的一些总结", 《HTTPS://WWW.CNBLOGS.COM/DYLANCAO/P/8673601.HTML》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10909012B2 (en) | System having persistent memory | |
| US20180267920A1 (en) | Expansion component | |
| US8719644B2 (en) | Method and system for diagnosing apparatus | |
| US10599547B2 (en) | Monitoring the operation of a processor | |
| KR101862112B1 (en) | Accelerating boot time zeroing of memory based on non-volatile memory (nvm) technology | |
| WO2018040494A1 (en) | Method and device for extending processor instruction set | |
| JP2012252576A (en) | Information processing device, start method and program | |
| CN104572211A (en) | FPGA program multi-image loading method based on ARM | |
| JP2695017B2 (en) | Data transfer method | |
| JPH08235010A (en) | Data processor with transparent operation in background mode | |
| US20180277236A1 (en) | Memory system with diagnose command and operating method thereof | |
| US9495177B2 (en) | Techniques for pre-OS image rewriting to provide cross-architecture support, security introspection, and performance optimization | |
| US10037284B2 (en) | Bridging and integrating devices across processing systems | |
| TW201616273A (en) | System and method for recovering BIOS data of a computer | |
| CN111538670A (en) | U-Boot debugging method and system | |
| US20160292108A1 (en) | Information processing device, control program for information processing device, and control method for information processing device | |
| CN114446381B (en) | eMMC fault analysis method, device, readable storage medium and electronic equipment | |
| CN115292077A (en) | Kernel exception handling method and system | |
| US8117427B2 (en) | Motherboard, storage device and controller thereof, and booting method | |
| CN100342361C (en) | Method and apparatus for fast reading and writing memory data | |
| EP4296860A1 (en) | Method for running startup program of electronic device, and electronic device | |
| US20130124925A1 (en) | Method and apparatus for checking a main memory of a processor | |
| EP2639692A2 (en) | Memory dump program, information processing apparatus, and memory dump method | |
| CN114385524A (en) | Embedded firmware simulation system and method and device thereof, and electronic equipment | |
| TWI779630B (en) | Systems and methods for storing debug information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200814 |
|
| RJ01 | Rejection of invention patent application after publication |