23 Juillet 2011 from (comp.sys.transputer) Damien :
a long time without new from my litle Parsytec MC2-32 !
what news ...
- that's it ! I can boot without worry the NCU on MSDOS like on
helios.
(Note : NCU = Network Configuration Unit, the C004 card of the
parsytec)
For the hardware side, I use to host card, a IMS B004 and a little
editing done with four logic gates 74LS31 and 74LS32, to convert the
INmos LINK to UniLink.
On Sofware Side, on MsDOS. I use the Parsytec Mtool to boot the NCU,,
and the NCM tool to configure the cluster topologie.
For a complete boot, the parsytec documentation give this order :
1°/ Connect link 3 of the host (B004) to the "ConfigIn" of the
parsytec
2°/ Boot the NCU (that consiste to load the Network configuration
Manager on the NCU)
some possibility for that, on Heliso with "boot_ncm", on dos, there
are two possibilities...
the first non interactive who load direcly the software on NCU, and
the second interactive by a occam tool (call Mtool)
3°/ Unconnect ling 3 from ConfigIN
4°/ Connect Link 2 of the host to a UserEntry link on parsytec
5°/ Load a network topologie on the parsytec (by the user Entry), Two
possibilities too, by a non interactive methode or by the Mtool
On Helios, that done by a software "Hconfig"
So for 1 and 2, on MsDOS or Helios, no proplem, all work's !
but for 5... nothink work...
Curently, the only methode i have fond to configure a network, Is to
configure everything manually, one link at a time...
Forl this, i connect the link 3 of my host transputer from B004 to the
"ConfigIn" on the MT2. And use the Mtool. but that not the normal
procedure.
Normaly a tool from the Mtool can load a fully network easily in one
time from a script. but this tool never found the NCU...
(The Parsytec Documentation give the correct connection. Normaly i
need to use the link 2 of the host transputer connected on One USer
Entry on the Parsytec for this application...)
On Helios... I can just boot the NCU, the software "Hconfig" don't
work.
when i call "Hconfig" Helios answer :
%hconfig
/helios/bin/hconfig : Exec format error.
%
So there is still work!
Best Regards
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
30 janvier 2011 from (comp.sys.transputer)
A lot of good news today.
to date, I redid a small conversion interface B004 <==> Parsytec with
2 and 2 26LS31 26LS32.
I retrieve the corresponding microkernel of my Multicluster 2
(T4M32.bin) in PARIX and use them in the NCM in Helios. The 2 NCU boot
with no errors
Next tape : load a topologie on the NCU.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
7 janvier 2011 from (comp.sys.transputer)
Hi Mike
thank you for this details !
one less thing to worry, now I xon connect the B004 link to on 10MB/S
on Parsytec
Somone have send me the MCM2-11 documentation this night so the 4x3
block are for the error control
I find too a scaneed engenering Datasheet of the IMS T800, do you want
it ?
- Damien
PS: i need to remake my litle website for include all Transputer
document !
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6 janvier 2011 from (comp.sys.transputer)
Mike B.
Hi!
A quick continuity tester session on my MTM2-11 Rev 1.0 yield for the
8x3 jumper block:
(please use a fixed font to see my drawings)
Component side up, the frontpanel is left, the 96-way DIN connector
right.
__VCC
/ _____MemAD4 (3 cycle)
/ / ____MemAD6 (5 cycle)
O-O-O-O-O-O O O
1 2 3 4 5 6 O-O----MemConfig
O-O-O-O-O-O O O____MemAD7 (6 cycle)
\ \_____MemAD5 (4 cycle)
\__GND
1 .. LinkSpecial
2 .. Link0Special
3 .. Link123Special
4 .. ProcSpeedSelect0
5 .. ProcSpeedSelect1
6 .. ProcSpeedSelect2
Don't connect more than one MemAD to MemConfig!
Example:
O O O O O O O O
| | | | |
O O O O O O O O
| |
O O O O O O O O
* all links at 20MHz
* transputer speed 30Mhz
* 4 cycle memory configuration (60ns)
-Mike
PS: The 4x3 block is unknown.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6 janvier 2011 from (comp.sys.transputer)
Hello boy !
I have a Parsytec Multicluster 2 since 6 years but I never found à
card host. I find a B004 resently and I seek how to communicate with
the Parsytec. (old post "what do with a Multicluster 2")
I instaled Helios 1.31 on the host PC and is running perfectly on the
B004.! ( \o/)
I know than Parsytec calbing are not Standard INMOS cabling (reset
link in and out on each link, and symetical link)
it seems that this is not very complicated to build a balanced /
unbalanced line With Some TTL gate (or Just With A diode).
But what do with the oser control signal ? (Analyse and Error) from
the B004 ?
i take all information about Multicluster 2 XBAR-L and XBAR-R,
internal cabling and so one !
My litle Box have this card :
16 x MTM2-11 : 2 node T800G25 with 2MBytes/node = 32 node T800G25 with
2MBytes/node
1 x GDS-2 (1xT800 and 1x G300 2MBytes VRAM, 2MBytes DRAM)
2 x XBAR-Reset level
2 x XBAR-Link Level
(i have MTM-2-11, unfortunably different that the MTM2 documentation
on RAM's site)
Best Regard
Damien