Servo system

Abstract

A servo system is electrically connected to a peripheral component. The servo system includes a system module, a management module, and a transmission interface. When the management module detects an abnormal operation event of the electrically connected peripheral component, an interrupt trigger signal is transmitted to the system module through a single corresponding transmission interface. When the system module receives the interrupt trigger signal, it switches to the system interrupt mode and sends an inquiry signal to the management module through the transmission interface in a polling manner, and searches for the corresponding service type according to the error code returned by the management module that detected the interrupt event, thereby greatly reducing the physical circuit for the system module to detect abnormal operation events.

Description

Technical Field

[0001] The present invention relates to a system for electronic digital data processing, and more particularly to a servo system that deals with interruptions caused by abnormal operating states. Background Art

[0002] Refer to Figure 1 , the existing servo system includes a system chip 7, a plurality of management modules 8, and a plurality of peripheral components 1. The system chip is a central processing unit 71, and a platform path controller 72 electrically connected to the central processing unit. Each management module 8 monitors the operating conditions of several of the peripheral components 1 respectively. When a fault event occurs in the peripheral component 1, for example, the corresponding management module 8 triggers a system management interrupt, and transmits a corresponding signal to the central processing unit 71 via the platform path controller 72. Then, the central processing unit 71 provides a corresponding service type.

[0003] However, in the existing architecture design, when a fault event occurs in each peripheral component 1, the corresponding management module 8 must trigger a system management interrupt via an independent physical line, such as a system management interrupt (SMI) line 9. That is to say, the number of physical lines connecting each management module 8 to the platform path controller 72 of the system chip 7 must be the same as the number of peripheral components 1 connected to the management module 8. And according to the number of interrupt types that the management module 8 also needs to trigger a system management interrupt according to its own needs, the same number of physical lines are connected to the platform path controller 72 of the system chip 7. For example: when the number of management modules 8 is M, the number of peripheral components 1 connected to each management module 8 is N, and the number of interrupt types that each management module 8 itself needs to trigger a system management interrupt is P, then the number of physical lines connecting all management modules to the platform path controller 72 will be as high as M×(N + P). Since each physical line will occupy at least one pin of the management module 8, in this way, the space inside the servo system where other components or lines can be configured will be limited, and the number of pins that the management module 8 can configure for other functions will also be limited. Therefore, there is a need for improvement. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a servo system that can improve the disadvantages of the prior art.

[0005] To solve the above technical problem, the servo system of the present invention is electrically connected to a peripheral component. The servo system includes a system module, a management module, and a transmission interface.

[0006] The system module executes a basic input / output system program, which records a look-up table related to multiple service types corresponding to multiple interrupt codes respectively, and these interrupt codes respectively correspond to multiple interrupt events.

[0007] The management module is electrically connected to the peripheral components.

[0008] The transmission interface is correspondingly electrically connected between the management module and the system module.

[0009] When the management module detects an interrupt event, the management module generates an interrupt trigger signal and a corresponding interrupt code according to the interrupt event, and transmits the interrupt trigger signal to the system module via the corresponding transmission interface.

[0010] The system module sends an inquiry signal to the management module according to the received interrupt trigger signal.

[0011] The management module transmits the interrupt code corresponding to the interrupt event to the system module.

[0012] The system module looks up and executes the corresponding service type from the look-up table according to the received interrupt code.

[0013] Compared with the prior art, when the management module detects an interrupt trigger signal in the present invention, the system module switches to the system interrupt mode and sends an inquiry signal to the management module in a polling manner via the transmission interface, and looks up the corresponding service type according to the error code returned by the management module that detects the interrupt event, thereby greatly reducing the physical lines for the system module to configure and detect abnormal operation events. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Other features and effects of the present invention will be clearly presented in the embodiments with reference to the drawings, wherein:

[0015] Figure 1 is a block diagram illustrating an existing servo system; and

[0016] Figure 2 is a block diagram illustrating an embodiment of the servo system of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0017] The main purpose of this proposal is a way to reduce the physical circuit of the system management interrupt (SMI) in the servo system. When the slave controller in the servo system triggers the system management interrupt due to different requirements, it is triggered through the same set of physical circuits for the management interrupt inside the servo system. Then, the servo system asks the slave controller about the type of service required through the communication interface. By triggering different service types through the same set of physical circuits, the physical circuit of the servo system management interrupt is reduced.

[0018] Refer to Figure 1 , an embodiment of the servo system of the present invention is electrically connected to a peripheral component 1. The servo system includes a system module 2, a management module 3, and a transmission interface 4. It should be noted that in this embodiment, N peripheral components, M management modules 3, and M transmission interfaces 4 will be used as examples below. However, the number of peripheral components, management modules, and transmission interfaces can be changed according to actual needs, and M is a positive integer.

[0019] The system module 2 executes a Basic Input Output System program (BIOS Image: Image of Basic Input Output System). The Basic Input Output System program records a look-up table related to multiple service types corresponding to multiple interrupt codes respectively. These interrupt codes respectively correspond to multiple interrupt events. It should be noted that, in this embodiment, the system module 2 specifically includes a Central Processing Unit (CPU) 21 and a Platform Controller Hub (PCH) 22. The system module 2 can be presented in the form of a System on Chip (SoC) integrated by the Central Processing Unit 21 and the Platform Controller Hub 22, or can be implemented by the Central Processing Unit 21 in combination with the Platform Controller Hub 22. In addition, it should be supplemented that, in this embodiment, the look-up table can be stored in a non-volatile memory connected to the Platform Controller Hub 22 together with the Basic Input Output System program. When the servo system is powered on, the Central Processing Unit 21 loads the Basic Input Output System program together with the look-up table existing in the Basic Input Output System program from the non-volatile memory to the execution memory connected to the Central Processing Unit 21 for the Central Processing Unit 21 to execute. In addition, to improve the convenience for users to modify and edit the look-up table, the look-up table can also be stored in the form of parameters of the Basic Input Output System program (stored in the same non-volatile memory as the Basic Input Output System program and loaded into the memory connected to the Central Processing Unit 21 together when the Central Processing Unit 21 executes the Basic Input Output System program), or stored in other storage devices connected to the Platform Controller Hub 22. When the Central Processing Unit 21 executes the Basic Input Output System program, it can directly read from the memory connected to itself (because the Basic Input Output System program has been loaded), or read the memory connected to itself through the Platform Controller Hub 22 to obtain the look-up table. And among the multiple interrupt codes in the look-up table, some interrupt codes can respectively correspond to different service types, some interrupt codes can correspond to the same service type, or each interrupt code can respectively correspond to different service types.

[0020] Each management module 3 is electrically connected to these peripheral components, where M≥1. Among them, each management module 3 is one of a Baseboard Management Controller (BMC) and a Complex Programmable Logic Device (CPLD).

[0021] Each transmission interface 4 is electrically connected between the corresponding management module 3 and the system module 2. Among them, each transmission interface 4 includes a first bus 41 and a second bus 42. When any one of these management modules 3 detects an interrupt event, it triggers and generates an interrupt trigger signal, and transmits the interrupt trigger signal to the system module 2 via the first bus 41. The system module 2 automatically generates and transmits an inquiry signal to the corresponding management module 3 via the corresponding second bus 42 according to the received interrupt trigger signal, that is, the management module 3 corresponding to the received interrupt trigger signal. Further explanation, the central processing unit 21 of the system module 2 receives the interrupt trigger signal through the platform path controller 22 to automatically generate the inquiry signal, and automatically transmits the inquiry signal to the management module 3 corresponding to the interrupt trigger signal through the platform path controller 22 and via the corresponding second bus 42 for the corresponding management module 3 to receive. In addition, in this embodiment, each first bus 41 is a line such as SMI, ADC or GPIO, etc., to electrically connect to a pin of one of SMI, ADC or GPIO of the platform path controller 22, so that the platform path controller 22 can detect the high / low level of the voltage of one of SMI, ADC or GPIO and selectively trigger an interrupt according to the detected voltage high / low level. And each second bus 42 is a bus with two-way communication functions such as Intelligent Platform Management Interface (IPMI), Inter-Integrated Circuit (I2C) bus, low pin count, etc. More specifically, when the specific implementation aspect of the management module 3 is a baseboard management controller, the first bus 41 electrically connected between the management module 3 and the system module 2 is an SMI line, and the form of the second bus 42 can be an intelligent platform management interface or an integrated circuit bus; when the specific implementation aspect of the management module 3 is a complex programmable logic device, the first bus 41 electrically connected between the management module 3 and the system module 2 is a GPIO line, and the form of the second bus 42 can be an intelligent platform management interface or a low pin count bus. In addition, the first bus 41 and the second bus 42 can also be arbitrarily combined according to actual needs.

[0022] When one of the management modules 3 detects an interruption event occurring in a peripherally connected component 1, the management module 3 is triggered to generate an interrupt trigger signal and an interrupt code corresponding to the interruption event according to the interruption event, and transmit the interrupt trigger signal to the system module 2 via a corresponding transmission interface 4. Specifically, the management module 3 transmits the interrupt trigger signal to the platform path controller 22 via the first bus 41, and the platform path controller 22 transmits the interrupt trigger signal to the central processing unit 21.

[0023] When the system module 2 receives the interrupt trigger signal transmitted by one of the management modules 3 (i.e., when the central processing unit 21 receives the interrupt trigger signal), it enters a corresponding system interrupt management mode (SMM: system management mode) by executing the basic input / output system program. In the corresponding system interrupt management mode, the system module 2 issues an inquiry signal according to the interrupt trigger signal, and transmits the inquiry signal to the management modules 3 corresponding to the received interrupt trigger signal via the transmission interfaces 4 corresponding to the received interrupt trigger signal.

[0024] When the management module 3 that issues the interrupt trigger signal receives the inquiry signal, the management module 3 transmits the interrupt code corresponding to the interruption event to the system module 2 via a corresponding transmission interface 4. It should be further noted that after the management module 3 that issues the interrupt trigger signal receives the inquiry signal, it transmits the interrupt code corresponding to the interruption event to the system module 2 via a corresponding second bus 42, that is, transmits the interrupt code corresponding to the interruption event to the platform path controller 22 via the corresponding second bus 42 and then transmits it from the platform path controller 22 to the central processing unit 21.

[0025] The system module 2 looks up the corresponding service type from the look-up table according to the received interrupt code, that is, when the central processing unit 21 receives the interrupt code from the platform path controller 22, it looks up the corresponding service type from the look-up table stored in the system module 2.

[0026] In the above embodiments, each management module 3 detects whether multiple peripheral components 1 have interrupt events respectively. When any one of them detects an interrupt event, it triggers the generation of the interrupt trigger signal and sends the interrupt trigger signal to the platform path controller 22 through its own single corresponding first bus 41, and transmits it to the central processing unit 21 through the platform path controller 22. When the central processing unit 21 receives the interrupt trigger signal, it generates a corresponding inquiry signal, and transmits the inquiry signal to the management module 3 corresponding to the received interrupt trigger signal through the second bus 42 of the platform path controller 22 corresponding to the received interrupt trigger signal. When the management module 3 that issues the interrupt trigger signal receives the inquiry signal, it transmits the interrupt code corresponding to the interrupt event to the central processing unit 21 through its own single corresponding second bus 42 and the platform path controller 22, so that the central processing unit 21 can look up and execute the service mechanism corresponding to the corresponding service type according to the received interrupt code. When the same management module then detects another interrupt event, it triggers the generation of another interrupt trigger signal and sends the another interrupt trigger signal to the platform path controller 22 through the same single corresponding first bus 41 of the same management module 3, and transmits it to the central processing unit 21 through the platform path controller 22. When the central processing unit 21 receives the another interrupt trigger signal, it generates a corresponding another inquiry signal, and transmits the another inquiry signal to the same management module 3 corresponding to the received interrupt trigger signal through the second bus 42 of the platform path controller 22 corresponding to the received another interrupt trigger signal. When the same management module that issues the another interrupt trigger signal receives the another inquiry signal, it transmits the another interrupt code corresponding to the another interrupt event to the central processing unit 21 through the same single corresponding second bus 42 of the same management module 3 and the platform path controller 22, so that the central processing unit 21 can look up and execute the service mechanism corresponding to the corresponding service type according to the received another interrupt code. Therefore, no matter how many different peripheral components 1 the same management module detects interrupt events from, or no matter how many different types of interrupt events the same management module has to trigger the central processing unit 21 to interrupt and provide services of corresponding different service types through the platform path controller, it only needs to communicate with the central processing unit through the same first bus 41 and the same second bus 42 of the same management module through the platform path controller, so as to reduce the number of physical lines for the management module to be configured to the platform path controller for the central processing unit 21 to receive interrupt events corresponding to different service types. Specifically, in this embodiment, even when the number of peripheral components electrically connected to each management module 3 is N = 100, since there are still only two physical lines electrically connecting each management module 3 to the system module 2. In another embodiment,When each management module 3 is designed to trigger an interrupt trigger signal corresponding to 100 different service requirements, there are still only two groups of buses for the physical lines electrically connected between each management module 3 and the system module 2, such as the aforementioned first and second buses 41 and 42, which is independent of the number of peripheral components electrically connected to each management module 3 and also independent of the number of types of service requirements according to which each management module 3 needs to trigger an interrupt trigger signal. Therefore, the number of physical lines connecting the system module 2 to all management modules 3 will only change according to the number of management modules designed to issue interrupt trigger signals. For example, if the number of management modules designed to issue interrupt trigger signals is M, then the number of physical lines related to system management interrupts between these management modules and the system module is 2×M. This number of lines is much smaller than that in the prior art where each management module needs to design one physical line related to system management interrupt for each different service type. That is to say, when there are M management modules in the prior art and each has N service type requirements, then the prior art needs to design N×M physical lines on the system module for the mechanism to execute system management interrupts. Therefore, implementing the technology of this case will greatly reduce the number of physical lines configured between the system module 2 and all management modules 3 for executing system management interrupts. That is to say, this embodiment can achieve simplified design, reduce the setting of lines related to the servo system, improve the compatibility between platforms, thereby shortening the development time and reducing costs, so it truly achieves the creative purpose of this invention.

[0027] The above is only a specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A servo system is electrically connected to a peripheral component, characterized in that, The servo system includes: A system module that executes a basic input / output system program to record a look-up table related to multiple service types corresponding to multiple interrupt codes, where the interrupt codes respectively correspond to multiple interrupt events; A management module, which is electrically connected to the peripheral components; And A transmission interface, which is correspondingly electrically connected between the management module and the system module. When the management module detects one of the interrupt events, the management module generates an interrupt trigger signal according to the interrupt event, and the interrupt code corresponding to the interrupt event, and transmits the interrupt trigger signal to the system module via the corresponding transmission interface. The system module sends an inquiry signal to the management module according to the received interrupt trigger signal. Among them, the transmission interface includes a first bus and a second bus. When the management module detects an interrupt event, it transmits the interrupt trigger signal to the system module via the first bus, and the system module sends the inquiry signal to the management module via the second bus. The management module transmits the interrupt code corresponding to the interrupt event to the system module. The system module looks up and executes the corresponding service type from the look-up table according to the received interrupt code.

2. The servo system according to claim 1, wherein, The management module is one of a baseboard management controller and a complex programmable logic device.

3. The servo system according to claim 1, characterized in that, The second bus is one of an intelligent platform management interface, an integrated circuit bus, and a low pin count bus.

4. The servo system according to claim 1, characterized in that, After receiving the inquiry signal, the management module that issues the interrupt trigger signal transmits the interrupt code corresponding to the interrupt event to the system module via the corresponding second bus.

5. The servo system according to claim 1, wherein, The system module includes a platform path controller electrically connected to the first bus and the second bus, and a central processing unit electrically connected to the platform path controller. The central processing unit receives the interrupt trigger signal through the platform path controller and transmits the inquiry signal through the platform path controller.

6. The servo system according to claim 5, characterized in that, The interrupt event detected by the management module occurs when the management module sends a request for executing a service from the central processing unit, and the management module transmits the interrupt trigger signal to the system module via the corresponding transmission interface.

7. The servo system according to claim 1, wherein When the system module receives the interrupt trigger signal, it executes the basic input / output system program to enter a corresponding system interrupt mode.

8. The servo system according to claim 1, characterized in that, The interrupt event detected by the management module occurs in the peripheral components electrically connected to the management module, and the management module transmits the interrupt trigger signal to the system module via the corresponding transmission interface.

Images