🚀 go-pugleaf

In article <1991Jan9.141133.26616@cs.hope.edu> jipping@cs.hope.edu writes:
>weiman@jargon.whoi.edu (Bob Weiman) writes:
>
>> If someone is using the new Inmos ANSI C compiler and 
>According to the tech support guy we correspond with, YES it is true.
>The INMOS C debugger is NOT capable of interactive debugging with T800s,
>but post-mortems can still be done.  Our support guy daid that he thought
>TRAMs whose model numbers ended in 1 or 5 were capable of interactive
>debugging, and the rest were not.
>

I don't understand this so I'll detail our numbering scheme
for those who remain perplexed:

   All T-Series TRAMs are numbered IMS B4xx-y .

   The "xx" part of the number is allocated in chronological
   order, missing out "13" which is reserved for designs we
   don't ever want to finish :) Some other numbers were missed
   in order to aviod confusion with other products. For instance,
   there is no B425. 

   The "y" part is determined by the transputer for "compute only" TRAMs:

     -1  IMS T212-20
     -2  IMS T414-20
     -3  IMS T800-20
     -4  IMS T800-17
     -5  IMS T800-25
     -6  IMS T800-30
-    -7  IMS T425-20
     -8  IMS T425-25
     -9  IMS T425-30
     -10 IMS T222-20
     -11 IMS T801-20
     -12 IMS T801-25
     -14 IMS T400-20

  For I/O and graphics TRAMs, the "y" part is allocated
  in chronological order for different variations.

There are other numbers marked on the actual TRAMs.
These are manufacturing build identifiers, used for
traceability and tend to incorporate a letter after
the product code (IMS B404-5B). 


Happy New Year.
David.

David Boreham, INMOS Limited | mail(uk): davidb@inmos.co.uk or ukc!inmos!davidb
Bristol,  England            |     (us): uunet!inmos.com!davidb
+44 454 616616 ex 547        | Internet: davidb@inmos.com