KR100750477B1 - Data communication method for real-time monitoring of embedded systems - Google Patents

Abstract

A method for communicating monitoring data in an embedded system in real-time is provided to debug CPU firmware of a target embedded system in real-time or monitor a fast operation state of the target embedded system in real-time without connecting to an address and data bus of a target CPU by transmitting a monitoring data packet to a real-time monitor from the executed target embedded system. If a user inputs a start signal through a keyboard, the real-time monitor starts monitoring data packet communication with the target embedded system by outputting a signal for starting monitoring data packet transmission in a position level. If a communication error is found based on a monitoring data packet during the packet communication, the real-time monitor displays a communication error message to a monitor screen and terminates the packet communication by outputting the start signal in a negative level. If a size of the communication data of fast sync serial communication set to the target embedded system is disagreed to the size of the fast sync serial communication set to the real-time monitor, the real-time monitor displays the communication error message and terminates the packet communication by outputting the start signal in the negative level.

Description

Real-time monitoring data communication method of embedded system {DATA COMMUNICATION METHOD FOR REAL-TIME MONITORING OF EMBEDDED SYSTEMS}

1 is a block diagram of a high speed real-time monitoring device of the embedded system according to the present invention.

2 is a structure of a monitoring data packet protocol according to the present invention.

       <Description of Symbols for Major Parts of Drawings>

10: target embedded system 20: real-time monitoring equipment

22: Monitor screen 24: Hard disk drive

26: keyboard

30: 8 bit monitoring data packet protocol

40: 16 bit monitoring data packet protocol

31,41: Packet start data 32,42: Block size data

33, 43: monitoring data block 34, 44: checksum

35,45: packet end data

The present invention relates to a real-time monitoring data communication method of an embedded system, and more particularly, a target embedded system and a real-time monitoring device by transmitting and receiving a monitoring data packet by a mutually defined protocol using a high-speed synchronous serial communication method, a target embedded system The present invention relates to a real-time monitoring data communication method of an embedded system that can debug an electronic circuit and CPU firmware of a real time or monitor a high-speed operating state in real time.

CPUs are embedded in embedded systems such as digital and electronic devices such as wired / wireless communication systems, network equipment, industrial automation equipment, medical electronics, office equipment, home appliances, audio / video equipment, automotive electronics, and aerospace electronics. Microcontrollers (DSPs) or Digital Signal Processors (DSPs), which are used as controllers, enable the operation of embedded systems by performing signal processing and control as well as high-speed operation of digital data. It is not only necessary for verifying and debugging hardware electronic circuits or CPU firmware, but also for periodically evaluating the performance and operation of an embedded system that is already installed and performing its own task.

However, with the addition of various functions of the embedded system and the need for high performance, the operation speed of the MCU / DSP is getting faster as the CPU manufacturing technology is developed. For example, MCUs / DSPs are operating at speeds of up to 100 MHz and hundreds of MHz.

In the conventional embedded system monitoring, the operation status of the target embedded system was examined by connecting to the address bus and data bus connected to the external pins of the target MCU / DSP. However, recently, a large-capacity flash memory is embedded in the MCU / DSP to address the bus. Not only do external pins connected to the data bus exist on the MCU / DSP, but the monitoring method becomes very difficult due to the high speed of the MCU / DSP.

On the other hand, monitoring method using RS-232C standard asynchronous communication provided by SCI or UART module, which is one of the external connection peripheral modules of MCU / DSP, without connecting to address bus and data bus, is monitored by monitoring equipment in target embedded system. Since the maximum data transfer rate is only about 100 kBPS, there are many problems in real time monitoring of high-performance embedded systems operating at high speed.

SUMMARY OF THE INVENTION The present invention has been made to solve such a conventional problem, and an object of the present invention is that a running target embedded system transmits a monitoring data packet in a protocol that is mutually defined with a real-time monitoring device using a high speed synchronous serial communication method. Real-time monitoring data communication method of the embedded system that can debug the CPU firmware of the target embedded system in real time or monitor the high speed execution status in real time without connecting to the address bus and data bus of the target CPU. To provide.

The real-time monitoring data communication method of the embedded system of the present invention to achieve this object is that the target embedded system 8-bit or 16-bit, 32-bit monitoring variables corresponding to the variables in the register or memory content or firmware of the CPU core Alternatively, if a monitoring data block is composed by separating 16-bit data elements and the monitoring data packet generated based on the monitoring data block is transmitted to the real-time monitoring device through a high speed synchronous serial communication method capable of a transmission rate of several tens of MBPS, The monitoring equipment extracts the monitoring variables by applying the input file in which the monitoring variables are defined to the received monitoring data packet, and displays the monitoring variables on the monitor screen as well as saving them in the hard disk drive. .

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a real-time monitoring device of the embedded system according to the present invention, the target embedded system 10 operates in the main form of the high-speed synchronous serial communication and the real-time monitoring equipment 20 in the vertical form of the high-speed synchronous serial communication In operation, when the user inputs a monitoring start signal through the keyboard 26, the real-time monitoring device 20 outputs the monitoring data packet transmission start signal 2 to a positive logic level and outputs it to the target embedded system 10, and the target. If the monitoring data packet transmission start signal (2) input after the execution of a specific embedded process is positive logic level, the embedded system 10 is based on the monitoring variables corresponding to the registers of the CPU core or the contents of the memory or variables in the firmware. Generates a monitoring data packet that is made up of digital The clock signal 4 and the digital data signal 6 are output to the real-time monitoring device 20, and the real-time monitoring device 20 inputs the digital clock signal 4 and the digital data signal 6 of the high speed synchronous serial communication method. ), The monitoring data packet is extracted, and the monitoring variable is displayed on the monitor screen 22 as a real-time graph, and the monitoring variable is stored in the hard disk drive 24. On the other hand, when the user inputs the monitoring end signal through the keyboard 26, the real-time monitoring equipment 20 makes the monitoring data packet transmission start signal (2) to the negative logic level to output to the target embedded system 10, the target embedded The system 10 only executes its own embedded process and does not generate the monitoring data packet if the input monitoring data packet transmission start signal 2 is negative logic level.

The target embedded system 10 operating as a main form of high-speed synchronous serial communication may use 8 bits or 16 bits as the communication data size. The monitoring data packet protocol for each case has a communication data size as shown in FIG. In case of 8-bit, the target embedded system 10 and the real-time monitoring device 20 communicate with the 8-bit monitoring data packet protocol 30 in which all components are 8-bit data, respectively, while the communication data size is 16-bit. The target embedded system 10 and the real-time monitoring device 20 communicate with the 16-bit monitoring data packet protocol 40 in which all components are 16-bit data, respectively.

First, the 8-bit monitoring data packet protocol 30 is composed of packet start data 31 and block size data 32, monitoring data block 33, checksum 34 and packet end data 35. The data 31 and the packet termination data 35 become 8-bit values mutually defined by the target embedded system 10 and the real-time monitoring device 20, and the block size data 32 forms the monitoring data block 33. Represents the number N of 8-bit data, the monitoring data block 33 consists of N 8-bit monitoring data elements DATA8 [0], .. DATA8 [N-1], and the checksum 34 is the block size. 8-bit data representing the arithmetic sum of all the monitoring data elements DATA8 [0], .., DATA8 [N-1] constituting the data 32 and the monitoring data block 33.

16-bit monitoring data packet protocol 40 is composed of packet start data 41 and block size data 42, monitoring data block 43, checksum 44 and packet end data 45. The data 41 and the packet termination data 45 are 16-bit values defined by the target embedded system 10 and the real-time monitoring device 20, and the block size data 42 forms the monitoring data block 43. Represents the number N of 16-bit data, the monitoring data block 43 consists of N 16-bit monitoring data elements DATA16 [0], .., DATA16 [N-1], and the checksum 44 is the block size. 16-bit data representing the arithmetic sum of all the monitoring data elements DATA16 [0], .., DATA16 [N-1] constituting the data 42 and the monitoring data block 43.

The target embedded system 10 and the real-time monitoring device 20 may communicate with the 8-bit monitoring data packet protocol 30 when the minimum embedded access unit of the target embedded system 10 CPU register is 8 bits. As shown in Table 1, 8-bit character variable or 8-bit unsigned / unsigned integer variable, 16-bit unsigned / unsigned integer variable, 32-bit unsigned / unsigned integer variable, and 32-bit IEEE-754 format floating-point real variable It is possible.

Variable form Number of bits Number of DATA8 Elements Variable type char 8 One 8-bit character int8 8 One 8-bit signed integer uint8 8 One 8-bit unsigned integer int16 16 2 16-bit signed integer uint16 16 2 16-bit unsigned integer int32 32 4 32-bit signed integer uint32 32 4 32-bit unsigned integer float 32 4 IEEE-754 floating point real number

In this case, in the monitoring data packet generation unit of the target embedded system 10 CPU firmware, the 8-bit character variable and the 8-bit unsigned / unsigned integer variable become the DATA8 element of the 8-bit monitoring data block 33, but are 16 bits. Unsigned and unsigned integer variables are separated into two DATA8 elements, 32-bit unsigned and integer variables are separated into four DATA8 elements, and 32-bit IEEE-754 format floating-point real variables are separated into four DATA8 elements. This constitutes an 8-bit monitoring data block 33.

On the other hand, when the target embedded system 10 and the real-time monitoring device 20 communicates with the 16-bit monitoring data packet protocol 40, as the monitoring variables, 16-bit unsigned and unsigned integer variable, 32-bit Unsigned integer variables and floating point real numbers in 32-bit IEEE-754 format are possible.

Variable form Number of bits Number of DATA16 Elements Variable type int16 16 One 16-bit signed integer uint16 16 One 16-bit unsigned integer int32 32 2 32-bit signed integer uint32 32 2 32-bit unsigned integer float 32 2 IEEE-754 floating point real number

In this case, in the monitoring data packet generation unit of the target embedded system 10 CPU firmware, the 16-bit unsigned integer variable becomes the DATA16 element of the 16-bit monitoring data block 43 as it is, but it is a 32-bit unsigned integer. The variable is divided into two DATA16 elements, and a 32-bit IEEE-754 floating point floating point variable is divided into two DATA16 elements to form a 16-bit monitoring data block 43.

On the other hand, the real-time monitoring device 20 is the 8-bit monitoring data packet received from the target embedded system 10 when the monitoring data packet protocol is set to 8 bits is a valid data packet without a communication error or invalid data generated a communication error Packet start data 31, block size data 32, monitoring data block 33 and checksum 34 from the monitoring data packet received on the basis of the 8-bit monitoring data packet protocol 30. ) And after the packet end data 35 is extracted, if the received packet start data 31 and the packet end data 35 do not coincide with the prescribed values, respectively, a corresponding communication error message is displayed on the monitor screen 22. Monitoring is terminated by outputting the monitoring data packet transmission start signal (2) to the negative logic level. If the packet start data 31 and the packet end data 35 coincide with the prescribed values, respectively, the next step is to calculate a checksum from the received block size data 32 and the monitoring data block 33, and then do this. If the checksums do not match each other compared with the received checksums 34, a communication error message is displayed on the monitor screen 22, and the monitoring data packet transmission start signal 2 is output at a negative logic level, so that the monitoring ends. Only when they match each other, it is determined that a valid monitoring data packet has been received.

In addition, even if the monitoring data packet protocol is set to 16 bits, the real-time monitoring device 20 determines whether the 16-bit monitoring data packet received from the target embedded system 10 is a valid data packet without a communication error or invalid data with a communication error. The packet start data 41, the block size data 42, the monitoring data block 43, and the checksum 44 are first determined from the received monitoring data packet based on the 16-bit monitoring data packet protocol 40. ) And after the packet end data 45 has been extracted, if the received packet start data 41 and the packet end data 45 do not coincide with the prescribed values, respectively, the corresponding communication error message is displayed on the monitor screen 22. Monitoring is terminated by outputting the monitoring data packet transmission start signal (2) to the negative logic level. When the received packet start data 41 and the packet end data 45 coincide with the prescribed values, respectively, the next step is to calculate a checksum from the received block size data 42 and the monitoring data block 43. If the checksums are not matched with each other by comparing them with the received checksums 44, a communication error message is displayed on the monitor screen 22, and the monitoring data packet transmission start signal 2 is output at a negative logic level, so that the monitoring ends. It is determined that a valid monitoring data packet has been received only when the checksums match each other.

Now, the real-time monitoring equipment 20 extracts the monitoring variable from the received valid monitoring data packet by using the input file in which the monitoring variable name, the variable type, and the monitoring data element number are defined, one monitoring variable in a row.

First, if the monitoring data packet protocol is 8-bit, the input file defines an 8-bit monitoring data block by defining <variable name>, <variable type>, and <DATA8 element number>, one monitoring variable per line, as shown in Table 3. Extracting the monitoring variable from (33), 8-bit character variable and 8-bit unsigned integer variable consist of one DATA8 element number and 16-bit unsigned integer variable consists of two DATA8 element numbers. The 32-bit unsigned integer variable and the 32-bit IEEE-754 floating point floating point variable are composed of four DATA8 element numbers. Each DATA8 element number represents a monitoring data block (33) in the target embedded system (10). ) Must be consistent with the specified DATA8 element number to properly extract the monitoring variable values.

In the case of two or four DATA8 element numbers, the leftmost DATA8 element number represents the most significant element, and the rightmost DATA8 element number represents the least significant element. Therefore, if the CPU core of the target embedded system 10 is a little-endian processor, the byte located at the highest memory address is the most significant element, so that it is the leftmost DATA8 element number, whereas the CPU of the target embedded system 10 is If the core is a big-endian processor, the byte located at the lowest memory address is the most significant element, so make it the leftmost DATA8 element number. For example, in Table 3, the variable var666 is a 32-bit signed integer variable and consists of four DATA8 element numbers 10,9,8,7, where the DATA8 element of monitoring data block 33 starting at 0 is the most valid. Element and DATA7 element is the lowest effective element.

        <Variable name> <variable type> <DATA8 element number>          var111 char 0 var222 int8 1 var333 uint8 2 var444 int16 4 3 var555 uint16 6 5 var666 int32 10 9 8 7 var777 uint32 14 13 12 11 var888 float 18 17 16 15

If the monitoring data packet protocol is 16-bit, the input file defines the <variable name>, <variable type>, and <DATA16 element number>, one monitoring variable per line, as shown in Table 4. Extracting the monitoring variable from (43), the 16-bit unsigned integer variable consists of one DATA16 element number, the 32-bit unsigned integer variable and the 32-bit floating point real number in 32-bit IEEE-754 format are 2 In the data 16 element number, each DATA 16 element number must match the DATA 16 element number determined when configuring the monitoring data block 43 in the target embedded system 10 to properly extract the monitoring variable value.

In the case of two DATA16 element numbers, the leftmost DATA16 element number represents the most significant element, and the rightmost DATA16 element number represents the least significant element. Therefore, if the CPU core of the target embedded system 10 is a little-endian processor, the 16-bit data located at the highest memory address is the highest valid element, so that it is the leftmost DATA16 element number, whereas the target embedded system 10 If the CPU core is a big-endian processor, 16-bit data located at the lowest memory address is the most significant element, so make it the leftmost DATA16 element number. For example, in Table 4, variable var555 is a floating-point floating point variable in 32-bit IEEE-754 format and consists of two DATA16 element numbers 7,6. The best valid element, and the No. 6 DATA16 element are the lowest effective element.

        <Variable name> <variable type> <DATA16 element number>          var111 int16 0 var222 uint16 1 var333 int32 3 2 var444 uint32 5 4 var555 float 7 6

Meanwhile, in defining the monitoring variables in the input file of the real-time monitoring device 20 as described above, all the monitoring variables transmitted by being included in the monitoring data blocks 33 and 43 by the target embedded system 10 are defined in the input file. It is not necessary to define only the variables to be monitored in the real-time monitoring equipment (20).

In addition, the input file also defines whether the monitoring data packet protocol is 8 bits or 16 bits. Therefore, the communication data size of the high speed synchronous serial communication set in the target embedded system 10 and the high speed synchronous serial set in the real time monitoring equipment 20 are defined. If the communication data size of the communication does not coincide with each other, the real-time monitoring device 20 displays the corresponding communication error message on the monitor screen 22 and monitors it after outputting the monitoring data packet transmission start signal 2 to a negative logic level. Will end.

As described above, according to the present invention, since the target embedded system and the real-time monitoring device transmit and receive the monitoring data packet through a mutually defined protocol, communication errors that may occur during high-speed synchronous serial communication can be prevented, and the target embedded system can achieve high speed synchronization Due to the very short transmission time because the monitoring data packet is transmitted in serial communication, the monitoring device can debug the electronics and CPU firmware of the target embedded system in real time or execute it at high speed without interrupting the unique process execution of the target embedded system. The effect can be monitored in real time.

If the target embedded system transmits the changed monitoring data packet by adding or deleting the monitoring variable to the monitoring data blocks 33 and 43 by modifying the firmware, the corresponding monitoring variable is further defined by modifying the input file of the real-time monitoring device. Or by deleting a defined monitoring variable, the monitoring of the target embedded system can be simply resumed according to the monitoring data packet protocol.

On the other hand, when using SPI (Serial Peripheral Interface) communication in the target embedded system, a maximum transmission speed of 20 MBPS is possible.If the CPU of the target embedded system is an 8-bit processor, only 8-bit SPI communication is normally supported. While embedded systems and real-time monitoring devices can send and receive monitoring data packets using the 8-bit monitoring data packet protocol, SPI communications if the target embedded system's CPU is a 16-bit or 32-bit processor that supports 16-bit SPI communications. By setting the communication data size of the module to 16 bits and communicating with the 16-bit monitoring data packet protocol, the transmission time of the monitoring data packet can be shortened.

Claims (1)

Real-time monitoring data of an embedded system that sends and receives monitoring data packets to and from the 8-bit or 16-bit protocol in which a target embedded system operating as a main form of high-speed synchronous serial communication and a real-time monitoring device operating in a sub-type of high-speed synchronous serial communication are mutually defined. In the communication method, The 8-bit monitoring data packet protocol 30 in which all components each consist of 8-bit data is a block representing the packet start data 31 and the number N of 8-bit data constituting the monitoring data block 33. The monitoring data block 33 consisting of size data 32, N 8-bit monitoring data elements DATA8 [0], ..., DATA8 [N-1], and the block size data 32 and monitoring data block. A checksum 34 representing an arithmetic sum of the N 8-bit monitoring data elements DATA8 [0], .., DATA8 [N-1] constituting (33), and packet termination data 35; The 16-bit monitoring data packet protocol 40 in which all components each consist of 16-bit data is a block representing the packet start data 41 and the number N of 16-bit data constituting the monitoring data block 43. The monitoring data block 43 consisting of size data 42, N 16 bit monitoring data elements DATA16 [0], .., DATA16 [N-1], and the block size data 42 and monitoring data block. A checksum 44 representing an arithmetic sum of the N 16-bit monitoring data elements DATA16 [0], .., DATA16 [N-1] constituting (43), and packet termination data 45; The 8-bit monitoring data packet generator of the CPU of the target embedded system 10 makes an 8-bit character variable and an 8-bit unsigned / unsigned integer variable as a DATA8 element, and converts the 16-bit unsigned / unsigned integer variable into two DATA8 elements. The 8-bit monitoring data block 33 by separating the 32-bit unsigned integer variable into four DATA8 elements, and the 32-bit IEEE-754 floating point floating point variable into four DATA8 elements. Generate; The 16-bit monitoring data packet generator of the CPU of the target embedded system 10 makes the 16-bit unsigned integer variable into the DATA16 element as it is, and separates the 32-bit unsigned integer variable into the two DATA16 elements. Generate the 16-bit monitoring data block 43 by dividing a floating-point real variable of bit IEEE-754 format into two DATA16 elements; The input file applied to the 8-bit monitoring data packet communication in the real-time monitoring device 20 defines <variable name>, <variable type> and <DATA8 element number>, one monitoring variable per line, and high speed synchronous serial communication. The communication data size of the scheme is defined as 8 bits; The input file applied to the 16-bit monitoring data packet communication in the real-time monitoring device 20 defines <variable name>, <variable type> and <DATA16 element number>, one monitoring variable per line, and high speed synchronous serial communication. The communication data size of the scheme is defined as 16 bits; The real-time monitoring device 20 outputs a monitoring data packet transmission start signal 2 to a positive logic level when the user inputs a monitoring start signal through the keyboard 26 to communicate with the target embedded system 10 and monitoring data packet. When the user inputs the monitoring end signal through the keyboard 26, the monitoring data packet transmission start signal 2 is output to the negative logic level to terminate the monitoring data packet communication with the target embedded system 10. and; The real-time monitoring device 20 detects a communication error based on the 8-bit monitoring data packet protocol 30 or the 16-bit monitoring data packet protocol 40 while executing the monitoring data packet communication with the target embedded system 10. If a corresponding communication error message is displayed on the monitor screen 22 and the monitoring data packet transmission start signal 2 is output at a negative logic level, the monitoring data packet communication is terminated, and the high speed set by the target embedded system 10 is terminated. If the communication data size of the synchronous serial communication and the communication data size of the high speed synchronous serial communication set in the real time monitoring device 20 do not coincide with each other, the real time monitoring device 20 displays a corresponding communication error message on the monitor screen 22. Display and monitoring data packet transmission start signal (2) is negative logic level Real-time monitoring of the data communication method output embedded systems, characterized by the end doeeojim monitoring data packet communication to a.

Images