This PepCard product is carefully designed for a long and fault-free life; nonetheless, its life expectancy can be drastically
reduced by improper treatment during unpacking and installation.
Observe standard anti-static precautions when changing piggybacks, ROM devices, jumper settings, etc. If the product
contains batteries for RTC or memory back-up, ensure that the board is not placed on conductive surfaces, including antistatic plastics or sponges. These can cause shorts and damage to the batteries or tracks on the board.
When installing the board, switch off the power mains to the chassis. Do not disconnect the mains as the ground
connection prevents the chassis from static voltages, which can damage the board as it is inserted.
Furthermore, do not exceed the specified operational temperature ranges of the board version ordered. If batteries are
present, their temperature restrictions must be taken into account.
Keep all of the original packaging material for future storage or warranty shipments. If it is necessary to store or ship the
board, re-pack it as it was originally packed.
IssueBrief Description of ChangesPCB IndexDate of Issue
1Issue 101-01/2March, 1995
2General Corrections throughout Manual01-01/4June, 1995
2.0.1Correction of Figure 3.2.0.1 (Jumper Layout Solder Side)01-01/4July, 1995
3Updated for board index 0202December, 1995
This document contains proprietary information of PEP Modular Computers. It may not be copied or transmitted by
any means, passed to others, or stored in any retrieval system or media, without the prior consent of PEP ModularComputers or its authorized agents.
The information in this document is, to the best of our knowledge, entirely correct. However, PEP ModularComputers cannot accept liability for any inaccuracies, or the consequences thereof, nor for any liability arising from
the use or application of any circuit, product, or example shown in this document.
PEP Modular Computers reserve the right to change, modify, or improve this document or the product described
herein, as seen fit by PEP Modular Computers without further notice.
We grant the original purchaser of PEP products the following hardware and system warranty. No other warranties that
may be granted or implied by anyone on behalf of PEP are valid unless the consumer has the express written consent of
PEP Modular Computers.
PEP Modular Computers warrants their own products (excluding software) to be free from defects in workmanship
and materials for a period of 24 consecutive months from the date of purchase. This warranty is not transferable nor
extendible to cover any other consumers or long term storage of the product.
This warranty does not cover products which have been modified, altered, or repaired by any other party than
PEP Modular Computers or their authorized agents. Furthermore, any product which has been, or is suspected of
being damaged as a result of negligence, misuse, incorrect handling, servicing or maintenance; or has been damaged as a
result of excessive current/voltage or temperature; or has had its serial number(s), any other markings, or parts thereof
altered, defaced, or removed will also be excluded from this warranty.
A customer who has not excluded his eligibility for this warranty may, in the event of any claim, return the product at
the earliest possible convenience, together with a copy of the original proof of purchase, a full description of the
application it is used on, and a description of the defect; to the original place of purchase. Pack the product in such a way
as to ensure safe transportation (we recommend the original packing materials), whereby PEP undertakes to repair or
replace any part, assembly or sub-assembly at our discretion; or, to refund the original cost of purchase, if appropriate.
In the event of repair, refund, or replacement of any part, the ownership of the removed or replaced parts reverts to
PEP Modular Computers, and the remaining part of the original guarantee, or any new guarantee to cover the
repaired or replaced items, will be transferred to cover the new or repaired items. Any extensions to the original guarantee
are considered gestures of goodwill, and will be defined in the "Repair Report" returned from PEP with the repaired or
replaced item.
Other than the repair, replacement, or refund specified above, PEP Modular Computers will not accept any liability
for any further claims which result directly or indirectly from any warranty claim. We specifically exclude any claim for
damage to any system or process in which the product was employed, or any loss incurred as a result of the product not
functioning at any given time. The extent of PEP Modular Computers liability to the customer shall not be greater
than the original purchase price of the item for which any claim exists.
PEP Modular Computers makes no warranty or representation, either express or implied, with respect to its
products, reliability, fitness, quality, marketability or ability to fulfill any particular application or purpose. As a result,
the products are sold "as is," and the responsibility to ensure their suitability for any given task remains the purchaser's.
In no event will PEP be liable for direct, indirect, or consequential damages resulting from the use of our hardware or
software products, or documentation; even if we were advised of the possibility of such claims prior to the purchase of, or
during any period since the purchase of the product.
Please remember that no PEP Modular Computers employee, dealer, or agent are authorized to make any
modification or addition to the above terms, either verbally or in any other form written or electronically transmitted,
without consent.
The computer user today requires high performance to meet high expectations. At the same time, the mass of data that
has to be processed is dramatically increasing, for instance the data that a modern graphic user interface generates.
Additionally, there is a further demand on the communications ability and multi-functionality of the computer.
The VM62(A)/VM42(A) meets all the above requirements, combining high computational performance with excellent
communication ability via the AutoBahn™ Spanceiver™ chip.
A combination of the high performance CPU (Motorola MC68060 or 68040) and the Quad Integrated Communications
Controller chip, the Motorola MC68EN360 or QUICC, not only enables a pure computation performance from
approximately 35 MIPS to over 100 MIPS, but dispenses with the usual restrictions associated with communications
over serial interfaces. Communication tasks are dealt with by the QUICC chip, freeing the CPU from such timeconsuming chores. Fieldbus protocol, such as PROFIBUS, are also handled by the QUICC. In addition, the QUICC,
used together with PEP’s expanding CXC interface is ideally suited for communication tasks extending from 6 serial
interfaces over LAN to WAN (X.25, ISDN) applications. The ‘EN’ version of the QUICC also supports Ethernet on 2
channels (only one usable on the VM42(A)/VM62(A) using PEP standard software).
The various I/O interfaces are realised using piggybacks attached to the main board. Five options are at the moment
available. They are:
PEP’s AutoBahn technology has solved one of the major problems that exist in information technology - data transfer
over the various bus systems. Normally the data transfer rate over a bus system is below the data transfer capability of a
modern CPU chip. The AutoBahn chip (the Spanceiver MC100SX1451) allows transfer rates of up to 100 Mbyte/sec
over the VMEbus using the VMEbus lines SERA and SERB.
PEP has also developed a cost-effective VMEbus backplane series that support AutoBahn, called VBP4A, in 7, 12 and 15
slot options. These backplanes allow direct connection of the main power supply, hence reducing cabling costs
dramatically.
A CXM-SIO3 module is available in order to make all three serial interfaces that are available on the CXC accessible on
the VM62(A)/VM42(A). This is achieved by using RS232, SC-xxx or SI-xxx interfaces. For more details, please refer to
the CXM-SIO3 user’s manual.
AutoBahn ™ and Spanceiver ™ are trademarks of PEP Modular Computers.
VM62-BASEVMEbus single board computer comprising MC68060 @ 50 MHz,
MC68EN360 @ 25 MHz, 256 kByte dual-ported SRAM (with Gold Cap for
backup), configured for use with the AutoBahn interface piggyback, up to 6
serial interfaces (2 available on the front panel as RS232 and an additional 4
divided between the CXC interface and SI-Interface), CXC Interface, PEPbug.
VM62-BASESame as order no. 12349 but with 1 MByte dual-ported SRAM12350
VM42-BASEVMEbus single board computer comprising MC68040 @ 33 MHz,
MC68EN360 @ 33 MHz, 256 kByte dual-ported SRAM (with Gold Cap for
backup), configured for use with the AutoBahn interface piggyback, 6 serial
interfaces (2 available on the front panel as RS232 and an additional 4 divided
between the CXC interface and SI-Interface), CXC Interface, PEPbug.
VM42-BASESame as order no. 12344 but with 1 MByte dual-ported SRAM12345
VM42-BASESame as order no. 12344 but with MC68040V @ 33 MHz (3.3-V technology)12346
VM42-BASESame as order no. 12346 but with 1 MByte dual-ported SRAM12347
DM600Memory piggyback with 4 MByte DRAM and 1 MByte Flash EPROM11852
DM600Memory piggyback with 4 MByte DRAM and 4 MByte Flash EPROM11853
DM601Memory piggyback with 16 MByte DRAM and 1 MByte Flash EPROM11854
DM601Memory piggyback with 16 MByte DRAM and 4 MByte Flash EPROM11855
DM602Memory piggyback with 1 MByte DRAM and 1 MByte Flash EPROM12765
12349
12344
DM603Memory piggyback with 32 MByte DRAM and 512 kByte Flash EPROM13027
DM603Memory piggyback with 32 MByte DRAM and 2 MByte Flash EPROM13627
SI-10B210Base2 (Thin) Ethernet (cheapernet) interface with RG58 (coax) connector9925
SI-10B510Base5 (AUI) Ethernet interface piggyback with 15-pin D-Sub connector9924
SI-10BT10BaseT (Twisted pair) Ethernet interface piggyback with RJ45 connector9926
SI-DUMMYFront panel only fitted when no SI piggyback required12351
SI-PB232Serial interface piggyback for 2 RS232 connections (Modem interface) with 2
RJ45 connectors
SI-PB232-ISOSerial interface piggyback for 1 RS232 optoisolated connection with 1 RJ45
connector (Available in 1996 if requested)
SI-PBPRORS485 optoisolated interface piggyback for 2 wire half-duplex (PROFIBUS)
connection with 9-pin D-Sub connector
MP-AB100AutoBahn interface piggyback complete with all control logic, 128 kByte 32-
bit fast SRAM as buffer for AutoBahn data transfer with Spanceiver MC
100SX1451 of 50/100 MByte/s
CABLE-VM42-
232
3 meter RS232 Serial Interface cable for VM42(A) / VM62(A) with 9-pin
CXM-SIO3-1CXM module with 3 RJ45 connected RS232 ports for use with a CXC
backplane
CXM-SIO3-1CXM module with 3 RJ45 connected RS232 ports, compatible for direct
connection to a CPU board
CXM-SIO3-2CXM module with 2 RJ45 connected SC piggyback ports and one SI
piggyback interface, no front panel (delivered with SC piggyback) for use with
a CXC backplane
CXM-SIO3-2CXM module with 2 RJ45 connected SC piggyback ports and one SI
piggyback interface, no front panel (delivered with SC piggyback), compatible
for direct connection to a CPU board
CXM-SIO3-3CXM module with 3 RJ45 connected SC piggyback ports for use with a CXC
backplane
CXM-SIO3-3CXM module with 3 RJ45 connected SC piggyback ports, compatible for direct
connection to a CPU board
CXM-SIO3-4CXM module with 3 15-pin D-Sub connected SC piggyback ports, 8TE front
panel for use with a CXC backplane
CXM-SIO3-4CXM module with 3 15-pin D-Sub connected SC piggyback ports, 8TE front
panel, compatible for direct connection to a CPU board
TBD
13692
TBD
13693
TBD
13694
TBD
13695
Each VM62(A)/VM42(A) comes complete with 2 RS232 serial interfaces situated on the lower half of the front panelThese interfaces are provided with TxD and RxD signals by the SMC1 and SMC2 channels of the ‘QUICC’ controller.
The SCC1 channel of the ‘QUICC’ provides the interface to one of the available SI-xxx piggybacks. All other channels
(SCC2, SCC3 and SCC4) of the ‘QUICC’ are ported to the CXC interface except for the SI-PB232 piggyback which has
on-board additional control provided by the SCC4 channel through the SI Interface.
As mentioned above, a CXM-SIO3 module is available in order to make all the serial interfaces accessible on the
VM62(A)/VM42(A). For more details, please refer to the CXM-SIO3 user’s manual.
Important: The VM62(A)/VM42(A) must be ordered with a memory module (DM60x) and a front
MC6806066 or 50 MHz(3.3V)
MC6804033 or 25 MHz
MC68040V33 or 25 MHz(3.3V)
MC68LC04033 or 25 MHz
MC68EN360, 25 or 33MHz used in companion mode
1, 4, 16 or 32 Mbyte
0.5, 1, 2, or 4 MByte
1 MByte or 256 kByte (dual-ported, backed-up using Gold-Caps)
2 kbit (serial); 1 kbit available for applications
Master and slave with optional AutoBahn Interface (100 MBytes/sec)
Single level (BR3*), release-when-done daisy-chain
Standard Superv./User Prog./DataHEX 39/3A/3D/3E
User DefinedHEX 10-17/18-1F
Short I/OHEX 29/2D
System controller functions
•Automatic First Slot Detection (FSD)
•SYSRES*(disabled by jumper)
•SYSCLK*(disabled by jumper)
•ACFAIL*
•SYSFAIL*
•Power monitor
•Bus monitor(programmable)
•VME IRQ mask register
A24:D16
Dual-port SRAM
1 Mailbox IRQ
Interrupt Control
7 Level VME IRQ Handler,
maskable via VME IRQ mask
register
System vectors
* Available for Index 02 boards or later.
Slave
1 Mbyte window, software programmable base (1 out of 16 addresses)
Lower 8kBytes of the SRAM area
RISC controller (in the 68EN360) with 14 dedicated DMA channels
4*multiprotocol SCCs up to 8 MBaud
with one (two) supporting IEEE 802.3/Ethernet up to 10 Mbit/s
10Base5, 10Base2 or 10BaseT
2*UARTs RS232 (XON/XOFF) RS232 up to 120 kBaud
4 independent baud rate generators
CXC Interface
- 16 bit asyncronous data transfer with 4 IRQs,
independent DMA channel
- 3 serial interfaces
TICK
General Purpose
Watchdog
Special Functions
Real-time clock (backed-up)
Serial EEPROM
DMA
Front Panel Functions
Data Retention
Short term backup for RTC and
SRAM via on-board Gold-Cap
Periodic Interrupt Timer, programmable
4*16 bit or 2*32 bit, programmable
512 ms time-out for reset, programmable
Date (year, month, week, day)
Time (hour, minute, second)
1 kbit for board specific data (serial number, Internet address, etc.)
+ 1 kbit for application purposes
2 independent channels (supports single and dual address transfers
between all offboard locations including DRAM, FLASH,
AutoBahn memory, CXC and VME)
RESET button
ABORT button
HALT LED (red)
Watchdog LED (yellow)
General purpose LED (green)
The Table below illustrates the capabilities of the available CPUs. The 68060 processors operating at 50 MHz deliver up
to 100 MIPs while the 68040 processors operating at 33 MHz give performances up to 35 MIPs.
25/33 MHz - the ‘QUICC’ chip used in ‘companion mode’ is tightly coupled to the CPU. Working as an I/O and system
controller, it provides all the necessary interfaces, timers and clocks etc. in addition to the DRAM memory controller.
Serial Channels
Six are provided by the ‘QUICC’ - Two SMC channels are ported to the front panel and the remaining four SCC channels
may be optionally configured as shown below.
Three different piggybacks complete with all the associated control logic are available providing 10Base5, 10Base2 or
10BaseT interfaces.
Note
The SI-10B5 piggyback requires an external +12V power source to operate.
Fieldbus Interface (SI-PBPRO)
This is a fully optoisolated RS485 (PROFIBUS) interface piggyback with a 9-pin D-Sub connector.
RS232 Serial Interface
Two piggybacks are available with RJ45 connectors for MODEM compatible communication.
AutoBahn Interface (MP-AB100)
This is realised via a piggyback containing all the necessary control logic, 128 kByte high speed SRAM (10 ns) as a
memory buffer between the processor and the AutoBahn chip (MC 100SX1451) for communication on the high speed
serial data lines over pins b21 and b22 of the VMEbus.
DMA Channels
2 independent channels are provided by the ‘QUICC’ chip and can be used by applications requiring data transfer between
CXC-modules, DRAM, FLASH memory, dual-ported SRAM and AutoBahn memory buffers. This memory can be
configured with different memory options allowing tremendous flexibility when customising memory requirements for
real-time applications.
DRAM/FLASH
This memory, complete with a 32 bit data wide access bus is placed on a piggyback with addressing capability for up to
two memory banks of 64 MByte each. On-board +5V FLASH memory provides the latest ROM technology allowing the
user to take advantage of the on-board programming facility to produce low cost upgrades by simply overwriting existing
stored data.
SRAM
This is a dual-ported battery-backed (Gold-Cap) memory area with a 16 bit data wide access bus. Users of the VMEbus
and the on-board CPU both have access to this memory. The lower 8 kByte are reserved for the location monitor.
EEPROM
Although a 2 kbit EEPROM is provided on-board, 1 kbit has been pre-programmed with PEP production data (boot info,
Ethernet registration, etc) leaving the remaining 1 kbit for user application code. A write protect jumper prevents
accidental erasure.
Motorola’s MC68EN360 is a 32 bit high performance communication controller, combining powerful peripheral
functions with system integration functions and an on-chip microprocessor core (CPU32+).
On the VM62(A) / VM42(A), the on-chip CPU core is disabled and replaced with a more powerful external CPU, the
MC68040 or MC68060. The 68EN360 operates as a slave to the CPU in so-called ‘Companion Mode’. In this mode, the
68EN360 provides complete I/O functionality. The DMA channels can still obtain ownership of the CPU’s system bus
and therefore all on-chip DMA channels can address the whole of the address space. Moreover, important functions for
system integration, such as memory controller, clock generation, interrupt controller etc. are available in this mode,
meeting the requirements for the initialisation of the 68EN360, described later in this manual.
The programming of the 68EN360 begins by determining the block of on-chip RAM and registers via the MBAR
register. This register is located at a fixed address and can only be accessed in CPU space.
2.2 Address Decoder
2.2.1 Basic Structure
The address decoder of the VM62(A) / VM42(A) consists of two basic parts. A primary address decoder pre-decodes the
select signals for the processor data bus (in front of the bussizer) and for the I/O data bus (behind the bussizer). With
reference to initial boot cycles, the primary address decoder passes or enables a secondary address decoder stage. The
secondary address decoder stage is realised using the programmable chip slect logic of the MC68EN360. The 8 outputs of
the 68EN360 chip select logic are used for the base addresses of the various memory and I/O address ranges.
2.2.2 Boot Decoding
Due to the fact that the default boot memory used by the VM62(A) / VM42(A) is FLASH memory, which is completely
reprogrammable, a special boot decoder is provided. The boot memory is jumper selectable, the user having the choice
between FLASH (default), VMEbus memory or the on-board AutoBahn Interface. The boot decoder redirects the physical
address range 0H to 1000000H from either FLASH (DM60x), VMEbus or MP piggyback, providing the selected boot
memory is initially accessed.
Note
VMEbus boot memory must be located at VME base address 0H in Standard Supervisor Program/Data
address space.
The primary address decoder generates the following select signals.
CS_360Secondary address decoder (68EN360, DRAM, FLASH)
CS_VMEVMEbus address range
CS_AUTAutoBahn Interface address range
CS_BSSBussizer address range (VME, SRAM, AutoBahn, I/O)
BERR_0Reserved address range (Bus Error)
EN_BSS68EN360 DMA address range
IACKInterrupt Acknowledge Cycle
2.2.4 Secondary Address Decoder
The secondary address decoder is built by the 68EN360 chip select logic and is therefore programmable. The outputs are
used as base address selects, as shown below.
68EN360 Chip SelectConnected to
CS0FLASH
CS1DRAM
CS2VME via 68EN360 DMA
CS3AutoBahn Interface
CS4SRAM
CS5CXC
CS6RTC
CS7Control / Status Registers
00 xx xx xx
04 xx xx xx
07 00 0x xx
09 xx xx xx
0A xx xx xx
0B xx xx xx
0C xx xx xx
0D xx xx xx
1x xx xx xx
2x xx xx xx
3x xx xx xx
4x xx xx xx
5x xx xx xx
6x xx xx xx
82 xx xx xx
83 xx xx xx
85 00 xx xx
87 xx xx xx
87 xx xx xx
9x xx xx xx
Ax xx xx xx
Bx xx xx xx
C0 xx xx xx
C4 xx xx xx
C7 xx xx xx
CA xx xx xx
CB F7 0x xx
CC xx xx xx
CD 00 00 01
CD 00 00 05
CD 00 00 07
Dx xx xx xx
Ex xx xx xx
Fx xx xx xx
The following address area is non-cachable serialised.
VMEbus (CS_VME), user-defined AM code
VMEbus (CS_VME), user-defined AM code
VMEbus (CS_VME), short I/O AM code
VMEbus (CS_VME), user-defined AM code
DMA-VME, 68EN360’s CS2
In order to determine the base of the 68EN360’s internal memory map, the module base address register
(MBAR) must be set. The location of this register is fixed in the address area Supervisor CPU Space at
3FF00H. For more information, please refer to the Software Configuration chapter in this manual.