Newsgroups: comp.sys.transputer
From: schedan@eskimo.com (Daniel Scheurell)
Subject: Re: HELP WANTED!
Organization: Eskimo North (206) For-Ever
Date: 25 May 94 03:42:18 GMT
Message-ID: <CqCAAI.42E@eskimo.com>

Ronald in 't veld (ronald@dutepp13.et.tudelft.nl) wrote:
: Recently I started working with 4 805 Transputers fitted to a Paratech
: Solutions Limited PSM004-3 PC card. A connector on the back of this thing
: allows the transputer links to be connected.
: The problem begins when I connect the links.
: But when I connect the pipehead link, the problems begin.

For single board systems, the pipehead is usually jumpered to the T2 network 
configuration processor (I don't have any specific experience with the 
Paratech board, so accpet my words with a grain of salt :).  The pipehead is 
slot 0, link 1, and could be the entry point on a second or subsequent 
board for the pipetail (slot 9, link 2) from the previous board.

: Single transputer programs without a configuration file work fine.
: Multitransputer programs however don't work, even when they don't use the
: pipehead link (this is the Host transputer's link 0). When I attempt to
: start a multitransputer program, IServer reports: Cannot send byte 1045 to
: host.

If the multitransputer program is configured to use the pipehead edge 
connection, it won't boot on a board that has slot 0, link 1 connected to 
the board's T2 configuration processor.  The error report indicates that 
the physical processor interconnections do not match those expected by the 
bootable program, or perhaps all the transputers are not being reset 
properly.  The programs that don't use the "pipehead" must also be confused.

: Suggestions anyone?

Check that the board's jumpers/switches are correctly set.
Check the configuration source file and see that it correctly describes 
the network topology.

--

Dan

