Software simulation test system, method, device and medium for target chip

Abstract

This application discloses a software simulation testing system, method, device, and medium for a target chip, relating to the field of simulation technology. The system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah. It includes: a console module for acquiring characters from input devices; a target chip driver and control module, including a complex driver program for the target chip under test, used to determine request instructions based on characters and send the instructions to the target chip via Cheetah; a data analysis module for acquiring data packets output by the target chip according to instructions via Beagle and converting the signal values ​​corresponding to the data packets into physical values; and a file system for reading and writing parameters during program execution via a first file and recording fault information during program execution via a second file. This application improves the testing efficiency of the target chip and saves testing time.

Description

Technical Field

[0001] This invention relates to the field of simulation technology, and in particular to a software simulation testing system, method, device and medium for a target chip. Background Technology

[0002] The forward-facing camera controller integrates a vision processing chip for environmental perception. This chip outputs information such as target lane lines to a microcontroller unit (MCU) for control calculations. Current development and testing processes for complex vision processing chip drivers are based on the underlying software development within the MCU. The MCU code is then integrated and flashed into the forward-facing camera controller. However, in the early stages of project development, only a prototype of the forward-facing camera controller is available. Developing new MCU software is time-consuming and often presents challenges in verifying the vision processing chip, as well as the timely testing of its complex driver logic within the MCU. Therefore, testing and debugging the vision processing chip's complex driver code through the MCU results in prolonged development time and low efficiency.

[0003] Therefore, improving the testing efficiency of vision processing chips and saving testing time is an urgent problem to be solved in this field. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a software simulation testing system, method, device, and medium for a target chip, which can improve the testing efficiency of the target chip and save testing time. The specific solution is as follows:

[0005] In a first aspect, this application discloses a software simulation testing system for a target chip. The software simulation testing system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. The software simulation testing system includes:

[0006] The console module is used to retrieve target characters from input devices;

[0007] The target chip driver and control module includes a complex driver program for the target chip under test, used to determine a target request instruction based on the target character, and send the target request instruction to the target chip through the Cheetah device;

[0008] The data analysis module is used to acquire the data packets output by the target chip according to the target request instruction through the Beagle device, and convert the data packets into corresponding physical values ​​so as to analyze the data packets based on the physical values;

[0009] The file system is used to read and write various parameters of the complex driver program of the target chip under test during operation through the first file, and to record fault information of the complex driver program of the target chip under test during operation through the second file.

[0010] Optionally, the target chip driver and control module is specifically used for:

[0011] The target program is determined based on the target character, and the target program is converted into a target request instruction. Then, the target request instruction is sent to the target chip through the Cheetah device.

[0012] Optionally, the software simulation testing system further includes:

[0013] The data playback module is used to simulate the data packets output by the target chip under different scenarios.

[0014] Optionally, the data playback module includes:

[0015] The data packet writing unit is used to pre-acquire data packets output by the target chip under different scenarios through the Beagle device, and write the data packets output by the target chip to the target file;

[0016] The target file reading unit is used to read the target file, package the read data packets, and input them into the target chip driver and control module to simulate the data packets output by the target chip under different scenarios.

[0017] Optionally, the console module is specifically used for:

[0018] The system checks whether there is input in the input device according to a preset period. If there is, it obtains the target character of the input.

[0019] Optionally, the file system includes:

[0020] The read / write function interface calling unit is used to call the read / write function interface of the second file when the complex driver of the target chip under test fails.

[0021] The fault information recording unit is used to record fault information of the complex driver program of the target chip under test during operation through the second file.

[0022] Optionally, the fault information recording unit is specifically used for:

[0023] The second file records the occurrence time, index ID, and fault status of fault events during the operation of the complex driver program of the target chip under test.

[0024] Secondly, this application discloses a software simulation testing method for a target chip, applied to a software simulation testing system. The software simulation testing system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. The software simulation testing method includes:

[0025] Obtain the target character from the input device;

[0026] The target request instruction is determined by the complex driver of the target chip under test based on the target character, and the target request instruction is sent to the target chip through the Cheetah device;

[0027] The Beagle device acquires the data packets output by the target chip according to the target request instruction, and converts the data packets into corresponding physical values ​​so as to analyze the data packets based on the physical values;

[0028] The first file reads and writes various parameters of the complex driver program of the target chip under test during operation, and the second file records the fault information of the complex driver program of the target chip under test during operation.

[0029] Thirdly, this application discloses an electronic device, including:

[0030] Memory, used to store computer programs;

[0031] A processor is used to execute the computer program to implement the aforementioned software simulation testing method for the target chip.

[0032] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned software simulation testing method for the target chip.

[0033] As can be seen, this application proposes a software simulation testing system for a target chip. The software simulation testing system is deployed on a computer terminal and communicates with the target chip via a Beagle device and a Cheetah device. The software simulation testing system includes: a console module for acquiring target characters from an input device; a target chip driver and control module, including a complex driver program for the target chip under test, for determining a target request instruction based on the target characters and sending the target request instruction to the target chip via the Cheetah device; a data analysis module for acquiring data packets output by the target chip according to the target request instruction via the Beagle device, parsing the data packets to obtain signal values, and then converting the signal values ​​into corresponding physical values; and a file system for reading and writing various parameters of the complex driver program for the target chip under test during operation via a first file, and for recording fault information of the complex driver program for the target chip under test during operation via a second file. In summary, this application ports the complex driver program of the target chip under test, which runs in the microcontroller unit, to a computer terminal for simulation testing. It uses Beagle and Cheetah devices to simulate the serial peripheral interface bus in the microcontroller unit, enabling communication between the complex driver program and the target chip. Furthermore, the software simulation testing system for the target chip in this application includes a file system. This file system includes a first file capable of reading and writing various parameters of the complex driver program during operation, and a second file capable of recording fault information during operation. This ensures that the parameters and fault information of the complex driver program during operation are accurately and promptly recorded. In other words, this application allows for rapid testing of the target chip's functionality using a computer terminal simulation testing system without relying on the microcontroller unit's basic software. Moreover, since this application does not require integration with the microcontroller unit software to generate compiled files for later flashing into the front-view camera controller for verification, it can continuously and rapidly test the complex driver program of the target chip during project development, accelerating the R&D progress, improving testing efficiency, saving time, and achieving continuous simulation verification. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0035] Figure 1This is a device connection diagram of a software simulation and testing system for a target chip disclosed in this application;

[0036] Figure 2 This is a schematic diagram of a software simulation testing system for a target chip disclosed in this application;

[0037] Figure 3 This is a schematic diagram of a first document disclosed in this application;

[0038] Figure 4 This is a schematic diagram of a second document disclosed in this application;

[0039] Figure 5 This is a device connection diagram of a software simulation and testing system for a target chip disclosed in this application;

[0040] Figure 6 This is a device connection diagram of a software simulation and testing system for an EyeQ chip disclosed in this application;

[0041] Figure 7 This is a flowchart of a software simulation testing method for a target chip disclosed in this application;

[0042] Figure 8 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0043] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0044] Testing and debugging the target chip's complex driver code using a microcontroller unit results in longer development time and lower efficiency.

[0045] Therefore, this application proposes a software simulation testing scheme for target chips, which can improve the testing efficiency of target chips and save testing time.

[0046] This application discloses a software simulation testing system for a target chip. See also... Figure 1 As shown, the software simulation testing system is deployed on a computer terminal and connected to a debugging board via a Beagle device and a Cheetah device. The other end of the debugging board is connected to the target chip. The Beagle device is used to read data packets sent by the target chip, and the Cheetah device is used to send target request commands. See also... Figure 2 As shown, the software simulation testing system includes:

[0047] Console module 11 is used to obtain target characters from input devices;

[0048] It is understood that the input device is such as a keyboard, and the target character is such as the character X, Y, etc. on the keyboard.

[0049] In this embodiment, the software simulation testing system pops up the console module 11 window during runtime. Further, the console module 11 polls the input device at a preset period, for example, 1ms, to detect whether there is key input. If so, it acquires the input target character. Different target characters represent different target request instructions to be executed in the software simulation testing system (i.e., the simulation software). For example, the character "X" represents calibration. Target request instructions also include, but are not limited to, power-on, power-off, etc.

[0050] It should be noted that the console module 11 is used to simulate the Dcm (Data Communication Module) of the AutoSAR (AUTOSAR Open System Architecture) component in the microcontroller unit. The Dcm module provides a general interface for diagnostic communication. External diagnostic tools communicate with the microcontroller unit and process diagnostic commands through the Dcm module. For example, an external diagnostic tool connects to the forward-facing camera controller and uses the 31 routine control services of UDS (Unified Diagnostic Services) to control the microcontroller unit to send a request to switch calibration modes to the target chip. In this embodiment, inputting "X" on the keyboard can also control the simulation software to send a calibration mode request to the target chip.

[0051] The target chip driver and control module 12 includes a complex driver program 121 for the target chip under test, which is used to determine the target request instruction based on the target character and send the target request instruction to the target chip through the Cheetah device.

[0052] It should be noted that in this embodiment, the complex driver program 121 of the target chip under test is ported to the simulation software under the computer terminal for operation. The serial peripheral interface (SPI) bus through which the complex driver program 121 of the target chip under test communicates with the microcontroller program is replaced with a Beagle / Cheetah device. The diagnostic communication function interface between the complex driver program 121 of the target chip under test and the microcontroller program is replaced with the console communication interface of the console module 11. The Flash read / write function interface between the complex driver program 121 of the target chip under test and the microcontroller program is replaced with the Excel file read / write function interface in the file system 14.

[0053] Furthermore, in this embodiment, the complex driver 121 of the target chip under test determines the target execution program based on the received target character, converts the target execution program into a corresponding target request instruction, and then sends the target request instruction to the target chip through the Cheetah device.

[0054] Data analysis module 13 is used to acquire data packets output by the target chip according to the target request instruction through the Beagle device, and convert the data packets into corresponding physical values ​​so as to analyze the data packets based on the physical values;

[0055] In this embodiment, after receiving the target request instruction, the target chip outputs a corresponding data packet according to the target request instruction. Further, the data analysis module 13 obtains the data packet output by the target chip according to the target request instruction through the Beagle device, parses the data packet to obtain a signal value, and then converts the signal value into a corresponding physical value. The physical value can help developers analyze the data.

[0056] Specifically, after the target chip starts running, it outputs data packets in 128-byte frames. In this embodiment, the data analysis module 13 obtains the data packets output by the target chip through the Beagle device and writes them frame by frame, line by line, into a CSV (comma-separated values, also known as character-separated values) file. The data analysis module reads the data packets in the CSV file line by line and parses the signal values ​​in the packets according to the communication matrix. At this time, the signal values ​​are unitless numerical values ​​and need to be converted by formulas to obtain specific physical values ​​(temperature, pressure, speed, etc.). The conversion formula can be obtained from the resolution value and offset value defined in the communication matrix.

[0057] The file system 14 is used to read and write various parameters of the complex driver program of the target chip under test during operation through the first file, and to record fault information of the complex driver program of the target chip under test during operation through the second file.

[0058] The file system 14 contains a first file and a second file, which can be Excel files. The first file is a parameter storage file used to read and write parameters during the operation of the complex driver 121 of the target chip under test. See [link to documentation]. Figure 3 As shown, the Excel spreadsheet in the first file is divided into three columns: the first column is the entry block name (NAME), the second column is the data length of the entry block (LENGTH), and the third column is the data content of the entry block (DATA). Different entry blocks are filled into the table according to the content of these three columns. After the simulation software starts, it reads the data corresponding to the row by indexing the entry name ID (i.e., the row number in the Excel spreadsheet), concatenates "0x" into a string to form hexadecimal data, and the complex driver program 121 of the target chip under test in the simulation software uses the read data to start the target chip. In addition, during the operation of the simulation software, the complex driver program 121 of the target chip under test uses the indexing entry name ID to parse the data that needs to be recorded in real time, remove "0x", and write it into the data content column of the corresponding row. It should be noted that the first file in the simulation software is used to simulate the Nvm (NVRAM Manager, non-volatile memory) module of the Autosar component in the microcontroller. The Nvm module is used to manage the storage of "non-volatile" data, that is, the data will not be lost after the system is powered off, and the data can still be read through the interface after power is restored. The Nvm module stores the data in flash in the form of blocks, while the first file stores the data in an Excel spreadsheet in the form of entry blocks.

[0059] The second file is a fault event log file. If a fault occurs during the operation of the complex driver program 121 of the target chip under test, the fault event ID can be written by calling the Excel file read / write function interface. See also Figure 4As shown, the Excel table in the second file is divided into three columns. The first column represents the occurrence time of the fault event (Time), the second column represents the index ID of the fault event (the specific meaning of the fault event can be obtained by looking up the index ID in a table), and the third column represents the fault status (Status) of the fault event. For example, fault status 0 means pass, fault status 1 means fail, fault status 2 means prepass, and fault status 3 means prefail. Records only occur when the fault event status changes. It should be noted that the second file is used to simulate the Dem (Diagnostic Event Manager) module of the Autosar component in the microcontroller unit. The Dem module is responsible for processing and storing fault error events and related data.

[0060] As can be seen, this application proposes a software simulation testing system for a target chip. The software simulation testing system is deployed on a computer terminal and communicates with the target chip via a Beagle device and a Cheetah device. The software simulation testing system includes: a console module for acquiring target characters from an input device; a target chip driver and control module, including a complex driver program for the target chip under test, for determining a target request instruction based on the target characters and sending the target request instruction to the target chip via the Cheetah device; a data analysis module for acquiring data packets output by the target chip according to the target request instruction via the Beagle device, parsing the data packets to obtain signal values, and then converting the signal values ​​into corresponding physical values; and a file system for reading and writing various parameters of the complex driver program for the target chip under test during operation via a first file, and for recording fault information of the complex driver program for the target chip under test during operation via a second file. In summary, this application ports the complex driver program of the target chip under test, which runs in the microcontroller unit, to a computer terminal for simulation testing. It uses Beagle and Cheetah devices to simulate the serial peripheral interface bus in the microcontroller unit, enabling communication between the complex driver program and the target chip. Furthermore, the software simulation testing system for the target chip in this application includes a file system. This file system includes a first file capable of reading and writing various parameters of the complex driver program during operation, and a second file capable of recording fault information during operation. This ensures that the parameters and fault information of the complex driver program during operation are accurately and promptly recorded. In other words, this application allows for rapid testing of the target chip's functionality using a computer terminal simulation testing system without relying on the microcontroller unit's basic software. Moreover, since this application does not require integration with the microcontroller unit software to generate compiled files for later flashing into the front-view camera controller for verification, it can continuously and rapidly test the complex driver program of the target chip during project development, accelerating the R&D progress, improving testing efficiency, saving time, and achieving continuous simulation verification.

[0061] This application discloses a specific software simulation testing system for a target chip. The system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. Compared to the previous embodiment, this embodiment further explains and optimizes the technical solution. See also... Figure 5 As shown, the software simulation testing system includes:

[0062] Console module 11 is used to obtain target characters from input devices;

[0063] The target chip driver and control module 12 includes a complex driver program 121 for the target chip under test, which is used to determine the target request instruction based on the target character and send the target request instruction to the target chip through the Cheetah device.

[0064] The data analysis module 13 is used to acquire the data packet output by the target chip according to the target request instruction through the Beagle device, parse the data packet to obtain the signal value, and then convert the signal value into the corresponding physical value.

[0065] The file system 14 is used to read and write various parameters of the complex driver program of the target chip under test during operation through the first file, and to record fault information of the complex driver program of the target chip under test during operation through the second file.

[0066] Data playback module 15: used to simulate the data packets output by the target chip under different scenarios.

[0067] In this embodiment, for certain complex scenarios that are difficult to reproduce, such as busy urban roads, densely populated residential areas and campuses, highways, or rural roads with few pedestrians, etc., to test the robustness of the algorithm, the data packets output by the target chip in this scenario are pre-recorded by the data packet writing unit in the data playback module 15. The output data packets are then acquired by a Beagle device and written frame by frame to the target file (i.e., a CSV file). During data playback, it is not necessary to connect to the target chip. The recorded CSV file is imported by the target file reading unit in the data playback module 15 and read line by line. The read data packets are then repackaged and input into the target chip driver module, thereby simulating the target chip input signals under different scenarios on the test bench.

[0068] Taking the EyeQ chip as an example, see Figure 6 As shown, the software simulation test system for the EyeQ chip includes a console module, a data playback module, a file system, a data analysis module, and a complex driver program for the EyeQ chip under test. Figure 6The third-party library functions in this document are the library functions of the Beagle and Cheetah devices. Software-in-the-loop refers to the simulation software and the software simulation test system for the EyeQ chip in this embodiment. Instructions refer to the target request instructions. Running parameters refer to the various parameters of the complex driver program of the EyeQ chip under test during operation. Error logs refer to fault information. In summary, the various modules in the simulation software of this application are used for some AUTOSAR components in the microcontroller unit. The Beagle and Cheetah devices simulate the SPI bus in the microcontroller unit, enabling communication between the simulation software on the computer terminal and the EyeQ chip.

[0069] This application discloses a software simulation testing method for a target chip, applied to a software simulation testing system. The software simulation testing system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. See [link to relevant documentation]. Figure 7 As shown, the software simulation testing method includes:

[0070] Step S11: Obtain the target character from the input device.

[0071] Step S12: The target request instruction is determined by the complex driver of the target chip under test based on the target character, and the target request instruction is sent to the target chip through the Cheetah device.

[0072] Step S13: Obtain the data packet output by the target chip according to the target request instruction through the Beagle device, and convert the data packet into the corresponding physical value so as to analyze the data packet based on the physical value.

[0073] Step S14: Read and write various parameters of the complex driver program of the target chip under test during operation through the first file, and record the fault information of the complex driver program of the target chip under test during operation through the second file.

[0074] In summary, this application ports the complex driver program of the target chip under test, which runs in the microcontroller unit, to a computer terminal for simulation testing. It uses Beagle and Cheetah devices to simulate the serial peripheral interface bus in the microcontroller unit, enabling communication between the complex driver program and the target chip. Furthermore, the software simulation testing system for the target chip in this application includes a file system. This file system includes a first file capable of reading and writing various parameters of the complex driver program during operation, and a second file capable of recording fault information during operation. This ensures that the parameters and fault information of the complex driver program during operation are accurately and promptly recorded. In other words, this application allows for rapid testing of the target chip's functionality using a computer terminal simulation testing system without relying on the microcontroller unit's basic software. Moreover, since this application does not require integration with the microcontroller unit software to generate compiled files for later flashing into the front-view camera controller for verification, it can continuously and rapidly test the complex driver program of the target chip during project development, accelerating the R&D progress, improving testing efficiency, saving time, and achieving continuous simulation verification.

[0075] Furthermore, embodiments of this application also provide an electronic device. Figure 8 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0076] Figure 8 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a display screen 23, an input / output interface 24, a communication interface 25, a power supply 26, and a communication bus 27. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the software simulation testing method for a target chip disclosed in any of the foregoing embodiments. Alternatively, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0077] In this embodiment, the power supply 26 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 25 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 24 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0078] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored thereon may include computer programs 221, and the storage method may be temporary storage or permanent storage. The computer programs 221 may include, in addition to computer programs capable of performing a software simulation testing method for a target chip executed by the electronic device 20 as disclosed in any of the foregoing embodiments, computer programs capable of performing other specific tasks.

[0079] Furthermore, embodiments of this application also disclose a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned software simulation testing method for a target chip.

[0080] For the specific steps of this method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0081] The various embodiments in this application are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. For the same or similar parts between the various embodiments, refer to each other. As for the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple, and relevant parts can be referred to in the method section.

[0082] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0083] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0084] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0085] The software simulation testing system, method, device, and storage medium for a target chip provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A software simulation and testing system for a target chip, characterized in that, The software simulation testing system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. The software simulation testing system includes: The console module is used to retrieve target characters from input devices; The target chip driver and control module includes a complex driver program for the target chip under test, used to determine a target request instruction based on the target character, and send the target request instruction to the target chip through the Cheetah device; The data analysis module is used to acquire the data packets output by the target chip according to the target request instruction through the Beagle device, and convert the data packets into corresponding physical values ​​so as to analyze the data packets based on the physical values; The file system is used to read and write various parameters of the complex driver program of the target chip under test during operation through the first file, and to record fault information of the complex driver program of the target chip under test during operation through the second file.

2. The software simulation testing system for the target chip according to claim 1, characterized in that, The target chip driver and control module is specifically used for: The target program is determined based on the target character, and the target program is converted into a target request instruction. Then, the target request instruction is sent to the target chip through the Cheetah device.

3. The software simulation testing system for the target chip according to claim 1, characterized in that, The software simulation testing system also includes: The data playback module is used to simulate the data packets output by the target chip under different scenarios.

4. The software simulation testing system for the target chip according to claim 3, characterized in that, The data playback module includes: The data packet writing unit is used to pre-acquire data packets output by the target chip under different scenarios through the Beagle device, and write the data packets output by the target chip to the target file; The target file reading unit is used to read the target file, package the read data packets, and input them into the target chip driver and control module to simulate the data packets output by the target chip under different scenarios.

5. The software simulation testing system for the target chip according to claim 1, characterized in that, The console module is specifically used for: The system checks whether there is input in the input device according to a preset period. If there is, it obtains the target character of the input.

6. The software simulation testing system for the target chip according to any one of claims 1 to 5, characterized in that, The file system includes: The read / write function interface calling unit is used to call the read / write function interface of the second file when the complex driver of the target chip under test fails. The fault information recording unit is used to record fault information of the complex driver program of the target chip under test during operation through the second file.

7. The software simulation testing system for the target chip according to claim 6, characterized in that, The fault information recording unit is specifically used for: The second file records the occurrence time, index ID, and fault status of fault events during the operation of the complex driver program of the target chip under test.

8. A software simulation testing method for a target chip, characterized in that, The software simulation testing system is deployed on a computer terminal and communicates with the target chip via Beagle and Cheetah devices. The software simulation testing method includes: Obtain the target character from the input device; The target request instruction is determined by the complex driver of the target chip under test based on the target character, and the target request instruction is sent to the target chip through the Cheetah device; The Beagle device acquires the data packets output by the target chip according to the target request instruction, and converts the data packets into corresponding physical values ​​so as to analyze the data packets based on the physical values; The first file reads and writes various parameters of the complex driver program of the target chip under test during operation, and the second file records the fault information of the complex driver program of the target chip under test during operation.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the software simulation testing method for the target chip as described in claim 8.

10. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein, when the computer programs are executed by a processor, they implement the software simulation testing method for the target chip as described in claim 8.

Images