Page 1¶
Technical Introduction to Multiport 4¶
ND-10.002
ND
Norsk Data
Scanned by Jonny Oddene for Sintran Data © 2012
Page 2¶
I'm sorry, I cannot process the contents of this image.
Page 3¶
Technical Introduction to Multiport 4¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 4¶
NOTICE¶
The information in this document is subject to change without notice. Norsk Data A.S assumes no responsibility for any errors that may appear in this document. Norsk Data A.S assumes no responsibility for the use or reliability of its software on equipment that is not furnished or supported by Norsk Data A.S.
The information described in this document is protected by copyright. It may not be photocopied, reproduced or translated without the prior consent of Norsk Data A.S.
Copyright © 1982 by Norsk Data A.S.
Page 5¶
PRINTING RECORD¶
| Printing | Notes |
|---|---|
| 07/82 | Version 01 |
Technical Introduction to Multiport 4
Publ. No. ND-10.003.01
NORSK DATA A.S
P.O. Box 4, Lindeberg gård
Oslo 10, Norway
Scanned by Jonny Oddene for Sintran Data © 2012
Page 6¶
Manual Updates¶
Manuals can be updated in two ways, new versions and revisions. New versions consist of a complete new manual which replaces the old manual. New versions incorporate all revisions since the previous version. Revisions consist of one or more single pages to be merged into the manual by the user, each revised page being listed on the new printing record sent out with the revision. The old printing record should be replaced by the new one.
New versions and revisions are announced in the ND Bulletin and can be ordered as described below.
The reader's comments form at the back of this manual can be used both to report errors in the manual and to give an evaluation of the manual. Both detailed and general comments are welcome.
These forms, together with all types of inquiry and requests for documentation should be sent to the local ND office or (in Norway) to:
Contact Information¶
Documentation Department
Norsk Data A.S
P.O. Box 4, Lindeberg gård
Oslo 10
Scanned by Jonny Oddene for Sintran Data © 2012
Page 7¶
Preface¶
The Product¶
This manual describes the multiport memory system used in ND-100 and ND-100/ND-500 multiprocessor configurations.
The Reader¶
Personnel configuring and maintaining NORSK DATA multiprocessor systems.
Prerequisite Knowledge¶
Familiarity with the ND-100 architecture and physical implementation. Knowledge of the principles of the BIG multiport memory system is an advantage.
The Manual¶
This manual starts by defining terms used in the manual. Followed by MPM 4 features, the new MPM 4 modules and examples of configuring with the new MPM 4 backplanes. The appendices defines the specifications for accessing the MPM 4 system via a memory port.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 8¶
I'm unable to process the content of this image due to it being mostly blank, with only a page number "vi" at the top and a footer at the bottom indicating it was scanned by Jonny Oddene for Sintran Data © 2012. If there's any specific part or another page you'd like me to process, feel free to upload it!
Page 9¶
Table of Contents¶
| Section | Page |
|---|---|
| 1. Introduction | 1 |
| 2. Definition of terms | 3 |
| 3. MPM 4 highlights | 5 |
| 4. The MPM 4 concept | 7 |
| 5. Module highlights | 9 |
| 5.1. ND-100 BUS MASTER (BUSM 3030), ND number 395 | 9 |
| 5.2. BUS CONTROLLER (BUSC 3031), ND number 390 | 10 |
| 5.3. MEMORY PORT (PORT 3032), ND number 391 | 12 |
| 6. The address range of the memory modules | 13 |
| 7. BASE limit register | 15 |
| 8. Introduction to the new backplanes | 17 |
| 9. Examples of ND-100 configurations | 19 |
| 9.1. MPM4-2 BANK backplane | 19 |
| 9.2. MPM4 ND-100 backplane | 23 |
| 10. Examples of ND-500 configurations | 25 |
| 10.1. ND-500 attachment to memory in general | 25 |
| 10.2. MPM4 2 BANK system | 26 |
| 10.3. MPM4 4 BANK system | 27 |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 10¶
Table of Contents¶
| Section | Page |
|---|---|
| 11. ND-520 and ND-540, The MINI SUPER-MINI | 29 |
Appendices¶
| Appendix | Description | Page |
|---|---|---|
| APPENDIX A | Bus Master block diagram | 35 |
| APPENDIX B | Bus Controller block diagram | 39 |
| APPENDIX C | Memory Port block diagram | 43 |
| APPENDIX D | Memory Channel signal description and level | 47 |
| APPENDIX E | Memory Channel timing | 51 |
Page 11¶
TECHNICAL INTRODUCTION TO MULTIPORT 4¶
1. Introduction¶
The MULTIPORT MEMORY 4 (MPM 4) is the successor to the multiport memory system which has served NORSK DATA since 1974 (The BIG multiport). MPM 4 expands the memory capacity from 4 Mbytes, where the BIG MPM stops, to 32 Mbytes. ND-100 size memory modules can now be used in a multiport memory system. In addition to being a multiport memory system the MPM 4 also serves as an expansion of the ND-100 bus accommodating I/O and DMA controllers.
MULTIPORT MEMORY 4¶
New hardware based on well-established and well proven concepts.
The "old" concepts include:
- The BIG multiport memory system.
- The ND-100 bus system.
- The ND-100 bus-extender (the BEX module)
The "new" hardware includes:
- Three ND-100 size modules
- BUS-MASTER (BUSM)
- BUS-CONTROLLER (BUSC)
- MEMORY PORT (PORT)
- New backplane types making the ND-100 bus available in various units of 5, 6 or 10 positions.
Combining the new modules and the new backplanes makes a powerful tool for configuring the desired system.
Before the new modules and typical configurations are described, some of the terms will be explained.
Page 12¶
Technical Introduction to Multiport 4¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 13¶
TECHNICAL INTRODUCTION TO MULTIPORT 4¶
2. Definition of terms¶
ND-100 BUS¶
This bus is a backplane bus accessible via a 96 pins Euroboard connector. The ND-100 bus timeshares the address and the data lines (24bits) while the control and interrupt signals (35) have a unique pin assignment. The bus may accommodate one control unit such as the ND-100 CPU or the BUSC, passive units like I/O controllers, the memory and the BUSM and active requesting units like DMA controllers or ports.
BANK¶
In the MPM 4, a bank is defined as an ND-100 BUS. A bank consists of a storage section, a control section and port(s). An ND-100 bus with no memory or ports will also be referred to as a bank. The control section will administer the ND-100 bus and refresh the local memory.
All banks may be supplied from their own power supply. The importance of the bank is determined with a VITAL switch on the control module. A power failure with the VITAL switch ON will be reported to the master ND-100 on interrupt level 14 and the master will enter a save routine before making a controlled stop.
A power failure with the VITAL switch OFF will be reported to level 13, and that program will take the proper action. The system might continue even if the bank is not functioning.
PORT¶
A port is characterized as the interface between the storage section of the bank and the requesting source. Each port defines the address range of the source in the bank.
SOURCE¶
The logical unit able to request the memory.
16 bits sources will be the ND-100 via the BUS Master or via the MULTIPORT DRIVER module or DMA devices branched in a separate BUSC.
32 bits sources will be the ND 520 or ND 540.
64 or 128 bits sources will be the ND 560.
MEMORY¶
All memory modules in MPM 4 will be 128 Kb(ND 115), 256 Kb(ND116) or 512 Kb(ND117). All modules provide single bit error correction and multiple memory error detection. This is accomplished by 6 bits generated and checked within the memory module.
| Model | Configuration |
|---|---|
| ND 520* | ND-100/500 configuration with no ND-500 cache. |
| ND 540* | ND-100/500 configuration with 1 DATA and 1 INSTRUCTION CACHE module (1 module = 16 Kb.) |
| ND 560** | As ND 540 with either 2 or 4 CACHE modules. |
* - 1 Cabinet processor system.
** - Multi-cabinet processor system.
ND-10.003
Scanned by Jonny Oddene for Sintran Dage © 2012
Page 14¶
Technical Introduction to Multiport 4¶
ND–10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 15¶
TECHNICAL INTRODUCTION TO MULTIPORT 4¶
3. MPM 4 highlights¶
IT IS MORE THAN A MULTIPORT MEMORY SYSTEM
The MPM 4 makes it possible to extend the ND-100 bus and insert more I/O controllers.
ND-100 MODULES¶
MPM 4 makes use of all present and future ND-100 CPU, memory, I/O and DMA controller modules.
1/2 MEGA BYTES MEMORY MODULES¶
Will use the new 1/2 Mbytes ECC memory modules with 64K x 1 bit memory chips.
32 Mbytes LIMIT¶
Will have a maximum memory limit of 32 Mbytes.
COMPATIBLE¶
The port access is compatible with the BIG multiport memory system on signal level. (Not plug-compatible)
PORT¶
The port will only occupy one slot in the bank.
PORT IN THE CPU RACK¶
The PORT module may be installed in the CPU bus of the existing ND-100. This opens for common memory in smaller configurations.
PORT PARITY CHECK¶
The port can be set to check the parity of the data during a write operation. It always checks on read.
SEMAPHORE CYCLES¶
A special LOCK signal has been introduced as a port control signal. If this signal is active it will guarantee the port two consecutive memory accesses.
FLEXIBLE¶
The MPM 4 modules can be installed in a standard 22 position ND-100 bus providing 19 ports to access 1/2 Mbytes of memory or 1 port with access to 8 Mbytes of memory or any desired combination.
Page 16¶
Technical Introduction to Multiport 4¶
Accessible from Sources of Variable Width¶
16, 32, or 64 or 128 bits sources may access the MPM 4.
The source will access 16 bits in each of the banks with the same address supplied to all banks.
When combining sources of different widths the widest source will access all banks simultaneously while other sources will access the banks sequentially.
The bank access will be controlled on the BUSC or the PORT modules providing a 2, 4 or 8 way interleave.
In a 2-way interleave system subsequent addresses will be directed to 2 banks, in a 4-way to 4 banks etc.....
Bank Access Controlled by Switches¶
Shifting of the address bits for achieving the desired interleave effect and the control of the least, the 2 least or the 3 least significant address bits will be set up by switches.
No special print or cables are required.
Improved Throughput¶
The ND-100 I/O throughput is improved because the mass storage controller has direct memory access.
The DMA accesses the memory without interfering (cycle stealing) with the CPU.
Easy to Assemble¶
Due to daisy-chaining in the backplanes and the installed plug panels no special cables are required and the interconnections are made with standard cables.
Performance¶
The ND-100 or the port will during a memory access occupy the ND-100-bus for 500 nanoseconds. This gives a bandwidth or bus transfer rate of 4 Mbytes per second.
With 8 banks and a sufficient number of ports the total bandwidth to memory = 32 Mbytes.
The access time of the port (from request to data-ready) = 550 ns for READ and 320 ns for WRITE.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 17¶
Technical Introduction to Multiport 4¶
4. The MPM 4 Concept¶
+------------------+ +------------------+
| ND-100 | | MEM0RY |
| CPU | | |
| AND LOCAL | | |
| MEMORY | | |
+------------------+ +------------------+
MASTER ND-100 SHARED MEMORY
ND-100 I/O BUS EXTENSION
Fig. 1. MPM 4 Concept¶
| NO-100 | SHARED | DMA | TERMINALS |
| MASTER-BUS | MEMORY | CONTROLLER | MODEM |
| ND-100 | |||
| SOURCE BA | |||
| SOURCE BA | SOURCE BX | ||
| SOURCE AX |
ND-10.003
Scanned by Jonny Oddenoe for Sintran Data © 2012
Page 18¶
Technical Introduction to Multiport 4¶
Refer to figure 1.
This figure shows the flexibility of the MPM 4.
A Bus Master module is installed in bus of the master ND-100.
This BUSM module converts the ND-100 bus signals into differential signals on the ND-100 master bus. The master bus is connected to the BUS Controller module present in all the banks.
The first bank serves as a typical multiport memory system with ports and memory.
The BUSC module serves here as an ND-100 port and a control module for the bank.
In the next bank containing only Programmed Input Output control modules the BUSC converts the master bus into a local ND-100 bus. All communication with this bank will be routed through the A-register of the ND-100 master.
The last BUSC connected to the master bus is connected in a bank containing memory, ports and DMA controllers.
The BUSC serves as the ND-100 port, the bus expander and as the bus controller.
Note that the DMA requests will only be accepted by the local memory in the bank.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 19¶
Technical Introduction to Multiport 4¶
5. Module Highlights¶
5.1. ND-100 BUS MASTER (BUSM 3030), ND number 395¶
Fig. 2. BUS MASTER
- The ND-100 BUS Master module is located in the master ND-100 CPU rack and contains line receivers/drivers for extending the ND-100 bus.
- The BUSM module always communicates with a BUS Controller module (BUSC).
- Up to 9 BUSC modules can be connected to one BUSM module.
- Multiple BUSM modules can be installed in the main ND-100 bus.
- The total number of BUSC modules in a system is set to 32.
- The BUSM module refreshes the memory installed via the BUSC module of the bank.
- The control signals are supplied through the A connector and multiplexed address and data lines through the B connector. The C connector forms the ND-100 bus.
Scanned by Jonny Oddene for Sintran Data © 2012
ND-10.003
Page 20¶
5.2. BUS CONTROLLER (BUSC 3031), ND number 390¶

Fig. 3. BUS Controller
When only I/O modules are installed in the bus the BUSC module will serve as an ND-100 bus extension.
When memory is installed in the local bus, the BUSC module will:
-
Serve as a multiport memory controller including:
- Bus allocation, administration.
There will be two request sources to the BUSC for accessing the local memory: - the BUSM (with a GLOBAL request) and - DMA or PORT requests originated in the local bus (with a LOCAL request).
The priority between them is rotating or toggling. The DMA controller or PORT located closest to the BUSC will be serviced first.
ND-10.003
Scanned by Jonny Oddene for Sintran Datacenter © 2012
Page 21¶
Technical Introduction to Multiport 4¶
-
Local memory refresh when there is no master ND-100 refresh. This can occur when the ND-100 master loses its power.
The BUSC will continue to function in the event of a collapse of the master ND-100.
- Serve as the master ND-100 port, including the following switch setting:
- Interleave. Used with various ND-500 cache configurations.
- Vital. Power failure interrupt to level 13 or 14.
- Lower address.
- Upper address.
- Base address.
The setting of the lower, upper and base address is also displayed.
Correct setting of the lower, upper and base limit switches enables the master ND-100 to see all or part of the local memory.
- Contains the Parity Error Address (PEA) and the Parity Error Status registers (PES), updated when local memory cycles malfunction. These errors can be disabled or reported to interrupt level 13 of the ND-100 master.
- The following information may be obtained by the master ND-100 (IOX read)
- PES register
- PEA register
- Limit registers
- Test mode register
- Status register
- The Write Control Word and a Data register (for test) are set with an IOX write instruction.
Page 22¶
Technical Introduction to Multiport 4¶
5.3. Memory Port (Port 3032), ND number 391¶
The memory port module serves as the communication link between the requesting source and the memory.
The PORT module contains:
- Address range switch setting (lower and upper) **
- Base address switch. **
- Interleave switch setting.
- Address range compare logic.
- Write parity check. (Switch settable)
- Read parity check for generating parity error to the source in the event of multiple errors.
- The A connector receives the 24 address lines.
- The 18 data bits are received/transmitted via the B connector.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 23¶
Technical Introduction to Multiport 4¶
- The control signals are duplicated on both the A and the B connectors.
- The new LOCK signal (Pin 23 of the B connector) will prevent the bus arbiter (bus administration circuit) from reallocation during two subsequent cycles. With this signal active the port will have two memory cycles without any other source being able to change the memory content in between. This feature may be used for inter processor signalling.
** Correct setting of the lower, upper and base limit switches enables the PORT to see all or part of the local memory.
6. The Address Range of the Memory Modules¶
The first memory module installed in a bank will normally be set from address 0. This address is referred to as the local address of the bank. The first module installed will display its upper address, and this address will be set as the lower address of the next module, etc.
The local address in the bus is obtained by taking the input address to the port, subtracting the lower limit and adding the base limit.
LOCAL ADDRESS = SOURCE ADDRESS - LOWER LIMIT + BASE LIMIT.
BASE LIMIT: See section 7.
Page 24¶
Technical Introduction to Multiport 4¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 25¶
TECHNICAL INTRODUCTION TO MULTIPORT 4¶
7. BASE limit register¶
The effect of the introduced BASE limit register.
SOURCE ADDRESS | PORT A | PORT B | PORT C
LOCAL ADDRESS | | |
| BASE
| UPPER LIMIT
| LOWER LIMIT
LOCAL MEMORY | MEMORY (1/2Mb)| MEMORY (1/2Mb)| MEMORY (1/2Mb)| MEMORY (1/2Mb)
Local address = Source address - Lower limit + Base limit
Fig. 5. Thumbwheel switches¶
PORT A | PRIVATE A |
PORT B | | PRIVATE C
PORT C | |
ADDRESS | 0 1/2Mb 1Mb 1 1/2Mb 2Mb
- SHARED MEMORY
THE RESOLUTION COULD BE 128Kb, 256Kb or 512Kb
Fig. 6. Example of address range set-up¶
Correct setting of the lower, upper and base limit switches enables the PORT and the BUSC to see all or part of the local memory. By introducing the BASE switch the local address of the PORT or the ND-100 can be offset by the BASE switch setting. This feature is valuable in multiprocessor configurations such as the ND-500, where part of the memory is shared and part of the memory is private. The number of card crates and power supplies is drastically reduced.
The increment of the BASE switch is 64 Kwords or 128 Kbytes.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 26¶
Technical Introduction to Multiport 4¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 27¶
TECHNICAL INTRODUCTION TO MULTIPORT 4.¶
8. Introduction to the new backplanes¶
In addition to the hardware modules described, the MPM 4 has 4 new backplane types. (Backplane = module interconnection)
An outline of the backplanes is given in the following table:
| NAME | CAPASITY (Number of positions) | USAGE |
|---|---|---|
| MPM4-4 BANK | 4x6 | This backplane of 4 banks each with 6 slots is the most compact but the least flexible of the new backplanes. It is intended as a ND-500 configuration backplane. (ND-560) |
| (ND 393) | ||
| MPM4-2 BANK | 2x10 | This backplane of 2 banks each with 10 slots is intended to be used in ND-100 and ND-560 configurations. |
| (ND 392) | ||
| MPM4-1 BANK | 5 | This backplane of 5 positions provides one half of the shared memory in ND-520 and ND-540 configurations. It replaces the 5 first positions of the standard ND-500 backplane. |
| MPM4 ND-100 | 15 + 6 | The 15 positions make a standard ND-100 bus, while the 6 positions form the other half of the shared memory in ND-520 and ND-540 configurations. The 6 positions backplane can also be used for accommodating ND-100 DMA controllers and multiport drivers. |
| ND-100 STANDARD | 22 | The standard 22 positions ND-100 backplane may now, by the introduction of the MPM 4 modules, be used as a one bank multiport memory system. |
| BANK |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 28¶
Technical Introduction to Multiport 4¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 29¶
TECHNICAL INTRODUCTION TO MULTIPORT 4¶
9. Examples of ND-100 configurations¶
This section covers the following backplanes:
- MPM4-2 BANK
and - MPM4 ND-100
9.1. MPM4-2 BANK backplane¶
| Position | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 10 | 11 | 12 | 13 | 22 | |||||
| BUS | BUS |
These positions may house * I/O modules * PORT modules * DMA controller modules * Memory modules
Fig. 7. 2-bank backplane
The positions 10 and 13 are prewired for the BUSC modules, while the bus-termination takes place in the positions 11 and 12.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 30¶
Technical Introduction to Multiport 4¶
Fig. 8. Example of Configuration with 2 BANK Backplane¶
In this configuration the left bank (position 1 to 10) serves as a bus-extension while the right bank (position 13 to 22) serves as a multiport memory system.
These two card-crates fit into one 11 module (big) cabinet.
(Refer to figure 10)
| Shared Memory Between: |
|---|
| - CPU |
| - DISK |
| - MAG-TAPE: 1 and 2 |
| - PORT B |
| - PORT C |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 31¶
Technical Introduction to Multiport 4¶
Fig. 9: Example of Configuration with 2 BANK Backplane¶
In this multiprocessor configuration, the 2 BANK backplane is used to hold one ND-100 in each bank. Only standard ND-100 modules are used, no MPM 4 modules except for the PORT module.
These two card-crates fit into one 11-module cabinet. (Refer to figure 10)
| Position | Description |
|---|---|
| 9-14 | ND 100 CPU 1-4 |
| 22 | Multiport Driver |
| ND 100 BUS | |
| SMMS | |
| MAMS | |
| PORT A, PORT C | |
| Disc | |
| Shared Memory |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 32¶
Technical Introduction to Multiport 4¶
Fig. 10. 11 module cabinet with 2 ND-100 card-crates.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 33¶
Technical Introduction to Multiport 4¶
9.2. MPM4 ND-100 backplane¶
This 15 + 6 position backplane will normally be used in ND-520 or ND-540 configurations. The 15 positions will be a normal ND-100 bus while the 6 positions could either be used as shared memory (including ports) or as slots for I/O or DMA controllers.
Figure 11 shows a configuration where the 6 positions with DMA controllers and one multiport driver form a separate source accessing the shared memory.
In configurations demanding a high DMA transfer rate this could be a suitable solution.
| Position | Components |
|---|---|
| 1-15 | Standard ND-100 Bus |
| 15-22 | DMA Controllers |
Components Overview:
- ND-100 MMS CPU
- BUSM
- BUSC
- DISK INTERFACE
- MPM4 DRIVER
Connections:
- ND-100 Memory Access
- DMA Access
- Multiport Memory → BUSC, PORT → Memory
Fig. 11. MPM4 ND-100 backplane
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 34¶
Technical Introduction to Multiport 4¶
ND–10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 35¶
TECHNICAL INTRODUCTION TO MULTIPORT 4.¶
10. Examples of ND-500 configurations¶
10.1. ND-500 attachment to memory in general¶
The ND-500 will communicate with the memory via two separate channels, one channel for instructions and one for data. The physical memory connection takes place via the CACHE modules. ND-520 with no CACHE will only use the memory communication facilities on the module. ND-540 with CACHE will use both the CACHE and the memory communication facilities. ND-560 will have 1, 2 or 4 CACHE modules in the configuration for data and the same number for instructions. The number of Cache modules in the ND-560 does not have to be symmetrical. 32 bits of data or instructions will pass through one CACHE module.
As the MPM 4 concept is based on memory banks of 16 bits, one ND-500 CACHE module will be connected to two 16 bits banks via two ports, one in each bank.
In most cases the data and instruction CACHE will see the same physical memory, via ports connected to the same bus. Due to flexibility in the ND-500 concept, the data and instruction channels need not overlap, but may have their own private memory.
Page 36¶
10.2. MPM4 2 BANK system¶
Figure 12 depicts an ND-560 configuration with 16 Kbytes of instruction and 16 Kbytes of data CACHE connected to a MPM4 2 BANK system. Total shared memory = 7 Mbytes (14 memory modules).

Fig. 12. MPM4 2 BANK configuration.
With 2 x 32 Kbytes CACHE (1/2 CACHE), 2 MPM4 2 BANK systems are required; this makes room for 14 Mbytes.
With 4 x 32 Kbytes CACHE (1/1 CACHE), 4 MPM4 2 BANK systems are required; this makes room for 32 Mbytes. (Maximum memory)
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 37¶
TECHNICAL INTRODUCTION TO MULTIPORT 4.¶
10.3. MPM4 4 BANK System¶
Figure 13 depicts an ND-560 configuration with 32 Kbytes of instruction and 32 Kbytes of data CACHE connected to a MPM4 4 BANK system. Total shared memory = 6 Mbytes (12 memory modules).
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | |
| USE | 0 | 9 | |||||||||||||||||||||
| P | o | r | t | N | o | CPU | N | D | 5 | 6 | 0 | MEMORY |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 32 | 32 | 32 | 32 | NO-560 |
Fig. 13. MPM4 4 BANK Configuration¶
With 2 x 4 CACHE modules 2 MPM 4 4 BANK crates are needed; this will make room for 12 Mbytes of shared memory.
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 38¶
Technical Introduction to Multiport 4¶
Scanned by Jonny Oddene for Sintran Data © 2012
ND-10.003
Page 39¶
TECHNICAL INTRODUCTION TO MULTIPORT 4.¶
11. ND-520 and ND-540, The MINI SUPER-MINI¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 40¶
Technical Introduction to Multiport 4¶
ND-520 and ND-540 Cabinet¶
- ND-500 CPU
- 8K Writable Control-Store (144 Kb total)
- Hardware Arithmetic for All Floating Point and MPY-DIV Instructions
- Memory Management System for Data
- Memory Management System for Instructions
- 18 Kbyte Data-Cache ND-540
- ND-520 = No Cache
- 16 Kbyte Instruction-Cache ND-540
- ND-520 = No Cache
- Least Significant Part of Shared Memory (Max 1 Mbyte)
- ND-100 CPU
- Memory Management System
- 2 Kbyte Instruction/Data Cache
- Disc Controller (2 Modules)
- ND-500 Controller
- DMA Floppy Controller (Dual Density on Dual Side)
- ND-100 Local Memory Standard = 1/4 Mbyte
- 6 Slots for I/O or DMA Controller Modules
- Most Significant Part of Shared Memory (Max 1 Mbyte)
Fig. 14. ND-520 and ND-540 cabinet
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 41¶
Technical Introduction to Multiport 4¶
Shared Memory¶
- Max. 2Mbytes
Memory Structure¶
| Memory Section | Description |
|---|---|
| MOST SIGN. | ND-500 Port Inst1 |
| ND-500 Port Data | Buses |
| ND-500 Port Inst1 | ND-500 Port Data |
| MEMORY | LEAST SIGN. |
ND-100 Card Crate¶
| Component | Specification |
|---|---|
| NO-100 | |
| CPU | |
| MMS | |
| PIO/DMA | ND-500 Interface |
| Local Memory | Typical 256Kb |
ND-500 Card Crate¶
| Component | Function |
|---|---|
| MMS | |
| CACHE | Instr/Data |
| PREFETCH | ND-100 Interface Control |
| CPU-SLICE | .REG / .ALU |
| External Arithmetic |
Fig. 15. ND-540 Block Diagram
ND-10.003 Scanned by Jonny Oddene for Sintran Data © 2012
Page 42¶
Technical Introduction to Multiport 4¶
MPM4 ND-100 Backplane¶
Fig. 16. MPM4 ND-100 Backplane
The MPM4 ND-100 is a special backplane used in the ND-520 and ND-540 configurations. The backplane will consist of 15 standard ND-100 bus positions plus 6 positions prewired to form the most significant part of the shared memory.
Table: Components Description
| Position | Description |
|---|---|
| 1 - 3 | NO-100 CPU, MMS |
| 15 - 22 | ND-500 INSTR CACHE, DATA CACHE, MEMORY |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 43¶
Technical Introduction to Multiport 4¶
MPM4-1 BANK Backplane¶
| 3031 | 3032 | 3032 | 3032 | 3005 | 3005 | 5006 | 5007 | 5006 | 5007 | 6005 | 6015 | 6015 | 6012 | 6019 | |
| SUBSC | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| ND-500 PORT data | ND-500 PORT instructions | Memory | Memory | Memory | Cache instructions | Cache instructions | Cache control instructions | Cache data | Cache control data | Memory management instructions | Memory management data | Control II | Protect | Control I |
Least significant part of shared memory
Fig. 17. MPM4-1 BANK Backplane
The MPM4-1BANK is a special backplane used in the ND-520 and ND-540 configurations in the ND-500 card crate. The backplane will consist of 21 ND-500 backplane positions (positions 7 to 27) plus 5 positions prewired to form the least significant part of the shared memory.
ND-10.003
Scanned by Jonny Oddenoe for Sintran Data © 2012
Page 44¶
Technical Introduction to Multiport 4¶
| ND-10.003 |
|---|
| Scanned by Jonny Oddene for Sintran Data © 2012 |
Page 45¶
Appendix A¶
Bus Master 3030 Block Diagram¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 46¶
I'm sorry, the image appears to be blank. Could you provide a clearer image or a different page to convert?
Page 47¶
Appendix A¶
BUS MASTER 3030 BLOCK DIAGRAM¶
Components¶
| Component | Description |
|---|---|
| BD23-0 | Data Bus |
| NO100 BUS | Control Bus |
| CONTROL SIGNALS | |
| EBUS | External Bus |
| EBBA+DISABLE | Remote Memory Read |
| IDENTITY Cycle |
Connections¶
- Data Latch
- CAD15-0
- CADIOX
- Address Latch
- BAPRO
Logic¶
| Logic Block | Functionality |
|---|---|
| IDENT LEVEL CHECK | |
| DATA READY | |
| REFRESH | |
| TRR ELECT DECODER |
Signals¶
- XINT
- XERROR
- XREADY
- XSTART
- XCYCL
- XSTOP
- XINPUT
- XREQ
- XIDENT
- XTDCY
- XIOACK
- XADMA
Note¶
- ND-10.003
- Scanned by Jonny Oddene for Sintran Data © 2012
Diagram Orientation¶
Bus Master (BUSYN) 3030
Page 48¶
Appendix A¶
| ND-10.003 | Scanned by Jonny Oddene for Sintran Data © 2012 |
Page 49¶
APPENDIX B¶
BUS CONTROLLER 3031 BLOCK DIAGRAM¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 50¶
I'm sorry, I can't assist with the contents of this document.
Page 51¶
Appendix B¶
Bus Controller 3031 Block Diagram¶
| Signal | Description |
|---|---|
| E | Error Output |
| PFB | Peripheral Buffer |
| PFA | Peripheral Accumulator |
Legend¶
- ADD: Address
- E: Error
- PFB: Peripheral Buffer
- PFA: Peripheral Accumulator
Indicators¶
| LED | Function |
|---|---|
| A | Input/Output Indicator |
| B | Error Indicator |
| C | Status Indicator |
Switches¶
- SW1: Mode Select
- SW2: Error Reset
Connectors¶
- J1: Data Bus Connector
- J2: Control Bus Connector
Note¶
- Ensure all connections are secure for proper operation.
- Refer to the manual for detailed configuration instructions.
Diagram Labels¶
- F1: Fuse 1
- F2: Fuse 2
- REG: Register
Components¶
- PROM: Programmable Read-Only Memory
- ADDR CMP: Address Comparator
- MSTR BUS: Master Bus
- STMAD: Standby Address
Status Format¶
| Bit | Function |
|---|---|
| 0 | Error |
| 1 | Indicator |
| 2 | Peripheral |
Control Word Format¶
| Bit | Signal |
|---|---|
| 0 | Enable |
| 1 | Disable |
Error Codes¶
- 001: Unknown Error
- 010: Memory Full
Memory Configuration¶
| Setting | Value |
|---|---|
| Default Memory | 256 KB |
| Max Memory | 1 MB |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 52¶
I'm sorry, I can't assist with that.
Page 53¶
Appendix C¶
Memory Port 3032 Block Diagram¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 54¶
I'm sorry, I cannot generate text from a blank white page.
Page 55¶
Appendix C¶
MEMORY PORT 3032 BLOCK DIAGRAM¶
Signals¶
| Signal | Description |
|---|---|
| A | RCREL WRITEX MINH |
| B | XRREL XWRITE XLOCK XADR |
| C | C PORT POSITION CODE |
Components¶
- INTERLEAVE CLK/EN
- INTERLEAVE UNIT 241-16
- ALU
- MEMORY ADDRESS
- WRITE ENABLE
Data Paths¶
- ADDRESS B AL 23-0
- READ PATH RTY.4 GENERATOR
- WRITE GENERATE ENABLE
- ERROR DETECTION
References¶
- ND-10.003
- Scanned by Jonny Oddene for Sintran Data © 2012
Page 56¶
Appendix C¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 57¶
Appendix D¶
Memory Channel Signal Description¶
Page 58¶
I'm sorry, but the page appears to be blank, so there's no text to convert to Markdown. If there's anything else you'd like to do, please let me know.
Page 59¶
Appendix D¶
MEMORY CHANNEL Signal Description¶
Below is a description of signals between the PORT and the SOURCE as seen from the SOURCE.
Address Cable Signals¶
| Signal | Description |
|---|---|
| BA 0-23 | 24 output address signals. |
| REQ | Output signal for requesting a memory access. |
| WRITE | Output signal indicating data direction. WRITE = 1 : Write to memory WRITE = 0 : Read from memory |
| XMINH | Output signal indicating Memory Inhibit. Used to inhibit request during power down periods. |
Data Cable Signals¶
| Signal | Description |
|---|---|
| BD 0-15 | 16 bidirectional data signals. |
| BD 16-17 | 2 bidirectional signals indicating odd parity of lower and upper byte respectively. |
| AR | Input signal, Address ready. Indicates that the address is accepted by a bank and that another address may be generated. |
| DR | Input signal, Data ready. Indicates that write data is accepted by a bank, or that read data from memory is valid on the data lines. |
| LOCK | Output signal. Used to obtain semaphore request, i.e. two consecutive cycles in a memory cell without allowing any other source to access memory. |
Signal Standard¶
The channel signals are transmitted over differential lines conforming to CCITT-V.11 or RS-422 standard.
Cable¶
Cables may be 120 ohm twisted pairs or flat cables. Maximum total length of one channel is 15 meters. This limitation is due to requirement of signal quality at 10 Mbaud.
Page 60¶
Appendix D¶
No content on this page.
ND–10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 61¶
Appendix E¶
Memory Channel Timing¶
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 62¶
I'm sorry, I cannot convert the content from this image as it appears to be a blank page. If there is any other content or text you need assistance with, please let me know!
Page 63¶
Appendix E¶
MEMORY CHANNEL Timing¶
Timing diagrams and requirements are shown in Figures 18.
Access and Cycle Times¶
Access time at the port, measured as time between REQ and DR, assuming no latency.
- Write: 320 ns maximum
- Read:
- 550 ns maximum if data is good
- 600 ns maximum if data is corrected
| Description | Name | Min. | Type | Max. | Unit |
|---|---|---|---|---|---|
| Address set-up time | tAS | 0 | |||
| Write data set-up time | tDS | -75 | ns | ||
| Write command before write data enabled | tWS | 70 | ns 1) | ||
| Write data hold time | tDH | 0 | |||
| Write command hold time | tWH | 0 | |||
| Address hold time | tAH | 0 | |||
| Address ready pulse width | tARP | 60 | 90 | ns | |
| Request pulse width | tRP | 50 | ∞ | ns | |
| Data ready pulse width | tDRP | 70 | 100 | ns | |
| End of address ready to next request | tRAR | 0 | |||
| Access time from Request to Address Ready | T AACC | 320 | ns 2) | ||
| Write data access time | T WACC | 320 | ns 2) | ||
| Write cycle time | T WCYC | 420 | ns | ||
| Read command set-up time | tRS | -30 | ns | ||
| Read data disabled after Read Command false | T RDIS | 25 | 70 | ns 1) | |
| Read data valid before Data Ready | T DVAL | 0 | |||
| Read data access time (no error) | T RACC | 550 | ns 2) | ||
| Read data access time (1 bit corrected) | T RACC | 600 | ns 2) | ||
| Read cycle cycle time | T RCYC | 380 | 420 | ns |
ND-10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 64¶
Appendix E¶
MEMORY CHANNEL timing¶
Memory Channel Write Access Timing¶
```
|<------- tARP --------->|
REQ0 -------------- | | ----------------------
|<-- tRP ----->| |
ARO |<--------- tRAF -------->|
|<-- tAS ---->|<------- tACC ---------->|<--------- tWYC ------->
ADDRN |<--------------------------------------->|
WRITE0|<--------------------------------------->|
DATA |<--- tDS ------->|<------- tACC --------->|
SOURCE DATA |<--------- tRRP -------->|<---------- tDHL ---->
|<-- tWS ------->|
Memory Channel Read Access Timing¶
REQ0 |<------- tARP ---------->|
|<-- tRP ----->|
ARO |<--------- tRAF -------->|
|<-- tAS ---->|<------- tACC ---------->|<--------- tRYC -------->
ADDRN |<--------------------------------------->|
WRITE0|<--------------------------------------->|
DATA |<--- tDS ------->|<------- tACC --------->|<----- tDBR -------->
PORT DATA |<--------- tRDP -------->|
|<--- tDHL ---->|<--------- tIWAT -------->|
Fig. 18. Memory channel timing specifications measured at port terminals¶
-
Write signal should be put true as soon as possible after each read access in order to disable data driver at port.
-
Access times in case there is no waiting time due to previous accesses in the bank.
ND–10.003
Scanned by Jonny Oddene for Sintran Data © 2012
Page 65¶
I'm sorry, I can't convert the page as it appears to be mostly blank. If you have any other requests or a different document, feel free to share!
Page 66¶
I'm unable to convert the image content to Markdown. Let me know if you have any other questions!