JP2010128987A - Simulation method and system of the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To secure the simulation accuracy without reducing the simulation efficiency by making respective simulators cooperate with each other by triggering by change of a timer caused by software itself when simulation is used for verifying the software. <P>SOLUTION: When a change occurs in a software timer of a CPU simulator itself, the occurrence of the change is reported to peripheral simulators via a process connecting section, then the simulation is stopped until the start of the next simulation is commanded. When the peripheral simulators receive the occurrence of the change of the software timer of the CPU simulator via the process connecting section, and then the simulation corresponding to the time of the change of the software timer is completed, the completion of the simulation is reported to the process connecting section. When the completion of the simulation is reported from all of the peripheral simulators to the process connecting section, the CPU simulator and the peripheral simulators are commanded to start the simulation. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a simulation method and a system thereof. In particular, the present invention relates to a simulation method and a system for causing a plurality of simulators operating as independent processes to verify the operation of software to operate in cooperation through an intermediate interface as a single system.

  The software is released after testing whether the software is performing an illegal operation and performing debugging. As a software operation verification method, there is a method of simulating on a computer a CPU on which software operates and a control target device of the software. A simulation system that executes such a simulation includes a simulator that simulates the function for each function of the control target device. Then, a plurality of simulators that simulate each function are operated in cooperation to operate as one simulation system.

  Patent Document 1 below shows an example of device control simulation in which a plurality of simulators as described above are operated in cooperation to operate as a single simulation system. This equipment control simulation includes a central processing unit (CPU) simulator (hereinafter referred to as a simulation debugger) that controls the apparatus. In addition, the system is configured by a simulator of a device model, a simulator of various device configurations, a simulator that supports a system that supports simulation (hereinafter simply referred to as a simulator), and the like. In a simulation of a simulation target (program execution processing by a CPU, operation of a virtual mechanical component, etc.), a cooperative operation method of each process when each process has virtual time is shown as an example.

FIG. 19 shows a schematic diagram of a cooperative operation mode between simulators of the simulation system. Ts in FIG. 19 is a reference synchronization time in virtual time on the simulation system. Each simulator stops the virtual time every time the processing of Ts time is executed, and after all the simulators finish executing the processing performed in Ts time, all the simulators start executing the processing of the next Ts time all at once.
JP2005-339029

  When the purpose of use of the simulation is verification of CPU software for controlling the apparatus (hereinafter simply referred to as apparatus control software), the following information is important in the simulation. That is, an input result to the simulator of the device control software and an output result from the software simulator. Here, the device control software generally controls the device using a timer created by the software itself. Therefore, in the conventional synchronization method between the simulators, the synchronization timing between the simulators is determined by using, as a trigger, the switching of the virtual time of the simulation system created by the process connection unit that operates the plurality of simulators in cooperation. For this reason, the reference timer (hereinafter referred to as software timer) for the verification target software to perform processing is irrelevant to the synchronization timing, and the following problems occur.

  An example of a problem that occurs in a conventional simulation system will be described.

  For example, it is assumed that the device control software operates based on a software timer that changes every 1 ms. In addition, the device to be controlled is assumed that the mechanical component B operates 500 ms after the device control software outputs the drive signal of the mechanical component A, and outputs the operation result of the mechanical component B to the device control software. . As an example, the apparatus control software is simulated by a conventional simulation system. In this example, the simulator of the device control software (hereinafter referred to as a CPU simulator) and the simulator of the device to be controlled (hereinafter referred to as a mechanism component simulator) are linked to each other to form one simulation system.

  20 and 21 are conceptual diagrams when this example is simulated by a conventional simulation system. FIG. 20 and FIG. 21 show that even if the behavior of the verification target software is exactly the same, an event for the CPU simulator controlled by the verification target software is transmitted at different times based on the software timer. Yes.

  In FIG. 20 and FIG. 21, the transmission timing of the simulation change to the CPU simulator differs depending on whether the output timing of the operation result of the mechanism component B of the mechanism component simulator is before or after the switching of the software timer value. . For example, A and B in FIG. 20 are before and after 500 ms, and A and B in FIG. 21 are before and after 501 ms.

  In FIG. 21, when the CPU simulator outputs a drive signal for the mechanical part A, the processing for one synchronization of the mechanical part simulator has already been completed. Therefore, the simulation process of the mechanical component simulator by the drive signal output starts from the next synchronization when the CPU simulator outputs the drive signal (in FIG. 21, it starts from the virtual time of 2 ms). This is also the cause of the difference in the transmission timing of events to the CPU simulator.

  As described above, in the conventional simulation system, the software timer value from when the CPU simulator outputs the driving signal of the mechanism component A to when the operation result of the mechanism component B is transmitted to the CPU simulator is 499 to 501 ms. It will vary between. For example, the transmission of the operation result of the mechanical component B in FIG. 20 is 500 ms in terms of the software timer value, and the transmission of the operation result of the mechanical component B in FIG. 21 is 501 ms in terms of the software timer value. Therefore, a highly accurate simulation cannot be performed by the cooperative operation method in which the simulators are synchronized at the virtual time timing of the simulation system.

  Here, in order to ensure the simulation accuracy, it is conceivable to shorten the synchronization time interval of each simulator. However, the shorter the synchronization interval, the greater the proportion of processing performed by the process connection unit for synchronization with the simulation processing performed by each simulator. For this reason, the overhead of synchronization processing performed per unit time of virtual time increases, and the time required for simulation execution also increases.

  As described above, in the conventional simulation system synchronization method, there is a problem that the simulation accuracy cannot be ensured without reducing the execution efficiency of the simulation.

  Therefore, according to the present invention, when a simulation is used for software verification in a simulation system in which a plurality of simulators operate in cooperation, a change in a timer created by the software itself is used as a trigger. Thereby, the simulation accuracy is ensured without degrading the simulation efficiency by causing the simulators to cooperate with each other by using the change of the software timer for the synchronization processing between the simulators.

  In order to solve this problem, a simulation method of the present invention includes a CPU simulator for simulating a CPU, at least one peripheral simulator for simulating a peripheral part to be controlled by the CPU, and each simulator. A simulation is performed while synchronizing the CPU simulator and at least one peripheral simulator using a process connection unit for realizing synchronization, and the CPU simulator changes a software timer included in the CPU simulator. When the occurrence of the change occurs, the process connection unit is notified of the occurrence of the change, and after the CPU simulator notifies the occurrence of the change, an instruction to start the next simulation to the CPU simulator is sent from the process connection unit. Simulate until The process connection unit receives a notification of the occurrence of the change of the software timer from the CPU simulator, and notifies the peripheral simulator of the occurrence of the change of the software timer, and the peripheral A step of receiving the occurrence of a change in the software timer of the CPU simulator from the process connection unit; and the peripheral simulator is configured to receive a change in the software timer after receiving the occurrence of the change in the software timer. When the simulation corresponding to time is completed, the process connection unit is notified of the end of the simulation, and when the process connection unit is notified of the end of the simulation from all of the peripheral simulators, the CPU simulator and the Around Characterized in that a step of instructing the start of simulation simulator.

  Further, the simulation system of the present invention provides a CPU simulator for simulating a CPU, at least one peripheral simulator for simulating a peripheral part to be controlled by the CPU, and synchronization between the simulators. A simulation system that executes a simulation while synchronizing the CPU simulator and at least one peripheral simulator, and the CPU simulator causes a change in a software timer of the CPU simulator, Means for notifying the process connection unit of the occurrence of a change, and means for stopping the simulation until the next instruction to start the simulation is sent from the process connection unit to the CPU simulator after notifying the occurrence of the change Means for receiving the occurrence of a change in the software timer of the CPU simulator from the process connection unit, and after receiving the occurrence of the change in the software timer, the peripheral simulator changes the software timer. And a means for notifying the end of the simulation to the process connection unit, and the process connection unit is notified of the occurrence of a change in the software timer from the CPU simulator. Means for notifying the peripheral simulator of the occurrence of a change in the software timer, and means for instructing the CPU simulator and the peripheral simulator to start the simulation when the end of the simulation is notified from all of the peripheral simulators. Characterized in that it.

  Further, the simulation system of the present invention simulates the operation of the mechanical device by a computer system, and is defined corresponding to the CPU terminal of the target device according to the CPU control program installed in the target device of the simulation. One or more CPU simulators that read information on the virtual input terminal and control the virtual output terminal to simulate the operation of the CPU of the target device, and a mechanism of a mechanical device including a plurality of parts including an actuator and a sensor Actuation of the actuator corresponding to the information defined as the actuator operation signal input from the outside, with the computer system defining the model, the interference and cooperation between the mechanism model and the signal connected to the actuator and the sensor And interference between mechanical parts and In accordance with the definition of the mobile phone, the operation of all related mechanism parts is reproduced as an image on the display device of the computer system, and the result of the operation of the mechanism model is converted into a predefined operation for the mechanism model defined as the sensor. In response to one or more mechanical component simulators that output information defined as sensor signals to the outside and the components of the simulation target device, operations of the components not supported by the CPU simulator and the mechanical component simulator And one or more simulators having a function of pseudo-reproducing an external action on the target device, a function of analyzing, displaying and saving a simulation result, and a function of a user interface for the simulation And the simulation in the simulation And a process connection unit that operates as a single device control simulation system. The process connection unit is configured to cooperate between simulators using a timer change generated by the CPU program to be verified as a trigger. And having a cooperative operation module for advancing virtual time with the change of the timer as one unit and performing synchronization processing between the various simulators based on the virtual time.

  According to the present invention, the virtual time of the simulation system can be managed based on the software timer, which is the virtual time when the verification target software executes processing, and the virtual times of a plurality of simulators can be matched. Therefore, the resources of the simulation system execution environment can be effectively used without unnecessarily reducing the synchronization interval, and the simulation accuracy can be ensured without reducing the simulation efficiency.

  In addition, according to the present invention, even when the software timer used when the verification target software performs processing during the execution of the simulation is changed, it is possible to switch the software timer serving as a trigger for cooperative operation between simulators. Therefore, simulation accuracy can be ensured without reducing the simulation efficiency.

  Further, according to the present invention, simulation accuracy can be ensured even when software that executes a plurality of processes based on different time criteria is verified.

  Hereinafter, the configuration and operation of the simulation system of the present invention will be described in detail with reference to the accompanying drawings.

[Embodiment 1]
Embodiment 1 of the present invention is a device control simulation system in which a plurality of simulators each operating as an independent process are connected to operate as one system. In such a system, when a device control simulation for the purpose of verifying the software for controlling the device is executed, a change in a timer (hereinafter referred to as a software timer) created by the verification target software itself is used as a trigger. As a result, the virtual times between the plurality of simulators are made to coincide with each other to synchronize the plurality of simulators. Note that the device control simulation of the simulation system according to the first embodiment is realized as a program executed by a computer system.

<Configuration Example of Computer System for Realizing Simulation of this Embodiment>
FIG. 2 is a diagram illustrating a schematic configuration example of a computer system that realizes the simulation according to the present embodiment. Note that the simulation of the first and second embodiments is realized by this computer system.

  The computer system 501 includes a main unit 502 that includes a central processing unit 502a (hereinafter referred to as a CPU), a main storage device 502b (hereinafter referred to as a RAM), a hard disk 502c, and the like. In addition, a display device 503 that performs screen display according to an instruction from the main body unit 502 is provided. In addition, a keyboard 504 for inputting user instructions and character information to the main body 502 and an instruction corresponding to an icon or the like displayed at that position by inputting an arbitrary position on the display device 503 are input. And a mouse 505.

  The hard disk 502c stores a program for realizing each function in the device control simulation, and various data for simulation including device information to be simulated. In the simulation, the program and various data are loaded into the RAM 502b, and the program is executed by the CPU 502a to simulate each device control.

  These basic operations of the computer system 501 are executed via an operating system (hereinafter referred to as OS) which is a basic program. Hereinafter, in this embodiment, the OS of the computer system 501 will be described as an example of an OS (registered trademark) of Microsoft Corporation. However, the present invention is not limited to the system on the OS.

<Functional Configuration Example of Simulation System of Embodiment 1>
FIG. 1 is a diagram illustrating a functional configuration example of a simulation system according to the first embodiment.

  As shown in FIG. 1, the simulation system includes a CPU simulator 101, a mechanical component simulator 102, and a general-purpose operation simulator 103 that are three simulators constituting the system. In addition, a simulator hub (hereinafter referred to as HUB) 104 which is a process connection unit for managing these simulators is provided. The CPU simulator 101, the mechanical component simulator 102, and the general-purpose operation simulator 103 are simulators that individually operate on the OS, and exist as independent processes.

  Next, the function of each component will be described.

(CPU simulator 101)
The CPU simulator 101 is a function that realizes the operation of a CPU to be simulated (hereinafter referred to as a target CPU) on the computer system 501. Here, the target CPU is not a CPU 502a mounted on the computer system 501 but a CPU that is mounted on a device to be simulated and controls the device.

  The CPU simulator 101 reads information on virtual input terminals defined corresponding to the terminals of the target CPU according to the control program of the target CPU (hereinafter referred to as target firmware), and controls the virtual output terminals.

  The CPU simulator 101 prepares a virtual address space corresponding to the address space of the target CPU. Here, the virtual address space is defined on the RAM 502b of the computer system 501 as an area corresponding to each area on the address space managed by the target CPU on a one-to-one basis. The real address value on the computer system 501 in the virtual address space is different from the address value handled by the target CPU. Then, the CPU simulator 101 accesses a corresponding area in the virtual address space in accordance with an access instruction to the address value in the address space of the target CPU by the target firmware. In the registers of the target CPU, corresponding areas are set on the virtual address space, and access to the registers is simulated by accessing the virtual address space.

  There are the following two methods for simulating the processing of the target firmware on the computer system 501. One is a method of executing the target firmware source program after converting it into the native language of the computer system 501. The other is a method of interpreting the execution instruction of the target CPU one by one and executing it while translating it into an execution instruction corresponding to the CPU of the computer system 501. This embodiment corresponds to any CPU simulation method.

  The CPU simulator 101 notifies the HUB 104 of the occurrence of its own event every time an event of its own simulator occurs. As an example in which the CPU simulator 101 notifies the occurrence of an event, there are events (memory access, interrupt occurrence, etc.) in the operation simulation of the target CPU. Further, the CPU simulator 101 suspends execution of the simulation process at the same time that the HUB 104 is notified of the event occurrence at the time of the event occurrence. And it stops until the execution of the simulation process is again instructed from the HUB 104, and when there is an instruction again, the simulation process is resumed.

(Mechanical component simulator 102)
The mechanical component simulator 102 simulates mechanical components of a mechanical device including a plurality of components including actuators and sensors, interference and cooperation between the mechanical components, and signals connected to the actuators and sensors on the computer. Then, the simulation result is displayed on the display device 503.

  For each mechanical component, information related to the simulation of the mechanical component, such as the shape, type, operation, interference between the mechanical components and cooperation conditions, is defined by the user. Furthermore, external signals are defined for sensors and actuators. The definition of these mechanical parts is performed by automatic setting from a CAD drawing, setting by operating a special mechanical part creation software by a user, or a combination of both. The types of mechanical parts defined as described above include those defined as simple objects and those defined as functions (motors, solenoids, clutches, sensors, gears, cams, rollers, etc.). Further, the mechanical parts include those that are not components of the apparatus to be simulated and are necessary for the operation simulation of the apparatus. For example, when the simulation target apparatus is a printer apparatus, paper in the printer apparatus is necessary for the operation simulation of the apparatus.

  In response to the actuator operation signal sent from the CPU simulator 101 via the HUB 104, the mechanical component simulator 102 simulates the mechanical component operation of the corresponding actuator. Further, the mechanical component connected to the actuator simulates the operation with the movement defined in association with the operation of the actuator. Regarding the mechanism that is operated by the operator's operation, the operation of the mechanical part by the operator is simulated by using the keyboard 504 and the mouse 505, and the target mechanical part is operated in a defined motion according to the simulated operation. Simulate. Furthermore, the operation of all related mechanical parts is simulated according to the definition of interference and cooperation between the mechanical parts.

  As a result of simulating the operation of these mechanical components, an event that changes the sensor signal in response to an external event occurs when various predefined external actions (hereinafter referred to as external events) occur in the mechanical component defined as a sensor. Is generated. The event of the sensor signal is notified to the HUB 104, and the simulation process is continued. The sensor signal is transmitted to the CPU simulator 101 via the HUB 104.

  Here, a display example of a mechanism model by the mechanism component simulator 102 is shown.

  FIG. 3 is a display example by a result display application of a mechanical component simulation of a printer device which is an example of a target device in the present embodiment.

  Reference numeral 601 denotes a paper feed cassette, 602 denotes print paper, 603 denotes a paper conveyance path, 604 denotes a sensor, 605 denotes a roller, 606 denotes a flapper, and 607 denotes a mechanical part model of a paper discharge tray. These mechanical part models refer to the simulation data of the operation of the mechanical part simulated by the mechanical part simulator 102 and the signal connected to the mechanical part. In this example, the mechanical component is moved in accordance with the change in the simulation data and displayed as a graphic on the display device 503.

(General motion simulator 103)
The general-purpose operation simulator 103 has a simulation function corresponding to various device configurations other than the CPU simulator 101 and the mechanical component simulator 102, and various action setting functions for virtual devices. An actual device to be simulated (in this example, a printer device) operates in response to an operator who uses the device or an external event connected to the device. The general-purpose operation simulator 103 provides a method of setting a pseudo-event other than the mechanical external event set by the mechanical component simulator 102 among these external events. It also has the function of analyzing, displaying and storing the simulation results.

  In the example of the printer device that is the target device in the present embodiment, mechanical external events include operation of a paper feed cassette, removal / attachment of consumable parts, and the like. On the other hand, other external events include reception of various commands from the host PC, operation of the operation panel by the operator, change in environmental temperature, and the like.

  The general-purpose operation simulator 103 provides a dedicated user interface (hereinafter referred to as UI) for setting these. Further, the general-purpose operation simulator 103 applies a predetermined external event to the CPU simulator 101 and the mechanical component simulator 102 via the HUB 104 according to the setting by the UI.

  Further, the general-purpose operation simulator 103 reads a macro instruction file describing a procedure for setting continuous external events and a file describing a series of external event data stored in the hard disk of the computer system 501 as necessary. Then, a series of external events are given to the CPU simulator 101 and the mechanical component simulator 102 via the HUB 104.

  Note that the general-purpose operation simulator 103 may be configured by a plurality of independent processes depending on functions.

  Hereinafter, the two simulators, the mechanical component simulator 102 and the general-purpose operation simulator 103, are collectively referred to as a peripheral simulator that simulates the peripheral portion to be controlled by the CPU. The peripheral simulator holds information related to simulation processing (hereinafter referred to as simulation processing information) executed by the simulator at the virtual time in the simulator. The simulation processing information is stored in a simulation processing information storage unit (not shown) in the order of execution of the simulation processing, and the simulation processing is executed in the order of storage in the simulation processing information storage unit.

(Simulator interfaces 107a, 107b, 107c)
The CPU simulator 101, the mechanical component simulator 102, and the general-purpose operation simulator 103 are connected to the HUB 104 via simulator interfaces 107a, 107b, and 107c that connect each simulator to the HUB 104. The simulator interfaces 107a, 107b, and 107c are well-known techniques and will not be described in detail. In the following description, the term “simulator” includes the CPU simulator 101, the mechanical component simulator 102, and the general-purpose operation simulator 103.

  Each simulator performs a process in accordance with a process execution instruction from a process execution instruction unit 113 (details will be described later). Further, when the peripheral simulator finishes executing the simulation process instructed by the process execution instructing unit 113, the peripheral simulator notifies the HUB 104 of the end of the process execution via the simulator interfaces 107b and 107c. Hereinafter, the notification of completion of execution of the instructed process is referred to as execution completion notification. Note that the end of execution of the simulation process will be described later.

(HUB104)
The HUB 104 includes a core unit 105 and interface modules 106a, 106b, and 106c. The interface modules 106a, 106b, and 106c have a function of mediating connection between the core unit 105 and each simulator. Note that the interface modules 106a, 106b, and 106c are well-known techniques, and thus detailed description thereof is omitted.

  The core unit 105 includes a cooperative operation definition information management module 109 and a cooperative operation module 112, and has a function of performing data transmission management between simulators, synchronization processing, and acquiring data transmission history. Note that the HUB 104 operates in a process independent of other applications such as the device model simulator 102 and the general-purpose operation simulator 103.

  The cooperative operation definition information management module 109 is a module that manages information for causing cooperative operation between simulators, and includes software timer information 110 and wiring definition information 111 between simulators. The software timer information 110 is information relating to a software timer serving as a cooperative operation trigger between simulators, and includes timer specifying information and timer interval information. Here, the timer specifying information corresponds to information specifying which of the variables handled by the target firmware is a software timer variable. The timer interval information corresponds to setting information indicating how many change intervals of the software timer value are equivalent to the virtual time.

  The wiring definition information 111 is various setting information related to data connecting simulators. The wiring definition information 111 is information that, for example, a motor drive signal in the device control simulation system is output from the CPU simulator 101 and input to the mechanical component simulator 102.

  The cooperative operation module 112 includes a process execution instruction unit 109 and an event transmission unit 114. The cooperative operation module 112 performs a synchronization process in which the change of the software timer is regarded as one unit of the virtual time, and the virtual time between the simulators is matched for each unit. In addition, a process for transmitting an event generated with the simulation operation of each simulator to the simulator according to the wiring definition information 111 is performed.

  The event transmission unit 114 determines whether an event that occurred during the simulation operation is a change in software timer value (hereinafter referred to as a timer event) or an event other than a timer event (hereinafter referred to as a data event). . Then, information specifying whether the event type is a timer event or a data event is added to the event, and the event is transmitted to the simulator.

  When the generated event is a change in the simulation data value corresponding to the software timer specified by the software timer information 110, the event transmission unit 114 determines that the generated event is a timer event. On the other hand, if the generated event is not a change in the simulation data value corresponding to the software timer, it is determined as a data event. Note that if the generated event is a timer event, the event transmission unit 114 transmits the event to all the peripheral simulators. On the other hand, when the generated event is a data event, the event transmission unit 114 transmits the generated event to the simulator according to the wiring definition information 111 set in advance. Each simulator performs a simulation operation related to the data event in response to the occurrence of the data event.

  The process execution instruction unit 113 issues a simulation process execution instruction (hereinafter referred to as a process execution instruction) to each simulator. The process execution instruction instructs the CPU simulator 101 to execute a process without specifying a virtual time for executing the simulation process. On the other hand, the peripheral simulator is instructed to execute a simulation process corresponding to the virtual time indicated by the timer interval information. The processing execution instruction is transmitted to each simulator via the simulator interfaces 107a, 107b, and 107c.

  When the event transmission unit 114 determines that the event generated in the simulation system is a data event generated in the CPU simulator, the process execution instruction unit 113 immediately instructs the CPU simulator 102 to start processing execution. When the event transmission unit 114 determines that an event that has occurred in the simulation system is a timer event, the following processing is performed. That is, when execution end notifications are received from all the peripheral simulators that are to be linked, the simulators are again instructed to execute the simulation processing at the next virtual time.

(External interface 108)
The external interface 108 is an interface for passing various information set by the operator 108 a for performing a cooperative operation by a plurality of simulators constituting the simulation system from the outside of the core unit 105 to the core unit 105.

<Setting example of software timer of this embodiment>
Here, the setting method of the software timer information 110 of the present embodiment will be described by taking as an example a case where a GUI (graphical user interface) is used as the external interface 108.

  FIG. 4 is a display example for setting software timer information displayed on the display device 503 by the GUI. The GUI includes a variable name setting field 401 and a timer interval setting field 402 that are handled by the target firmware corresponding to the software timer. The operator of the simulation system designates a setting target field with the mouse 505 and enters a number or a character from the keyboard 504 at the designated position. For the software timer variable name setting field 401, the software timer variable name handled by the software is entered. In the timer interval setting field 402, the number of changes in the software timer value corresponding to the virtual time on the simulator is entered as a number, and the number of virtual time units corresponding to the virtual time is set. .

  When the operator clicks the OK button 403 with the mouse 505 after the setting of the software timer variable name and the timer interval, the timer specifying information and the timer interval information are determined. The determined timer specifying information and timer interval information are stored in the cooperative operation definition information management unit 109 via the external interface 108. The stored information is software timer information 110. When the operation of the simulation system starts, the address of the target CPU where the software timer variable indicated by the variable name is arranged is acquired from the variable name of the software timer set as the timer specifying information of the software timer information 110. For obtaining the address of the software timer variable, debug information (not shown) of the CPU simulator 101 is used.

  In the above description, the GUI is used as the external interface 108. However, in addition to the GUI, there is a method in which the core unit 105 acquires software information using an external file interface or inter-process communication. When using an external file interface, a user prepares a file describing software information edited according to a predefined format, and acquires the software information through the external file interface. When using inter-process communication, an application for designating a simulation execution environment (not shown) connected to the core unit 105 by inter-process communication (a process different from the core unit) is used, and the user sets software timer information. There is also a method of setting 110.

<Example of Operation Procedure of Simulation System of Embodiment 1>
Hereinafter, operation procedure examples of the HUB 104, the CPU simulator 101, and the peripheral simulator during simulation will be described with reference to flowcharts.

(Operation procedure example of HUB104)
FIG. 5 is a flowchart showing an example of an operation procedure of the HUB 104 for causing a plurality of simulators constituting the simulation system to operate in cooperation.

  First, the process execution instructing unit 113 instructs the CPU simulator 101 to start simulation process execution via the interface module 106a (S801). Subsequently, the peripheral modules are instructed to execute simulation processing for a virtual time corresponding to one unit of the software timer via the interface modules 106b and 106c (S802). Note that one unit of virtual time of the software timer is a virtual time indicated by timer interval information.

  Next, the process waits until an event from each simulator occurs (S803). The event transmission unit 113 checks whether the event generated in step S803 is a timer event (S804).

  If the event generated as a result of the check in step S804 is a timer event, the event transmission unit 113 transmits timer event information to all peripheral simulators via the interface modules 106b and 106c (S805). After the timer event is transmitted to all the peripheral simulators, the process execution instructing unit 113 waits until it receives an execution end notification from all the peripheral simulators (S806). When the process execution instructing unit 113 receives execution end notifications from all the peripheral simulators, the process returns to the process of step S801 and shifts to the cooperative operation process at the next virtual time.

  If the event generated as a result of the check in step S804 is not a timer event (that is, a data event), the event transmission unit 113 transmits a data event to the simulator according to the wiring definition information 111 (S807). Subsequently, it is checked whether or not the source of the data event transmitted in step S807 is the CPU simulator 101 (S808). If the result of the check in step S808 is that the data event generation source is the CPU simulator 101, the CPU simulator 101 is instructed to start processing (S809). If the data event generation source is not the CPU simulator 101 (peripheral simulator) as a result of the check in step S808, the process returns to step S803 and waits until an event from each simulator occurs.

(Operation procedure example of CPU simulator 101)
Next, the operation during the simulation of the CPU simulator 101 that simulates the software operation to be verified will be described with reference to FIG.

  FIG. 6 is a flowchart showing an example of the operation procedure of the CPU simulator 101.

  The CPU simulator 101 waits until a process execution instruction is received from the process execution instruction unit 113 (S901). After receiving the process execution instruction, the simulation process is executed (S902). When an event occurs during the execution of the simulation (S903), the event generation is notified to the HUB 104 (S904), and the simulation process is temporarily stopped (S905). After suspending the simulation process in step S905, the process returns to step S901 and waits until an instruction to execute the process is received (see steps S801 and S809 in FIG. 5).

(Example of operation procedure of peripheral simulator)
FIG. 7 is a flowchart showing an example of the operation procedure of the peripheral simulator.

  The peripheral simulator waits until it receives a process execution instruction from the process execution instruction unit 113 (S1001). After receiving the process execution instruction, the simulation process is executed (S1002). If an event occurs during the simulation (S1003), the occurrence of the event is notified to the HUB 104 (S1004). Then, it is checked whether the simulation process for the virtual time instructed from the process execution instructing unit 113 is completed (S1005).

  If the simulation processing for the designated virtual time has been completed as a result of the check in step S1005, an execution completion notification is transmitted to the HUB 104 (S1006), and the process waits until the processing execution instruction is received by returning to step S1001. On the other hand, if the result of the check in step S1005 is that the simulation process for the designated virtual time has not been completed, the process returns to the simulation process execution process in step S1002.

  Note that the determination condition of “simulation process end for specified virtual time” in step S1005 is as follows. That is, the simulation process predetermined as the process at the virtual time is finished, and all the simulation processes related to the data event received before the timer event transmitted from the event transmission unit 113 are completed.

  With the above processing, the peripheral simulator performs a simulation operation using the data event received before the timer event reception as simulation data change at the virtual time. Thereby, regardless of the simulation process execution timing, the change in the simulation data can be reflected in the process at the same virtual time as the virtual time when the change in the simulation data occurs.

<Example of Cooperation Operation of Simulation System of Embodiment 1>
(Specific Configuration Example of Simulation System of Embodiment 1)
Here, a case will be described as an example in which the CPU simulator and the mechanism component simulator are operated in cooperation with each other according to the first embodiment to operate as one printer engine simulator.

  In this example, the software that controls the simulation target CPU operates based on a software timer (variable name: TimerA) that changes every 1 ms. Further, in the printer device to be simulated, paper at a predetermined position of the printer device is transported by a paper transport roller whose drive source is a paper transport motor. It is assumed that 500 ms after the drive signal of the paper transport motor is output, the leading edge of the transported paper reaches the paper detection sensor, and the paper detection sensor signal is changed to the paper detection state.

Each simulator operates in cooperation as shown in FIG. 8 and operates in the following order 1) -7).
1): The CPU simulator 101 starts the paper conveyance control 101b.
2): The CPU simulator 101 outputs a motor drive signal (101a).
3): The motor model of the mechanical component simulator 102 is driven by the output of the motor drive signal (102a).
4): By driving the motor, the paper transport roller model using the motor as the drive source transports the paper model (102b).
5): The paper detection sensor model (hereinafter simply referred to as a sensor) on the mechanical component simulator 102 installed at a predetermined position on the paper conveyance path is changed to a paper detection state by the conveyance of the paper model (102c).
6): Sensor change is input to the CPU simulator 101.
7): The CPU simulator 101 performs paper conveyance control according to the sensor signal change (101b).
8): The CPU simulator 101 outputs a motor drive signal (101a).
The user of the simulation system sets the software timer information as shown in Table 1 below.

(Operation example of simulation system of embodiment 1)
FIG. 9 is a schematic diagram showing a cooperative operation between each simulator and the HUB 104 in the first embodiment.

  First, (1): HUB (process connection unit) 104 instructs each simulator to execute simulation processing. (2): The CPU simulator 101 receives a process execution instruction. (3) (4): The mechanical component simulator 102 and the general-purpose operation simulator 103 receive an instruction to execute a simulation for the timer interval of the software timer information 110. Start the simulation process in each simulator.

  (5): When a software timer value change (elapse of 1 ms) occurs in the CPU simulator 101, the CPU simulator 101 notifies the HUB 104 of the occurrence of an event and temporarily stops its own simulation.

  (6): The event transmission unit 113 of the HUB 104 determines that the event generated in (5) is a timer event, and transmits the timer event generation to the mechanical component simulator 102 and the general-purpose operation simulator 103. (7) (8): The mechanical part simulator 102 and the general-purpose operation simulator 103 receive a timer event from the HUB. Then, the simulation process for the timer interval including the simulation process related to the data event received from the HUB 104 before the timer event transmission is executed. The simulation process for the timer interval is a simulation process for both a simulation determined in advance at the virtual time and a simulation by occurrence of a data event. The simulation by the generation of the data event is, for example, a driving simulation of the mechanism component A for the timer interval executed by the mechanism component simulator 102 by the generation of the data event by the drive signal output of the mechanism component A of the CPU simulator 101.

  (9) (10): The mechanical part simulator 102 and the general-purpose operation simulator 103 notify the HUB of the completion of execution when the simulation process for the virtual time corresponding to the timer interval is completed. (11): When the HUB 104 receives notification of completion of execution from all peripheral simulators, the HUB 104 instructs the CPU simulator 101, the mechanical component simulator 102, and the general-purpose operation simulator 103 to execute processing.

  (12) (13) (14): Each simulator that has received the processing execution instruction starts processing execution again.

  By repeating the above, the simulation is performed by matching the virtual time between the plural simulators.

<Results of simulation of Embodiment 1>
FIG. 10 is a diagram showing a simulation result when a simulation between a plurality of simulators is performed in the simulation system of the first embodiment (see FIGS. 20 and 21 of the conventional example). FIG. 10 conceptually shows that events for the CPU simulator controlled by the verification target software are transmitted at the same time on the basis of the software timer when the behavior of the verification target software is exactly the same. Yes.

  The HUB 104 of the first embodiment performs a cooperative operation between a plurality of simulators triggered by a change in the software timer value of the verification target software. Therefore, there is no variation in event transmission depending on whether the event occurrence timing occurring in the conventional simulation system is before or after the switching of the software timer value. This means that the sensor signal change event is transmitted to the CPU simulator at the same software timer time (500 ms in FIG. 10) regardless of whether the sensor signal event occurrence timing is A or B in FIG. It is understood from what is done.

  In addition, the peripheral simulator in the first embodiment performs a simulation process at the virtual time for the data event received before the timer event, that is, the occurrence of the change of the software timer value is transmitted. That is, the simulation process related to the output of the motor drive signal generated by the CPU simulator is always performed at the same virtual time (1 ms in FIG. 10) as the motor drive signal is output. Therefore, in the simulation system of the first embodiment, the software timer value from when the CPU simulator outputs a motor drive signal to when the change of the sensor signal is transmitted to the CPU simulator is 500 ms. That is, according to this method of synchronizing each simulator at the timing of the change of the software timer value, the sensor signal is changed to the paper detection state after 500 ms by the software timer from the time when the CPU simulator outputs the motor drive signal. Can be guaranteed. Therefore, a highly accurate simulation can be performed.

<Effect of Embodiment 1>
As described above, the cooperative operation between a plurality of simulators is performed using the software timer of the verification target software as one unit. Thereby, the virtual times of all simulators constituting the simulation system can be matched with the operation unit of the timer used by the verification target software for device control.

  Also, the peripheral simulator regards the data event received before the timer event reception as a change in simulation data generated at the virtual time. A simulation process associated with the data event can be executed in the simulation operation at the virtual time. Therefore, regardless of the process execution timing of each simulator, the change in the simulation data can be reflected in the simulation process at the virtual time when the change in the simulation data occurs.

  Furthermore, since the simulation system synchronization processing is performed in units of software timers of the verification target software, it is possible to execute a highly accurate simulation without reducing the synchronization interval more than necessary. That is, the cooperative operation between simulators can be performed at an optimal synchronization interval to satisfy the simulation execution purpose. As a result, the simulation execution environment resource can be effectively used, and the use efficiency of the simulation can be improved.

[Embodiment 2]
In the first embodiment, the software timer serving as a cooperative operation trigger between a plurality of simulators is always the same during simulation execution. However, there is a case where it is desired to change the cooperation operation trigger between simulators during the simulation execution depending on the processing contents of the software.

  Therefore, in the second embodiment, a simulation system in the case where the software timer for the cooperative operation trigger between a plurality of simulators is changed during the execution of the simulation will be described.

<Functional Configuration Example of Simulation System of Embodiment 2>
The simulation system according to the second embodiment is obtained by adding one new component to the simulation system configuration of the simulation system according to the first embodiment.

  FIG. 11 shows a functional configuration example of the simulation system of the second embodiment. Note that reference numerals 1401 to 1414 in FIG. 11 correspond to 101 to 114 in FIG.

  The software timer information management unit 1415, which is a new component of the second embodiment, holds information 1416 indicating conditions for changing a software timer (hereinafter referred to as a cooperative operation trigger timer) serving as a cooperative operation trigger between simulators. This information is hereinafter referred to as cooperative operation trigger timer change information 1416. According to the cooperative operation trigger timer change information 1416, the cooperative operation trigger timer is determined and the software timer information 1410 is updated at the virtual time of the simulation.

  In the first embodiment, the software timer serving as a cooperative operation trigger between simulators is not changed during simulation execution. Therefore, the software timer information 110 serving as a cooperative operation trigger between simulators is timer specifying information and timer interval information set by a user using a GUI, an external file interface, or the like.

  In the case of the second embodiment, the software timer information management unit 1415 performs the following process in order to change the software timer serving as a cooperative operation trigger between simulators during simulation execution. That is, the timer specifying information and the timer interval information are set in the software timer information 1410 according to the cooperative operation trigger timer change information 1416 set from the outside of the HUB (process connection unit) 1404. The timer specifying information and the timer interval information become the timer specifying information and timer interval information of the software timer that becomes a cooperative operation trigger between simulators at the virtual time of the simulation.

<Example of changing the cooperative operation trigger timer>
(Example of change information for cooperative operation trigger timer)
For example, when the predetermined variable (variable name: A) handled by the software is a predetermined value (predetermined value: B), the variable (variable name: TimerA) handled by the software becomes the cooperative operation trigger. This is a condition such as a software timer.

  FIG. 12 is an example of a GUI for setting the cooperative operation trigger timer change information 1416. The GUI includes a variable name setting field 121 handled by target firmware corresponding to a software timer, a timer interval setting field 122, and a condition setting field 123 using the software timer as a cooperative operation trigger. The GUI in FIG. 12 indicates the following cooperative operation trigger timer change information.

  When the variable A handled by the software is “1”, the software timer “TimerA” is used as the cooperative operation trigger timer. When the variable A handled by the software is “10”, the software timer “TimerB” is used as the cooperative operation trigger timer. When the variable A handled by the software is “20”, the software timer “TimerC” is used as the cooperative operation trigger timer. The timer intervals of each timer are Timer A: 1 [ms], Timer B: 10 [ms], and Timer C: 20 [ms].

  The user sets in the variable name setting field 121 the variable name of the software timer that is used as a cooperative operation trigger between a plurality of simulators at the time of simulation execution. In the timer interval setting field 122, a virtual time corresponding to the interval at which the value of the software timer changes is set. Furthermore, the condition setting field 123 is set with a condition for the cooperative operation using the software timer as a trigger. The method of entering numerical values and characters in each setting column is the same as that when setting the software timer information 110 in FIG.

  When the user finishes entering the cooperative operation trigger timer change information, the user clicks the OK button 124 on the GUI with the mouse 505. When the OK button 124 on the GUI is pressed, the timer specifying information, the timer interval information, and the use condition information of the cooperative operation trigger timer are determined. Then, it is stored in the software timer information management unit 1415 via the external interface 1408. In addition, when the user wants to add a column for the cooperative operation trigger timer change condition, clicking the add button 125 adds a column for the cooperative operation trigger timer change condition below the existing setting column.

(Example of operation procedure of software timer information manager)
Here, an example of the management procedure of the cooperative operation trigger timer of the software timer information management unit 1415 will be described.

  FIG. 13 is a flowchart illustrating an example of a processing procedure for the software timer information management unit 1415 to manage the cooperative operation trigger timer.

  The software timer information management unit 1415 waits until an event occurs (S1601). When an event occurs, it is checked whether the event matches the cooperative operation trigger timer change condition indicated by the cooperative operation trigger timer change information 1416 held by the software timer information management unit 1415 (S1602).

  If the check result in step S1602 shows that the cooperative operation trigger timer change condition is satisfied, the software timer information 1410 is updated to the timer specific information and timer interval information of the coordinated cooperative trigger timer (S1603), and step S1601 Return to. As a result of the check in step S1602, if the cooperative operation trigger timer change condition is not satisfied, the process returns to step S1601 to wait for the event occurrence.

<Example of Simulation Operation of Embodiment 2>
Functions related to the simulation system of the second embodiment will be described by taking as an example a case where the CPU simulator 1401 and the mechanism component simulator 1402 are operated in cooperation with each other to operate as one printer engine simulator.

  The verification target CPU uses the software timer A (variable name: TimerA) as a processing timer in the software during paper transport control. When paper conveyance control is not performed, software timer B (variable name: TimerB) is used as a processing timer in the software. Whether or not the CPU is in control of paper conveyance is represented by the value of a variable (variable name: State) indicating the paper conveyance control state. In this example, it is assumed that the value of the variable “State” is “1” when the CPU is performing paper conveyance control, and the value of the variable “State” is “0” when the paper conveyance control is not being performed.

  The user of the simulation system sets the cooperative operation trigger timer change information 1416 through the external interface 1408 as shown in Table 2 below.

  When an event occurs in which the value of the variable “State” handled by software changes to “1”, the software timer information management unit 1415 sets the timer specifying information of the software timer information 1410 to “TimerA” and the timer interval information to “1 ms”. Set to ". On the other hand, when an event occurs in which the value of the variable “State” handled by the software changes to “0”, the timer specifying information of the software timer information 1410 is updated to “TimerB” and the timer interval information is updated to “10 ms”.

  The process execution instructing unit 1413 instructs each peripheral simulator to execute the simulation process for the virtual time indicated by the timer interval information of the software timer information 1410. Further, when a change occurs in the simulation data indicated by the timer specifying information of the software timer information 1410, the event transmission unit 1414 determines that a timer event has occurred and transmits the timer event generation to each peripheral simulator.

<Effect of Embodiment 2>
As described above, the cooperative operation between multiple simulators is performed with the software timer of the software to be verified as one unit, and the software timer that triggers the cooperative operation between simulators is changed during simulation according to the designation from the outside To do. Thereby, even when the verification target software changes the software timer used for the device control process according to the control content, the virtual times of all simulators constituting the simulation system can be matched. Such matching is performed in units of timer operations that the verification target software uses for each device control. Therefore, even when the verification target software changes the software timer used for each device control, the simulation accuracy can be ensured without reducing the simulation efficiency.

[Embodiment 3]
In the first and second embodiments, all simulators constituting the simulation system are cases in which one software timer is used as a trigger for the cooperative operation.

  In the third embodiment, a simulation system is described in which a peripheral simulator and a verification target CPU simulator constituting the simulation system operate in cooperation with a change in a plurality of software timer values as a trigger. When verifying software that executes a plurality of processes based on different time criteria, it is necessary to perform simulation using the simulation system shown in the third embodiment.

<Functional Configuration Example of Simulation System of Embodiment 3>
In the functional configuration of the simulation system of the third embodiment, new functions are added to the processing execution instruction unit 113 and the event transmission unit 113 of the simulation system configuration of the first embodiment, and information handled by the software timer information 110 is added. .

  The software timer information 110 in the first embodiment and the software timer information 1410 in the second embodiment are a set of timer specifying information and timer interval information.

  On the other hand, in the third embodiment, the software timer information includes the following information for each software timer serving as the cooperative operation trigger timer because the software timer for the cooperative operation trigger with the verification target CPU simulator is set for each peripheral simulator. . That is, it has timer specification information of the software, a simulator ID of a peripheral simulator that cooperates using the software timer, and timer interval information of the software timer. In the third embodiment, the simulator ID is “1”, the mechanical component simulator is “2”, and the general-purpose operation simulator is “3” as each simulator ID.

<Setting example of software timer of embodiment 3>
FIG. 14 is a display example in which a software timer for a trigger in which the CPU simulator displayed on the display device 503 and each peripheral simulator operate in cooperation with each other is set by the GUI.

  The GUI has a variable name setting field 142 that is handled by target firmware corresponding to a software timer serving as a cooperation operation trigger with the CPU simulator for each peripheral simulator. The timer variable name entered in the variable name setting field 142 is stored in the cooperative operation definition information management module 109 as timer specifying information. Further, the user sets the timer specifying information and the timer interval information using a GUI as shown in FIG. The timer specifying information and the timer interval information of each software timer set from the GUI are stored in the cooperative operation definition information management module 109.

  The cooperative operation definition information management module 109 handles the timer specifying information and timer interval information of the cooperative operation trigger timer for each peripheral simulator as software timer information. That is, as shown in FIG. 15, the change of the software timer value is used as a trigger to associate the simulator ID of the peripheral simulator that operates in cooperation with the CPU simulator and the timer interval of the software timer, and treats it as software timer information.

  The processing execution instructing unit 113 in the simulation system according to the third embodiment uses the same software timer, and when the end of processing execution is notified from all peripheral simulators operating in cooperation with the CPU simulator, the next virtual time Instruct the minute processing. That is, at that time, all peripheral simulators that operate in cooperation with the CPU simulator using the same software timer so as to execute processing for the virtual time indicated in the timer interval information associated with the software timer. Instruct. Simultaneously with the above instruction, the CPU simulator is instructed to execute the process, and proceeds to the next virtual time.

  The event transmission unit 114 during simulation in the third embodiment transmits a data event to each simulator according to the wiring definition information 111. The change (timer event) of the software timer value specified by the timer specifying information of the software timer information is transmitted to all the peripheral simulators that operate in cooperation with the CPU simulator by the change of the software timer value.

<Example of HUB Processing Procedure of Embodiment 3>
Here, FIG. 16 shows a flowchart of an example of an operation procedure during simulation of the HUB 104 including the cooperative operation definition information management unit 109, the process execution instruction unit 113, and the event transmission unit 114 in the simulation system of the third embodiment.

  The operation procedure example during the simulation of the HUB 104 of the third embodiment is obtained by adding new processing to the operation procedure example of the HUB 104 of the first embodiment shown in FIG. 16 correspond to S801 to S804 in FIG. 5, and S1909 to S1911 in FIG. 16 correspond to 807 to S809 in FIG.

  When the event transmission unit 114 determines that the event generated in step S1903 is a timer event (Y in S1904), the timer event is transmitted to all peripheral simulators operating in cooperation with the CPU simulator by the timer event (S1905). . Of the simulators constituting the simulation system, the peripheral simulator that operates in cooperation with the CPU simulator at the timer event is the following peripheral simulator. That is, it is a peripheral simulator corresponding to a simulator ID managed in association with timer specifying information corresponding to the software timer of the timer event.

  The process execution instructing unit 113 waits until execution completion is notified from all the peripheral simulators to which the timer event has been transmitted in step S1905 (S1906). In step S1906, when the process execution instructing unit 113 receives execution end notifications from all the peripheral simulators to which the timer event is transmitted, it instructs the CPU simulator to execute the simulation process (S1907). Subsequently, in step S1905, execution of simulation processing for a virtual time corresponding to the timer interval of the software timer of the timer event is instructed to all simulators that have transmitted the occurrence of the timer event (S1908). When the peripheral simulator is instructed to execute the process in step S1908, the process returns to step S1903.

<Example of Cooperation Operation of Simulation System of Embodiment 3>
(Specific Example of Simulation System of Embodiment 3)
Here, an apparatus control simulation will be described as an example in which a printer device that forms a toner image on a paper surface, heats the toner image on the paper surface, and fixes the image on the paper surface is a simulation target.

  The contents of the simulation are the temperature of the heat source heater in the fixing unit for fixing the image, the operation of the paper transport motor, and the paper transport operation by the operation of the paper transport motor. The temperature of the heat source heater is calculated from the drive signal output time of the heat source heater, and the operation of the paper transport motor drives the motor with the motor drive signal output.

  FIG. 17 shows a schematic diagram of an information flow between simulators constituting the device control simulation system of this example. The temperature of the heat source heater is simulated by the general-purpose operation simulator 103, and the paper transport operation simulation is performed by the mechanical component simulator 102.

(Heat source heater temperature simulation)
The heat source heater drive signal is output from the CPU simulator 101 and input to the general-purpose operation simulator 103 (101c). The general-purpose operation simulator 103 calculates the temperature of the heat source heater according to the output time of the heater drive signal output from the CPU simulator 101 (103 a), and inputs the calculated temperature of the heat source heater to the CPU simulator 101. The CPU simulator 101 performs temperature control 101d according to the input temperature of the heat source heater.

(Paper transport operation simulation)
The paper transport motor drive signal is output from the CPU simulator 101 and input to the mechanical component simulator 102 (101a). The mechanical component simulator 102 drives the paper transport motor 102a. Then, the mechanical component simulator 102 transports the paper by driving the paper transport motor (102b), and inputs the change (102c) of the paper detection sensor on the paper transport path caused by the paper transport to the CPU simulator 101. The CPU simulator 101 performs the paper conveyance control 101b according to the input change of the paper detection sensor.

  The CPU software for controlling the printer device controls the drive signal of the heat source heater using a software timer A (timer variable name: Timer A, timer interval: 1 ms) generated based on the frequency of the AC power supply of the printer device. To do. Then, the temperature of the heater heat source input to the CPU is fed back to the control of the heater drive signal.

  Further, the paper transport motor that is the drive source of the paper transport roller is controlled using a software timer B (timer variable name: Timer B, timer interval: 5 ms) generated based on the operation clock of the CPU. The paper detection sensor signal input to the CPU is fed back to the paper transport control control. The software timer A is generated based on a time reference different from that of the software timer B by using, for example, an interval interrupt function included in the software debugger.

  When one software timer performs a cooperative operation between simulators as in the simulation systems of the first and second embodiments, in the above case, it is not possible to ensure the synchronization accuracy required for more accurate control. This is because the simulators are linked to each other based on one of the software timers.

  First, the user of the simulation system sets cooperative operation trigger timer information as shown in Table 3 via the external interface 1408.

  In the simulation system shown in this example, the cooperative operation trigger timer information is handled by the three item contents shown in FIG.

(Operation Example of Simulation System of Embodiment 3)
FIG. 18 is a schematic diagram showing the cooperative operation of each simulator and HUB in this example.

  (1): First, the HUB instructs each simulator to execute simulation processing. (2): Instructs the CPU simulator to execute processing. (3): Instruct the general-purpose operation simulator to execute a 1-ms simulation. (4): Then, a simulation for a virtual time of 5 ms is instructed to the mechanical part simulator (4). Start the simulation process in each simulator.

  (5A): A value change of software timer “Timer A” occurs in the CPU simulator, and the CPU simulator temporarily stops the simulation. (6A): The HUB determines that the event generated in (5A) is a timer event, and transmits the timer event occurrence to a general-purpose operation simulator that operates in cooperation with the CPU simulator by a change in the value of the software timer “TimerA”. (7A): The general purpose operation simulator receives a timer event from the HUB.

  (8A): The general-purpose operation simulator ends the simulation process execution for 1 ms including the simulation process related to the data event received from the HUB before the timer event transmission, and notifies the HUB of the end of the execution. (9A): When the HUB receives the execution end notification, it instructs the CPU simulator and the general-purpose operation simulator to execute processing. (10A) (11A): Each simulator that receives the process execution instruction starts the process execution again.

  (5B): Also, when a change in the value of the software timer “TimerB” occurs, processing is performed in the same manner as when a change in the value of the software timer “TimerA” occurs. That is, (6B): The HUB transmits a timer event to the mechanism component simulator that operates in cooperation with the CPU simulator by a change in the value of “TimerB”. (7B): The general-purpose operation simulator receives a timer event from the HUB.

  (8B): When the simulation of the simulation process for the virtual time of 5 ms instructed by the HUB is completed, the mechanical component simulator notifies the HUB of the end of the process execution. (9B): When the HUB receives the execution end notification from the mechanical component simulator, the HUB instructs the simulator (the CPU simulator and the mechanical component simulator in this example) to perform processing in cooperation with the software timer “TimerB”. (10B) (11B): Each simulator that receives the process execution instruction starts the process execution again.

  By repeating the above, the peripheral simulator performs a cooperative operation with the CPU simulator, triggered by changes in different software timer values, and causes the simulation system to perform a cooperative operation. In this example, one peripheral simulator and the CPU simulator operate in cooperation with one timer, but a plurality of peripheral simulators and the CPU simulator can operate in cooperation with one timer.

<Effect of Embodiment 3>
As described above, the CPU simulator cooperates with a change in the software timer value that differs for each peripheral simulator. As a result, even when the verification target software uses a plurality of software timers to perform device control, the simulator can be divided for each software timer used by the verification target software to configure a simulation system. Accordingly, each simulator can be linked to the target software that controls the verification target CPU for each unit for which the target software performs CPU control. As a result, the simulation accuracy can be ensured without reducing the use efficiency of the simulation.

  The present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.

  The present invention can also be achieved by supplying a software program for realizing the functions of the above-described embodiments directly or remotely to a system or apparatus. Then, a computer included in the system or the like reads and executes the supplied program code.

  Accordingly, since the functions and processes of the present invention are implemented by a computer, the program code itself installed in the computer also implements the present invention. That is, the computer program itself for realizing the functions and processes is also one aspect of the present invention.

  In this case, the program may be in any form as long as it has a program function, such as an object code, a program executed by an interpreter, or script data supplied to the OS. Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. Examples of the recording medium include a magnetic tape, a non-volatile memory card, a ROM, and a DVD (DVD-ROM, DVD-R).

  The program may be downloaded from an Internet / intranet website using a browser of a client computer. That is, the computer program itself of the present invention or a compressed file including an automatic installation function may be downloaded from the website onto a recording medium such as a hard disk. It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different website. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer may be a constituent requirement of the present invention.

  Further, the program of the present invention may be encrypted and stored in a storage medium such as a CD-ROM and distributed to users. In this case, only the user who has cleared the predetermined condition is allowed to download key information for decryption from the website via the Internet / intranet. Then, the program encrypted with the key information may be decrypted and executed, and the program may be installed in the computer.

  Further, the functions of the above-described embodiments may be realized by the computer executing the read program. Note that an OS or the like running on the computer may perform part or all of the actual processing based on the instructions of the program. Of course, also in this case, the functions of the above-described embodiments can be realized.

  Furthermore, the program read from the recording medium may be written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Based on the instructions of the program, a CPU or the like provided in the function expansion board or function expansion unit may perform part or all of the actual processing. In this way, the functions of the above-described embodiments may be realized.

It is a figure which shows the function structural example of the simulation system which concerns on Embodiment 1. FIG. It is a figure which shows the example of schematic structure of the simulation system which concerns on this embodiment. It is the figure which showed the example of a display of the mechanism component simulator which concerns on this embodiment. 6 is a diagram illustrating an example of a GUI for setting software timer information according to the first embodiment. FIG. 3 is a flowchart illustrating an example of an operation procedure of a process connection unit according to the first embodiment. 3 is a flowchart illustrating an example of an operation procedure of the CPU simulator according to the first embodiment. 3 is a flowchart illustrating an example of an operation procedure of a peripheral simulator according to the first embodiment. It is a schematic diagram which shows the example of a data flow between CPU simulator and mechanism component simulator in Embodiment 1. FIG. FIG. 5 is a schematic diagram illustrating an example of a cooperative operation between each simulator and a process connection unit in the first embodiment. It is the conceptual diagram which showed that the event with respect to CPU simulator was transmitted at the same time on the basis of a software timer in the simulation system of Embodiment 1. It is a figure which shows the function structural example of the simulation system which concerns on Embodiment 2. FIG. It is the figure which showed the example of GUI which sets the cooperation operation | movement trigger timer change information which concerns on Embodiment 2. FIG. 10 is a flowchart illustrating a procedure example of cooperative operation trigger timer management of the software timer information management unit according to the second embodiment. It is the figure which showed the example of GUI which sets the cooperation operation | movement trigger timer which concerns on Embodiment 3. FIG. It is a schematic diagram of the software timer information according to the third embodiment. 10 is a flowchart illustrating an example of an operation procedure of a process connection unit according to the third embodiment. It is a schematic diagram which shows the example of a data flow among the CPU simulator in Embodiment 3, a mechanism component simulator, and a general purpose operation simulator. FIG. 10 is a schematic diagram illustrating an example of a cooperative operation between each simulator and a process connection unit in the third embodiment. It is a schematic diagram about the form of the cooperation operation | movement between the conventional simulators. It is the conceptual diagram which showed that the event with respect to CPU simulator by a conventional simulation system was transmitted at different time on the basis of a software timer. It is the conceptual diagram which showed that the event with respect to CPU simulator by a conventional simulation system was transmitted at different time on the basis of a software timer.

Claims (16)

Using a CPU simulator for simulating a CPU, at least one peripheral simulator for simulating a peripheral part to be controlled by the CPU, and a process connection part for realizing synchronization between the simulators, A simulation method for executing a simulation while synchronizing a CPU simulator and at least one peripheral simulator,
The CPU simulator, when a change in the software timer of the CPU simulator occurs, notifying the process connection unit of the occurrence of the change;
After the CPU simulator notifies the occurrence of the change, stopping the simulation until the next instruction to start the simulation to the CPU simulator is from the process connection unit;
The process connection unit receives notification of the occurrence of a change in the software timer from the CPU simulator and notifies the peripheral simulator of the occurrence of a change in the software timer;
The peripheral simulator receiving the occurrence of a change in the software timer of the CPU simulator from the process connection;
When the peripheral simulator finishes the simulation corresponding to the time of the software timer change after receiving the occurrence of the change of the software timer, the step of notifying the end of the simulation to the process connection unit,
And a step of instructing the CPU simulator and the peripheral simulator to start the simulation when the process connection unit is notified of the end of the simulation from all of the peripheral simulators. The process connection unit accepting and storing an input of a change time of a software timer of the CPU simulator;
The simulation method according to claim 1, further comprising: a step of notifying the CPU simulator of a change time of the software timer. The process connection unit receiving and storing input of different change times of the plurality of software timers of the CPU simulator;
The process connection unit determining which of the plurality of software timers the CPU simulator uses;
The simulation method according to claim 1, further comprising a step of notifying the CPU simulator of the determined change time of the software timer. The process connection unit accepts and stores input of different change times of the plurality of software timers of the CPU simulator and information indicating a peripheral simulator to be used for synchronization of the plurality of software timers. When,
The process connection unit notifying the CPU simulator of different change times of the plurality of software timers and information indicating a peripheral simulator to be used for synchronization of the plurality of software timers;
The process connection unit receives notification from the CPU simulator of the occurrence of the change of the software timer and the information indicating the peripheral simulator to be used for synchronization of the software timer, and the occurrence of the change of the software timer. And notifying the surrounding simulator of the target,
In the step of notifying the process connection unit of the occurrence of the change, the CPU simulator includes information indicating a peripheral simulator to be used for synchronization along with the occurrence of the change of the software timer. The simulation method according to claim 1, wherein notification is performed.   5. The simulation method according to claim 2, wherein in the step of receiving and storing the input, information is input by a user via a graphical user interface.   5. The method according to claim 2, wherein in the step of receiving and storing the input, information is input through an external file interface from a file edited by a user according to a predefined format. The simulation method described.   5. The simulation method according to claim 2, wherein in the step of receiving and storing the input, information is input via communication between processes.   The program for performing each process of the simulation method of any one of Claim 1 thru | or 7 with a computer.   A computer-readable storage medium storing the program according to claim 8. A CPU simulator for simulating a CPU, at least one peripheral simulator for simulating a peripheral part to be controlled by the CPU, and a process connection part for realizing synchronization between the simulators, A simulation system for executing a simulation while synchronizing a CPU simulator and at least one peripheral simulator,
The CPU simulator is
When a change in the software timer included in the CPU simulator occurs, means for notifying the process connection unit of the occurrence of the change;
After notifying the occurrence of the change, means for stopping the simulation until the next instruction to start the simulation to the CPU simulator is from the process connection unit,
The peripheral simulator is
Means for receiving the occurrence of a change in the software timer of the CPU simulator from the process connection;
Means for notifying the process connection unit of the end of the simulation when the peripheral simulator ends the simulation corresponding to the time of the change of the software timer after receiving the occurrence of the change of the software timer;
The process connection is
Means for notifying the peripheral simulator of the occurrence of a change in the software timer upon receiving a notification of the occurrence of the change in the software timer from the CPU simulator;
A simulation system comprising: a CPU simulator and a means for instructing the peripheral simulator to start a simulation when the end of simulation is notified from all of the peripheral simulators. The process connection is
Means for receiving and storing an input of a change time of a software timer included in the CPU simulator;
The simulation system according to claim 10, further comprising means for notifying the CPU simulator of a change time of the software timer. The process connection is
Means for receiving and storing input of different change times of a plurality of software timers of the CPU simulator;
Means for determining which of the plurality of software timers the CPU simulator uses;
The simulation system according to claim 10, further comprising means for notifying the CPU simulator of the determined change time of the software timer.   13. The simulation system according to claim 12, wherein the means for receiving and storing the input stores information specifying one of a plurality of software timers in association with a corresponding change time. The process connection is
Means for accepting and storing input of different times of change of the plurality of software timers of the CPU simulator and information indicating a peripheral simulator to be used for synchronization of the plurality of software timers;
Means for notifying the CPU simulator of different change times of the plurality of software timers and information indicating a peripheral simulator to be used for synchronization of the plurality of software timers;
Upon receiving notification from the CPU simulator of the occurrence of the change in the software timer and the information indicating the target peripheral simulator that uses the software timer for synchronization, the occurrence of the change in the software timer is detected by the target peripheral simulator. And a means for notifying
The means for notifying the process connection unit of the occurrence of the change of the CPU simulator is configured to notify the process connection unit of information indicating a peripheral simulator to be used for synchronization with the occurrence of the change of the software timer. The simulation system according to claim 10, wherein notification is performed.   The means for receiving and storing the input stores information specifying one of the plurality of software timers, the corresponding change time, and the peripheral simulator to be used for synchronization of the software timer in association with each other. The simulation system according to claim 14. The operation of the mechanical device is simulated by a computer system, and in accordance with a CPU control program mounted on the device to be simulated, information on the virtual input terminal defined corresponding to the CPU terminal of the target device is read. One or more CPU simulators that simulate the operation of the CPU of the target device by controlling the virtual output terminal;
A mechanism model of a mechanical device composed of a plurality of parts including an actuator and a sensor, interference and cooperation between the mechanism models, and a signal connected to the actuator and the sensor are defined by a computer system and input from the outside. In accordance with the definition of the actuator operation corresponding to the information defined as the actuator operation signal and the interference and linkage between the mechanical components, the operation of all related mechanical components is reproduced as an image on the display device of the computer system, and the mechanism model One or more mechanism component simulators that output information defined as sensor signals to the outside in response to a predefined action for the mechanism model defined as the sensor;
The simulation target device is a component that is not supported by the CPU simulator and the mechanical component simulator, a function that simulates an external action on the target device, and a simulation result One or more simulators having a function to analyze, display and save, and a function to provide a user interface for simulation;
Process connection means for connecting a simulator in the simulation and operating as a device control simulation system,
The process connection means cooperates between simulators triggered by a change in a timer created by the CPU program to be verified as a trigger, advances a virtual time with the change in the timer as one unit, and the various times are determined according to the virtual time. A simulation system comprising a cooperative operation module for performing synchronization processing between simulators.

Images