CN112765018B - Instrument debugging system and method - Google Patents

Abstract

The invention provides an instrument debugging system and method. The system includes: an instrument business logic module, which is used to process the written instrument business logic code and build a simulation environment for PC-side compilation, debugging and running; a peripheral hardware device simulation module, which uses It is used to simulate the display of TFT/LED, and simulate the operation of buttons, storage devices, and communication; the shared memory module is used to provide shared memory for access by the peripheral hardware device simulation module and the instrument business logic module to realize data transmission. The solution can facilitate the debugging and testing of embedded system codes, reduce hardware costs, and improve the efficiency of instrument debugging and development.

Description

Instrument debugging system and method

technical field

The invention relates to the field of computers, in particular to an instrument debugging system and method.

Background technique

With the development of science and technology, all kinds of instruments and meters are constantly appearing. Instruments and meters have various functions and are widely used in scientific experiments, mechanical equipment, automobiles and other fields. Instruments and meters are generally used for testing and displaying specific data. Instruments and meters need to be debugged before they leave the factory or are used to ensure normal operation.

At present, the existing instrument debugging system is shown in Figure 1, and its development technology completely relies on hardware devices such as the actual instrument, debugger, CANoe tool, and software such as embedded IDE, and the support of the compilation environment. During large-scale development, it is necessary to prepare a lot of hardware, and also to take into account the compilation of the software development environment and the code programming on the development board, etc., the debugging efficiency is low, and the hardware cost is high.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide an instrument debugging system and method, so as to solve the problems of low debugging efficiency and high hardware cost of the existing instrument debugging system.

In a first aspect of the embodiments of the present invention, an instrument debugging system is provided, including:

The instrument business logic module is used to process the written instrument business logic code and build a simulation environment for compiling, debugging and running on the computer;

Among them, the instrument business logic module includes a common function library developed according to GDC and OpenGL interface specifications for business logic calls, replacing MCU registers and absolute addresses with global variables or static memory, simulating Task scheduling, interrupt triggering, timer, CAN and GPIO update, convert embedded platform UI image into PC platform image format through decompression algorithm;

The peripheral hardware device simulation module is used to simulate the display of TFT/LED, and simulate the operation of buttons, storage devices and communications;

The shared memory module is used to provide shared memory for the peripheral hardware device simulation module and the instrument business logic module to access to realize data transfer.

In a second aspect of the embodiments of the present invention, an instrument debugging method is provided, including:

Process the written instrument business logic code, and build a simulation environment for compiling, debugging and running on the computer;

Among them, common function libraries are developed according to GDC and OpenGL interface specifications for business logic calls, global variables or static memory are used to replace MCU registers and absolute addresses, and task scheduling, interrupt triggering, timers, CAN and GPIO updates are simulated, and decompression algorithms are used. Convert the embedded platform UI image to the PC platform image format;

Display simulation of TFT/LED and operation simulation of buttons, storage devices and communications;

Data transfer between simulated peripheral hardware devices and instrument business logic is performed through shared memory.

In a third aspect of the embodiments of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the computer The steps of the method described in the first aspect of the embodiments of the present invention are implemented in the program.

In a fourth aspect of the embodiments of the present invention, a computer-readable storage medium is provided, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program provided in the first aspect of the embodiments of the present invention is implemented. the steps of the method.

In the embodiment of the present invention, the debugging system realized by PC-side software replaces the microprocessor and peripheral hardware equipment required by the traditional debugging method, and simulates and debugs the business code of the embedded development project of the instrumentation. Based on the debugging system, the embedded development process of instrumentation can be continuously adjusted, which is convenient for code development and testing, so that the development and testing process of intelligent instrumentation does not need to rely on too many hardware devices, reducing hardware costs, improving development efficiency, and reducing product rework, and Simple and practical.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that are used in the description of the embodiments or the prior art. Obviously, the drawings described below are only some implementations of the present invention. For example, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

1 is a schematic structural diagram of an existing instrumentation debugging system provided by an embodiment of the present invention;

2 is a schematic structural diagram of an instrumentation debugging system provided by an embodiment of the present invention;

3 is another schematic structural diagram of an instrumentation debugging system provided by an embodiment of the present invention;

FIG. 4 is a schematic flowchart of an instrument debugging method according to an embodiment of the present invention.

Detailed ways

In order to make the purpose, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the following The described embodiments are only some, but not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present invention. The examples are only used to explain the present invention, not to limit the scope of the present invention.

The term "comprising" and other similar meaning expressions in the description or claims of the present invention and the above-mentioned drawings are intended to cover non-exclusive inclusion, such as a process, method or system, and device comprising a series of steps or units not limited to Listed steps or units.

Please refer to FIG. 2. FIG. 2 is a schematic structural diagram of an instrumentation debugging system provided by an embodiment of the present invention, including:

The instrument business logic module 210 is used to process the written instrument business logic code and build a simulation environment for compiling, debugging and running on the computer;

The instrument business code is written in the instrument business logic module, which can include APP, UI and basic software layers, etc., as well as the data display engine library. Through the business logic code, a simulation environment for code compilation, running and debugging actions can be constructed, and general code compilation, debugging and running.

The instrument business logic module includes a common function library developed according to GDC (Graphic display control, that is, graphic display control) and OpenGL interface specifications for business logic calls, replacing MCU registers and absolute addresses with global variables or static memory, simulating Task (task) scheduling, interrupt triggering, timer, CAN (control local area network) and GPIO (general purpose input and output port) update, and convert the embedded platform UI image into the PC platform image format through decompression algorithm;

Instrument display drivers are usually provided by static libraries. Take Sapphire and Amber series hardware as examples, develop common function libraries according to GDC and OpenGL interface specifications, and provide them for business logic calls; in the debugging system, use global variables or static memory instead of MCU Registers, absolute addresses, etc.; simulate Task scheduling, interrupt triggering, timers, etc.; develop common decompression algorithms (eg ETC2EAC, ETCRGB) to convert the UI image format of the embedded platform into the PC platform image format.

The peripheral hardware device simulation module 230 is used to simulate the display of TFT/LED, and simulate the operation of buttons, storage devices and communications;

Peripheral hardware equipment generally mainly includes three parts: display, key and communication. In this embodiment, the function debugging of the button program of the embedded device is realized by simulating the hardware device.

Specifically, the peripheral hardware device simulation module 220 includes:

The display simulation unit is used to store the pre-display data in the memory, specify the bitmap data through the predetermined function in the MFC bitmap processing basic class, and design the LED bitmap, load the bitmap resource based on the function in MFC, and use the Windows image device interface. Bitmap functions specify pixel blocks;

The button simulation unit is used to create a simulated button, correspond the button interface function name to the button name in the hardware library, and simulate the button processing logic based on the predetermined trigger event of the input device;

The communication simulation unit is used for setting the simulation signal input and output interface to correspond to the business logic code interface according to the communication protocol, so as to associate the simulation peripheral hardware device with the business logic code.

For TFT display, put the display data prepared by the business logic into the memory, and then use the SetBitmapBits function in the basic class CBitmap of MFC's bitmap processing to specify the bitmap data. For LED display, design an LED bitmap, use MFC's LoadBitmap to load the bitmap resource, and then use the Windows Graphics Device Interface (GDI) bitmap function BitBlt to specify the pixel bit block.

For the simulation of the button part, first create a simulated button. All the interface functions of the button have the same name as the hardware library. There are many ways to trigger the button. You can use the control logic design of reading a button on the keyboard as a button. You can use the mouse to click the buttons of the simulation display screen to carry out the logic design of the buttons.

For the simulation of the communication part, according to the corresponding communication protocol, set various simulation input and output interfaces for communication, which must correspond to the interfaces used by the business code, so that the simulation hardware device and the business code are connected.

The shared memory module 220 is used to provide a shared memory for the peripheral hardware device simulation module and the instrument business logic module to access, so as to realize data transfer.

Peripheral device emulation and business logic operation are two processes. The two share and transmit data through a common memory. For business needs, the memory data includes TFT display data area, CAN data area, buttons/LEDs and other data. The design of the two processes can make business logic debugging without affecting the real-time performance of peripheral device simulation. When a developer is debugging any process, the other process is running normally.

In one embodiment, as shown in FIG. 3, in the Visual Studio (IDE) environment, the system includes instrument business code and debugging part, and the instrument business code includes BSW (basic software layer), APP and UI (user interface) , and display engine libraries (including GDC, EGL, OpenGL, etc.).

Among them, the business code replaces MCU registers, absolute addresses, assembly code, etc. with global variables or static memory, and simulates Task scheduling, interrupt processing, Timer, CAN, and GPIO updates, etc., to realize UI code parsing and conversion to PC-side image format, through EGL and OpenGL implement graphics drawing, implement GDC Rendering simulation, and provide a common memory access interface.

For peripheral hardware device simulation, including TFT/LED display, S/W and I/O operations, EEPROM file read and write, CAN data access and Task schedule, etc., and provide a common memory access interface.

In addition, the debugging system also includes UI resource conversion tools and shared memory, which can be accessed by instrument business logic and external simulation hardware devices to realize data transfer between the two.

It should be noted that the main application environment of the system in this embodiment is Microsoft Visual Studio software, the central control is developed based on C language, and the display control is mainly developed by MFC programming. When using, put the business code and the debugging system in the same file, use VS to open the project of the debugging system, the business code will be automatically added to the project, run the entire project, and an interface similar to the hardware instrument will be generated , the corresponding functions can be realized by clicking the buttons on the interface, and the corresponding functions of the hardware instrument can be truly restored.

It should also be noted that the debugging system mainly provides a platform for quickly and conveniently compiling and debugging business logic codes. After using the debugging system, developers can quickly verify whether the code written by themselves conforms to the design logic, the analysis and processing of data becomes easier, and some low-level coding errors can also be avoided. For testers, the debugging system can quickly and comprehensively carry out various tests.

Screen test screenshot, under certain conditions, what screen should be displayed on the screen of the instrument, you can take a quick screenshot, and the picture can be used as the test basis; the screen coordinate test, when confirming the position of the text and picture on the display screen, you can also use the screenshot, combined with Computer tools, quickly analyze and compare the position of text and pictures; test the button control function, the button press function can be divided into switch button, confirm button, position button. Button test, the instrument is turned on and off, a certain function is turned on or off, the movement of the cursor on the display screen, the confirmation of entering a certain mode, etc., continuously operate the buttons set by the operating system, and display the corresponding screen according to the corresponding button operation to confirm whether the button function is normal; communication For functional testing, a large instrument will have many sensors to transmit various data, and the business code will process the transmitted data accordingly, display the corresponding screen, and directly test the communication processing results that can be confirmed by observing the screen. The signal affects the value of a variable in the business code, and it cannot be displayed on the screen whether a certain communication function is implemented. Run the code project, enter the debug mode, and interrupt the debugging to visually check the change of the value. It can be understood that, in addition to some of the above tests, other tests can be tested by using a method similar to the above.

It should be understood that for development and testing in traditional hardware environments, the debugging system can greatly improve the efficiency of development and testing, as follows:

In the traditional hardware debugging scheme, in the development stage, the development board is used for debugging, and hardware must be prepared for each debugging, including power supply, development board, debugger, CAN communication tool, etc. At the same time, it is necessary to use Softune or other embedded IDE, and the effect of the corresponding implementation of the function cannot be verified immediately. Before debugging, the Program must be downloaded to the development board and connected to the actual machine for debugging. Due to the limited number of breakpoints, the inconvenience of stack/memory confirmation, the slow retrieval speed, the inability to quickly jump to the function definition, the disconnection of the Debugger, etc. Debugging efficiency is very low. At the same time, the resource file must be downloaded to Flash, which is time-consuming; every time the image is changed, the image resource must be downloaded again, and the download takes about two hours. It may also occur that the download fails or cannot be downloaded due to poor hardware device contact. When the development board is changed, debugging and verification can only be carried out after the hardware is changed; the hardware standard should be equipped with: 1 set of test works of more than 50,000 yuan, 1 set of debuggers of thousands to tens of thousands of yuan, and 1 set of thousands of yuan to tens of thousands of yuan Million CAN Bus Debug tool.

In the traditional hardware debugging solution, the development board is used for testing during the testing phase. Under the combined test (CT), the real machine test, in the case where there is no need to interrupt the test, as long as the development board is programmed and the resources are downloaded, start the development board, and test some operation procedures and the like, but sometimes it is necessary to use special Tools, such as rulers, etc., the subtleties of the picture are unrecognizable, tools are required, and data analysis needs to be recorded. It is difficult to take into account the development board and the code when it is necessary to interrupt the debug scene or the communication test scene, and after modifying the code, it takes 10 to 20 minutes to reprogram the development board, which is very difficult to test. Under the system test (ST), when the system test is implemented, it is necessary to record the results and keep them as the results of the test. Taking the TFT display results as an example, the development board cannot automatically record the TFT display results of the development board, and requires the help of photography tools. Since the actual development board screen is seriously affected by light, the tester must adjust various angles and light to get a picture. A clearer picture is very inefficient. Like other tests, you must use some tools to perform various complex operations, and the test efficiency is low.

The debugging system provided in this embodiment only needs one PC and one integrated development environment (Visual Studio) for debugging. Based on the Visual Studio compilation environment, the compilation is fast, and the corresponding implementation effects of Error, Warning and verification functions can be quickly detected, which is convenient for Debug analysis of code logic and functional bugs. Before Debugging, you can do Debug only on the PC side without downloading the Program. There is no limit to the number of breakpoints, stack/memory confirmation is convenient, retrieval speed is fast, and you can quickly jump to function definitions, etc., and the debugging efficiency is high. Image display verification, without downloading resources to Flash. Impact of development board changes: Just change the debugging system code without affecting the progress of software development. When the debugging system is introduced in the development and testing stage, more than half of the hardware will not be needed, the utilization rate of the owned hardware equipment will be greatly reduced, and the hardware damage rate will be reduced.

The debugging system is used for testing. Under the combined test (CT), because the CT has a large workload and depends on the actual machine, using the debugging system instead of the actual machine to implement the CT can reduce the dependence on external hardware input and configuration, and make the instrument The input of test data outside the system is more convenient, which improves the confirmation efficiency of Domain integration test output. Under the system test (ST), when implementing the system test, if you need to store the TFT display results, you can use the image clipping function of the debugging system to save the TFT display in bmp format. It can not only be used in automated testing, but also can compare the bmp image and the original image to verify whether the position and color of each display element are consistent with the design.

4 is a schematic flowchart of a method for debugging an instrument according to an embodiment of the present invention, and the method includes:

S401. Process the written instrument business logic code, and build a simulation environment for compiling, debugging and running on the computer;

Among them, common function libraries are developed according to GDC and OpenGL interface specifications for business logic calls, global variables or static memory are used to replace MCU registers and absolute addresses, and task scheduling, interrupt triggering, timers, CAN and GPIO updates are simulated, and decompression algorithms are used. Convert the embedded platform UI image to the PC platform image format;

S402, perform display simulation on TFT/LED, and perform operation simulation on buttons, storage devices, and communications;

Specifically, the pre-display data is stored in the memory, the bitmap data specified by the predetermined function in the basic class is processed by the MFC bitmap, the LED bitmap is designed, the bitmap resource is loaded based on the function in MFC, and the bitmap of the Windows image device interface is used. The function specifies the pixel block;

Create a simulated button, correspond the button interface function name to the button name in the hardware library, and simulate the button processing logic based on the predetermined trigger event of the input device;

According to the communication protocol, the simulation signal input and output interface is set to correspond to the business logic code interface, so that the simulation peripheral hardware device is associated with the business logic code.

S403, performing data transfer between the simulated peripheral hardware device and the instrument business logic through the shared memory.

Wherein, the shared memory at least includes display data, CAN data, and key data.

It should be understood that the sequence numbers of the steps in the above embodiments do not imply the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

It can be understood by those of ordinary skill in the art that, in one embodiment, the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing The computer program implements steps S401 to S403 to realize software emulation debugging of instruments. In another embodiment, the computer program can also be stored in a computer-readable storage medium, and the storage medium includes, for example, ROM/RAM, magnetic disk, optical disk, and the like.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (4)

1. an instrumentation debugging system, is characterized in that, comprises: The instrument business logic module is used to process the written instrument business logic code and build a simulation environment for compiling, debugging and running on the computer; Among them, the instrument business logic module includes a common function library developed according to GDC and OpenGL interface specifications for business logic calls, replacing MCU registers and absolute addresses with global variables or static memory, simulating Task scheduling, interrupt triggering, timer, CAN and GPIO update, convert embedded platform UI image into PC platform image format through decompression algorithm; The peripheral hardware device simulation module is used to simulate the display of TFT/LED, and simulate the operation of buttons, storage devices and communications; Wherein, the peripheral hardware device simulation module includes: The display simulation unit is used to store the pre-display data in the memory, process the bitmap data specified by the predetermined function in the basic class through the MFC bitmap, and design the LED bitmap, load the bitmap resource based on the function in MFC, and use the Windows image device interface. The bitmap function of the specified pixel block; The button simulation unit is used to create a simulated button, correspond the button interface function name to the button name in the hardware library, and simulate the button processing logic based on the predetermined trigger event of the input device; The communication simulation unit is used to set the simulation signal input and output interface to correspond to the business logic code interface according to the communication protocol, so as to associate the simulation peripheral hardware device with the business logic code; The shared memory module is used to provide shared memory for the access of the peripheral hardware device simulation module and the instrument business logic module to realize data transfer; The shared memory at least includes display data, CAN data, and key data. 2. an instrumentation debugging method, is characterized in that, comprises: Process the written instrument business logic code, and build a simulation environment for compiling, debugging and running on the computer; Among them, common function libraries are developed according to GDC and OpenGL interface specifications for business logic calls, global variables or static memory are used to replace MCU registers and absolute addresses, and task scheduling, interrupt triggering, timers, CAN and GPIO updates are simulated, and decompression algorithms are used. Convert the embedded platform UI image to the PC platform image format; Display simulation of TFT/LED and operation simulation of buttons, storage devices and communications; Wherein, the display simulation of TFT/LED and the operation simulation of buttons, storage devices and communications include: Store the pre-display data in the memory, specify the bitmap data through the predetermined function in the basic class of MFC bitmap processing, and design the LED bitmap, load the bitmap resource based on the function in MFC, and use the bitmap function of the Windows image device interface to specify the pixel. piece; Create a simulated button, correspond the button interface function name to the button name in the hardware library, and simulate the button processing logic based on the predetermined trigger event of the input device; According to the communication protocol, set the simulation signal input and output interface to correspond to the business logic code interface, so as to associate the simulation peripheral hardware device with the business logic code; Data transfer between simulated peripheral hardware devices and instrument business logic through shared memory; The shared memory at least includes display data, CAN data, and key data. 3. An electronic device, comprising a processor, a memory, and a computer program stored in the memory and running on the processor, wherein the processor implements the computer program described in claim 2 when the processor executes the computer program The steps of the instrumentation debugging method. 4. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the instrument debugging method according to claim 2 are implemented.

Images