System and method for controlling access to memory configured within an I/O module in a distributed I/O system

• US 6,098,117 A
• Filed: 04/20/1998
• Issued: 08/01/2000
• Est. Priority Date: 04/20/1998
• Status: Expired due to Term

• Current Assignee: National Instruments Corporation (Emerson Electric Company)
• Original Assignee: National Instruments Corporation (Emerson Electric Company)
• Inventors: Foote, Garritt W., Mehta, Pratik M.
• Primary Examiner(s): Shin, Christopher B.
• Application Number:
  US09/063,177
• Time in Patent Office: 834 Days
• Field of Search: 710/8-19, 710/36-45, 710/101-106, 710/129-200, 710/220, 710/246, 713/100
• US Class Current: 710/8
• CPC Class Codes: G06F 13/4095 in incremental bus architectures, e.g. bus stacks
• CPC Class Codes: G06F 2213/0052 Assignment of addresses or identifiers to the modules of a bus system

Abstract

A modular distributed I/O system includes a computer coupled to module banks through a network bus. A module bank includes a communication module, terminal bases, and I/O modules. The adjoined terminal bases form a local bus mastered by the communication module. The I/O modules connect to the local bus through terminal bases. I/O modules are pluriform and programmable. The communication module maintains a memory image of the configuration state of each I/O module resident in the module bank. A memory image persists when an I/O module is removed from its terminal base. The memory image is used to configure a new I/O module which is inserted into the same terminal base. The communication module monitors for communication failure on the network bus, and is configured to capture the state of the module bank and automatically restore this captured state after a power-loss event. The terminal bases realize a local bus which includes a parallel bus, a serial bus, and an address assignment bus. Each terminal base receives a value from a preceding terminal base, increments this value, and asserts the increment value to a succeeding terminal base. Each terminal base is automatically assigned an physical proximity address. An I/O module controls read/write access to its register space by a semaphore mechanism which supports multi-threaded processing. The I/O module latches an ungranted semaphore request and assumes a self-exclusion state upon releasing the semaphore wherein the semaphore is reserved for the communication module.

Claims

1. A method for controlling read/write access to a register space of an I/O module in a distributed I/O system, the distributed I/O system including a computer system coupled to a module bank, the module bank including a communication module and one or more I/O modules, wherein the I/O module includes a register space, wherein the I/O module is coupled to the communication module, the method comprising:

a first process executing in the communication module requesting access to the register space of the I/O module, wherein said requesting access includes initiating a first read operation on a semaphore register;

the I/O module determining if a process executing in the communication module already controls access to the register space of the I/O module;

the I/O module granting register space access to the first process executing in communication module;

wherein the granting includes providing information to the first process indicating whether a process executing in the communication module already controls access to the register space of the I/O module;

wherein the information is useable by the first process to affect register accesses by the first process.

2. The method of claim 1, further comprising said first process performing a semaphore release write operation to said I/O module, wherein said semaphore release write operation forces any process executing in the communication module and currently controlling access to the register space of the I/O module to release control of the register space of the I/O module.

3. The method of claim 2, wherein said information indicates that a second process executing in the communication module already controls access to the register space of the I/O module, wherein said first process has a high priority relative to said second process, the method further comprising:

the first process performing said semaphore release write operation and thereby forcing said second process to release control of said register space.

4. The method of claim 1, wherein said information indicates that a second process executing in the communication module already controls access to the register space of the I/O module, wherein said first process has a low priority relative to said second process, the method further comprising:

the first process waiting until the second process releases access to the register space of the I/O module.

5. The method of claim 4, wherein said first process waiting until the second process releases access to the register space of the I/O module includes the first process repeatedly requesting access to the register space of the I/O module, wherein the first process repeatedly requests access until said information indicates that no process executing in the communication module currently controls access to the register space of the I/O module.

6. The method of claim 1, further comprising:

the I/O module determining if the register space is available in response to the first process executing in the communication module requesting access to the register space of the I/O module, wherein the register space is determined to be available if the I/O module does not currently control the register space;

wherein the I/O module grants register space access to the first process executing in communication module in response to determining that the register space is available.

7. The method of claim 1, wherein the I/O module granting register space access and said providing information to the first process indicating whether a process executing in the communication module already controls access to the register space of the I/O module comprises:

said I/O module writing one or more values to the semaphore register;

the first process completing said first read operation to read said one or more values written to the semaphore register.

8. The method of claim 1, further comprising:

a third process executing in the communication module requesting access to the register space of the I/O module after the I/O module granting register space access to the first process, wherein said third process requesting access includes initiating a third read operation on the semaphore register;

the I/O module determining that said first process executing in the communication module previously has been granted access to the register space of the I/O module;

the I/O module granting register space access to the third process executing in communication module;

wherein the granting includes providing information to the third process indicating that a process executing in the communication module previously had been granted access to the register space of the I/O module;

wherein the information is useable by the third process to affect register accesses by the third process.

9. The method of claim 1, further comprising:

the I/O module gaining access to the register space of the I/O module;

a fourth process executing in the communication module requesting access to the register space of the I/O module, wherein said fourth process requesting access to the register space includes initiating a fourth read operation on the semaphore register, wherein said fourth process requesting access occurs while said I/O module controls the register space of the I/O module;

said I/O module denying the request of the fourth process for the register space of the I/O module;

said I/O module storing an indication of said fourth process requesting access to the register space of the I/O module;

the I/O module releasing access to the register space;

wherein the I/O module is unable to regain access to the register space until after a process executing in the communication module performs a semaphore release write operation to the I/O module.

10. The method of claim 9, wherein said denying the request of the fourth process for the register space of the I/O module comprises:

said I/O module writing one or more values to the semaphore register;

the fourth process completing said fourth read operation to read said one or more values written to the semaphore register.

11. The method of claim 9 further comprising:

said communication module reading a semaphore request time parameter from the I/O module, wherein said semaphore request time parameter specifies the maximum time duration said I/O module may control access to the register space of the I/O module after the communication module has requested access to the register space of the I/O module;

said fourth process asserting one or more subsequent requests for access to the register space after said I/O module denying the request associated with the fourth read operation, wherein said fourth process uses said semaphore request time parameter to determine times for said one or more subsequent requests.

12. A method for controlling read/write access to a register space of an I/O module in a distributed I/O system, the distributed I/O system including a computer system coupled to a module bank, the module bank including a communication module and one or more I/O modules, wherein the I/O module includes a register space, wherein the I/O module is coupled to the communication module, the method comprising:

initializing the I/O module in an available state which indicates availability of the register space of the I/O module;

said communication module performing a first request for access to the register space of the I/O module, wherein said performing a first request comprises performing a first read operation of a semaphore register;

said I/O module non-trivially granting register space access to the communication module in response to said first request, wherein said non-trivially granting indicates that the communication module did not possess said register space access prior to said first request;

said communication module performing a second request for access to the register space of the I/O module, wherein said performing a second request comprises performing a second read operation of said semaphore register;

said I/O module trivially granting register space access to the communication module in response to said second request, wherein said trivially granting register space access indicates that the communication module already possessed said register space access prior to said second request.

13. An access control system comprising:

an I/O module which includes a register space and a semaphore register;

a communication module coupled to the I/O module;

wherein the communication module is configured to read the semaphore register, wherein the initiation of a read operation on the semaphore register asserted by the communication module comprises a request for access to the register space of the I/O module, wherein the I/O module is configured to update the contents of the semaphore register in response to the initiation of the read operation, wherein the contents of the semaphore register returned by the read operation indicates;

whether the request for access has been granted or denied; and

in the case where the request is granted, whether the communication module already had access to the register space prior to the initiation of the read request.

14. The access control system of claim 13, wherein the communication module is configured to execute a plurality of processes in a multi-threaded fashion, wherein a first process of said plurality of processes is configured to access the register space of the I/O module in response to (a) the first process asserting a first request for access to the register space of the I/O module, and (b) the first process being granted access with the indication that the communication module did not already have access to the register space prior to said first process performing said first request, wherein the first process is configured to conditionally access the register space of the I/O module in response to (c) the first process asserting a second request for accessing to the register space of the I/O module, and (d) the first process being granted access with the indication that the communication module already had access to the register space prior to said first process performing said second request.

15. The access control system of claim 13, wherein the communication module is configured to release access to the register space of the I/O module by writing a predetermined pattern to the I/O module.

16. The access control system of claim 15, wherein the I/O module is configured to assume control of the register space and perform read/write operations to the register space while it has assumed control of the register space.

17. The access control system of claim 16, wherein a second process of said plurality of processes is configured to perform a second request for access to the register space of the I/O module, wherein the I/O module is configured to (a) deny said second request and (b) store an indication of said second request, if said second request occurs while said I/O module controls access to the register space, wherein after the I/O module has released control of the register space, the I/O module is unable to regain control of the register space until after a process executing in the communication module performs a semaphore release write operation to the I/O module.

18. The access control system of claim 17, wherein the I/O module is configured to store a semaphore request time parameter which specifies the maximum time duration the I/O module may control access to the register space of the I/O module after the communication module has requested access to the register space, wherein said communication module is configured to read the semaphore request time parameter, wherein said second process of said plurality of processes is configured to perform one or more subsequent requests for access to the register space after said second request has been denied, wherein said second process is configured to use said semaphore request time parameter to determine times for said one or more subsequent requests.