COS99284@UFRJ.BITNET (Luiz Felipe Perrone) (03/07/91)
Here is have a problem for experienced transputer hackers out there:
We work with an 8 nodes (T800) hypercube and, as occam programmers,
we use TDS2. Whenever trying to debug a program running on this machine
we have great pains because we don't know how to generate a core dump
for the transputer network. Although we have restlessly searched the
TDS2 Manual we never found out how to do this. We suspect it is indeed
possible to do it because in Chapter 9 of this manual the actual
procedure is described. Once in the monitor screen, one only has to
select "N" to write a network dump.
However, we can never get to the monitor screen when the transputer
error flag is set in any processor other than the root transputer.
And the reason for this seems to be quite strange: the error flag can't
be reset and TDS2 can't be loaded again.The only way to load TDS2
after the error is to turn off the machine.
If you think you can help us please send us a message. We will be
forever indebted to you. (I'm not sure that means much, though...)
------------------------------------------------------------------------
Luiz Felipe Perrone
MSc student - COPPE - Dept. of Systems Engineering and Computer Science
Federal University of Rio de Janeiro - Brazil
E-mail: COS99284@UFRJ (BITNET)
Mailiing address: Rua Senador Vergueiro 157/305
Flamengo - Rio de Janeiro, RJ - Brazil
CEP 22230
Phone number: (55)-(21)-5519063
------------------------------------------------------------------------heller@LISBOA.KS.UIUC.EDU (Helmut Heller) (03/07/91)
>Felipe writes about problems debugging a network of Transputers. He >can not boot the root Transputer as long as there is an error flag >set in anyone of the network Transputers. Felipe, First let me ask you what kind of motherboard you use (B004, B008, B014) and what your host computer (PC, SUN, IRIS) is. Your problem is that the error signal from the network SHOULD NOT be propagated to the host computer (iserver or server14) DIRECTLY (as does, e.g. the UP/DOWN port), but should rather be connected to the SUBsystem port of your mothertransputer. For unknown reasons (most likely a hardware bug/wrong connection/wrong configuration) the network error signal is directly routed to your host computer, causing all the problems. So, first, check that your network is wired to your SUBSYSTEM port and that there are no short circuits. We are using here a B004, B008, and B014 and we are experiencing similar problems in our B014-system --- all the other ones work fine. We think that we've checked everything and so I would like to use the opportunity to ask people on the net about similar experiences with the B014 board in particular (also I would like to know positive experiences with the B014 board). Cheers, Helmut (W9/DH0MAD) _________________________________________________ heller@lisboa.ks.uiuc.edu "Knowledge must be gathered and cannot be given" u27013@ncsagate.bitnet ZEN, one of BLAKES7 Phone: (217)244-1586 ------------------------------------------------- Helmut Heller, University of Illinois at Urbana-Champaign, Beckman Institute Theoretical Biophysics Group, Transputer Lab, Room 3151 405 N. Mathews Ave., Urbana, IL 61801, U.S.A.