This SYS68K/CPU-30 R4 Technical Reference Manual provides a
comprehensive guide to the CPU-30 R4 board you purchased from
FORCE COMPUTERS. In addition, each board delivered by FORCE
includes an Installation Guide.
CAUTION: Before installing the board, please read the complete
installation instructions.
1.1.1SYS68K/CPU-30
R4 Technical
Reference Manual
Set
1.1.2Overview of the
Manual
When purchased from FORCE, this set includes the SYS68K/CPU-30 R4
Technical Reference Manual, a copy of the circuit schematics, and copies
1. The FDC37C65C is pin-to-pin compatible with Industry Standard
WD37C65C
Section 1 provides a brief overview of the product, the specifications, the
ordering information, and the publication history of the manual.
Information concerning the installation, default configuration,
initialization, and connector pinouts is included in Section 2. A detailed
hardware description is described in Section 3. The CPU board operates
under the control of VMEPROM, which is described in Sections 5, 6, 7,
8, and 9. There is additional space allocated in the manual for user notes,
modifications, etc.
1)
NOTE: Please take a moment to examine the Table of Contents of the
i
SYS68K/CPU-30 R4 Technical Reference Manual to see how this
documentation is structured. This will be of value to you when looking
for information in the future.
This CPU board is a high performance single-board computer based on
the 68030 microprocessor and the VMEbus. The CPU board also
includes an enhanced Floating Point Coprocessor 68882. The board
design utilizes all of the features of the powerful FORCE Gate Array
FGA-002.
The CPU-30 R4 provides an A32/D32 VMEbus interface including
DMA, up to 32 Mbyte shared DRAM on-board, up to 8 Mbyte System
Flash Memory, an Ethernet Interface, a single-ended SCSI interface, a
floppy interface, four RS-232 serial I/O channels, up to 256 Kbyte
SRAM and a Real-Time Clock, both with on-board battery backup.
Besides the CPU-30 R4, there will be a CPU-30Lite R4 without a
coprocessor, a SCSI, an Ethernet, and a floppy disk interface.
SEE ALSO: Please refer to Table 2, “Ordering Information,” on page 9
☞
for more detailed information.
1.2.1Features of the
CPU-30 R4
The shared DRAM is accessible from the 68030 CPU, the FGA-002
DMA controller, and also from other VMEbus masters.
The CPU-30 R4 has an Ethernet port and three serial ports available on
the front panel permitting a console port, download and data
communication channels. One further serial port, as well as the SCSI
interface and the Floppy interface are available via the 3-row VMEbus P2
connector. A 20-bit parallel interface and the three serial ports on the
front panel are available via the optional 5-row VMEbus P2 connector.
The main features of the SYS68K/CPU-30 R4 board are listed below.
Processor
- 68030 with 25 MHz frequency
- Flexible high bandwidth synchronous bus
- 68020 compatible integer unit
- Memory management unit
- Independent data and instruction memory management units
- Dual 256-byte on-chip caches for instructions and data
Page 2
- 4-Gbyte addressing range
- Upward user object code compatible with the 68020
Table 1: Specifications for the CPU-30 R4 Board (Continued)
RESET and ABORT switchesyes
VMEPROM firmware installed on all board versions512 Kbyte
Power requirements
+ 5 V max
+12 V max
- 12 V max
typical 2.3A
typical 0.4A
typical 0.1A
Operating temperature with forced air cooling
Storage temperature
Relative humidity (non-condensing in %)
(With a battery installed, the storage temperature is -40 to +60˚C)
Board dimensions160 x 233 mm
No. of slots used1
1. The FDC37C65C is pin-to-pin compatible with Industry Standard WD37C65C
4 serial ports, 32-bit VMEbus interface, VMEPROM firmware,
Installation Guide.
CPU-30/TM Rev. 4Technical Reference Manual Set for the CPU-30 Rev. 4 including
a detailed hardware description, a VMEPROM User’s Manual and
a FGA-002 User’s Manual.
CABLE 9-25 SETFour cable adapters DSub-9 to DSub-25.
IOBP-1I/O back panel board for VMEbus P2 with flat cable connectors for
SCSI, floppy and one serial I/O interface. Extends 4” behind P2.
IOBP-1 Serial CableIOBP-1 cable to 3U backpanel for the 4th serial port of the
CPU-30.
IOPI-2I/O back panel board for VMEbus P2 with flat cable connectors for
SCSI and floppy interface. Extends 3” behind P2.
Documentation included.
FH-002/SET10 pcs. of Hybrid Modules for the Serial Interface to provide
RS-232
FH-003/SET10 pcs. of Hybrid Modules for the Serial Interface to provide
RS-422.
FH-007/SET10 pcs. of Hybrid Modules for the Serial Interface to provide
RS-485.
VxWorks/DEV 68KVxWorks development package for 68K based products.
VxWorks/BSP CPU-30VxWorks board support package for CPU-30.
SYS68K/BusNet/VxWorksBusNet runtime package for VxWorks on 68K VMEbus boards.
in the section “VMEPROM”
has been corrected.
“Ethernet address” has
been changed. NETLOAD,
NETSAVE commands
have been extended.
“Erase flash memory”
description has been corrected.
Boot flash devices 256K * 8
have been replaced by
128K * 8 devices.
This Installation Section provides guidelines for powering up the
SYS68K/CPU-30 R4 board. The Installation Section, which you have in
your hand now, appears both as Section 2 of the SYS68K/CPU-30 R4Technical Reference Manual and as a stand-alone Installation Guide.
This stand-alone Installation Guide is delivered by FORCE
COMPUTERS with every board. The SYS68K/CPU-30 R4 TechnicalReference Manual provides a comprehensive hardware and software
guide to your board and is intended for those persons who require
complete information.
2.1.1Caution
CAUTION: Read the following safety note before handling the board.
To ensure proper functioning of the product over its usual lifetime, take
the following precautions before handling the board.
Electrostatic discharge and incorrect board installation and uninstallation
can damage circuits or shorten their lifetime.
• Before installing or uninstalling the board, read this Installation section.
• Before installing or uninstalling the board in a VME rack:
- Check all installed boards for steps that you have to take before
turning off the power.
- Take those steps.
- Finally turn off the power.
• Before touching integrated circuits, ensure that you are working in an
electrostatic free environment.
• Ensure that the board is connected to the VMEbus via both connectors,
the P1 and the P2 and that power is available on both.
• When operating the board in areas of strong electro-magnetic radiation,
ensure that the board
The installation of the board is easy, requiring only a power supply and a
VMEbus backplane. The power supply must meet the specifications
described in Table 1, “Specifications for the CPU-30 R4 Board,” on
page 7. The processor board requires +5 V supply voltage; ±12 V are
needed for the RS-232 serial interface and the Ethernet Interface.
For the initial power up, a terminal can be connected to the 9-pin D-Sub
microconnector of serial port 1, which is located on the front panel. The
serial port provides RS-232 interface signal level.
SEE ALSO: Before powering up check that the default switch settings
are correct as outlined in Section 2.3 ‘Default Switch Settings’.
2.2 Location Diagrams of the SYS68K/CPU-30 R4 Board
A location diagram showing the important components on the top side of
the CPU-30 R4 appears on the next page. On the page next to it, there is a
location diagram showing the bottom side of the CPU-30 R4.
SEE ALSO: Figure 2, “Diagram of the CPU-30 R4 (Bottom View),” on
☞
page 14 shows the location of all the switches on the board.
2.2.1Before
Powering Up
Both of these diagrams only show the components on the board which are
of interest to the user.
Before powering up, please make sure that the default switch settings are
all configured according to Table 4, “Default Switch Settings,” on
page 15. Since the board is configured for power up according to these
default settings, please check them before powering up your
SYS68K/CPU-30.
NOTE: The battery backup for SRAM and RTC is disabled with the
NOTE: Pin 1 is always
located near the diagonal
line shown on each
switch and the OFF side
of the switch is also
always located near
the diagonal line.
The following table shows the default settings for all the switches on the
board. Please make sure you check the default settings before powering
up the board.
SEE ALSO: For the position of the switches on your CPU-30 R4 board,
☞
please see Figure 2, “Diagram of the CPU-30 R4 (Bottom View),” on
page 14.
Table 4: Default Switch Settings
Diagram of Switch
with Default Setting
SW5
OFFON
SW6
OFFON
Switches
SW5-1OFFOFF = Boot PROM access to default Boot PROM and
4
3
2
SW5-2OFFOFF = Optional Boot PROM Pinout for Flash PROM
1
SW5-3OFFOFF = Write to Boot PROM enabled
SW5-4OFFOFF = Write to System Flash Memory enabled
SW6-1OFF
4
SW6-2OFF
3
Default
Setting
SWITCH 5
SWITCH 6
Function
optional Boot PROM
ON = Boot PROM access to optional Boot PROM only
(Access to default Boot PROM is disabled)
ON = Optional Boot PROM Pinout for EPROM
ON = Write to Boot PROM disabled
ON = Write to System Flash Memory disabled
BUSTIMER (1:0)
SW6-1 OFF = VME Bustimer bit 1=1OFFOFF83.53ms
SW6-1 ON = VME Bustimer bit 1=0OFFON1.30 ms
SW6-2 OFF = VME Bustimer bit 0=1
SW6-2 ON = VME Bustimer bit 0=0
SW6-1 SW6-2 Time
ONOFF81.6 µs
ONON10.2 µs
2
1
SW6-3OFF
SW6-4OFF
SW6-3 OFF = VME BRSEL bit 1=1SLOT-x detected, 10 : 2
SW6-3 ON = VME BRSEL bit 1=0SLOT-x detected, 01 : 1
SW6-4 OFF = VME BRSEL bit 0=1SLOT-1 detected, -- : 3
SW6-4 ON = VME BRSEL bit 0=0
The table below outlines the layout on the front panel. Additionally, there
is a drawing of the front panel on the next page. The front panel devices
are briefly described on the pages following the drawing.
The RESET key generates an on-board reset. The ABORT key generates
an IRQ on a programmable level. Both keys can be disabled via the
switches described below:
SW7-1Description
OFF (default)RESET key enabled
ONRESET key disabled
SW7-2Description
OFF (default)ABORT key enabled
ONABORT key disabled
2.4.2Status LEDsThe CPU-30 R4 includes two front panel LEDs: RUN/HALT LED and
BM LED.
The RUN/HALT LED displays the condition that the processor is halted
or reset is active and, in this case, the LED turns red. The RUN/HALT
LED turns green on normal operation.
The bus master BM LED is used to indicate VMEbus mastership of the
CPU-30 R4 and, in this case, the LED turns green.
2.4.3Voltage SensorThe voltage sensor generates a power-up reset if the voltage level is
below 4.75 V.
2.4.4Watchdog
Timer
2.4.5Two Rotary
Switches
This timer can be enabled by software and will generate an NMI followed
by a power-up reset, when it is not retriggered.
SW13-2Description
OFF (default)Watchdog reset disabled
ONWatchdog reset enabled
Two software readable four-bit rotary switches are installed on the board
and are accessible via the front panel.
The CPU-30 R4 has three serial I/O channels available via 9-pin D-Sub
connectors on the front panel. All channels will support RS-232, RS-422
and RS-485 interfaces via the FORCE hybrids FH-00x. The default
configuration is RS-232.
The following table shows the pinout of the serial I/O channels for
RS-232.
Table 6: 9-pin D-Sub Connector Pinout1) (RS-232)
PinSignalDirectionDescription
1DCDinData Channel Detector
2RxDinReceive Data
3TxDoutTransmit Data
4DTRoutData Terminal Ready
5GND-Signal Ground
6DSRinData Set Ready
7RTSoutRequest to Send
8CTSinClear to Send
9GND*-Signal Ground
1. Default terminal port setup: 9600 Baud, 8 data bits, 1 stop bit, no parity.
6
7
8
9
1
2
3
4
5
NOTE: *With FH-002, this signal is provided by the hybrid being used.
i
The signal DTR is always driven active and the signal DSR is always
read active by software. The RS-232 interface on your current CPU-30
revision 4.x board is fully compatible to the RS-232 interface on the
earlier CPU-30 revision 3.2 board. However, the default jumper settings
prescribed for the earlier board must be used to obtain this functionality.
The AUI-Ethernet Interface is available on the front panel via a 15-pin
D-Sub connector.
The unique Ethernet address is displayed by the banner when entering the
FGA Boot debugger. FGA Boot also provides a utility function to get the
CPU board’s Ethernet address: “#40 (0x28) Get Ethernet Number”.
The following table shows the pinout of the AUI-Ethernet connector.
Table 8: Signal Assignment of the VME P2 Connector
PINRow Z
(factory option)
1PIT2 A0SCSI Data 0FDC RPM
2GNDSCSI Data 1FDC HLOAD
3PIT2 A1SCSI Data 2FDC DSEL2TxD Port 1
4GNDSCSI Data 3FDC INDEXRxD Port 1
5PIT2 A2SCSI Data 4FDC DSEL1RTS Port 1
6GNDSCSI Data 5FDC DSEL2CTS Port 1
7PIT2 A3SCSI Data 6FDC DSEL1DTR Port 1
8GNDSCSI Data 7FDC MOTORDCD Port 1
9PIT2 A4SCSI DPFDC DIRECGND Port 1
10GNDGNDFDC STEPXTxD Port 2
11PIT2 A5GNDFDC WDATARxD Port 2
12GNDGNDFDC WGATERTS Port 2
13PIT2 A6TERMPWRFDC TRK00CTS Port 2
14GNDGNDFDC WPROTDTR Port 2
15PIT2 A7GNDFDC RDATADCD Port 2
16GNDSCSI ATNFDC SDSELGND Port 2
17PIT2 H1GNDFDC RDYTxD Port 3
18GNDSCSI BSY(RTS Port 2)RxD Port 3
19PIT2 H2SCSI ACKGNDRTS Port 3
20GNDSCSI RSTGNDCTS Port 3
21PIT2 H3SCSI MSG(CTS Port 2)DTR Port 3
22GNDSCSI SELGNDDCD Port 3
23PIT2 H4SCSI CDGNDGND Port 3
24GNDSCSI REQ(TxD Port 3)DSR Port 1
25PIT1 H1SCSI IO(RxD Port 3)DSR Port 2
26GND(RTS Port 1)(RTS Port 3)DSR Port 3
27PIT1 H2GND(CTS Port 3)PIT1 C0
28GND(CTS Port 1)(TxD Port 1)PIT1 C1
29PIT1 H3DSR Port 4DCD Port 4
30GNDRTS Port 4RxD Port 4PIT1 C7
31PIT1 H4CTS Port 4TxD Port 4NC
32GNDGND Port 4DTR Port 4NC
Row ARow CRow D
(factory option)
NC
(TxD Port 2)
NC
(FDC EJECT)
(RxD Port 2)
PIT1 C4
(RxD Port 1)
Page 24
NOTE: The signals marked in parenthesis are only available with the use
i
of FH-002 hybrids, which are available at FORCE COMPUTERS.
The VMEPROM firmware is a full multitasking multiuser real-time
system. It is stored in the on-board System Flash Memory and provides
the following functionality:
- Configuration of the board
- Starting an application
- Application hooks
- Shell with over 80 commands
- Programming of Boot Flash devices.
2.10.1 Booting up
VMEPROM
To start VMEPROM, the rotary switches must both be set to ‘F’:
Table 9: Rotary Switches
MODE 1F
MODE 2F
The different functions of the rotary switches are described in detail in
the VMEPROM section of the SYS68K/CPU-30 R4 Technical Reference
Manual.
Correct Operation
To test the correct operation of the CPU board, the following command
must be typed in:
# SELFTEST <CR>
The selftest command tests some I/O devices, the main memory and the
system timer tick interrupt. Depending on the size of the main memory, it
may last a different amount of time (count about one minute per
megabyte).
After all tests are done, the following message will appear on the terminal
screen:
FORCE COMPUTERS offers an IOBP-1 back panel for easy connection
of I/O signals through the VMEbus P2 connector. This board can be
plugged into the VMEbus P2 connector of a VMEbus board which
carries the SCSI, FDC, and serial I/O signals on the VMEbus P2. It
contains a SCSIbus connector (P2), a floppy disk interface connector
(P3), and a serial I/O connector (P5). All VMEbus P2 connector row A
and C pins are routed to the 64-pin male connector (P4). The pinout of
these connectors is shown in the following table.
This CPU board is a high performance single-board computer based on
the 68030 microprocessor and the VMEbus. The CPU board also
includes an enhanced Floating Point Coprocessor 68882. The board
design utilizes all of the features of the powerful FORCE Gate Array
FGA-002.
Besides the CPU-30 R4, there will be a CPU-30Lite R4 without a
coprocessor, a SCSI, an Ethernet, and a floppy disk interface.
SEE ALSO: Please refer to Table 2, “Ordering Information,” on page 9
☞
for more detailed information.
The CPU-30 R4 provides an A32/D32 VMEbus interface including
DMA, up to 32-Mbyte shared DRAM on-board, up to 8-Mbyte System
Flash, an Ethernet Interface, a single-ended SCSI interface, a Floppy
interface, four RS-232 serial I/O channels, up to 256-Kbyte SRAM and a
Real-Time Clock, both with on-board battery backup.
The shared DRAM is accessible from the 68030 CPU, the FGA-002
DMA controller, and also from other VMEbus masters.
The CPU-30 R4 has an Ethernet port as well as three serial ports
available on the front panel permitting a console port, download and data
communication channels.
One serial port, as well as the SCSI interface and the Floppy interface are
available via the 3-row VMEbus P2 connector.
A 20-bit parallel interface and the three serial ports from the front panel
are available via the optional 5-row VMEbus P2 connector.
The CPU-30 R4 is fully software compatible to the CPU-30 R3 with the
exception of the floppy controller FDC37C65C, which has replaced the
WD1772.
The 68030 uses a nonmultiplexed address and data bus. Asynchronous
signals allow easy interfacing to the outside world; synchronous signals
perform fast interaction.
The CPU drives the address signals (A0-A31), the size signals (SIZ0,
SIZ1) and the function code signals (FC0-FC2) on every cycle,
independent of a cache hit or miss. These signals are used to decode the
memory map of the CPU board.
The hardware on the CPU board is notified by the address and data strobe
signals that the current cycle is not a cache cycle, and that the decoding
outputs are strobed to be valid.
The 32 data lines (D0-D31) are also driven from the processor on write
cycles and sensed on read cycles.
The size of the data transfer is defined by the SIZE + A0 - A1 output
signals (always driven from the CPU). During asynchronous cycles the
data bus width is determined by the Data Size Acknowledge Input signals
(DSACK0, DSACK1). Synchronous cycles acknowledged by the
Synchronous Termination Input signal (STERM) acknowledge the
indicated data width during writes, whereas during reads a 4-byte width
is always acknowledged.
3.2.2The
Instruction Set
If a bus error occurs (BERR sensed from the CPU), exception handling
starts because the current cycle has been aborted (illegal transfer or
incorrect data).
On local bus operation, a bus error will be generated if a device does not
respond correctly.
VMEbus transfers may also be aborted via a BERR.
For the 68030 instruction set and further information relative to
programming, please refer to the 68030 User's Manual.
The 68882 is a non-DMA type coprocessor which uses a subset of the
general purpose coprocessor interface supported by the 68030.
Features of the interface implemented in the 68882 are as follows:
- Main processor and 68882 communicate via standard bus cycles.
- Main processor and 68882 communication is not dependent upon
instruction sets or internal details of individual devices (e.g.
instruction pipes or caches, addressing modes).
- The main processor and 68882 may operate at different clock
speeds.
- 68882 instructions utilize all addressing modes provided by the
main processor; all effective addresses are calculated by the main
processor at the request of the coprocessor.
- All data transfers are performed by the main processor at the
request of the 68882; thus memory management, bus errors,
address errors, and bus arbitration function as if the 68882
instructions are executed by the main processor.
- Overlapped (concurrent) instruction execution enhances throughput
while maintaining the programmer's model of sequential instruction
execution.
- Coprocessor detection of exceptions which require a trap to be
taken are serviced by the main processor at the request of the
68882; thus exception processing functions as if the 68882
instructions were executed by the main processor.
- Support of virtual memory/virtual machine systems is provided via
the FSAVE and FRESTORE instructions.
- Up to eight coprocessors may reside in a system simultaneously;
multiple coprocessors of the same type are also allowed.
- Systems may use software emulation of the 68882 without
reassembling or relinking user software.
For further details, please refer to the User's Manual of the 68881/68882.
The 68882 is addressed via the function codes of the 68030 and a part of
the address bus. This is done automatically within the opcodes generated
by most 68030/68882 floating-point compilers and assemblers.
The following table lists the conditions for addressing the 68882.
SignalValueDescription
FC0
FC1
FC2
A13
A14
A15
A16
A17
A18
A19
1
1
1
1
0
0
0
1
0
0
CPU Space Cycles
Coprocessor ID = 1
Coprocessor Access Cycle
All instructions for the FPCP must include the coprocessor ID (001).
Please note that the VMEPROM Assembler supports this function by
default.
3.3.5Detection of the
68882
3.3.6Summary of
the 68882
The SENSE pin of the FPCP is connected to PI/T #1. This allows
automatic detection whether or not the 68882 is installed.
CAUTION: PI/T #1 pin PC6/PIACK must be programmed as an input.
PC6Function
0FPCP installed
1FPCP not installed
Allowed Function Codes1 1 1 (CPU Space Cycle)
Coprocessor ID0 0 1
Usable Data BitsD0 - D31
Supported Transfer TypesByte
3.4.2Shared DRAMThe CPU board contains a Shared dynamic RAM area with a capacity of
The CPU board also contains the FGA-002 Gate Array with 24,000 gates
and 304 pins.
The FGA-002 Gate Array controls the local bus and builds the interface
to the VMEbus. It also includes a DMA controller, complete interrupt
management, a message broadcast interface (FMB), timer functions, and
mailbox locations.
The gate array monitors the local bus. This in turn signifies that if any
local device is to be accessed, the gate array takes charge of all control
signals in addition to used address and data signals.
The FGA-002 Gate Array serves as a manager for the VMEbus. All
VMEbus address and data lines are connected to the gate array through
the buffers. Additional functions such as the VMEbus interrupt handler
and arbiter are also installed on the FGA-002 Gate Array.
The start address of the FGA-002 Gate Array registers is FFD0.0000
All registers of the gate array and associated functions are described in
detail in the FGA-002 Gate Array User’s Manual.
4, 8, 16 or 32 Mbytes. The Shared RAM area is optimized for fast
accesses from the 68030 CPU and the DMA controller in the FGA-002
Gate Array. The Shared RAM is also accessible by other VMEbus
masters.
16
.
The Shared RAM area is arranged in 36-bit wide memory banks. There
may be one or two of these banks on the CPU board, depending on the
overall memory capacity delivered. Each 36-bit wide bank is separated
into 32 data bits and 4 parity bits. A parity bit checks every eight
consecutive data bits (byte parity). Advanced on-board memory control
logic routes data to and from the on-board 68030 CPU, the DMA
controller, and the VMEbus interface.
For every read cycle, regardless of size (byte, word, long-word or cache
line) and regardless of master (68030, DMA or VMEbus), all 32 bits of
data and 4 bits of parity are read from the Shared RAM array. The 32 data
and 4 parity bits are stored in transceivers.
Parity is regenerated in FGA-002 and compared to the parity bits read
from memory. If a mismatch is found on an accessed byte, an error will
be flagged. A synchronous termination signal (STERM) is asserted, and
the cycle completes.
Write cycles are handled differently. In the case of a long-word access
aligned to a 4-byte boundary, the DRAM can be written immediately.
The parity info generated by FGA-002 will be written additionally to the
DRAM. A synchronous termination signal (STERM) is asserted, and the
cycle completed.
For all other write cycles (byte, word, long-word unaligned), the
momentary valid parity info stored in DRAM must be read. Then the
write to RAM Memory will be performed. Therefore, only the necessary
data will be written, the remaining data already stored in DRAM will stay
unmodified. Additionally, the new parity info generated by FGA-002 will
be merged with the read parity info from DRAM and finally all four
parity bits are written to DRAM. The synchronous termination signal
(STERM) will be generated to complete the cycle.
All write cycles are terminated before they are fully processed to allow
the master writing to DRAM to continue its operations (write posting).
3.4.2.1 Bank Selection
of DRAM
The bank selection depends on memory size. The Dual-Banks
architecture implements an interleaved organized DRAM (four
consecutive bytes located in bank A, the next four consecutive bytes
located in bank B, ...). The Single-Bank architecture implements a noninterleaved organized DRAM.
Table 13: Used Device Types for the Shared Memory
DRAM DeviceDevice CapacityTotal CapacityBankSupported Product
Shared RAM byte parity generation and check work for both local and
VMEbus accesses. If a parity error is detected during a VMEbus slave
read access, the CPU board drives BERR, informing the VMEbus master
about the parity error. On all local accesses, a normal STERM will be
generated, plus an interrupt on a software programmable level. The
access address is stored inside the FGA-002 Gate Array allowing easy
software controlled detection of the cycle which caused the parity error.
1)
9 * 1 Mbit * 44 Mbyte1CPU-30ZBE R4
Page 38
The Shared RAM is accessed from the VMEbus via FGA-002. The start
and end access addresses are programmable in 4 Kbyte steps. The
defined memory range can be write protected in coordination with the
VMEbus Address Modifier codes. For example, in privileged mode the
memory could be read and written, while in non-privileged mode the
memory could only be read, or a non-privileged access could be
prohibited altogether.
When the gate array detects a VMEbus access cycle to the programmed
address range of the Shared RAM, it requests local bus mastership from
the CPU. After the CPU has granted local bus mastership to the
FGA-002, the VMEbus access cycle is executed and all data is latched
(read cycles), or stored to RAM (write cycles). The read and write cycle
is then terminated and the FGA-002 immediately releases local bus
mastership back to the CPU. Simultaneously, it completes the fully
asynchronous VMEbus access cycle. The early completion of the
memory read or write cycle allows the CPU to continue processing while
the FGA-002 independently manages the VMEbus transaction overhead.
A programmable bit within the FGA-002 may be used to disable the early
bus release option. With early release disabled, the FGA-002 retains local
bus mastership until the VMEbus cycle is finished. This guarantees that
no other local bus master (CPU or DMA controller) will access the
Shared RAM until the VMEbus cycle is complete. In the case of a readmodify-write (RMW) cycle by another VMEbus master to the Shared
RAM, the FGA-002 will perform both transactions (a read followed by a
write) without releasing the local bus, thus guaranteeing that the cycle is
indivisible.
3.4.3Board Type
with Memory
Capacity
In short, the early release option allows the CPU access to the Shared
RAM sooner, but sacrifices the guaranteed indivisibility of VMEbus
RMW cycles. Because the 68030 CPU includes an on-chip cache
memory, this may not affect CPU performance at all.
The following table lists the CPU board type with the memory capacity
of the Shared RAM.
SEE ALSO: Please refer to Section 3.10.13, ‘I/O Configuration of PI/T
#2,’ on page 74 for more detailed information.
The access address of the Shared RAM is programmable within the
FGA-002 Gate Array. The default address range of the 4 Mbyte DRAM
array is from 0000.000016 to 003F.FFFF16. The default address range of
the 32 Mbyte DRAM array is 0000.0000
to 01FF.FFFF16. It is possible
16
to program nearly any address range desired in the FGA-002.
☞
3.4.6Shared RAM
Performance
Start AddressEnd AddressMemory Capacity
0000.0000
0000.0000
0000.0000
0000.0000
16
16
16
16
01FF.FFFF
00FF.FFFF
007F.FFFF
003F.FFFF
16
16
16
16
32 Mbytes
16 Mbytes
8 Mbytes
4 Mbytes
The access address of the Shared RAM from the VMEbus is also
programmable via FGA-002. That is the address range that other
VMEbus masters must use in order to access the Shared RAM on the
CPU board. This is not necessarily the same address range used by the
CPU for local accesses.
SEE ALSO: Please refer to Section 3.18, ‘VMEbus Slave Interface,’ on
page 101 for more information.
The memory interface logic controlling the Shared RAM array is
optimized for fast accesses from the 68030 CPU, providing the highest
possible performance. Because the 68030 CPU contains an on-chip data
and instruction cache, many CPU accesses are cache line "burst fills".
These burst transactions attempt to read 16 consecutive bytes into the
68030, using four 4-byte cycles.
The first read cycle of such a burst usually requires 5 CPU clock cycles
(200 nanoseconds at 25 MHz). Due to the optimized design of the
memory control logic, each subsequent cycle only requires 1 CPU clock
cycle (40 nanoseconds) to complete. This is commonly called a "5-1-1-1"
burst transfer. Overall, the total cache line "burst fill" operation requires 8
clock cycles to transfer 16 bytes, providing a memory bandwidth of over
50 Mbytes/second.
Not all CPU accesses are burst transfers. Single read and write
transactions are also supported at the fastest possible speed. A single read
or write access (1, 2, or 4 bytes) requires 5 CPU clock cycles. Distributed
asynchronous refresh is provided every 14 microseconds and an access
during a pending refresh cycle may be delayed by a maximum of five
additional clock cycles.
The first two read cycles after reset of the microprocessor are operand
fetches of the Initial Interrupt Stack Pointer (ISP) and the Initial Program
Counter (IPC). These operands are always fetched from addresses
0000.0000
3.5.1InitializationSpecial control logic in FGA-002 maps the Boot PROM (not the System
Flash Memory) down to this address to allow the 68030 to boot from a
single byte-wide PROM. This facilitates debugging and low-level
program development. However, when the initialization routines in the
Boot PROM are completed, control is transferred to the System Flash
Memory in such a way that the 68030 appears to have been booted from
the System Flash Memory, not the Boot PROM. For this reason, the
System Flash Memory must also have the ISP and IPC loaded at address
0000.0000
and 0000.000416, respectively.
16
and 0000.000416, respectively.
16
3.5.2Memory
Organization of
the System
PROM Area
3.5.3Read/Write to
the System
Flash Memory
0000.0000
0000.0004
in System Flash Memory: Initial Interrupt Stack Pointer
16
in System Flash Memory: Initial Program Counter
16
The data path of the System Flash Memory is 32-bit wide, separated into
4-byte paths. Each byte path is connected to one Flash Memory device.
Read cycles with any port size are allowed. Write cycles are flagged by
the FGA-002 Gate Array with BERR. A programmable bit within the
FGA-002 may be used to enable write operation to the System Flash
Memory. In this case the FGA-002 will respond with an asynchronous
data acknowledge (DSACK0, DSACK1). The write takes affect to the
System Flash Memory depending on switch SW5-4.
SW5-4Description
OFF (default)Write to System Flash Memory enabled
ONWrite to System Flash Memory disabled
Page 42
The status of SW5-4 is connected to PI/T #2.
Pin PC4 on the PI/T #2 interface signal protects the write to the System
The following device types or equivalent are used by the System Flash
Memory:
Table 14: Device Types used for System Flash Memory
DeviceDevice CapacityTotal CapacityDevice Speed
28F008SA1M * 84 Mbytes120 nsx
29F0162M * 88 Mbytes120 ns
The default configuration using 28F008SA devices is provided for
programming VMEPROM.
The start address of the System PROM Flash Area is mapped via the
FGA-002 Gate Array and cannot be changed. The size of this memory
area depends on the memory capacity of the devices used. The following
table lists the address map for the usable device types.
Default
Configuration
Table 15: Address Map of the PROM Area
Start AddressEnd AddressUsed DeviceTotal Capacity
Default
Configuration
3.5.7Summary of
the PROM
Area
FF00.0000
FF00.0000
Not Allowed Access with Function Code111
Usable Data BitsD00 - D31
Supported Port Size (read)Long, Word, Byte
Supported Port Size (write)Long (aligned!)
No. of Devices4
Capacity4 Mbytes
Default Configuration for28F008A Devices
Default Access Time120 ns
Access Address RangeFF00.000016 - FF3F.FFFF
The CPU board contains one or two 32-pin PROMs which are used to
boot up the processor and initialize register contents of the FGA-002
Gate Array. This program finishes in such a manner that the 68030
microprocessor appears to have booted from the System Flash Memory.
The Boot PROM devices are located in 32-pin PLCC sockets at location
J28 or J36.
Because the 68030 will unconditionally boot from the Boot PROM
memory after every power up or reset, there must always be a working
Boot PROM device installed in the CPU board.
During the bootup procedure, the FGA-002 will map all addresses to the
Boot PROM memory with the exception of FGA-002 internal registers.
After bootup the Boot PROM will be accessible at address FFE0.0000
The start address of the Boot PROM is fixed and cannot be changed.
16
.
3.6.1The Boot
PROM Sockets
☞
3.6.1.1 Boot PROM
Selection
The Boot PROM area is located in two 32-pin PLCC sockets. One socket,
the default Boot PROM socket, allows the usage of 12V programmable
Flash devices. The second socket, the optional Boot PROM socket,
allows the usage of 5V programmable Flash devices. Alternatively,
EPROM devices (e.g. OTP) can be used.
SEE ALSO: For information on which devices may be used, please see
the tables in Section 3.6.2, ‘The Boot PROM Address Map,’ on page 47.
The Boot PROM socket selection is controlled by switch SW5-1.
SW5-1Description
OFF (default)Default Boot socket J36 enabled with start address at FFE0.000016,
Optional Boot socket J28 enabled with start address at FFE8.0000
ONDefault Boot socket J36 disabled,
Optional Boot socket J28 enabled with start address at FFE0.0000
OFF (default)Optional Boot PROM (Socket J28) supports
5V Flash device (programmable) and
12V Flash device (non-programmable)
ONOptional Boot PROM (Socket J28) supports
EPROM (OTP) or
EEPROM (writeable)
3.6.1.3 Programming
the Boot
PROM Devices
☞
The programming of Boot PROM devices is supported for the default
Boot PROM (socket J36) for 12V Flash devices and for the optional Boot
PROM socket J28 for 5V Flash or EEPROM devices.
For correct programming, a communication sequence to the Boot PROM
devices must be used which is defined by the manufacturer of the device.
SEE ALSO: For further details, please refer to the data sheets in
Section 4, ‘Circuit Schematics and Data Sheets,’ on page 115.
The programming to the Boot PROM devices is dependent on switch
SW5-3.
SW5-3Description
OFF (default)Write to Boot PROM devices enabled
ONWrite to Boot PROM devices disabled
The status of switch SW5-3 is connected to the PI/T #2.
CAUTION: PI/T #2 pin PC2 must be programmed as an input.
Page 46
PC2Function
0Write to Boot PROM unprotected
1Write to Boot PROM protected
Besides the communication sequence, a programming voltage Vpp of
12V must be applied to the default Boot PROM (socket J36). Vpp is
generated by the CPU-30 R4 and is controlled by PI/T #2.
PC6Function
0Programming voltage enabled (Vpp = ON)
1Programming voltage disabled (Vpp = OFF)
The Vpp generator is shared between the System Flash Memory and the
default Boot PROM socket.
CAUTION: PI/T #2 pin PC6 must be programmed as an output.
Boot PROM access to default Boot PROM and optional Boot PROM
(Boot PROM selection switch SW5-1 in position OFF)
Used DeviceDevice TypeStart AddressEnd AddressTotal Capacity
Not Allowed Access with Function Code111
Supported Port SizeByte
Maximum Capacity1 Mbyte
Default Access Time200 ns
Access AddressFFE0.000016 - FFEF.FFFF
No. of Devices to be Installed1 or 2
The SRAM memory is dedicated to the on-board default SRAM and an
optional SRAM.
For the optional SRAM there are two 32-pin DIL socket positions
available. The socket position J87 allows the usage of a 28-pin SRAM or
a 32-pin SRAM with a high active chip select for pin 30. The socket
position J88 allows the usage of a 32-pin SRAM. The default SRAM is
located in socket position J86.
The SRAM address map between the default and the optional SRAM can
be controlled by switch SW11-4.
3.7.1Memory
Organization
SRAM
SW11-4
OFFFFC0.0000
ONFFC8.0000
Default SRAM Optional SRAM
Start Address of
16
16
FFC0.0000
Disabled
16
The SRAM memory at sockets J86, J87 and J88 allows the user to retain
data when the power supply is switched off. A backup provides the
current for the SRAM standby mode.
The local SRAM memory is connected to the local 8-bit data bus,
providing a byte-wide port. Succeeding bytes seen by the microprocessor
are handled in the same manner as succeeding bytes for the local SRAM
memory.
Byte, word, and long-word accesses are managed by the dynamic bus
sizing of the microprocessor. For further details, please refer to the
manual of the microprocessor.
Data can be read from and written to any address; odd, even or unaligned
in byte, word, or long-word format.
The following instruction is fully supported from the SRAM memory
area:
MOVE.X ($FFC0 000Y), D0
X = B = Byte1 Byte
X = W = Word2 Bytes
X = L = Long Word4 Bytes
Y = 0
Y = 1
Y = 2
Y = 3
.
.
.
All combinations of the listed instructions are allowed and possible.
3.7.2Used Devices
for SRAM
Area
The default SRAM capacity is 32 Kbyte. The following low power
device types (marked with -L or -LL) are supported by the J87 socket
position. The package type must be either 28-pin DIL or 32-pin DIL.
DeviceDevice Capacity
KM 62256L
MB 84256L
M5M 5256L
KM 681000L128K * 8
M5M 510008L128K * 8
1. These devices must be installed with pin 1, 2,
31, 32 left free.
1)
1)
1)
32K * 8
32K * 8
32K * 8
Default
Configuration
O p t i o n a l
The following DIL-device types are supported by the J88 socket position.
DeviceDevice Capacity
M5M 5408L512K * 8Optional
Default
Configuration
CAUTION: A device can only be assembled in either socket J87 or J88.
NOTE: The setup parameters of FGA-002 are stored in the SRAM
i
located in the lower half of the SRAM address space. If the optional
SRAM is enabled, the setup parameters of the optional SRAM will be
used.
3.7.3Access Time
Selection of the
SRAM Area
3.7.4Backup Power
for the SRAM
Area
The access time of the SRAM area is software programmable in the
FGA-002 Gate Array. Four fixed access times are available: 2.0, 1.0, 0.5
and 0.25 microseconds.
There are two sources for backup power. One from the VMEbus
+5VSTDBY line and the other one from a CR2032-type lithium battery
installed in the battery socket at location BAT 1.
Backup power from the VMEbus +5VSTDBY line is enabled by
SW11-2. Backup power from the battery is enabled by SW11-1.
The SRAM memory, both the default SRAM (on-board) and the optional
SRAM (sockets J87 and J88) are powered by backup power circuitry.
This maintains the power supply for the SRAM memory to retain its nonvolatile storage.
Under normal operation the backup power circuitry connects the +5V
power supply to the SRAM memory. When the main +5V supply fails,
backup power may be supplied from one of two alternate sources. The
VMEbus +5VSTDBY line may be used to provide backup power under
power-fail conditions. The switchover from normal +5V to +5VSTDBY
is fully automatic; whichever voltage is higher will be available to the
SRAM memory.
Page 52
As a second alternative, the backup power may be supplied by battery.
Should the +5V and/or +5VSTDBY supplies drop below approximately
+3.3 volts, the on-board battery will be used.
This is controlled for +5VSTDBY by switch SW11-2.
SW11-2Description
OFF (default)Backup from +5VSTDBY for RTC and SRAM disabled
ONBackup from +5VSTDBY for RTC and SRAM enabled
Backup from the battery is controlled by switch SW11-1 and SW11-3.
3.7.5Summary of
the SRAM
Area
SW11-1SW11-3
OFFOFFx
OFFON
ONOFFBackup from battery enabled for RTC,
ONONBackup from battery enabled for RTC and SRAM
Not Allowed Access with Function Code111
Supported Port SizeByte
Default Access Time100ns
Access AddressFFC0.000016 - FFCF.FFFF
Capacity of Default SRAM32 Kbytes
Maximum Capacity of Optional SRAM512 Kbytes
There is an RTC 72423 installed on the CPU board, containing its own
crystal to maintain accurate time and date. A battery is provided on the
CPU board to allow the RTC to run even under power-down conditions.
3.8.1Address Map
of the RTC
Registers
The RTC 72423 has a 4-bit data bus. It must be accessed in byte mode
and the upper four bits (4..7) are "don't care" during read and write
accesses. The base address of the RTC is FF80.3000
1 Second Digit Register
10 Second Digit Register
1 Minute Digit Register
10 Minute Digit Register
1 Hour Digit Register
PM/AM and 10 Hour Digit Register
1 Day Digit Register
10 Day Digit Register
1 Month Digit Register
10 Month Digit Register
1 Year Digit Register
10 Year Digit Register
Week Register
Control Register D
Control Register E
Control Register F
3.8.2RTC
Programming
Page 54
☞
The following programming example shows how to read from or write to
the RTC. Please note that the RTC must be stopped prior to reading the
date and time registers.
SEE ALSO: For further details, please refer to the RTC 72423 data sheet
in Section 4, ‘Circuit Schematics and Data Sheets,’ on page 115.
There are two sources for backup power. One from the VMEbus
+5VSTDBY line and the other one from a CR2032-type lithium battery
installed in the battery socket at location BAT 1.
Backup power from the VMEbus +5VSTDBY line is enabled by
SW11-2. Backup power from the battery is enabled by SW11-1.
The RTC is powered by backup power circuitry. This circuitry maintains
power supply for the RTC to guarantee continuous operation.
Under normal operation the backup power circuitry connects the +5V
power supply to the RTC. When the main +5V supply fails, backup
power may be supplied from one of two alternate sources. The VMEbus
+5VSTDBY line may be used to provide backup power under power-fail
conditions. The switchover from normal +5V to +5VSTDBY is fully
automatic; whichever voltage is higher will be available to the RTC.
As a second alternative, the backup power may be supplied by an onboard lithium battery. Should the +5V and/or +5VSTDBY supplies drop
below approximately +3.3 volts, the on-board battery will be used.
This is controlled for +5VSTDBY by switch SW11-2.
Page 56
SW11-2Description
OFF (default)Backup from +5VSTDBY for RTC and SRAM disabled
ONBackup from +5VSTDBY for RTC and SRAM enabled
The Dual Universal Serial Communications Controller 68562 (DUSCC)
is a single-chip MOS-LSI communications device that provides two
independent, multiprotocol, full duplex receiver/transmitter channels in a
single package. Each channel consists of a receiver, a transmitter, a 16-bit
multifunction counter/timer, a digital phase locked loop (DPLL), a
parity/CRC generator and checker, and associated control circuits.
3.9.1Features of the
DUSCC
- Dual full-duplex synchronous/asynchronous receiver and
transmitter
- Multiprotocol operation consisting of:
BOP: HDLC/ADCCP, SDLC, SDLC Loop, X.25 or X.75 link
level
COP: BISYNC, DDCMP, X.21
ASYNC: 5-8 bit plus optional parity
- Programmable data encoding formats: NRZ, NRZI, FM0, FM1,
Manchester
- 4 character receiver and transmitter FIFOs
- Individual programmable baud rate for each receiver and
transmitter
- Digital phase locked loop
- User programmable counter/timer
- Programmable channel modes full/half duplex, auto echo, local
loopback
- Modem control signals for each channel: RTS, CTS, DCD
- CTS and DCD programmable auto enables for receiver and
transmitter
The following tables contain the complete register map of DUSCC #1.
The first table pertains only to registers for Port #4, the second table for
Port #1, and the third table for registers common to both Port #1 and
Port #4.
Table 17: Serial I/O Port #4 (DUSCC #1) Register Address Map
The following tables contain the complete register map of DUSCC #2.
The first table pertains only to registers for Port #2, the second table for
Port #3, and the third table for registers common to both Port #2 and
Port #3.
Table 20: Serial I/O Port #2 (DUSCC #2) Register Address Map
Serial ports #1 and #4 are controlled by DUSCC #1 at location J90. Serial
ports #2 and #3 are controlled by DUSCC #2 at location J89. In both
cases, the DUSCC is connected to a local 8-bit data bus and is accessible
via byte transfers.
The RS-232 interfaces of port #1, #2, #3 and #4 are identical except that
port #4 is wired directly to the VMEbus P2 connector, while ports #1
through #3 are wired to 9-pin D-Sub connectors labeled "1" through "3"
on the front panel of the CPU board and to the optional 5-row VMEbus
P2 connector. As a factory option, ports #1 through #3 may also be
connected to the default assembled 3-row VMEbus P2 connector.
In the sections that follow the figures will refer to the hardware
configuration switches and to the serial driver/receiver hybrid sockets.
For reference, the switches and hybrids are assigned to the serial ports
according to the following table.
Table 23: Switches & Module Assignment for Serial Port
Configuration
DUSCCChannelHybridSwitch SW12-Port
#1AJ1184"4"
#1BJ1191"1"
3.9.5RS-232 and
RS-422/485
Driver Modules
3.9.6RS-232
Configuration
of Serial Ports
#2AJ1233"2"
#2BJ1242"3"
In order to conserve board space and to simplify varying the serial
interfaces, FORCE Computers has developed RS-232 and RS-422/485
hybrid modules: the FH-002 and FH-003.
These 21-pin single in-line (SIL) modules are installed in sockets so that
they may be easily changed to meet specific application needs. Please
refer to the preceding table for the assignment of hybrid modules to serial
ports.
By default, all four serial ports are configured for RS-232 compatibility.
For proper RS-232 operation, the correct driver/receiver hybrid module
must be installed (FH-002), and the serial interface switches SW12-1 –
SW12-4 must be configured for RS-232. The default switch setting is
detailed below.
The serial ports may be configured for RS-232 or RS-422/485.
SW12-1Description
OFF (default)RS-232 support for port #1
FH-002 hybrid must be installed for J118
ONRS-422/485 support for port #1
FH-003 hybrid must be installed for J118
SW12-2Description
OFF (default)RS-232 support for port #3
FH-002 hybrid must be installed for J124
ONRS-422/485 support for port #3
FH-003 hybrid must be installed for J124
SW12-3Description
OFF (default)RS-232 support for port #2
FH-002 hybrid must be installed for J123
ONRS-422/485 support for port #2
FH-003 hybrid must be installed for J123
SW12-4Description
OFF (default)RS-232 support for port #4
FH-002 hybrid must be installed for J126
ONRS-422/485 support for port #4
FH-003 hybrid must be installed for J126
When a serial port is configured for RS-232 operation, its I/O signals will
be connected to the front panel DB-9 connector as follows (ports #1, #2
and #3 only):
1)
9-pin D-Sub
Connector
1
2
3
4
5
6
7
8
9
Description
Data Carrier Detect
Receive Data
Transmit Data
Data Terminal Ready
Signal GND (supplied by FH-002)
Data Set Ready
Request to Send
Clear to Send
Signal GND
(x)
1)
Output
x
x
x
x
x
(x)
x
(x)
SignalInput
DCD
RXD
TXD
DTR
GND
DSR
RTS
CTS
GND
1. As a factory option signals marked in brackets may be connected to the 9-pin
D-Sub connector.
When serial port #4 is configured for RS-232 operation, its I/O signals
will be connected to the VME P2 connector as follows:
SignalInput
DCD
RXD
TXD
DTR
GND
DSR
RTS
CTS
1. As a factory option signals marked in brackets may be connected to the 9-pin
D-Sub connector.
1)
x
x
(x)
x
Output
x
x
(x)
(x)
1)
VME
Connector P2
C29
C30
C31
C32
A32
A29
A30
A31
Description
Data Carrier Detect
Receive Data
Transmit Data
Data Terminal Ready
Signal GND (supplied by FH-002)
Data Set Ready
Request to Send
Clear to Send
NOTE: For the connection to the IOBP-1 back panel, please refer to
i
Section 2.11, ‘The SYS68K/IOBP-1,’ on page 26.
When the serial ports #1, #2 and #3 are configured for RS-232 operation,
its I/O signals will be connected to the optional 5-row VME P2 connector
as follows:
PortSignalInput
1)
Output
1)
VME
Connector P2
Description
1DCD
RXD
TXD
DTR
GND
DSR
RTS
CTS
2DCD
RXD
TXD
DTR
GND
DSR
RTS
CTS
3DCD
RXD
TXD
DTR
GND
DSR
RTS
CTS
1. As a factory option, signals marked in brackets may be connected to the 9-pin D-Sub
connector.
(x)
(x)
(x)
x
x
x
x
x
x
x
x
x
x
x
(x)
x
(x)
x
x
(x)
x
(x)
x
x
(x)
x
(x)
D8
D4
D3
D7
D9
D24
D5
D6
D15
D11
D10
D14
D16
D25
D12
D13
D22
D18
D17
D21
D23
D26
D19
D20
Data Carrier Detect
Receive Data
Transmit Data
Data Terminal Ready
Signal GND (supplied by FH-002)
Data Set Ready
Request to Send
Clear to Send
Data Carrier Detect
Receive Data
Transmit Data
Data Terminal Ready
Signal GND (supplied by FH-002)
Data Set Ready
Request to Send
Clear to Send
Data Carrier Detect
Receive Data
Transmit Data
Data Terminal Ready
Signal GND (supplied by FH-002)
Data Set Ready
Request to Send
Clear to Send
3.9.7RS-422/RS-485
Hardware
Configuration
of Serial Ports
☞
It is possible to configure any or all of the four serial ports to be RS-422
compatible or – as factory option – RS-485 compatible. By default, all
four serial ports are configured for RS-232 operation. For proper RS422/485 operation, the correct driver/receiver hybrid module must be
installed (FH-003), and the serial interface switches must be properly
configured.
SEE ALSO: For a list of the serial interface switches on the CPU board,
please refer to Section 3.9.6, ‘RS-232 Configuration of Serial Ports,’ on
page 63.
The RS-422 compatible interface supports TXD, RXD, RTS, CTS with
differential outputs and inputs. Each port occupies the same nine pins of
the D-Sub connector as in the RS-232 compatible configuration, but with
a different signal association.
When a serial port is configured for RS-422 operation, its I/O signals will
be connected to the front panel DB-9 connector as follows (ports #1, #2
and #3 only):
x
x
x
x
9-pin D-Sub
Connector
1
2
3
4
5
6
7
8
9
Description
Transmit Data
Request to Send
Clear to Send
Receive Data
Receive Data
Transmit Data
Request to Send
Clear to Send
Signal GND
SignalInputOutput
TXD-
RTSCTS+
RXD+
RXDTXD+
RTS+
CTS-
GND-
x
x
x
x
Page 66
When serial port #4 is properly configured for RS-422 operation, its I/O
signals will be connected to the VME P2 connector as follows:
SignalInputOutput
TXD-
RTSCTS+
RXD+
RXDTXD+
RTS+
CTS-
x
x
x
x
x
x
x
x
VME
Connector P2
C29
C30
C31
C32
A32
A29
A30
A31
Description
Transmit Data
Request to Send
Clear to Send
Receive Data
Receive Data
Transmit Data
Request to Send
Clear to Send
When the serial ports #1, #2 and #3 are configured for RS-422 operation,
its I/O signals will be connected to the optional 5-row VME P2 connector
as follows:
VME
PortSignalInputOutput
Connector P2Description
3.9.8Termination
Resistors for
RS-422/RS-485
Configuration
1TXD-
RTS-
CTS+
RXD+
RXDTXD+
RTS+
CTS-
2TXD-
RTS-
CTS+
RXD+
RXDTXD+
RTS+
CTS-
3TXD-
RTS-
CTS+
RXD+
RXDTXD+
RTS+
CTS-
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
D8
D4
D3
D7
D9
D24
D5
D6
D15
D11
D10
D14
D16
D25
D12
D13
D22
D18
D17
D21
D23
D26
D19
D20
Transmit Data
Request to Send
Clear to Send
Receive Data
Receive Data
Transmit Data
Request to Send
Clear to Send
Transmit Data
Request to Send
Clear to Send
Receive Data
Receive Data
Transmit Data
Request to Send
Clear to Send
Transmit Data
Request to Send
Clear to Send
Receive Data
Receive Data
Transmit Data
Request to Send
Clear to Send
If termination resistors are necessary to compensate for various cable
lengths and to reduce signal reflections, it must be done externally from
the CPU-30 R4 (e.g. via a cable connector).
The resistor value is user application dependent, but a recommended
value is 1000 Ohms.
The MC68230 Parallel Interface/Timer provides versatile double
buffered parallel interfaces and an operating system oriented timer. The
parallel interfaces operate in unidirectional or bidirectional modes, either
8 or 16 bits wide. The PI/T contains a 24-bit wide counter and a 5-bit
prescaler.
3.10.1 Features of the
PI/T
16
- MC68000 Bus Compatible
- Port Modes Include:
Bit I/O
Unidirectional 8 bit and 16 bit
Bidirectional 8 bit and 16 bit
- Selectable Handshaking Options
- 24-bit Programmable Timer
- Software Programmable Timer Modes
- Contains Interrupt Vector Generation Logic
- Separate Port and Timer Interrupt Service Requests
- Registers are Read/Write and Directly Addressable
Port General Control Register
Port Service Request Register
Port A Data Direction Register
Port B Data Direction Register
Port C Data Direction Register
Port Interrupt Vector Register
Port A Control Register
Port B Control Register
Port A Data Register
Port B Data Register
Port A Alternate Register
Port B Alternate Register
Port C Data Register
Port Status Register
Timer Control Register
Timer Interrupt Vector Register
Counter Preload Register
Count Register
Timer Status Register
"
"
"
"
"
"
3.10.3 I/O Configuration
of PI/T #1
☞
The following table lists all I/O signals connected to PI/T #1. The
functions of these signals are described in the corresponding chapter.
SEE ALSO: Additional information is provided in the PI/T data sheet,
included in Section 4, ‘Circuit Schematics and Data Sheets,’ on
page 115.
User I/O via optional B5 or optional 5-row VME P2 connector
H2
"
H3
"
H4
"
I
I/O
I
I/O
3.10.4 Rotary Switches
at PI/T #1
PB0
PB1
PB2
1)
PB3
1)
PB4
PB5
PB6
PB7
PC0
PC1
PC2
PC3
PC4
PC5
PC6
PC7
1. reserved
Floppy Disk Drive Control
"
"
"
"
"
DMA Controller Control
"
User I/O via optional B5 or optional 5-row VME P2 connector
"
Not Used, Reserved
Timer Interrupt Request
User I/O via optional B5 or optional 5-row VME P2 connector
Port Interrupt Request
68882 FPCP Sense
User I/O via optional B5 or optional 5-row VME P2 connector
O
O
O
I
I
O
O
O
I/O
I/O
-
O
I/O
O
I
I/O
PA0-PA7 lines:
There are two rotary switches installed on the front panel of the CPU
board. The position of each switch can be read in via port A of PI/T #1.
Each rotary switch provides four bits of data. Therefore, each switch has
16 possible positions and the value printed on the switch (i.e., 0-9 and
A-F) can be read from the lines PA0-PA3 (SW1) and PA4-PA7 (SW2) of
PI/T #1.
Page 70
The following table lists the input signals of PI/T #1 in relation to the
rotary switch signals.
NOTE: The rotary switches serve a special function in conjunction with
i
the RESET and ABORT switches. This functionality is built into the
Boot EPROM and is described in detail in the Boot Software description
of the FGA-002 User’s Manual.
For application programs, the rotary switches can be used as a general
purpose input channel for diagnostics, configuration selection, or
automatic system boot with different configurations.
VMEPROM uses the rotary switches for automatic configuration.
3.10.5 Floppy Disk
Drive Control
Lines at PI/T #1
PB0-PB5:
These lines control the FDC37C65C floppy disk drive interface. They
perform the functions listed in the table below.
These lines control the local peripheral bus when the DMA controller is
active. The signal PC6 controls the direction of the DMA transfer (read
vs. write). The PC7 signal selects the target of the DMA transfer (SCSI
controller or Floppy controller). The following table clarifies all four
possible combinations.
PB7PB6Function
00DMA write to SCSI
01DMA read from SCSI
10DMA write to FDC
11DMA read from SCSI
NOTE: An additional DMA control line is described in Section 3.10.21,
‘DMA Control Line at PI/T #2,’ on page 78.
PC0, PC1, PC4, PC7, H1-H4: (FACTORY OPTION)
This 8-bit input port may be available (as a factory option) at the 16-pin
connector B5 and may be available (as a factory option) at the 5-row
VME P2 connector. Four bits are connected to port C of PI/T #1 and can
be used as inputs or outputs. The remaining four bits are connected to the
handshake pins of PI/T #1. Handshake pins H2 and H4 may be used as
either inputs or outputs. Handshake pins H1 and H3 may only be used as
inputs.
The PI/T #1 pin PC3 is used as an interrupt request output. The 24-bit
timer can generate interrupt requests at a software programmable level.
This interrupt request line is connected to the IRQ #2 of the FGA-002.
PIRQ:
The PI/T #1 pin PC5 may be used as a port interrupt request output.
Normally, this pin is not used. However, PC5 may be used to generate an
additional interrupt if switch SW13-1 is OFF. In this case, the Port
Interrupt Request and the Timer Interrupt Request will use the same
FGA-002 interrupt channel. Therefore, they will generate interrupts at the
same interrupt priority level, and the user's software may need to poll the
PI/T device to determine the actual cause of the interrupt. For
compatibility with earlier boards, this pin is normally not used.
SW13-1Function
OFF (default)Port Interrupt Disabled
ONPort Interrupt Enabled
NOTE: There is another timer interrupt signal at PI/T #2 which doesn’t
i
have anything to do with these signals of PI/T #1.
3.10.9 Floating Point
Coprocessor Sense
Line at PI/T #1
3.10.10 Reserved Line
at PI/T #1
PC6:
This line reports whether or not an FPCP is installed on the CPU board.
PC6Function
0FPCP Installed
1FPCP Not Installed
PC2:
This line is not used. In order to retain compatibility with earlier and
future versions, this line should not be used in any applications.
Port General Control Register
Port Service Request Register
Port A Data Direction Register
Port B Data Direction Register
Port C Data Direction Register
Port Interrupt Vector Register
Port A Control Register
Port B Control Register
Port A Data Register
Port B Data Register
Port A Alternate Register
Port B Alternate Register
Port C Data Register
Port Status Register
Timer Control Register
Timer Interrupt Vector Register
Counter Preload Register
Count Register
Timer Status Register
"
"
"
"
"
"
3.10.13 I/O Configuration
of PI/T #2
☞
Page 74
The following table lists all I/O signals connected to PI/T #2. The
functions of these signals are described in the corresponding chapter.
SEE ALSO: Additional information is provided in the PI/T data sheet,
included in Section 4, ‘Circuit Schematics and Data Sheets,’ on
page 115.
User I/O via optional B6 or optional 5-row VME P2 connector
PA1
"
PA2
"
PA3
"
PA4
"
PA5
"
PA6
"
PA7
"
H1
User I/O via optional B6 or optional 5-row VME P2 connector
H2
"
H3
"
H4
"
PB0
Memory Size
PB1
"
PB2
"
PB3
Board ID
PB4
"
PB5
"
PB6
"
PB7
"
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I
I/O
I
I/O
I
I
I
I
I
I
I
I
3.10.14 12-Bit User I/O
Port at PI/T #2
PC0
Hardware ID
PC1
Hardware ID
PC2
Status of write protection for (default and optional) Boot PROMs
PC3
Timer Interrupt Request
PC4
Status of write protection for SYSTEM-Flash Memory
PC5
DMA control
PC6
Flash programming voltage control
PC7
Unused, reserved
I
I
I
O
I
O
O
I
PA0-PA7, H1-H4:
This 12-bit I/O port may be available (as a factory option) at a 16-pin
connector B6 and may be available (as a factory option) at the 5-row
VME P2 connector, providing a convenient connection for a flat cable.
Eight bits are connected to port A of PI/T #2 and can be used as inputs or
outputs. The remaining four bits are connected to the handshake pins of
PI/T #2. This port can be used to build a Centronics type interface.
The connector B6 (factory option) provides, besides the 12-bit user port
signals, power signals. The +5V power on pin 1 and pin 16 is protected
by a non destroyable 1A-fuse. The GND power is connected at pin 8 and
pin 9.
PB0-PB2:
From these lines, the on-board Shared RAM capacity can be read in by
software. The following assignment is defined:
From these lines, the CPU board identification number can be read in by
software. Every CPU board has a unique number. Different versions of
one CPU board (i.e. different speeds, capacity of memory, or modules)
contain the same identification number. In the case of the CPU-30 R4, the
number is ten ("10" decimal or 0A
PI/T #2 pin PC3 is used as a Timer Interrupt Request output. The 24-bit
timer can generate interrupt requests at a software programmable
interval. The Timer Interrupt Request line is connected to the local IRQ
#3 of the FGA-002. Optionally, the Timer Interrupt Request may be used
as a "watchdog" reset generator.
If the PI/T #2 Timer Interrupt Request line is connected as a watchdog
reset generator, then the user can program the 24-bit timer to generate a
local hardware reset whenever the timer counts down to zero. This allows
the user to implement a simple watchdog timer. In normal operation, the
timer would never expire. Instead, the user's software (for example, a
background system task) would constantly restart the timer. Should the
timer fail to be restarted, the PI/T will generate a low level on the Timer
Interrupt Request output pin. That will trigger the Reset Generator,
resetting the entire CPU board. The watchdog reset generator option is
enabled and disabled via a switch at location SW13-2.
SW13-2Description
OFF (default)Watchdog Timer Disabled
ONWatchdog Timer Enabled
i
3.10.18 PC0-PC1
Hardware ID
at PI/T #2
3.10.19 Floppy Drive
Ready Signal at
PI/T #2
NOTE: There is another timer interrupt signal at PI/T #1 which doesn’t
have anything to do with these signals of PI/T #2.
To allow simple detection of different hardware implementations, a
hardware ID-number can be read in on the PI/T #2 pins PC0-PC1.
CAUTION: PI/T #2 pin PC2 must be programmed as an input.
PC2Function
0Write to Boot PROM unprotected
1Write to Boot PROM protected
3.10.20 Floppy Drive
Write Protect
Signal at PI/T #2
3.10.21 DMA Control
Line at PI/T #2
PC4:
From this line the status of the write protection for the System Flash
Memory may be monitored.
CAUTION: PI/T #2 pin PC4 must be programmed as an input.
PC4Function
0Write to System Flash Memory unprotected
1Write to System Flash Memory protected
CAUTION: Writes to the System Flash Memory must always be
performed with a 4-byte wide port size and must be aligned on 4-byte
boundaries.
PC5:
This line controls the local devices when a DMA transfer is in progress.
When the DMA controller accesses a local device (SCSI or FDC), this
line must be set to "0".
3.10.22 Flash
Programming
Control at PI/T #2
Page 78
☞
SEE ALSO: There are two other DMA Control Lines (controlling the
local peripheral bus) which are described in Section 3.10.6, ‘DMA
Control Lines at PI/T #1,’ on page 72.
PC6:
A 12V-Vpp-Generator must be controlled to support programming of the
System Flash Memory and the Boot PROM memory in the default Boot
PROM socket.
The MB 87033/34 SCSI Controller, with its up to 4 Mbytes/s data
transfer rate, is installed on the CPU to interface directly to SCSI
Winchester disks, optical drives or tape streamers.
All I/O signals are available on the user defined pins of the VMEbus P2
connector. The I/O signal assignment is compatible with the SYS68K/
ISCSI-1 Controller which allows the use of the SYS68K/IOBP-1 for
interconnection to mass storage devices.
SEE ALSO: For further information please refer to Section 9.1.5,
☞
‘SYS68K/ISCSI-1 Disk Controller,’ on page 153 and to Section 2.11,
‘The SYS68K/IOBP-1,’ on page 26.
The SCSI Controller on the CPU board is fully supported by the installed
real-time monitor debugger VMEPROM.
3.11.1 Features of the
87033/34 SCSI
Controller
3.11.2 Address Map
of MB 87033/34
Registers
☞
- Functional superset of the MB87031 SCSI Controller
- Direct interface to SCSI bus devices with on-chip drivers
- Full support for SCSI control
- Service of either initiator or target device
- Eight byte data buffer register incorporated
- Transfer byte counter (24 bit)
- Independent control and data transfer bus
- Asynchronous data transfer speed of 2 Mbytes/s
- Synchronous data transfer speed up to 4 Mbytes/s
The registers of the MB 87033/34 are accessible via the 8-bit local data
bus (byte mode).
SEE ALSO: Additional information is provided in the MB 87033/34
data sheet, included in Section 4, ‘Circuit Schematics and Data Sheets,’
on page 115.
3.11.3 The SCSI DMA
Controller
Page 80
The 8-bit DMA channel of the SCSI Controller is directly connected to
the installed DMA Controller (inside FGA-002 Gate Array) allowing
data transfer with a maximum speed of 4 Mbyte/s.
The DMA Controller includes a 32-byte FIFO which waits until the 32
bytes are filled and then requests local bus mastership for an eight cycle
data transfer (32 bit in parallel).
In addition to the 32-byte DMA FIFO, the DMA channel includes a
second FIFO (8 bytes deep) to fill the DMA FIFO if the DMA transfer to
main memory is taking place. This allows continuous data transfer on the
local DMA bus with a data rate of 4 Mbyte/s without any timing gaps in
between.
This technique permits the CPU to perform in a real time capacity
because the ratio of CPU and DMA operation at the maximum SCSI data
transfer rate of 4 Mbyte/s is 73% for the CPU, 20% for the DMA
Controller and 7% for arbitration overhead. If the data transfer rate is less
than 4 Mbyte/s, the percentage range of CPU operation increases and the
DMAC range decreases while the overhead of 7% remains unchanged.
3.11.3.1DMA Control
Lines
Two output pins of PI/T #1 and one output pin of PI/T #2 are used to
control the data direction, to start the DMA Controller, and select the
local peripheral devices.
PI/T #1 Port B bits 6 and 7 control the local devices when DMA transfers
are initiated. The following table shows which bit selects the direction of
the DMA transfer and which bit selects the FDC or SCSI Controller.
PB7PB6Function
00DMA write to SCSI
01DMA read from SCSI
10DMA write to FDC
11DMA read from FDC
Port C bit 5 of PI/T #2 controls the local devices in case of direct memory
access (DMA) as shown in the following table.
PC5Function
0DMA active
1DMA is not active
The listing below provides a programming example for DMA transfers.
*--------------------------------------------------------------* DATA OUTPUT TO SCSI TARGET, USING THE MB87033/34 AND THE
* FGA-002 DMA CHANNEL
*---------------------------------------------------------------
:
BCLR #$07,PBDR+PI_T ;SELECT DMA WORKS WITH SCSI
BCLR #$06,PBDR+PI_T ;SELECT TRANSFER DMA TO SCSI
* THE FOLLOWING AUX VALUES ARE ONLY VALID FOR THE CPU-30 !
MOVE.B #$00,FGA02+AUXPINC ;AUX PIN CONTROL
MOVE.B #$30,FGA02+AUXDST ;AUXDSTSTART
MOVE.B #$45,FGA02+AUXDTE ;AUXDSTTERM
MOVE.B #$00,FGA02+AUXDSTR ;AUXDSTWEX
MOVE.L #BCOUNT,FGA02+DMABCNT ;BYTE COUNT
MOVE.L #SADDR,FGA02+DMASADR ;DMA SOURCE ADDR
MOVE.B #$C5,FGA02+DMASATR ;DMA SOURCE ATTRIBUTE (DPR)
MOVE.B #$C8,FGA02+DMADATR ;DMA DEST ATTRIBUTE (AUX)
MOVE.B #$41,FGA02+DMAGEN ;DMA GENERAL CONTROL
:
MOVE.B #$00,SCSI+TMODREG ;SET SCSI TRANSFER MODE
MOVE.B #$80,SCSI+SCMDREG ;SCSI COMMAND
BCLR #$00,PCDR+PI_T2 ;SET TO DMA ACTIVE
MOVE.B #$01,FGA02+DMARUNC ;START DMA CONTROLLER
WAIT TST.B FGA02+DMARUNC ;POLL ON DMA READY
BMI.B WAIT
BSET #$00,PI_T2+PCDR ;SET TO CPU ACTIVE
:
3.11.4 The SCSIbus
3.11.4.1SCSIbus
Configuration
Communication on the SCSIbus is only allowed between two SCSI
devices at any given time. There may be a maximum of eight SCSI
devices. Each SCSI device has a SCSI ID bit assigned. When two SCSI
devices communicate on the SCSIbus, one acts as an initiator, and the
target performs the operation. A SCSI device usually has a fixed role as
an initiator or target, but some devices may be able to assume either role.
An initiator may address up to seven peripheral devices that are
connected to a target. An option allows the addressing of up to 2048
peripheral devices per target using extended messages.
Of the eight SCSI devices supported on the SCSIbus, there can be any
combination of initiators and targets. Certain SCSIbus functions are
assigned to the initiator and other functions are assigned to the target. The
initiator may arbitrate for the SCSIbus and select a particular target. The
target may request the transfer of COMMAND, DATA, STATUS, or
other information on the data bus, and in some cases, it may arbitrate for
the SCSIbus and reselect an initiator for the purpose of continuing an
operation.
Information transfers on the data bus are asynchronous and follow a
defined REQ/ACK handshake protocol. One byte of information may be
transferred with each handshake. An option is defined for synchronous
data transfer.
3.11.4.2SCSIbus Signal
Termination
3.11.4.3SCSIbus
Terminator
Power
Each SCSIbus signal should be terminated at the physical start and the
physical end of the SCSIbus. Therefore, the CPU-30 R4 provides
circuitry for active termination.
Active termination can be controlled by switch SW7-3.
SW7-3Description
OFFActive SCSI termination on
ONActive SCSI termination off
The power for the terminator of any SCSI device will be provided from
the CPU board directly, or from the SCSIbus itself. If termination power
is not delivered from any other SCSI device, it is delivered from the CPU
board.
The TERMPWR (terminator power) supply from the CPU board is
protected by a self resetting fuse (1A max) and a diode in series, as
defined in the SCSI specification.
The on-board terminators will draw power from the SCSIbus
TERMPWR.
The CPU board contains a single chip floppy controller, the
FDC37C65C. The FDC is connected to the DMA controller of the
FGA-002 Gate Array. The installed driver/receiver circuits allow direct
connection of 3 1/2" and 5 1/4" inch floppy drives. All I/O signals are
available on the VMEbus P2 connector. The I/O signal assignment is
compatible to the SYS68K/ISCSI-1 controller, which allows the use of
the SYS68K/IOBP-1 and IOPI-2 for interconnection to mass storage
devices.
3.12.1 Features of the
FDC37C65C
Controller
3.12.2 Address Map
of the FDC
☞
- Built-in data separator
- Built-in write precompensation
- 128-, 256-, 512- or 1024-byte sector lengths
- 3 1/2" or 5 1/4" single and double density
- Programmable stepping rate (2 to 6 ms)
The registers of the FDC are accessible via the 8 bit local I/O bus (byte
mode). The following table shows the register layout of the FDC37C65C
for the CPU-30 R4.
SEE ALSO: Additional information is provided in the FDC37C65C data
sheet included in Section 4, ‘Circuit Schematics and Data Sheets,’ on
page 115.
FF80.380016Read Main Status Register
(Write is illegal)
FF80.380116Read Data Register
Write Date Register
FF80.388016Read DCHG Register
Write Data Rate Selection Register
3.12.3 Data Rate
Support
☞
Page 84
FF80.390016Write Digital Output Register
(Read is illegal)
The FDC37C65C allows two Data Rate Selection Options controlled via
the Data Rate Selection Register. The CPU-30 R4 supports the 16 MHz
and 9.6 MHz options.
SEE ALSO: For further details please refer to Section 4, ‘Circuit
Schematics and Data Sheets,’ on page 115.
The CPU-30 R4 supports two drive selects - DSEL 1 and DSEL 2 which
are generated by the FDC37C65C-Controller.
The FDC37C65C Floppy Controller provides two signals for motor
control. On the CPU-30 R4 they are tied together to build the Motor-On
Signal.
Two output pins of PI/T #1 and one output pin of PI/T #2 are used to
control the data direction, to start the DMA Controller, and to control the
used local devices.
PI/T #1 Port B bits 6 and 7 control the local devices in case of direct
memory access (DMA). The following table shows which bit selects the
direction of the DMA transfer and which bit selects the FDC or SCSI
Controller.
PB7PB6Function
00DMA write to SCSI
01DMA read from SCSI
☞
3.12.7 Floppy Disk
Connector
Assignment
10DMA write to FDC
11DMA read from FDC
Port C bit 5 of PI/T #2 controls the local devices in case of direct memory
access (DMA) as shown in the following table.
PC5Function
0DMA active
1DMA is not active
SEE ALSO:The listing in Section 3.12.7.1, ‘DMA Transfer
Programming Example,’ on page 86 provides a programming example
for DMA transfers.
NOTE: For the connection to the IOBP-1 back panel, please refer to
Section 2.11, ‘The SYS68K/IOBP-1,’ on page 26.
*--------------------------------------------------------------* READ DATA FROM FLOPPY, USING THE FDC AND THE FGA-002
* DMA CHANNEL
*-------------------------------------------------------------- :
BSET #$07,PI_T1+PBDR(A4) ;SELECT DMA WORKS WITH FDC
BSET #$06,PI_T1+PBDR(A4) ;SELECT TRANSFER FDC TO DMA
* THE FOLLOWING AUX VALUES ARE FOR CPU-30 ONLY !!!
MOVE.B #$00,FGA02+AUXPINC ;AUX PIN CONTROL
MOVE.B #$07,FGA02+AUXSST ;AUXSRCSTART
MOVE.B #$03,FGA02+AUXSTE ;AUXSRCTERM
MOVE.B #$0F,FGA02+AUXSRCW ;AUXSRCWEX
MOVE.L #BCOUNT,FGA02+DMABCNT ;BYTE COUNT
MOVE.L #DADDR,FGA02+DMADADR ;DESTINATION ADDRESS
MOVE.B #$C8,FGA02+DMASATR ;DMA SOURCE ATTRIBUTE (AUX)
MOVE.B #$C5,FGA02+DMADATR ;DMA DEST ATTRIBUTE (DPR)
MOVE.B #$81,FGA02+DMAGEN ;DMA GENERAL CONTROL
MOVE.B #$01,FGA02+DMARUNC ;START DMA CONTROLLER
MOVE.B #$88,FDC+FCMDREG ;READ SECTOR COMMAND
BCLR #$00,PI_T2+PCDR ;SET TO DMA ACTIV
WAIT TST.B FGA02+DMARUNC ;WAIT UNTIL DMA IS READY
BMI.S WAIT
BSET #$05,PI_T2+PCDR ;SET TO CPU ACTIVE
: