<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.ndwiki.org/index.php?action=history&amp;feed=atom&amp;title=DOMINO</id>
	<title>DOMINO - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.ndwiki.org/index.php?action=history&amp;feed=atom&amp;title=DOMINO"/>
	<link rel="alternate" type="text/html" href="https://www.ndwiki.org/index.php?title=DOMINO&amp;action=history"/>
	<updated>2026-05-10T04:39:49Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://www.ndwiki.org/index.php?title=DOMINO&amp;diff=2867&amp;oldid=prev</id>
		<title>Gandalf: Initial page</title>
		<link rel="alternate" type="text/html" href="https://www.ndwiki.org/index.php?title=DOMINO&amp;diff=2867&amp;oldid=prev"/>
		<updated>2016-06-18T06:26:34Z</updated>

		<summary type="html">&lt;p&gt;Initial page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;#039;&amp;#039;&amp;#039;DOMINO&amp;#039;&amp;#039;&amp;#039; is a range of high speed IO-controllers for [[ND-5000]] computers. DOMINO introduces new hardware and software architecture.&lt;br /&gt;
&lt;br /&gt;
The DOMINO Controllers are connected to the common [[Multi-Function bus|MF-Bus]] memory (former [[MPM-5]]). Each controller is capable of transferring data to and from this memory via [[DMA]]. Synchronization between controllers and CPU:s is done via semaphore cycles.&amp;lt;ref&amp;gt;{{ND-doc|820026.1|preface}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Physical Implementation ==&lt;br /&gt;
&lt;br /&gt;
A DOMINO Controller is built according to common specifications. The local CPU is a 68020 running [[DOMINOS]], an operating system kernel.&lt;br /&gt;
DOMINO cards fits into the MF-bus crate and has a MF-bus controller. The MF-bus controller have a connector where a terminal can be connected for configuration and maintenance purpose.&lt;br /&gt;
&lt;br /&gt;
=== Local Memory ===&lt;br /&gt;
&lt;br /&gt;
A DOMINO controller can have between 1/2 to 8 Mbyte local memory with parity.&lt;br /&gt;
&lt;br /&gt;
=== Status LED ===&lt;br /&gt;
&lt;br /&gt;
A DOMINO controller has at least three LED:s in different colors.&lt;br /&gt;
* Yellow, shows activity of the 68020 controller. It shows running or idling.&lt;br /&gt;
* Green, shows if the application is running or not.&lt;br /&gt;
* Red, shows an error condition by flashing different patterns.&lt;br /&gt;
** Off, no errors detected.&lt;br /&gt;
** Constant on, selftest found some error after reset.&lt;br /&gt;
** Fast flashing (on and off in 0,5s pulses), OPCOM receives a NAK when expecting a ACK.&lt;br /&gt;
** Short one long off, something unusable received from OCTOBUS.&lt;br /&gt;
** Two short on one long off, error returned when connecting to OMD.&lt;br /&gt;
** Three short on one long off, MPROTSET returns error when setting up memory protection.&lt;br /&gt;
** One long and two short on, host switch stack is empty, nobody to send to.&lt;br /&gt;
** One long and three short on, OCTOBUS driver interface called with invalid function code.&lt;br /&gt;
** One long and four short on, OCTOBUS driver returns error when connecting to emergency message 177B or 176B.&lt;br /&gt;
** One long and seven short on, the path used in OPCOM is unknown.&lt;br /&gt;
** Regular very slow flashing, error returned from OCTOBUS driver when sending.&lt;br /&gt;
** Regular flashing long on short off, overflow on the host switch stack.&lt;br /&gt;
&lt;br /&gt;
== Software components ==&lt;br /&gt;
&lt;br /&gt;
[[PROMAN]], short for PROcessor MANager, is a server process running on ND-100. It is started immediately after system start and is responsible for booting the DOMINO controllers. Requests to PROMAN are sent by [[NUCLEUS]].&lt;br /&gt;
Configuration of DOMINO controllers are made either automatically via predetermined images or manually via a configuration file.&lt;br /&gt;
Configuration is normally done at system integration to suit the customers need but can be changed by field technicians.&lt;br /&gt;
&lt;br /&gt;
== Module numbers ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Module Number !! Hardware-id !! Type of module&lt;br /&gt;
|-&lt;br /&gt;
| 5B || VMEI || VME-bus interface&lt;br /&gt;
|-&lt;br /&gt;
| 20B || IPI3 || IPI level III controller&lt;br /&gt;
|-&lt;br /&gt;
| 21B || SCSI || SMDE controller (SCSI)&lt;br /&gt;
|-&lt;br /&gt;
| 22B || ETH3 || Ethernet III&lt;br /&gt;
|-&lt;br /&gt;
| 23B || FPS5 || FPS-5000 controller&lt;br /&gt;
|-&lt;br /&gt;
| 24B || TERM || Terminal controller&lt;br /&gt;
|-&lt;br /&gt;
| 25B || GRAP || Graphical controller&lt;br /&gt;
|-&lt;br /&gt;
| 26B || MFCC || Multi function comms controller&lt;br /&gt;
|-&lt;br /&gt;
| 27B || VMEC || VME-bus controller&lt;br /&gt;
|-&lt;br /&gt;
| 30B || DMAC || MF-DMA controller&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
[[Category:Glossary]]&lt;/div&gt;</summary>
		<author><name>Gandalf</name></author>
	</entry>
</feed>