WO2024055611A1 - 基于固件仿真的故障现场回溯方法、设备及可读存储介质 - Google Patents
基于固件仿真的故障现场回溯方法、设备及可读存储介质 Download PDFInfo
- Publication number
- WO2024055611A1 WO2024055611A1 PCT/CN2023/093077 CN2023093077W WO2024055611A1 WO 2024055611 A1 WO2024055611 A1 WO 2024055611A1 CN 2023093077 W CN2023093077 W CN 2023093077W WO 2024055611 A1 WO2024055611 A1 WO 2024055611A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- firmware
- traceback
- fault
- error signal
- data
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 230000001960 triggered effect Effects 0.000 claims abstract description 11
- 238000004088 simulation Methods 0.000 claims description 67
- 230000008569 process Effects 0.000 claims description 27
- 230000001419 dependent effect Effects 0.000 claims description 3
- 238000013024 troubleshooting Methods 0.000 description 8
- 238000001514 detection method Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/56—External testing equipment for static stores, e.g. automatic test equipment [ATE]; Interfaces therefor
- G11C29/56008—Error analysis, representation of errors
Definitions
- the present application relates to the field of firmware simulation technology, and in particular to a fault site traceback method, equipment and readable storage medium based on firmware simulation.
- SSD Solid State Disk
- firmware emulation that is, software is used to simulate the firmware environment to analyze and vulnerability check the firmware conveniently and efficiently.
- the error reported by the firmware simulation often has a lag. That is, when a problem occurs during the operation of the SSD, the actual error reporting time will be after the time when the problem occurs during the operation of the SSD. This lag will As a result, the staff cannot directly trace the firmware data information back to the time when the error occurred during the troubleshooting process, which increases the difficulty of troubleshooting and recovery.
- the main purpose of this application is to provide a fault site traceback method based on firmware simulation, aiming to solve the problem of how to trace firmware data information back to the time point before the error occurs.
- this application provides a fault site traceback method based on firmware simulation.
- the method includes:
- the flash memory traceback position, the firmware global variable and the host computer information are dependent variables when a fault occurs during the firmware simulation process.
- the firmware global variables and the host computer information are normal variables in the firmware simulation process.
- the traceback information is stored in a random access memory
- the step includes:
- the corresponding operation of the Nand command set is executed based on the traceback information, and the firmware is traced back to the fault occurrence site before the triggering time of the error signal according to the corresponding operation of the Nand command set.
- the Nand command set includes the Nand write command
- the error signal includes a data write error signal
- the corresponding operation of the Nand command set is executed based on the traceback information
- the Nand command set is executed based on the Nand write error signal.
- the corresponding operation of the command set is to trace back the firmware to the fault occurrence site before the triggering time of the error signal, including:
- the historical write data is written to the firmware, so that the firmware traces back to the fault occurrence site before the trigger time of the data write error signal.
- the Nand command set includes the Nand write command
- the error signal includes a data write error signal
- the corresponding operation of the Nand command set is executed based on the traceback information
- the Nand command set is executed based on the Nand write error signal.
- the corresponding operation of the command set is to trace back the firmware to the fault occurrence site before the triggering time of the error signal, including:
- the historical write data is written to the firmware, so that the firmware traces back to the fault occurrence site before the trigger time of the data write error signal.
- the Nand command set includes the Nand erase command
- the error signal includes a data erasure error signal
- the corresponding operation of the Nand command set is executed based on the traceback information
- the Nand command set is executed based on the Nand erase command.
- the corresponding operation of the command set is to trace back the firmware to the fault occurrence site before the triggering time of the error signal, including:
- the historical erasure data is re-erased in the firmware, so that the firmware traces back to the fault occurrence site before the triggering time of the data erasure error signal.
- the step of determining whether the execution time of the execution command is located after a preset lookback time point includes:
- the present application also provides a firmware simulation device, which includes: a memory, a processor, and a fault based on firmware simulation stored in the memory and capable of running on the processor.
- On-site traceback program when the firmware simulation-based fault on-site traceback program is executed by the processor, the steps of the firmware emulation-based fault on-site traceback method as described above are implemented.
- the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a fault site traceback program based on firmware simulation, and the fault site traceback program based on firmware simulation is processed When the controller is executed, the steps of implementing the fault scene traceback method based on firmware simulation as mentioned above are implemented.
- Embodiments of the present application provide a method, device, and readable storage medium for fault site traceback based on firmware simulation.
- the method includes: when receiving an execution command, determining whether the execution time of the execution command is within a preset traceback time. time point, the traceback time point is preset according to the preset cycle; when the execution time is at the traceback time point, the flash memory traceback position, firmware global variables and host computer information corresponding to the traceback time point are obtained; according to the At least one of the flash memory traceback position, the firmware global variable and the host computer information is used to determine the traceback information of the firmware, so that when an error signal is triggered, the firmware is traced back to the location where the error is reported according to the traceback information.
- the fault occurs before the triggering time of the signal.
- an error signal is received during the firmware simulation detection process, it can be traced back to the fault occurrence site before the trigger time of the error signal, thereby quickly troubleshooting the problem in the firmware during the firmware simulation, and reducing the troubleshooting during the firmware simulation process. Difficulty, solving the problem of how to trace the firmware data information back to the time when the error occurred.
- Figure 1 is a schematic diagram of the hardware architecture of a firmware emulation device involved in an embodiment of the present application
- Figure 2 is a schematic flow chart of the first embodiment of the fault site traceback method based on firmware simulation according to the present application
- Figure 3 is a schematic flowchart of the second embodiment of the fault site traceback method based on firmware simulation of the present application
- Figure 4 is a detailed flow chart of step S40 in the second embodiment of the fault site traceback method based on firmware simulation of the present application;
- FIG. 5 is another detailed flowchart of step S40 in the second embodiment of the fault site traceback method based on firmware simulation of the present application;
- FIG. 6 is another detailed flowchart of step S40 in the second embodiment of the fault site traceback method based on firmware simulation of the present application;
- This application sets the lookback time point in advance before the firmware executes the command.
- the flash memory traceback position firmware global variables and host computer information at the traceback time point are obtained.
- the flash memory traceback position firmware global variables and host computer information, At least one generates traceback information of the firmware to trace back the firmware to a fault occurrence site before the triggering time of the error signal according to the traceback information when the error signal is triggered.
- the hardware architecture of the firmware emulation device can be shown in Figure 1.
- the embodiments of this application relate to the hardware architecture of a firmware emulation device.
- the hardware architecture of the firmware emulation device includes: a processor 101, such as a CPU, a memory 102, and a communication bus 103.
- the communication bus 103 is used to realize connection communication between these components.
- the memory 102 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory.
- a memory 102 as a computer-readable storage medium may include a fault site traceback program based on firmware simulation; and the processor 101 may be used to call the fault site traceback program based on firmware simulation stored in the memory 102 , and do the following:
- the processor 101 may be configured to call a fault site traceback program based on firmware simulation stored in the memory 102 and perform the following operations:
- the corresponding operation of the Nand command set is executed based on the traceback information, and the firmware is traced back to the fault occurrence site before the triggering time of the error signal according to the corresponding operation of the Nand command set.
- the processor 101 may be configured to call a fault site traceback program based on firmware simulation stored in the memory 102 and perform the following operations:
- the historical write data is written to the firmware, so that the firmware traces back to the fault occurrence site before the trigger time of the data write error signal.
- the processor 101 may be configured to call a fault site traceback program based on firmware simulation stored in the memory 102 and perform the following operations:
- the traceback information determine the historical reading data of the firmware before the triggering time of the error signal
- the historical read data is re-read in the firmware, so that the firmware traces back to the fault occurrence site before the trigger time of the data read error signal.
- the processor 101 may be configured to call a fault site traceback program based on firmware simulation stored in the memory 102 and perform the following operations:
- the historical erasure data is re-erased in the firmware, so that the firmware traces back to the fault occurrence site before the triggering time of the data erasure error signal.
- the processor 101 may be configured to call a fault site traceback program based on firmware simulation stored in the memory 102 and perform the following operations:
- the fault site traceback method based on firmware simulation includes the following steps:
- Step S10 when receiving the execution command, determine whether the execution time of the execution command is at a preset lookback time point, and the lookback time point is preset according to a preset cycle;
- Execution commands can be sent by the host computer or by the user through the interactive interface during fault detection.
- each execution command has its corresponding execution time, and the execution time is the start time of the device processing the execution command.
- the device detects whether the execution time of the execution command corresponds to the timeline of the preset lookback time point in this embodiment.
- the lookback time point is before the device executes the firmware simulation process. According to the running cycle of the firmware, it is preset on the timeline during the process of the device processing the execution command. That is, a lookback time point is set every interval. This interval time is consistent with the firmware. associated with the runtime of the simulation. By looking back to a point in time, you can read the historical operation data performed by the device at that point in time.
- the backtracking time points in this application record the data recorded at the time nodes, and the changes between these data are recorded, rather than the data itself.
- some global variables in the firmware such as ST (System Table), BS (Boot Service), etc., are usually small in data volume (usually around a few MB). Since the data volume is small, even if the device's operating performance is limited, it is possible to set a backtracking time point at a shorter time interval (such as once per simulation cycle).
- the operation and maintenance personnel can more easily detect the actual error time point during the firmware operation process based on the backtracking time point, rather than the time point corresponding to the relatively delayed error signal, thus reducing the difficulty of troubleshooting and recovery.
- Step S20 when the execution time is at the traceback time point, obtain the flash memory traceback position, firmware global variables and host computer information corresponding to the traceback time point;
- the device when the execution time of the execution instruction is at the traceback time point, the device obtains the flash memory traceback position, firmware global variables and host computer information at the traceback time point.
- the flash memory traceback position is the corresponding moment of the device at the traceback time point.
- the running status of the data in the flash memory at this time is recorded, and an identifier is set, so that when traceback is needed, the data running status of the flash memory can be traced back through the identifier.
- the firmware global variables are the global variables in the program code that will change with the execution of the instructions when the firmware executes the instructions
- the host computer information is the host computer that sent the execution instructions.
- the computer's operating status data (generally analog) recorded when sending instructions.
- the flash memory traceback location, firmware global variables and host computer information are dependent variables that will change due to erroneous data during the process of firmware running.
- the flash memory traceback location, firmware global variables and host computer information corresponding to the point are the variables when the firmware is running normally.
- these three types of data reflect the changes in data between the flash memory, firmware and host computer during the firmware simulation process, rather than their data themselves. Therefore, the memory occupied by the traceback information obtained and stored will not Too large (usually between a few MB and several hundred MB).
- the execution time is not at the backtracking time point, the execution command at the next moment is received, and the step of determining whether the execution time of the execution command is at the preset backtracking time point is performed until the The execution time of the execution command is at the preset lookback time point.
- Step S30 Determine the traceback information of the firmware based on at least one of the flash memory traceback position, the firmware global variable and the host computer information, so as to trace back the firmware based on the traceback information when an error signal is triggered. Go to the fault occurrence site located before the triggering time of the error signal.
- the firmware is generated based on at least one of the flash memory traceback position, firmware global variables and host computer information.
- the causes are classified into three levels: upper level, middle level and bottom level.
- the upper layer corresponds to the host computer layer that sends execution commands
- the middle layer corresponds to the operating parameters of the firmware itself
- the bottom layer corresponds to the storage and exchange of general data in flash memory.
- a device when a device receives an execution command and processes it, it may misinterpret the task in the command when receiving the command, resulting in an error during the execution process, including the host computer information fed back by the device and the host computer itself. Therefore, based on the host computer information, it can be determined that an error occurred when receiving the execution command.
- the error link is in the process of command processing by the firmware.
- the flash memory in the device exchanges data while processing commands
- errors may occur in three situations: reading data, writing data, and erasing data.
- the flash memory traceback position it can be determined, The error occurred when the device was processing commands and there was an error in the underlying data interaction process.
- At least one of the above three examples may occur.
- the error link may appear at three different levels: the upper, middle and bottom layers, when performing firmware simulation, the entire process is detected during the running process of the firmware. Therefore, when the alarm signal is triggered, the alarm signal is triggered based on the traceback. When information is traced back, the firmware is traced back, not the host computer or flash memory.
- the traceback information is stored in a random access memory (Random Access Memory, RAM). Since the random access memory has characteristics such as read and write at any time and read and write speeds, the traceback information is stored in the random access memory. In this way, the firmware can quickly read the traceback information corresponding to the traceback time point when traceback is needed.
- the random access memory includes Nand Flash memory.
- the execution time of the execution command is at a preset lookback time point.
- the lookback time point is preset according to a preset period.
- the execution time When the time is at the traceback time point, the flash memory traceback position, firmware global variables and host computer information corresponding to the traceback time point are obtained, and then based on the flash memory traceback position, the firmware global variables and the host computer information At least one, determine the traceback information of the firmware in such a way that when the error signal is triggered, the firmware is traced back to the fault occurrence site before the trigger time of the error signal based on the traceback information, so that during the firmware simulation detection process When the error signal is received, it can be traced back to the fault occurrence site before the trigger time of the error signal, thereby quickly troubleshooting the problem in the firmware during firmware simulation, reducing the difficulty of troubleshooting during the firmware simulation process, and solving the problem of how to The firmware data is traced back to the time when the
- step S30 it includes:
- Step S40 Execute corresponding operations of the Nand command set based on the traceback information, and trace back the firmware to the fault occurrence site before the triggering time of the error signal based on the corresponding operations of the Nand command set.
- This embodiment provides a method of tracing firmware back to before a fault occurs based on Nand Flash commands (referred to as Nand commands).
- Nand commands Nand Flash commands
- the traceback information is stored in the Nand Flash memory, and the firmware is traced back through the Nand command set.
- the Nand Flash memory uses a nonlinear macrocell mode internally, which provides a cheap and effective solution for the realization of solid-state large-capacity memory. .
- Nand-flash memory has the advantages of large capacity and fast rewriting speed, and is suitable for storing large amounts of data.
- the Nand command set includes a Nand write command, a Nand read command and a Nand erase command.
- the Nand write command is used to write data to the firmware
- the Nand read command is used to read data
- the Nand erase command is used to erase data.
- the step S40 includes:
- Step S41 determine the historical written data of the firmware before the triggering time of the data writing error signal
- Step S42 Write the historical write data to the firmware according to the Nand write command, so that the firmware can trace back to the fault occurrence site before triggering the data write error signal.
- the firmware triggers the data writing error signal during operation, it means that the data writing fails at a certain moment. Therefore, it is determined based on the traceback information that the firmware triggers the data writing error signal at the time of the data writing error signal.
- the firmware triggers the data writing error signal at the time of the data writing error signal.
- step S40 also includes:
- Step S43 Based on the traceback information, determine the historical reading data of the firmware before the trigger time of the error signal;
- Step S44 According to the Nand read command, re-read the historical read data in the firmware, so that the firmware traces back to the fault occurrence site before triggering the data read error signal.
- the firmware if the firmware triggers the data reading error signal during operation, it means that the data reading failed at a certain moment. Therefore, it is determined based on the traceback information that the firmware triggers the data reading error signal when the data reading error signal is triggered. At a time point before the trigger time, obtain the read data corresponding to this time point as historical read data, and re-read the historical read data in the firmware through the Nand read command, so that the firmware can trace back to The fault occurs before triggering the data reading error signal.
- step S40 also includes:
- Step S45 Based on the traceback information, determine the historical erasure data of the firmware before the trigger time of the error signal;
- Step S46 reload the historical erasure data
- Step S47 according to the Nand erase command, re-erasure the historical read data in the firmware, so that the firmware can trace back to the occurrence of the fault before the trigger time of the data erase error signal. on site.
- the firmware if the firmware triggers a data erasure error signal during operation, it means that the data erasure failed at a certain moment (the erasure command may not be executed, or only part of the data may be erased). data), therefore, based on the traceback information, the firmware determines the time point before the trigger time of the data erasure error signal, and reloads the historical data of the erasure command executed at that time point as the historical erasure data, through the Nand erasure command , re-erasing the historical erasure data in the firmware, so that the firmware can trace back to the fault occurrence site corresponding to the trigger time before triggering the data erasure error signal.
- the actual problem occurrence time point during the running of the firmware is determined through the traceback information, and then the Nand command is used to allow the firmware to re-execute the data interaction operation corresponding to the time point, thereby allowing the firmware to trace back to the desired point.
- the fault occurrence site before the actual problem occurrence time is described, which reduces the difficulty of troubleshooting during the firmware simulation process and solves the problem of how to trace the firmware data information back to the time point when the error occurred.
- the computer program includes program instructions, and the computer program can be stored in a storage medium, and the storage medium is a computer-readable storage medium.
- the program instructions are executed by at least one processor in the firmware emulation device to implement the process steps of the embodiments of the above method.
- the present application also provides a computer-readable storage medium that stores a fault site traceback program based on firmware simulation.
- firmware simulation-based fault site traceback program is executed by a processor, the above implementation is implemented.
- the computer-readable storage medium may be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk, or any other computer-readable storage medium that can store program codes.
- ROM read-only memory
- the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
- the technical solution of the present application can be embodied in the form of a software product that is essentially or contributes to the existing technology.
- the computer software product is stored in a computer-readable storage medium as mentioned above (such as ROM/RAM, magnetic disk, optical disk), including several instructions to cause a terminal device (which can be a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present application.
Landscapes
- Debugging And Monitoring (AREA)
Abstract
本申请涉及固件仿真技术领域，尤其涉及一种基于固件仿真的故障现场回溯方法、设备及可读存储介质，其中，所述方法包括：在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
Description
本申请要求于2022年9月14日申请的、申请号为202211119321.4的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请涉及固件仿真技术领域，尤其涉及一种基于固件仿真的故障现场回溯方法、设备及可读存储介质。
固态硬盘（Solid State Disk，简称SSD），是用固态电子存储芯片阵列制成的硬盘，其凭借读写速度快的优势，广泛应用于各种电子领域。
在SSD检测的相关技术方案中，通常是通过固件仿真的方式来进行检测，即通过软件模拟固件环境来便捷高效的对固件进行分析和漏洞检查
然而，当SSD在运行过程中出现问题时，固件仿真的报错往往具有滞后性，即当SSD运行出现问题时，实际的报错时间点会在SSD运行出现问题的时间点之后，这种滞后性会导致工作人员在故障排查过程中无法直接将固件的数据信息回溯至报错出现的时间点之前，增加了故障排查恢复的难度。
上述内容仅用于辅助理解本申请的技术方案，并不代表承认上述内容是现有技术。
本申请的主要目的在于提供一种基于固件仿真的故障现场回溯方法，旨在解决如何将固件的数据信息回溯至报错出现的时间点之前的问题。
为实现上述目的，本申请提供的一种基于固件仿真的故障现场回溯方法，所述方法包括：
在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；
在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；
根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
在一实施例中，所述闪存回溯位置、所述固件全局变量和所述上位机信息为所述固件仿真过程中出现故障时的因变量，所述回溯时间点对应的所述闪存回溯位置、所述固件全局变量和所述上位机信息为所述固件仿真过程中的正常变量。
在一实施例中，所述回溯信息存储于随机存取存储器
在一实施例中，所述根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息的步骤之后，包括：
基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
在一实施例中，所述Nand命令集包括所述Nand写入命令，所述报错信号包括数据写入报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：
根据所述回溯信息，确定所述固件在所述数据写入报错信号的所述触发时间前的历史写入数据；
根据所述Nand写入命令，将所述历史写入数据写入至所述固件，以使所述固件回溯至位于所述数据写入报错信号之前触发时间之前的所述故障发生现场。
在一实施例中，所述Nand命令集包括所述Nand写入命令，所述报错信号包括数据写入报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：
根据所述回溯信息，确定所述固件在所述数据写入报错信号的所述触发时间前的历史写入数据；
根据所述Nand写入命令，将所述历史写入数据写入至所述固件，以使所述固件回溯至位于所述数据写入报错信号之前触发时间之前的所述故障发生现场。
在一实施例中，所述Nand命令集包括所述Nand擦除命令，所述报错信号包括数据擦除报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：
根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史擦除数据；
重载所述历史擦除数据；
根据所述Nand擦除命令，在所述固件中重新擦除所述历史擦除数据，以使所述固件回溯至位于所述数据擦除报错信号的触发时间之前的所述故障发生现场。
在一实施例中，所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤之后，包括：
若所述执行时间不位于所述回溯时间点，接收下一时刻的执行命令，并返回执行所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤。
此外，为实现上述目的，本申请还提供一种固件仿真设备，所述固件仿真设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的基于固件仿真的故障现场回溯程序，所述基于固件仿真的故障现场回溯程序被所述处理器执行时实现如上所述的基于固件仿真的故障现场回溯方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有基于固件仿真的故障现场回溯程序，所述基于固件仿真的故障现场回溯程序被处理器执行时实现如上所述的基于固件仿真的故障现场回溯方法的步骤。
本申请实施例提供一种基于固件仿真的故障现场回溯方法、设备及可读存储介质，其中，所述方法包括：在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。使得固件仿真检测过程中接收到报错信号时，能够回溯至位于报错信号的触发时间之前的故障发生现场，从而在固件仿真中快速排查固件中出现问题的地方，降低了固件仿真过程中的故障排查难度，解决了如何将固件的数据信息回溯至报错出现的时间点的问题。
图1为本申请实施例涉及的固件仿真设备的硬件架构示意图；
图2为本申请基于固件仿真的故障现场回溯方法的第一实施例的流程示意图；
图3为本申请基于固件仿真的故障现场回溯方法的第二实施例中流程示意图；
图4为本申请基于固件仿真的故障现场回溯方法的第二实施例中步骤S40的细化流程示意图；
图5为本申请基于固件仿真的故障现场回溯方法的第二实施例中步骤S40的另一细化流程示意图；
图6为本申请基于固件仿真的故障现场回溯方法的第二实施例中步骤S40的另一细化流程示意图；
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
本申请通过在固件执行命令之前，预先设置回溯时间点。在执行命令过程中，当命令的执行时间与回溯时间点对应时，获取回溯时间点下的闪存回溯位置、固件全局变量和上位机信息，根据闪存回溯位置、固件全局变量和上位机信息中的至少一个生成固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
为了更好的理解上述技术方案，下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
作为一种实现方案，固件仿真设备的硬件架构可以如图1所示。
本申请实施例方案涉及的是固件仿真设备的硬件架构，所述固件仿真设备的硬件架构包括：处理器101，例如CPU，存储器102，通信总线103。其中，通信总线103用于实现这些组件之间的连接通信。
存储器102可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。如图1所示，作为一种计算机可读存储介质的存储器102中可以包括基于固件仿真的故障现场回溯程序；而处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；
在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；
根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
在一实施例中，处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
在一实施例中，处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
根据所述回溯信息，确定所述固件在所述数据写入报错信号的所述触发时间前的历史写入数据；
根据所述Nand写入命令，将所述历史写入数据写入至所述固件，以使所述固件回溯至位于所述数据写入报错信号之前触发时间之前的所述故障发生现场。
在一实施例中，处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史读取数据；
根据所述Nand读取命令，在所述固件中重新读取所述历史读取数据，以使所述固件回溯至位于所述数据读取报错信号的触发时间之前的所述故障发生现场。
在一实施例中，处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史擦除数据；
重载所述历史擦除数据；
根据所述Nand擦除命令，在所述固件中重新擦除所述历史擦除数据，以使所述固件回溯至位于所述数据擦除报错信号的触发时间之前的所述故障发生现场。
在一实施例中，处理器101可以用于调用存储器102中存储的基于固件仿真的故障现场回溯程序，并执行以下操作：
若所述执行时间不位于所述回溯时间点，接收下一时刻的执行命令，并返回执行所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤。
基于上述基于固件仿真技术的固件仿真设备的硬件架构，提出本申请基于固件仿真的故障现场回溯方法的实施例。
参照图2，在第一实施例中，所述基于固件仿真的故障现场回溯方法包括以下步骤：
步骤S10，在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；
在本实施例中，在接收到执行命令时，确定执行命令的执行时间是否位于预设回溯时间点。执行命令可以由上位机发送，也可以由用户在故障检测过程中通过交互界面发送。固件仿真设备在处理执行命令时，每个执行命令都有其对应的执行时间，执行时间为设备处理执行命令的开始时间。在接收到执行命令时，设备检测该执行命令的执行时间，是否与本实施例中预设的回溯时间点的时间轴相对应。回溯时间点为设备执行固件仿真流程之前，按照固件的运行周期，预先设置在设备处理执行命令的过程中的时间轴上，即每间隔一段时间就设置一个回溯时间点，这段间隔时间与固件仿真的运行周期相关联。通过回溯时间点，可以读取到设备在该时间点是执行的历史操作数据。
需要说明的是，在一些传统技术方案中，会设置有可供查看历史操作数据的历史时间点，但与本实施例中的回溯时间点的不同之处在于，一般的历史时间点只能进行查看，而不能直接进行数据回溯。在另一些传统技术方案中，也会设本实施例有一些和本实施例功能类似的可回溯数据的时间节点，但与本方案中的回溯时间点的区别在于，本方案中回溯时间点的设置间隔较短，这是因为在传统技术方案中设置的可回溯时间节点，其所记录的回溯数据是较为庞大的（可能为几个G到几十个G），受限于设备的性能，可回溯时间节点之间的设置间隔不能太短（通常间隔为半小时及以上）。而本申请中的回溯时间点，在该时间节点上所对应记录的数据，记录这些数据之间的变化量，而非数据本身，例如，在固件仿真运行时，当固件运行出错时，其固件中的一些全局变量，例如，ST（System Table，系统表）、BS（Boot Service，启动服务）等，其数据量通常较小（一般在几MB左右）。由于其数据量较小，因此即便设备的运行性能有限，也能够在较短的时间间隔设置回溯时间点（如一个仿真周期设置一次）。并且，设置较短周期的时间回溯点，能够在固件仿真运行出错时，运维人员更容易根据回溯时间点检测到固件在运行过程中的实际出错的时间点，而非相对滞后的报错信号对应的时间点，降低了故障排查恢复的难度。
步骤S20，在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；
在本实施例中，当所述执行指令的执行时间位于所述回溯时间点时，设备获取在所述回溯时间点的闪存回溯位置、固件全局变量和上位机信息。
具体的，闪存回溯位置为设备在所述回溯时间点的对应时刻，记录下此时闪存中数据的运行状态，并设置一个标识，从而在需要回溯时，通过该标识将闪存的数据运行状态回溯到所述回溯时间点中对应的运行状态；固件全局变量为固件在执行指令时，其程序代码中会随着执行指令而发生改变的全局变量；上位机信息为发送所述执行指令的上位计算机在发送指令时记录的计算机的运行状态数据（一般为模拟量）。
需要说明的是，闪存回溯位置、固件全局变量和上位机信息，这些数据是在固件运行该过程中，当固件运行出现故障时，会由于错误数据而发生改变的因变量，并且，在回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息，则是固件正常运行时的变量。并且，这三种数据都反映在固件仿真过程中闪存、固件和上位机三者之间数据的变化量，而非它们的数据本身，因此，获取并存储的回溯信息所占用的内存并不会太大（通常为几MB到几百MB之间）。
在一实施例中，若执行时间不位于回溯时间点，则接收下一时刻的执行命令，并返回执行所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤，直至所述执行命令的执行时间位于预设回溯时间点。
步骤S30，根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
在本实施例中，在获取到回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息步骤之后，根据闪存回溯位置、固件全局变量和上位机信息中的至少一个，生成所述固件的回溯信息，由于固件运行中出错的原因较为复杂，在本实施例中将原因分类三个层级：上层、中层和底层。上层对应发送执行命令的上位机层，中层对应固件本身的运行参数；底层则是闪存中通用数据的存储和交换。
示例性地，当设备接收到的执行命令并处理时，可能在接收命令时错误解读了命令中的任务，导致在执行过程中出现报错，会出现设备反馈的上位机信息和上位机本身的信息不匹配的情况，因此，根据上位机信息，能够确定出，在接收执行命令时出现了错误。
示例性地，当设备在处理命令的过程中，若固件运行代码时出现了报错，则固件的全局变量，相较于正常运行时的变量会存在差异，因此，根据固件全局变量，能够确定出，出错环节是在固件处理命令的过程。
示例性地，当设备中的闪存在处理命令的过程中进行数据交换时，可能会在读取数据、写入数据以及擦除数据三种情况下出现错误，根据闪存回溯位置，能够确定出，出错环节是在设备处理命令的过程中，底层的数据交互过程出现了错误。
上述三种示例可以出现至少一种。
需要说明的是，虽然出错环节可能出现在上层、中层和底层三个不同的层级，但是在进行固件仿真的时候，整个流程都是在固件的运行过程中进行检测，因此在触发报警信号根据回溯信息进行回溯时，都是对固件进行回溯，而不是上位机或者闪存。
在一些实施方式中，回溯信息存储于随机存取存储器（Random Access Memory，RAM）中，由于随机存取存储器具有随时读写、读写速度块等特性，因此将回溯信息存储于随机存取存储器中，能够在需要进行回溯时，使固件快速读取到回溯时间点对应的回溯信息。在一些实施方式中，所述随机存取存储器包括Nand Flash存储器。
在本实施例提供的技术方案中，通过在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置，当所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息，然后根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的方式，使得固件仿真检测过程中接收到报错信号时，能够回溯至位于报错信号的触发时间之前的故障发生现场，从而在固件仿真中快速排查固件中出现问题的地方，降低了固件仿真过程中的故障排查难度，解决了如何将固件的数据信息回溯至报错出现的时间点的问题。
参照图3，在第二实施例中，基于第一实施例，所述步骤S30之后，包括：
步骤S40，基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
本实施例提供一种基于Nand Flash命令（简称为Nand命令），将固件回溯至故障发生前的方法。在本实施例中，回溯信息存储在Nand Flash存储器中，通过Nand命令集对固件进行回溯，Nand Flash存储器的内部采用非线性宏单元模式，为固态大容量内存的实现提供了廉价有效的解决方案。Nand-flash存储器具有容量较大，改写速度快等优点，适用于大量数据的存储。
在本实施例中，Nand命令集包括Nand写入命令、Nand读取命令和Nand擦除命令。Nand写入命令用于向固件中写入数据，Nand读取命令用于读取数据，Nand擦除命令用于擦除数据。通过回溯信息确定出固件运行过程中的实际问题发生时间点，然后通过Nand命令，让固件重新执行该时间点对应的数据交互操作，从而使固件回溯至所述实际问题发生时间点之前的故障发生现场。
其中，参照图4，所述步骤S40包括：
步骤S41，根据所述回溯信息，确定所述固件在所述数据写入报错信号的所述触发时间前的历史写入数据；
步骤S42，根据所述Nand写入命令，将所述历史写入数据写入至所述固件，以使所述固件回溯至触发所述数据写入报错信号之前的所述故障发生现场。
可选地，在本实施例中，若固件在运行过程中触发了数据写入报错信号，意味着在某个时刻数据写入失败，因此，根据回溯信息确定出固件在数据写入报错信号的触发时间前的时间点，获取该时间点对应的写入数据，作为历史写入数据；将所述历史写入数据，通过Nand写入命令，重新将该历史写入数据写入至固件中，以使固件回溯至触发所述数据写入报错信号之前的所述故障发生现场。
其中，参照图5，所述步骤S40还包括：
步骤S43，根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史读取数据；
步骤S44，根据所述Nand读取命令，在所述固件中重新读取所述历史读取数据，以使所述固件回溯至触发所述数据读取报错信号之前的所述故障发生现场。
可选地，在本实施例中，若固件在运行过程中触发了数据读取报错信号，则意味着在某个时刻数据读取失败，因此，根据回溯信息确定出固件在数据读取报错信号的所述触发时间前的时间点，获取该时间点对应的读取数据，作为历史读取数据，通过Nand读取命令，重新在固件中读取所述历史读取数据，以使固件回溯至触发所述数据读取报错信号之前的所述故障发生现场。
其中，参照图6，所述步骤S40还包括：
步骤S45，根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史擦除数据；
步骤S46，重载所述历史擦除数据；
步骤S47，根据所述Nand擦除命令，在所述固件中重新擦除所述历史读取数据，以使所述固件回溯至触发所述数据擦除报错信号的触发时间之前的所述故障发生现场。
可选地，在本实施例中，若固件在运行过程中触发了数据擦除报错信号，则意味着在某个时刻数据擦除失败（可能未执行擦除命令，也可能仅擦除了部分数据），因此，根据回溯信息确定出固件在数据擦除报错信号的触发时间前的时间点，重载该时间点被执行擦除命令的历史数据，作为历史擦除数据，通过Nand擦除命令，重新在固件中擦除所述历史擦除数据，以使固件回溯至触发所述数据擦除报错信号之前的触发时间对应的的故障发生现场。
在本实施例提供的技术方案中，通过回溯信息确定出固件运行过程中的实际问题发生时间点，然后通过Nand命令，让固件重新执行该时间点对应的数据交互操作，从而使固件回溯至所述实际问题发生时间点之前的故障发生现场，降低了固件仿真过程中的故障排查难度，解决了如何将固件的数据信息回溯至报错出现的时间点的问题。
此外，本领域普通技术人员可以理解的是实现上述实施例的方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成。该计算机程序包括程序指令，计算机程序可存储于一存储介质中，该存储介质为计算机可读存储介质。该程序指令被固件仿真设备中的至少一个处理器执行，以实现上述方法的实施例的流程步骤。
因此，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有基于固件仿真的故障现场回溯程序，所述基于固件仿真的故障现场回溯程序被处理器执行时实现如上实施例所述的基于固件仿真的故障现场回溯方法的各个步骤。
其中，所述计算机可读存储介质可以是U盘、移动硬盘、只读存储器（Read-Only Memory，ROM）、磁碟或者光盘等各种可以存储程序代码的计算机可读存储介质。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个计算机可读存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。
Claims (10)
- 一种基于固件仿真的故障现场回溯方法，其中，所述基于固件仿真的故障现场回溯方法包括：在接收到执行命令时，确定所述执行命令的执行时间是否位于预设回溯时间点，所述回溯时间点按照预设周期预先设置；在所述执行时间位于所述回溯时间点时，获取所述回溯时间点对应的闪存回溯位置、固件全局变量和上位机信息；根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息，以在触发报错信号时根据所述回溯信息将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
- 如权利要求1所述的基于固件仿真的故障现场回溯方法，其中，所述闪存回溯位置、所述固件全局变量和所述上位机信息为所述固件仿真过程中出现故障时的因变量，所述回溯时间点对应的所述闪存回溯位置、所述固件全局变量和所述上位机信息为所述固件仿真过程中的正常变量。
- 如权利要求1所述的基于固件仿真的故障现场回溯方法，其中，所述回溯信息存储于随机存取存储器。
- 如权利要求1所述的基于固件仿真的故障现场回溯方法，其中，所述根据所述闪存回溯位置、所述固件全局变量和所述上位机信息中的至少一个，确定所述固件的回溯信息的步骤之后，包括：基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场。
- 如权利要求4所述的基于固件仿真的故障现场回溯方法，其中，所述Nand命令集包括所述Nand写入命令，所述报错信号包括数据写入报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：根据所述回溯信息，确定所述固件在所述数据写入报错信号的所述触发时间前的历史写入数据；根据所述Nand写入命令，将所述历史写入数据写入至所述固件，以使所述固件回溯至位于所述数据写入报错信号之前触发时间之前的所述故障发生现场。
- 如权利要求4所述的基于固件仿真的故障现场回溯方法，其中，所述Nand命令集包括所述Nand读取命令，所述报错信号包括数据读取报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史读取数据；根据所述Nand读取命令，在所述固件中重新读取所述历史读取数据，以使所述固件回溯至位于所述数据读取报错信号的触发时间之前的所述故障发生现场。
- 如权利要求4所述的基于固件仿真的故障现场回溯方法，其中，所述Nand命令集包括所述Nand擦除命令，所述报错信号包括数据擦除报错信号，所述基于所述回溯信息执行Nand命令集的对应操作，并根据所述Nand命令集的对应操作将所述固件回溯至位于所述报错信号的触发时间之前的故障发生现场的步骤包括：根据所述回溯信息，确定所述固件在所述报错信号的触发时间前的历史擦除数据；重载所述历史擦除数据；根据所述Nand擦除命令，在所述固件中重新擦除所述历史擦除数据，以使所述固件回溯至位于所述数据擦除报错信号的触发时间之前的所述故障发生现场。
- 如权利要求1所述的基于固件仿真的故障现场回溯方法，其中，所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤之后，包括：若所述执行时间不位于所述回溯时间点，接收下一时刻的执行命令，并返回执行所述确定所述执行命令的执行时间是否位于预设回溯时间点的步骤。
- 一种固件仿真设备，其中，所述固件仿真设备包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的基于固件仿真的故障现场回溯程序，所述基于固件仿真的故障现场回溯程序被所述处理器执行时实现如权利要求1至8中任一项所述的基于固件仿真的故障现场回溯方法的步骤。
- 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有基于固件仿真的故障现场回溯程序，所述基于固件仿真的故障现场回溯程序被处理器执行时实现如权利要求1至8中任一项所述的基于固件仿真的故障现场回溯方法的步骤。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211119321.4 | 2022-09-14 | ||
| CN202211119321.4A CN115620799A (zh) | 2022-09-14 | 2022-09-14 | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024055611A1 true WO2024055611A1 (zh) | 2024-03-21 |
Family
ID=84858707
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/093077 WO2024055611A1 (zh) | 2022-09-14 | 2023-05-09 | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115620799A (zh) |
| WO (1) | WO2024055611A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115620799A (zh) * | 2022-09-14 | 2023-01-17 | 得一微电子股份有限公司 | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 |
| CN115781765B (zh) * | 2023-02-02 | 2023-07-25 | 科大讯飞股份有限公司 | 一种机器人的故障诊断方法、装置、存储介质及设备 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008191796A (ja) * | 2007-02-02 | 2008-08-21 | Mitsubishi Electric Corp | 解析装置及び解析方法及びプログラム |
| CN112015665A (zh) * | 2020-09-30 | 2020-12-01 | 北京百度网讯科技有限公司 | 测试验证的回溯方法、装置、电子设备及存储介质 |
| CN114153788A (zh) * | 2021-12-08 | 2022-03-08 | 浙江中控技术股份有限公司 | 一种执行器的可追溯控制方法、执行器和控制系统 |
| CN115620799A (zh) * | 2022-09-14 | 2023-01-17 | 得一微电子股份有限公司 | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 |
-
2022
- 2022-09-14 CN CN202211119321.4A patent/CN115620799A/zh active Pending
-
2023
- 2023-05-09 WO PCT/CN2023/093077 patent/WO2024055611A1/zh unknown
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008191796A (ja) * | 2007-02-02 | 2008-08-21 | Mitsubishi Electric Corp | 解析装置及び解析方法及びプログラム |
| CN112015665A (zh) * | 2020-09-30 | 2020-12-01 | 北京百度网讯科技有限公司 | 测试验证的回溯方法、装置、电子设备及存储介质 |
| CN114153788A (zh) * | 2021-12-08 | 2022-03-08 | 浙江中控技术股份有限公司 | 一种执行器的可追溯控制方法、执行器和控制系统 |
| CN115620799A (zh) * | 2022-09-14 | 2023-01-17 | 得一微电子股份有限公司 | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115620799A (zh) | 2023-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2024055611A1 (zh) | 基于固件仿真的故障现场回溯方法、设备及可读存储介质 | |
| US20080201661A1 (en) | Remote flash storage management | |
| US10621066B2 (en) | Automatic repair of scripts | |
| US7765526B2 (en) | Management of watchpoints in debuggers | |
| CN107608609B (zh) | 一种事件对象发送方法与装置 | |
| CN105573676A (zh) | 一种存储系统中验证数据一致性的方法 | |
| CN110716878A (zh) | 一种接口自动化测试方法、装置及系统 | |
| CN114924923A (zh) | 一种硬盘写入点正确性验证方法、系统、设备及介质 | |
| CN109189607B (zh) | 一种应用程序断点恢复的方法 | |
| CN113220319A (zh) | 一种数据更新方法、装置及车辆 | |
| WO2017076244A1 (zh) | 一种动态修复应用程序的方法、装置及相关系统 | |
| JP4902427B2 (ja) | 履歴情報管理方法及び履歴情報管理システム | |
| CN113470723B (zh) | 读重试测试方法、装置、可读存储介质及电子设备 | |
| CN114996955A (zh) | 一种云原生混沌工程实验的靶场环境构建方法及装置 | |
| CN113094107B (zh) | 数据保护方法、装置、设备及计算机存储介质 | |
| CN106408790B (zh) | 金融设备循环机芯日志信息写入方法及读取方法 | |
| KR102324950B1 (ko) | 취약점을 효율적으로 탐지할 수 있는 아키텍처로 구성된 힙 영역 메모리 관리 방법 및 그 장치 | |
| US9880926B1 (en) | Log structured reserved zone for a data storage device | |
| CN111522679A (zh) | 基于主机内存的ssd日志记录方法、系统和计算机设备 | |
| KR20080054592A (ko) | 내장형 시스템에서 고정위치 메모리 영역을 이용한 로그저장 방법 | |
| CN112162699A (zh) | 一种数据读写方法、装置、设备及计算机可读存储介质 | |
| CN110826114A (zh) | 基于ssd安全擦除后的用户数据测试方法和装置 | |
| CN116932275B (zh) | 一种数据刷洗控制方法、ddr控制器和片上系统 | |
| CN110187658B (zh) | 一种芯片处理方法、装置、芯片及电梯外呼板 | |
| CN114791868B (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: 23864350 Country of ref document: EP Kind code of ref document: A1 |