stiles@MULTI.EE.USU.EDU (G. S. Stiles) (09/15/90)
Has anybody out there developed any code to allow a user program running on a Sun talk to a program running on a B014 or B011? Thanks - Dyke Stiles stiles@cc.usu.edu
hagerer@perm.fmi.uni-passau.de (Andreas Hagerer) (09/17/90)
In article <9009142140.AA01847@multi.ee.usu.edu> stiles@MULTI.EE.USU.EDU (G. S. Stiles) writes: >Has anybody out there developed any code to allow a user program running >on a Sun talk to a program running on a B014 or B011? > >Thanks - >Dyke Stiles stiles@cc.usu.edu Communication between a program located on the SUN and a process running on the root transputer of a B011 can be performed in two ways: - communication via link The Link 0 of the board's root transputer is connected to the VME-bus via a link adapter. - direct access to the memory of the root transputer A dual-port-memory with connections to the transputer as well as to the VME-bus is placed on the board. The following steps have to be performed to establish both forms of communication (for implementation details: see source code of the B011- iserver offered by INMOS): 1) The environment variable TRANSPUTER which gives the location (base address) of the board is read. 2) The VME-device-driver (e.g. vme24d32) is opened. 3) Memory for a structure called B011Layout is allocated. This structure contains variables used for - reset and error flag - analyse flag - input & output status registers - input & output data registers - "shared" memory. 4) The structure's space is mapped onto/into (?) the address space that is used/offered by the device driver by using the system routine MMAP. By this way you are able to communicate with the transputer by reading/ writing the variables of the structure. An access to the structure's attributes is passed to the board's link adapter by the VME-device- driver. 5) A bootable file is loaded by writing each byte into the structure's output data register and by setting the corresponding status register. The following step has to be performed in case of loading bootable files produced by the OCCAM toolset: 6) When the root transputer receives the last byte of the bootable file a message is sent to the server. The format of the message is described in the manual of the OCCAM toolset (chapter F: Host file server protocol). The information how much memory is available on the root transputer is requested by this message. Therefore, the content of the environment variable IBOARDSIZE has to be transmitted to the transputer. 7) Now, the server can communicate with the process on the transputer using his own protocol which is independant from the standard iserver protocol. Bye Andreas Andreas Hagerer University of Passau P.O. 2540 D-8390 Passau Tel.: **49-851-509323 email: hagerer@perm.fmi.uni-passau.de