The product described in this manual is
in compliance with all ap plied CE standards.
Page 2
GeneralVSBC-32
Revision History
Manual/Product Title:VSBC-32
Manual ID Number:21168
Rev.
Index
0100Initial Issue00/1Aug 95
0200General corrections00/2D ec 95
0201J9 default setting chan ged00/2Nov 96
0300General corrections and new manual structure01Dec 96
0301New Preface01Aug 98
0311Improvement to Fig. 2.1.3. In Appendices, correc-
04Information of Er rata S heets 0100 _1/2 in tegra ted,
Brief Description of Ch angesBoard Index
01Sept 98
tions to flash a ddres ses on pag es MEM-2 to
MEM-4, page MEM-5 replaced.
01Ju ly 00
adequate manual structure , new mem ory piggybacks mentioned, desc riptio n of co mbi ned sys tem
and communications con troller fuc ntionality,
function-related board diagrams, cohere nt terminology (e.g. proce ssor and bo ard varia nt names)
etc. Appendices mod ified, upda ted, reduced .
This document contains information proprietary to
copied or transmitted by any means, disclosed to others or stored in any retrieval system or
media, without the prior written consent of
rized agents.
The information contained in this document is, t o the best of our knowledge, entirely correct .
However,
quences 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
cannot accept liability for any inaccuracies, or the conse-
PEP Modular Computers GmbH
PEP Modular Computers
PEP Modular Computers
or one of its autho-
without further notice.
. It may not be
Trademarks
PEP Modular Computers
marks owned by
document may include names, company logos and trademarks, which ar e registered trademarks and, therefore, proprietary to their respective owners.
PEP Modular Computers GmbH
, the
PEP
logo and, if occurring in this manual, “CXM” are trade
This symbol indicates that the product described in this manual
is in compliance with all applied CE standards. Please refer
also to the section “Applied Standards” in this manual.
Caution, Electric Sh ock!
This symbol and title warn of hazards due to electrical shocks
(> 60V) when touching products or parts of them. Failure to
observe the precautions indicated and/or prescribed by the law
may endanger your life/health and/or result in damage to your
material.
Please refer also to the section “High Voltage Safety Instructions” on the f ollowing page.
Warning, ESD Sensitive Dev ice!
This symbol and title inform that electronic boards and their
components are sensitive to static electricity. Therefore, care
must be taken during all ha ndling operat ions and ins pections of
this product, in order to ensure product integrity at all times.
Please read also the section “Special Handling and Unpacking
Instructions” on the following page.
Warning!
This symbol and title emphasize points which, if not fully understood and tak en into cons ider ation b y the read er, may endanger
your health and/or result in damage to your material.
Note...
This symbol an d title emph asi ze aspe cts the rea der sh ould read
through carefully for his or her own advantage.
PEP Advantage
This symbol and title emphasize advantages or positive aspects
of a product an d/or proce dure.
Your new
to ensure the renown electrical sa fety requirements. I t was also designed for a long fault-free
life. However, the life expectancy of your product can be drastically reduced by improper treatment during unpacking and installation. Therefore, in the interests of your own safety and of
the correct operation of your new
ing guidelines.
PEP
product was developed and tested carefully to provide all features necessary
PEP
product, you are requested to conform with the follow-
High Vol tage Safety Instructions
Warning!
All operations on this de vice must be carried out by sufficiently
skilled personnel only.
Caution, Electric Sh ock!
However, serious electrical shock hazards exist during all
installation, repair and maintenance operations with this product. Therefore, always unplug the power cable to avoid exposure to hazardous voltage.
Before installing your new
PEP
product into a system always
ensure that your ma ins power is switched off. This applies al so
to the installation of piggybacks.
Special Handling and Unpacking Instructions
ESD Sensitive Devic e!
Electronic boards and their components are sensitive to static
electricity. Therefore, care must be taken during all handling
operations and inspections of this product, in order to ensure
product integrity at all times.
•Do not handle this product out of its protective enclosure while it is not used for operational
purposes, unless it is otherwise protected.
•Whenever possible, unpack or pack this product only at EOS/ESD safe work stations.
Where safe work stations are not guaranteed, it is importa nt for the user to be electri-cally
discharged before touching the product with his/her hands or tools. This is most easily
done by touching a metal part of your system housing.
•It is particularly important to 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
anti-static plastics or sponges. They can cause short circuits and damage the batteries or
tracks on the board.
•In order to maintain
any way. Changes or modifications to the device, which are not explicitly approved by
Modular Computers
as a special handling instruction, will void your warranty.
•This device should only be installed in or connected to systems that fulfill all necessary
technical and specific environmental requirements. This applies also to the operational
temperature range of the specific board version, which must not be exceeded. If batteries
are present, their temperature restrictions must be taken into account.
•In performing all necessary installation and application operations, please, follow only th e
instructions supplied by the present manual.
•Keep all the original packaging material for future storage or warranty shipments. If it is
necessary to store or ship the board please re-pack it as nearly as possible in the manner
in which it was delivered.
•Special care is necessary when handling or unpacking the product. Please, consult the
special handling and unpacking instruction on the following page of this manual.
PEP’s
product warranty, this product must not be altered or modified in
granted or implied by anyone on behalf of
written consent of
WARRANTY
PEP Modular Computers
PEP Modular Computers
manufacturing and material defects for a period of 24 consecutive months from the date of
purchase. This warranty is not transferable nor extendible to cover any other users or longterm storage of the product. It does not cover products which have been modified, altered or
repaired by any other party than
more, any product which has been, or is suspected of being damaged as a result of negligence, improper use, incorrect handling, servicing or maintenance, or which has been
damaged as a result of excessive current/voltage or temperature, or which has had its serial
number(s), any other markings or parts thereof altered, defaced or removed will also be
excluded from this warranty.
If the customer’s eligibility for warranty has not been voided, in the event of any claim, he may
return the product at the earliest possible convenience to the original place of purchase,
together with a copy o f the original document of purchase, a full description of the application
the product is used on and a description of the defect. Pack the product in such a way as to
ensure safe transportation (see our safety instructions).
PEP
provides for repair or replacement of any part, as sembly or sub-assembly at their own
discretion, or to refund the original cost of purchase, if appropriate. In the event of repair,
refunding or replacement of any part, the ownership of the removed or replaced parts reverts
to
PEP Modular Computers
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” issued by
grants the original purchaser of
as described in the following. However, no other warranties that may be
PEP
are valid unless the consumer has the express
.
warrants their own products, excluding software, to be free from
PEP Modular Computers
, and the remaining part of the original guarantee, or any new
PEP
PEP
products a
or their authorized agents. Further-
with the repaired or replaced item.
TWO YEAR LIMITED
PEP Modular Computers
rectly from any warr anty claim, other than the above specified repair, replacement or refunding. In particular, all claims 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, are
excluded. The extent of
original purchase price of the item for which the claim exists.
PEP Modular Computers
respect to its products’ reliability, fitness, quality, marketability or ability to fulfil 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 rem ains that of the purchaser. In no event will
be liable for direct, indirect or consequential damages resulting from the use of our hardware
or software products, or documentation, even if PEP were advised of the possibility of s uch
claims prior to the purchase of the product or during any period since the date of its purchase.
Please remember that no
make any modification or addition to the above specified terms, either verbally or in any other
form, written or electronically transmitted, without the company’s consent.
will not accept liability for any further claims resulting directly or indi-
PEP Modular Computers
issues no warranty or representation, either explicit or implicit, with
VMEbus architecture. In addition, some products also support the CXC and/or
Enhanced CXC (eCXC) local mezzanine interface standards which represent a streamlined variant of the VMEbus standard itself. Thus a wide range of I/O functions for industrial applications are supplied. Some of the major advantag es of the VMEbus standard
are:
•internationally accepted VITA standards (VMEbus, CXC, eCXC);
•broad range of available VMEbus solutions
•scalable processor performance
In addition, in combination with (e)CXC technology the VMEbus equipment offers the
following advantages:
product described in this chapter operates with the
•lower costs and optimized reliability thanks to reduced design complexity;
•compact I/O sub-systems thanks to easier I/O wiring.
For detailled information concerning the VMEbus and (e)CXC standards, please consult
the VMEbus and CXC Specifications which are available via the
Trade Association (VITA): http://www.vita.com
Many system-relevant features that are specific for VMEbus systems can be found in
the ANSI/VITA VME64 Standard and in the VITA/
despite its name, applies also to VMEbus MPI carriers.
The VME64 Standard includes the following information:
•VMEbus Specification
•Signal Lines, Bus Modules, Typical Operation
•Electrical Specifications
•Mechanical Specifications
The CXC MPI Specification includes the following information:
•Mechanical dimensions
•Electrical specifications
•Interface description
•ID Byte assignment
With reference to the (e)CXC aspects of mixed VMEbus+CXC systems please refer
The VSBC-32(E) is a 3U (Enhanced) CXC combined system and communications controller board that can operate in either a VMEbus or a mixed VMEbus+CXC environment. The board is based on the Motorola Quad Integrated Communications Controller
“QUICC” MC68(EN)360. Therefore, it is particularly suitable for system control functions
within applications with communications requirements. Depending on the controller chip
used, there are two board variants with different CPU frequencies. The board’s external
interfacing consists of a twin RS232 interface connector, which can be extended by
means of a variety of seria l interface piggybacks and/or external seri al interface modules. Other piggybacks provide DRAM/ flash memory.
Some of the outstanding features of the product described in this manual are:
•VMEbus system and communications controller board
•Both VMEbus and eCXC connectivity
•Master/slave system controller functionality
•32-bit Motorola MC68(EN)360 integrated CPU and communications controller
•25Hz or 33Hz CPU frequency
•CPU on-chip background debugging
•1, 4, 16, 32 or 64 MB DRAM
•0, 0.5, 1, 2 or 4 MB flash memory
•256kB or 1 MB SRAM
•2kbit serial EEPROM
•256kB or 1MB DIP (flash) EPROM
•Real-time clock (backed-up)
•Six different communication standards possible:
•Serial I/O (RS232, RS485; RS422 on request)
•Ethernet (10Base2, 10Base5 or 10BaseT Ethernet)
•Up to six frontpanel serial interface connectors
•Compatibility with external serial interface module CXM-SIO3
•Reset and Abort control (frontpanel buttons)
•Halt, watchdog and general-purpose status indicators (frontpanel LED’s)
•OS-9 and VxWorks
®
drivers
1.2.2Boar d Variants
Two basic variants of the VSBC-32(E) with different processors are available. Depending on the controller chip used and the SRAM size, there are four vari ants o f the VSBC32(E) system and serial communications controller board. The distinctive features of the
variants are listed in the following
•Ethernet capability
•CPU frequency
•SRAM size
The following basic board variants are available:
•VSBC-32: MC68360 processor, no Ethernet control capability.
•VSBC-32E: MC68EN360 processor, Ethernet control capability.
The MC68EN360 processor is also available with two different clock rates:
•25MHz
•33MHz (this variant is again supplied with either 256kB or 1MB SRAM ).
The below described frontend connectivity and interface expandibility are common to all
board variants.
1.2.3Board Connectivity and Interface Expandibility
The VSBC-32(E) mainboard is provided with the following standard connectors:
•Non-optoisolated RS232 serial interface (two RJ45 connectors, on frontpanel)
•One set of piggyback inter face connectors for serial interface (SI) piggybacks
(three 7-pin row male connectors)
•One set of memory piggyback interface connectors
(two 50-pin row female connectors)
•Background debug mode (BDM) interface (one 12-pin row male connector)
•VMEbus backplane interface
(one 96-pin DIN 41612, style C male connector)
•Enhanced CXC mezzanine interface
(one 96-pin DIN 41612, style C male connector)
In addition, the mainboard external interfacing is usually integrated by one o f the follow ing piggyback-mounted frontpanel interface options (serial interface piggybacks). The
kinds of piggyback that can be used depend on the mainboard variant.
Table 1-1: Serial Interface Piggy backs
PiggybackDescriptionBoard Variant
SI-PB232Non-optoisolated RS232 serial interface (two RJ45 connectors)
SI-PB485-ISOOptoisolated RS485 serial interface (one 9-pin female DSUB connector)
Applications requiring further communication interfaces may be upgraded by means of
an external CXM-SIO3 serial interface module which provides the following interface
extension possibilities:
•RS232 serial interface connectors (non-optoisolated)
Maximum one CXM-SIO3 module can be controlled by a VSBC-32(E) board. The CXMSIO3 module provides access to internal communication signals of the base board that
are transferred to the module via the CXC bus.
For a detailled list and description of the frontpanel interface and serial interface/communication piggybacks please refer to the “Serial Interface Piggybacks” appendix of this
manual as well as to the CXM-SIO3 user’s manual and its “Serial Communications Piggybacks” appendix respectively.
1.2.4Memory Piggybacks
The VSBC-32(E) mainboard is not provided with any on-board DRAM/flash. These are
provided by special memory pig gybacks (DM60x). By means of these piggybacks the
following memory configurations are possible:
•≤64MB of DRAM
•≤4MB of flash/EPROM
For a detailled description of the memor y piggybacks please refer to the “Mem ory Pig-
gybacks” appendix of this manual.
1.2.5System-Relevant Information
System Configuration
Up to twenty-one VSBC-32(E) boards can be installed in a VMEbus 3U rack. Please
refer to the description of the VMEbus backplane connector in the Functional Description chapter of this manual. If used as a system controller, the board should be always
installed in the system slot.
If a CXM-SIO3 or a CXM-SCSI module is used in combination with the VSBC-32(E), the
module can be “sandwiched” with the controller, Communication between the controller
and the I/O module being acchieved via the VSBC-32(E)’s on-board CXC connector.
Master/Slave Functionality
The VSBC-32(E) is a combined system and communications controller boar d provided
with both a VMEbus backplane interface which can operate both as a VMEbus master
and slave simultaneously. Thanks to this feature all twenty-one VSBC-32(E) boards
possible in a VMEbus system can operate as VMEbus masters while at the same time
sixteen of them can act as VMEbus slaves. The VSBC-32(E) VMEbus master/slave (or
neither) operation is a function of the application software.
Bootstrap Loader
Via the VSBC-32(E) frontend serial interface connectors the flash memory of the
board’s memory piggyback can be re-programmed by means of the Bootstrap Loader
which is delivered already installed in the D M60x memory piggy backs. This standalone
software has the capability of loading flash memory from Motorola S-records or from
any absolute address. If the downloaded image does not work pr operly, the Bootstrap
Loader can be re-entered, the memory c ontents analyzed and a further programming
cycle initiated.
Warn in g!
To avoid damaging of your Bootstrap Loader and, consequently,
leaving your board unusable, please read the separate Bootstrap
Loader manual before re-setting the flash contents of your VSBC32 board.
Operating Systems
The VSBC-32(E) can operate under the following operating systems:
•OS-9
•VxWorks
Drivers are available for both operating systems.
Porting to other operating systems on request.
The additional frontend connector(s)
depend(s) on the type of serial interface
piggyback insta lled in combination with
the VSBC-32(E) mainboard. For any
details, please refer to the “Serial Interface Piggybacks” appendix in this manual.
The VSBC-32(E) is a 3U VMEbus combined system and communications controller
board based on the Motorola Quad Integrated Communications Controller “QUICC”
MC68(EN)360. Depending on the controller chip used and the SRAM size, there are
four board variants with different characteristics. The following table provides an overview of the various VSBC-32(E) board variants.
Table 1-1: VSBC-32(E) Board Variants
Board NameProc esso r
VSBC-32
MC68360—25MHz256kB
Ethernet
Capabilit y
+
VSBC-32E
MC68EN360
+
+
Being the MC68(EN)360 a CPU and serial communications contr oller, it is particularly
suitable for system control functions within applications with communications requirements such as LAN, WAN or fieldbusses (CAN, LON, PROFIBUS).
In fact, both the VSBC-32 and the VSBC-32E allow for a wide range of serial interfaces
based on the MC68(EN)360 controller which is able to handle up to six seri al communications channels. The channels can be configured in the following way:
•Four full modem interface connectors / multiprotocol channels (SCC interfaces).
Thus, the VSBC-32(E) mainboard comes complete with two non-optoisolated RS232
external interfaces which are located on the lower half of the front panel. However, the
external serial interfacing can be extended by means of a variety of serial interface (SI)
piggybacks and/or a CXM-SIO3 type external serial interface module. This external module can be either “sandwiched” with the controller or placed to the right of the VSBC-32(E).
In the first case, communication between the controller and the I/O module is acchieved
via the VSBC-32(E)’s on-board CXC connector, in the second case via the VMEbus.
Processor
Frequency
25MHz256k B
33MHz256k B
33MHz1MB
SRAM Size
As the CXM-SIO3 can be used again as a carrier for various serial interface (SI) and
serial communications (SC) piggy backs, the VSBC- 32/CXM-SIO3 tandem r epresents a
really powerful and versatile sytem control and serial communications control set.
Together with the two service/debug interfaces, a maximum of three (four with the serial
interface piggyback fitted) completely configured serial interfaces are available for the
base board. Three (two with serial interface piggy back fitted) serial interfaces may be
configured via the VMEbus where three of the four full modem Interfaces are routed.
The VSBC-32(E) allows also a significant variety of memory configurations, mainly
DRAM and flash memory located on special memory piggybacks, add-on flash/EPROM
on DIP s ockets, battery backed-up SRAM and EEPROM.
Under the aspect of system control the on-chip 32-bit CPU core of the Motorola
MC68(EN)360 provides system integration at different processor frequencies. The processor core acts essentially as a Motorola CPU32 microprocessor operating at 25MHz or
33MHz without cache memory. In addition, the MC68(EN)360 offers background debugging via the on-chip “Background Debug Mode” which allows direct communication with
the CPU.
To act as a system controller, the VSBC-32(E) is provided with arbiter, system clock
driver, power monitor with system reset driver, IACK daisy chain driver and 7-level
VMEbus interrupt controller.
Arbitration is single-level FAIR (compare VME64 Specification Rule 3.14/Observation
3.17). If the VSBC-32(E) is used as a system controller and consequently placed in the
VMEbus backplane’s system slot, a special detection function provided by the board
makes any “slot 1” jumper setting superfluous. The VSBC-32(E) also provides a bus
monitor for the VMEbus.
Interrupt Control
The interrupt control logic of the MC68(EN)360 processes internal interrupt requests
alongside with external autovectored interrupt requests and a “mailbox” interrupt request
from the VMEbus control/status register. The interrupt control logic is built up using the
processor’s internal interrupt control and an external IRQ7 interrupt handler.
Internal requests are related to all interrupt requests caused by the controller sources,
including the processor’s system integration functions (watchdog timer, periodic interrupt timer) and the communications processor module (RISC controller, timers, DMA’s,
SCC’s etc.).
In order to avoid conflicts regarding the different interrupt levels, it is recommended to
use IRQ level 4 for the MC68(EN)360 CPU internal requests and IRQ level 6 for the
MC68(EN)360 serial controller internal requests.
In addition, external interrupt sources can generate autovectored interrupts and an
external VMEbus master may require an interrupt by setting a “mailbox” IRQ in the
VMEbus control/status register.
For any detailled information as well as a complete list of the Motorola
controller signals please refer to the relating Data Sheet.
Table 2-2: External Autovector and Mailbox Interrupts
SourceInterrupt SourceInterrupt Type
ABORT / ACFAILMC68(EN)360, pin IRQ7Aut ovecto r 7
ReservedMC68 (EN)36 0, p in IRQ6Aut ovec tor 6
Mailbox IRQMC68(EN)360, pin IRQ5Autovector 5
ReservedMC68 (EN)36 0, p in IRQ4Aut ovec tor 4
SYSFAILMC68(EN)360, pi n IRQ3Autov ector 3
ReservedMC68 (EN)36 0, p in IRQ2Aut ovec tor 2
ReservedMC68 (EN)36 0, p in IRQ1Aut ovec tor 1
Mailbox Pendi ngBit P_IR Q5Control/stat us r egiste r
2.2.2Memory Configurations
The VSBC-32(E) allows a significant variety of memory configurations. The special
DRAM/flash piggybacks (DM60x), for instance, allows the user to take advantage of the
on-board programming facility to produce low cost upgrades by simply overwriting existing stored data. This memory can be configured with different memory options allowing
remarkable flexibility when customizing memory requirements for real-time applications.
The DM60x piggybacks provide between 1MB and 64MB o f DRAM with 32-bit access
and up to 4MB of +5V flash memory. In addition, a set of DIP sockets located on the
VSBC-32(E) mainboard allows the installation of an additional 1MB of flash/EPROM.
Both memory devices can be used for bootstrapping. The selection of the boot memory
is achieved by hardware jumpering.
Note...
Physically the DM60x piggybacks provide up to 64MB of DRAM.
However, the IUC-32(E) mainboard envisages addre ssing for up to
two memory banks of 6 4MB each.
Exchange and retention of system relevant data from the VMEbus to the CPU/DMA and
viceversa is provided by means of 256kB or 1MB of a 16-bit wide dual-ported SRAM
which is backed-up using Gold Caps. Both the VMEbus users and the on-board CPU
have access to the SRAM memory.
Note...
The upper 8kB of dual-ported SRAM are accessed by the
VMEbus, the lower 8kB a re reserved for mailbox interru pts.
Configuration data are stored in a 2kbit EEPROM. 1kbit is used for factory-specific configuration purposes, and 1kbit is available for application-specific configuration data.
A schematic overview of all possible memory c onfigurations is given in the fi gure on the
next page.
Figure 2-1: VSBC-32 Memory Configuration Variants
VSBC-32
MC68360
25MHz
VSBC-32E
MC68EN360
25MHz
33MHz
CPU Options
SRAM
256kB
SRAM
256kB
or
SRAM
1MB
2kbit EEPROMRTC
CPU/Serial
Comm.
Controller
Flash
or
EPROM
(256kB or
1 MB)
Memory Pi
- 1MB DRAM + 0 or 1 MB Flash EPROM
- 4MB DRAM + 1,2 or 4 MB Flash EPROM
- 8MB DRAM + 1,2 or 4 MB Flash EPROM
- 16MB DRAM + 1,2 or 4 MB Flash EPROM
- 32MB DRAM + 0.5,1 or 2 MB Flash EPROM
- 64MB DRAM + 1,2 or 4 MB Flash EPROM
backs
SRAM
DRAM
+
Flash
Mainboard
2.2.3DMA Channels
Two independent channels are provided by the MC68(EN)360 controller chip and can
be used by applications requiring data transfer between VMEbus modules (as well as
CXC modules, if present), DRAM, flash memory and dual-ported SRAM.
Memory-to-memory transfers with the DMA’ s of the MC68(EN)360 are possible with any
combination of on-board and VMEbus addresses.
Under the aspect of serial communications control, a major advantage of the
MC68(EN)360 serial communications controller cor e SIM60 is its compatibility with all
important communication standards. A detailled description of all control functions is
provided on the following pages alongside with a comprehensive list of the possible
serial interface piggybacks and their connectors.
For the mainboard interface connector pinouts refer also to the “Board Interfaces” section of this chapter. For a description and pinouts of the connectors of the serial interface/communication piggybacks as well as of the CXM-SIO3 frontpanel interface
connectors please refer instead to the “SI Piggy backs” appendix of this manual as well
as to the CXM-SIO3 user’s manual and its “Serial Communications Piggybacks” appendix respectively.
Communication Standards and Protocols
Six communication standards are available on the VSBC-32(E):
•Serial I/O (RS232, RS485; RS422)
•Ethernet (10Base2, 10Base5, 10BaseT)
Serial communications using the RS232 standard are available on the VSBC-32(E)
mainboard frontpanel as well as on a dedicated piggy back to be connected to its SI
Interface. In addition, RS232 communication is possible via a CXM-SIO3 external serial
interface module. Communications using the PROFIBUS protocol are supported by an
optoisolated, half-duplex RS485 serial I/O interface implemented on a dedicated piggy back to be connected to the SI Interface of either the VSBC-32(E) or the external serial
interface module. RS422 is not commonly available on the VSBC-32(E) but can be supplied by
The MC68(EN)360 processor is specified to support also a full set of IEEE 802.3/Ethernet CSMA/CD media access control and channel interface functions. Since the controller requires an external interface adapter and transceiver function, the Ethernet
interface can be adapted to all standard Ethernet functions, such as 1 0Base T, 10Base5
and 10Base2 via a piggyback connected to the SI Interface on the VSBC-32(E).
PEP Modular Computers
on special request.
Note...
The CXC bus does not support a 12V power supply. Therefore,
the 10Base5 Et hernet piggyback SI-10B5 ca nnot be used on the
IUC-32(E) controller bo ard.
Serial I/O Channelling
The VSBC-32(E) mainboard is provided with TxD and RxD signals by the controller’s
SMC1 and SMC2 channels and supply RS232 interface software handshake (XON/
XOFF) capability. They are configured as service/debug connectors by default.
All full modem interfaces located on the piggybacks and/or CXM-SIO3 external serial
interface module supply RxD, TxD, RTS, CTS, CD, DTR and RCLK/TCLK. Two of the
full modem interfaces can be configured on the piggyback interface with a variety of
serial interface (SI) piggybacks (RS232, RS485, Ethernet). The SCC1 channel of the
MC68(EN)360 provides the interface to the ser ial interface (SI) piggyback installed on
the VSBC-32(E). All other channels of the controller (SCC2, SCC3 and SCC4) 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 piggyback interface for
serial interface piggybacks.
Thanks to the fact that three out of four SCC channels ar e routed to the CXC interface
connector, also an CXM-SIO3 external serial i nterface module can be installed in the
system, which therefore becomes a sort of “privileged” serial I/O extension of the VSBC32(E) board itself. In addition to two non-optoisolated RS232 serial interface connectors
the external serial interface module supports again a serial interface piggyback and up
to three serial communications piggy backs with the relating interfacing options. Maximum one CXM-SIO3 module can be cont rolled by an VSBC-32(E) board.
Figure 2-2: MC68(EN)360 Serial Communication Channeling
The serial channel SCC4 is routed to both the piggyback interface for serial interface p iggyb acks a nd th e CXC and c an be used
by either one or the other, not both at the same time.
Depending on whether the piggyback interface for serial interface (SI) piggybacks is
configured as an Ethernet port (board versions with Ethernet piggyback) or not, the
serial interfaces channels of the VSBC-32(E) can assume the functions described in the
following figure.
Figure 2-3: VSBC-32(E) Serial Interface Channel Configurations
Port
Service/Debug 1SMC1Main board, upper RJ12
Service/Debug 2SMC2Main board, lowe r RJ12
Ethernet
Full MODEM 1
Full MODEM 2SCC2External serial inte rface module
Full MODEM 3SCC3External serial inte rface module
Full MODEM 4SCC4
Legend:
Board versions with Ethernet port
Board versions without Ethernet port
Independent of Ethernet configuration
1
SCC4 is not used by any of the Ethernet piggybacks. With these piggybacks, SCC4 can be used on the C XC bus.
Serial Communicati on
Channel
SCC1Mainboard, serial in terface pig gyback
Interface Location
External serial i nterface module
Mainboard or
Serial interface piggyback or
External serial i nterface module
The following section provides a description of the mainboard interface connector
pinouts. For a detailled list and description of the connectors of the serial interface/communication piggybacks and of the frontpanel interface connectors please refer to the “SI
Piggybacks” appendix of this manual a s well as to the CXM-SIO3 user’s manual and its
“Serial Communications Piggyba cks” appendix respectively.
2.4.1Serial I/O Interfaces
The mainboard RJ12 RS232 frontpanel connectors BU7 and BU8 of the VSBC-32(E) are provided with TxD and RxD signals by the controller’s
SMC1 and SMC2 channe ls and supply RS232
interface software handshake (XO N/XOFF) capability. They are configured as service/debug connectors by default.
The pinouts of the RJ12 connectors are shown in
the following table.
Table 2-3: Pinouts of the Mainboard Serial Interface Connectors BU7/BU8
PinPinouts
1N/C
2GND
3TxD
4RxD
gure 2-5: Orientation o
the VSBC-32(E) Mainboard
Serial Interfaces
2.4.2Piggy back Interface Connectors for Serial Interface Piggybacks
The VSBC-32(E) is equipped with a set of piggyback interface connectors for serial
interface (SI) piggybacks (three 7-pin row male connectors). The pinout of these piggyback interface connectors includes all signals for serial I/O (RS232), PROFIBUS
(RS485) and Ethernet (10BaseT, 10Base5, 10Base2) communication.
Note...
Although physically all piggybac ks fit on bott basic board variant s
(IUC-32 and IUC-32E), the MN68360 processor of the IUC-32
variant does not support Ethernet communication. Therefore,
Ethernet piggybacks should be used only on the IUC-32E board
variants.
For a detailled description of the pinouts of these piggyback interface connectors please
refer to the VITA/
PEP Modular Computers
CXC MPI Specification.
2.4.3Memory Piggyback Interface Connectors
The VSBC-32(E) is equipped with a set of memory piggyback interface connectors (two
50-pin row female connectors). The pinout of these piggyback interface connectors
includes all signals for t he con nection of u p to 128M B of DR AM and up to 4 MB o f flash
EPROM.
For a detailled description of the pinouts of these piggyback interface connectors please
refer to the VITA/
PEP Modular Computers
CXC MPI Specification.
2.4.4EPROM DIP Sockets
The VSBC-32(E) is equipped with two sets of (flash) EPROM DIP sockets (two 32-pin
row female sockets). The pinout of th es e DIP s oc kets includes all signals for the connection of up to 1MB of SRAM.
The VSBC-3 2(E ) is equipped wi t h a b ackground debu g mode (BDM) in terface connector
(one 12-pin row male connector). This connector allows an external debugger to be
interfaced to the MC68(EN)360 for controlling purposes. The interface connector is
specified by Motorola.
The pinouts of the BDM interface connector are shown in the following table. For any
further details, please refer to the Motorola MC68(EN)360 User ’s Manual.
The VSBC-32(E) is equipped with a VMEbus backplane interface connector.
The board is provided with a complete ma ster inter face f or the VMEbus backplane con-
nector. The VMEbus master interface consists of a VMEbus arbiter, requester, system
controller and buffers for data/address/control signals. Simultaneously, the VSBC-32(E)
can act as a VMEbus slave, as it is provided with a slave interface which consists of a
programmable board address decoder, a dual-ported SRAM access and a mailbox
interrupt controller.
To act as a system controller, the VSBC-32(E) is provided with arbiter, system clock
driver, power monitor with system reset driver, IACK daisy chain driver and 7-level
VMEbus interrupt controller.
Arbitration is single-level FAIR (compare VME64 Specification Rule 3.14/Observation
3.17) on BR3*. If the VSBC-32(E) is used as a system controller, a special detection
function provided by the board, which is also readable within the VMEbus control/status
register, makes any “slot 1” jum per setting superfluous. The VMEbus int erru pt acknowledgement is controlled via a daisy chain driver that is supplied with the board. IACK* is
connected via the VMEbus backplane for IACKIN* of the system slot.
The signals SYSCLK* and SYSRES* can be routed from on-board to the VMEbus
through the use of jumpers, leaving to the VMEbus user instead of the system controller
the initiative of generating these signals. SYSFAIL* generates a maskable on-board
autovectored level-3 interrupt (please refer also to the section System Control Functionality (Interrupt Control) of this chapter), whereas ACFAIL* generates a non-maskable
on-board level-7 interrupt.
The VSBC-32(E) also provides a bus monitor for the VMEbus. A 128µs bus error timer
monitors the cycle le ngths of the VMEb us data tra ns fer and generate s a V MEbus BERR*
signal on timeout. This timer is enabled and disabled via the VMEbus control/status register which conta ins a lsao a timeout statu s bit in order to ide ntify th e bus e rrors g enerate d
by the bus monitor.
Exchange and retention of system relevant data from the VMEbus to the CPU/DMA and
viceversa is provided by means of 256kB or 1MB of a 16-bit wide dual-ported SRAM
which is backed-up using Gold Caps. Both the VMEbus users and the on-board CPU
have access to the SRAM memory (upper 8kB, i.e. even Byte addresses).
Note...
The dual-ported SRAM cannot be accessed through its own
VMEbus interface. A bus monitor timeout would result due to the
fact that any access by the VMEbus to the DPRAM would be
blocked as long as the VSBC-32(E) is bu s master.
An external VMEbus master may interrupt the VSBC-32(E) by setting P_IRQ5 (“mailbox
interrupt pending”) in the VMEbus control/status register. Seen from the VMEbus, the
address of this dual-ported register is identical to the base address of the dual-ported
SRAM (lower 8kB, i.e. odd Byte addresses).
Note...
All bits of the VMEbus control/status register can be read from
the VMEbus, but only th e bit P_IRQ5 is read /write.
For a complete map of the VMEbus control/status register please refer to the relating
section in the Configuration chapter of this manual.
For any general VMEbus information including generic pinouts please refer to Appendix
B of the ANSI/VITA VME64 Specification.
2.4.7CXC Mezzanine Interface
The VSBC-32(E) is equipped with a CXC mezzanine interface connector.
CXC and eCXC both contain a 16-bit data bus, seven address lines and eight decoded
chip select lines. In total, there are eight control signals (CXC_CS0...CXC_CS7). The
base address of the CXC can be programmed via the CS5 line of the MC68(EN)360.
The main difference between the two VITA standards is the amount of address space
available for peripheral devices:
•CXC:8*256Bytes (overall length: 0x400H, 1024Bytes actually av ailable)
•eCXC:8*16MB (overall length: 0x1000 000, 16MB actually available)
Furthermore, the (e)CXC contains a 4-IRQ capability (4 edge-sensitive interrupt
requests), DMA capability (1 channel, DREQ + DACK), serial ports (3 channels, Full
MODEM) and a set of parallel port signals. These special CXC functions are based on
the MC68(EN)360 controlle r reso urc es.
For general CXC information, including generic pinouts and a comparison of the
MC68(EN)360 and the MC68302 CPU pinouts on the CXC, please refer to the “CXC”
appendix attached to this manual, the
or to the CXC Specification.
2.5 VSBC-to-VSBC-32 System Upgrading
In the following the porting information required by customers w anting to upgrade their
VSBC-based systems to an VSBC-32 based one is supplied.
The VMEbus/CXC ports SER1, SER2 and SER3 of the MC68302 are equivalent to
ports SCC2, SCC3 and SCC4 respectively on the MC68(EN)360 controller chip.
With regard to special VMEbus/CXC capabilities, the VMEbus/CXC pinout on the
VSBC-32(E) has been developed to provide maximum compatibi lity between the standard VMEbus/CXC functions. In addition, all signals are available in order to configure
two time division multiple xed channels via the VMEb us/CXC (ISDN, PCM, GCI and so on).
PEP Modular Computers
CXC Reference Manual
Multifunction pins with incompatible functions with regard to the MC68302 and
MC68(EN)360, which are called “user-defined” in the generic CXC Specification, are not
part of the VSBC-32(E) VMEbus or CXC specification.
Although the SMCs are configured on the mainboard, these ports are also integrated on
the VMEbus/CXC because of possible ISDN applications where SMCs can be integrated and other protocols supported by the M C 68(EN) 3 60.
Note...
If the RCLK2 signal (VMEbus/CXM pin C16) is required, jumper
J4 (24MHz clock) must be opened and the serial drivers delivered by
Table 2-5: IUC/IUC- 32 Por tin g Information (Sheet 1 of 2)
CXC
Function
IRQ_1A1YesPC0—
IRQ_2A2YesPC1—
IRQ_3A3YesPC2—
IRQ_4A4YesPC3—
DMA_ACKC2YesPB5—
DMA_REQC3YesPB4—
SER1_RCLKB1YesPA8—
SER1_TCLKB2YesPA10—
SER1_TXDB4YesPA3—
SER1_RXDB10YesPA2—
SER1_RTSB5YesPB13—
SER1_DTRA13YesPB17—
SER1_CTSB13YesPC6—
SER1_CDB14YesPC7—
SER2_RCLKC16YesPA13Cannot be used if J4 is set3
Pin
MC68302
HW
Comp.
MC68(EN)
360
Port
Comment
See
Note
SER2_TCLKC15YesPA12—
SER2_TXDC17YesPA5—
SER2_RXDC18YesPA4—
SER2_RTSC12YesPB14—
SER2_DTRA11YesPB16—
SER2_CTSC13YesPC8—
SER2_CDC11YesPC9—
SER3_RCLKC6YesPA15Not usable if SI piggyback uses SCC44
SER3_TCLKC5YesPA14—
SER3_TXDC8YesPA7Not usable if SI piggyback uses SCC44
Legend:
1 Reserved Pin: On a standard VSBC-32 board, this signals is used for UART ports at BU7 and BU8.
2 Reserved Pin: On a standard VSBC-32 board, this signal is used for SPI to which the EEPROM is already con-
nected. PB0 is chip select of the EEPROM.
3 Reserved Pin: On PA13, a 24 MHz clock signal is routed via jumper J4. This signal is alw ays needed for PEP
standard software (serial drivers).
4 Dual Functioning Pin: This signal is routed both to the mainboard’s interface for serial interface piggybacks
(ST5C) and the CXC backplane connector and can be used by either one or the other, but not both at the same
time. Due to this, a conflict exists if the SCC4 port is to be used with the SI232 piggyback and CX C boards
(such as CXM-SIO3), as both boards access this port. The SCC4 port can, therefore, not be used at the same
time by serial interface piggybacks and CXC boards.
Table 2-5: IUC/IUC-32 Porting Information (Sheet 2 of 2)
CXC
Function
SER3_RXDC9YesPA6Not usab le if SI pi ggyba ck use s SCC 44
SER3_RTSB7YesPB15Not usable if SI pi ggyba ck u ses SC C44
SER3_DTRA12YesPB9Not usable if SI piggyback uses SCC44
SER3_CTSB16YesPC10Not u sab le if SI pi ggyba ck u ses SC C44
SER3_CDB8YesPC11Not usable if SI piggyback uses SCC44
User-Defined
Pin
A5NoPB0
A6NoPB1
A8NoPB2
A9NoPB3
A10NoPB8See MC68360 User Manual
B11NoPB10Used on board SMC2 (Transmit)1
C1NoPB6Used on board SMC1 (Transmit)1
MC68302
HW
Comp.
MC68(EN)
360
Port
Comment
Used on board SPI SEL for EEPROM.
Cannot be used on CXC
SPI Clk: can be used if an ‘SPI SEL’
other than PB0 is used.
SPI TxD: can be used if an ‘SPI SEL’
other than PB0 is used.
SPI RxD: can be used if an ‘SPI SEL’
other than PB0 is used.
See
Note
2
C4NoPB11Used on board SMC2 (Receive)1
C10NoPB7Used on board SMC1 ( Recei ve)1
Legend:
1 Reserved Pin: On a standard VSBC-32 board, this signals is used for UART ports at BU7 and BU8.
2 Reserved Pin: On a standard VSBC-32 board, this signal is used for SPI to which the EEPROM is already con-
nected. PB0 is chip select of the EEPROM.
3 Reserved Pin: On PA13, a 24 MHz clock s ignal is routed via jumper J 4. This signal is al ways needed for PEP
standard software (serial drivers).
4 Dual Functioning Pin: This signal is routed both to the mainboard’s interface for serial interface piggybacks
(ST5C) and the CXC backplane connector and can be used by either one or the other, but not both at the same
time. Due to this, a conflict exists if the SCC4 port is to be used with the SI232 piggyback and CXC boards
(such as CXM-SIO3), as both boards access this port. The SCC4 port can, therefore, not be used at the same
time by serial interface piggybacks and CXC boards.
The three-wire serial interface real-time clock V3021 is a 1-bit device which is accessible over the CS6 of the MC68(EN)360. Its time-keeping features include as follows:
seconds, minutes, hours, day of mon th, month , year, week day and week number in B CD
•
format;
•leap year and week number correction;
•stand-by supply smaller than 1µA.
For further information p
manual and the EM Microelectronic V3021 data sheet.
lease refer also to the “Software Configuration” chapter in this
2.6.2EEPROM
The serial EEPROM is a 1-bit device which is accessible over the three- wire Interchip
SPI Interface of the MC68(EN)360. The first half of the EEPROM (1 kbit) is reserved for
factory data, including Board ID codes, Internet/Ethernet addresses, boot information
etc. The second half of the EEPROM is available for the user. See also the Software
Configuration chapter
For further information on the EEPROM, please refer also to the XICOR X25C02 data
sheet.
in this manual.
2.6.3PLL Opera ti on Mode
The MC68(EN)360 inputs EXTAL and CPU clock use the same input frequency. The
XT AL input is left open. The clock mode is selected via the hard-wired inputs MODCLK0
and MODCLK1. With the default settings of MODCLK0 = 1 and MODCLK1 = 0, the following configuration is selected:
no prescaler;
•
•multiplication factor = 1;
•CLKIN to the prescaler = CPU clock;
•internal frequency (VCO/2) = CPU clock;
2.6.4Tick Generator
The MC68(EN)360 internal Periodic Interrupt Timer is used b y the
ing system as Tick generator.
For further information please refer also to the Motorola MC68(EN)360 User ’s Manual.
The VSBC-32(E) provides an on-board bus error timer and a VMEbus error timer.
There are three cases of bus error
Table 2-6: Bus Error Types
CauseTimeoutEnable / Disable
Reserved address BERR0100nsPermanently enabled
:
On-board BERR18µs
VMEbus BERR2128µs
Enable / disable possible,
set in board control registe r
Enable / disable possible,
set in VMEbus control register
On-Board Bus Error Timer
An 8µs timeout on-board timer monitors the cycle lengths of data transfers to and from
locations beyond the CPU data bus buffer, including on-board I/O, VMEbus, SRAM and
CXC. After a timeout occurs, it generates an on-board bus error signal for error termination. This timer is enabled/disabled via the board control/status register, which also supplies a timeout status bit in order to identify bus errors generated by the on-board bus
error timer.
During VMEbus cycles the on-board bus error timer is reset as soon as the VSBC-32(E)
gains VMEbus ownership, i.e. the time gap between a VMEbus request and the starting
of the VMEbus cycle is monitored by the on-board bus error timer. The VMEbus cycles
themselves are monitored by the separate VMEbus error timer.
Note...
The internal MC68(EN)360 bus error timer (hardware watchdog
timer) is not used on the VSBC-32(E). Therefore, it should
remain disabled (default setting).
VMEbus Error Timer
In addition to the on-board bus error timer, the VSBC-32(E) provides a bus monitor for
the VMEbus. A 128µs timer monitors VMEbus data transfer cycle lengths and generates
a VMEbus bus error signal BERR* for er ror termination. This error is enabled and disabled via the VMEbus control/status register which also supplies a timeout status bit in
order to identify bus errors genrated by the bus monitor.
For a complete map of the VMEbus control/status register please refer to the relating
section in the Configuration chapter of this manual.
A 512ms watchdog timer triggers the on-board reset generator at timeout. Once
enabled via the board control/status register, the watchdog timer cannot be reset by
software. It must be re-triggered via the corresponding bit in the board control/status
register periodically within the timeout period. ‘Watchdog t imer running’ is a status that is
displayed by the yellow front panel LED.
For the location of the Watchdog LED please refer to the VSBC-32(E) Frontpanel figure
in the “Introduction” chapter of this manual.
2.6.7Reset Sources
The VSBC-32(E) interacts with the following reset sources:
Table 2-7: VSBC-32(E) Reset Sources
Reset SourceIdentification
Push ButtonNo
SYSRES* VMENo
WatchdogWDG bit on-board (Board Control/Status Register)
Power Monitor ( 4.65V )Inside the MC68(EN )360
2.6.8“Slot 1” Detection
During power-up the VSBC-32(E) dete cts whether it is being used as a system controller (slot 1). This information can be read from the VMEbus control/status register and is
valid until the next power-down of the sy stem.
For a complete map of the VMEbus control/status register please refer to the relating
section in the Configuration chapter of this manual.
The frontpanel status indicators consist of three LED’s with the following functions:
•YellowWatchdog LED
•GreenGeneral Purpose
•RedCPU Halt or Reset
The green LED is user-defined by the customer. It is set by the software during startup
when the MC68(EN)360 is initialized.
Figure 2-6: VSBC-32(E)
Frontpanel LED and
Button Locations
Legend:
YellowWatchdog LED
GreenGeneral Purpose
RedCPU Halt or Reset
RSTReset Button
ABAbort Button
A Reset button is fitted to the front panel to avoid false operation. The Reset button triggers the on-board system reset generator. In addition, an Abort button is also fitted to
the front panel. The Abort button generates a non-maskable level- 7 interrupt which is
used for debugging purposes.
WUH
RST AB
2.8 RTC and SRAM Data Retention
Short-term data retention for RTC and SRAM is gained with two Gold Caps, each with a
value of 0.22 Farad. In contrast to Lithium cells, Gold Caps do not require servicing.
This short-term backup is intended for short power failures or for reconfiguring systems.
An empty Gold Cap needs approximately three hours to charge up, with backup times
dependant on the temperature, memory size and memory ma nufacturer tolerances. A
well charged Gold Cap provides a minimum of 10 hours backup time.
Laboratory tests at
1MByte SRAM plus RTC (the typical on-board backup current is below 2µA). The
charge and discharge behaviour of Gold Caps is documented in the graphics overleaf.
For long-term data retention, 5V standby power supply could be provided via CXC
ST3A, pin 5 (user-defined line). This would require special wiring on the CXC backplane
or a special battery CXC module.
The address decoder of the VSBC-32(E) consists of external logic and the
MC68(EN)360 internal memory controll er. The MC68(EN)360’s internal chip select logic
decodes all the basic address areas following its initialization. The eight chip select outputs of the processor are connected to the different devices as shown in the following
tablle.
Table 2-8: Chip Select Output Connection
Chip SelectConnectionPort SizeAcknowledge
CS0
CS1DRAM on memory pig gybac k32Internal
CS2VMEbus16Exte rnal
CS3
CS4SRAM16External
CS5CXC16External
CS6RTC16External
CS7Control/status re gister16External
1
Chip selects for flash on memory piggybacks and EPROM sockets are exchanged depending on the selected boot
device (Jumper J18).
Flash on memory pi ggybac k o r EPROM
on flash/EPROM sockets
Flash/EPROM sock ets or
memory piggyback
1
1
32/16I nternal
16/32I nternal
The external address decoder switches the boot chip select CS0, memory piggyback or
EPROM on flash/EPROM sockets depending on the selected boot device. The interrupt
acknowledge cycles are also decoded by the external address decoder. Moreover, the
external address decoder includes a fast bus error (BERR) generator which monitors
the delay between external cycle start and generated CSx line.
2.9.2Boot Decoding
The type of boot device can be selected from the DRAM/flash memory piggyback or the
EPROM devices on the two flash/EPROM sockets. The flash/EPROM sockets can be
configured by the user with the EPROM or different flash devices. Please note that
regardless of the boot device selected both possible areas can be addressed due to the
fact that each area is connected to a seperate CS line of the controller. This means that
the CS0 line, which is the global boot select of the controller, is exchanged for the CS3
line by the boot decoder logic.
The board described in this manual can be installed in the system slot of any VME bus
compatible computer. The frontpanel of the board should be safely secured by screws to
the chassis to avoid lossening of the board through vibration and to ensure correct earth
connection.
Caution, Electric Shock s!
Switch off the VMEbus system before in stalling the board in a free
VMEbus slot. Failure to do so could endanger your life/health and
may damage your board or system.
ESD Equipment!
Your VMEbus board contains electrostatically sensitive devices.
Please observe the necessary precautions to avoid damage to
your board:
• Discharge your clothing before touching the assembly. Tools
must be discharged before us e.
• Do not touch compon ents, connector-p ins or traces.
• If working at an anti-static workbench with professional discharging equipment, please do not omit to use it.
To install the board, please proceed as follows:
•Ensure that the safety requirements indicated above are observed
•Ensure that the serial interface piggyback is properly installed and the relating frontpanel secured to the mainboard (see appropriate documentation for configuration)
•Ensure that the flash/DRAM memory piggyback and the DIP flash/EPROM is properly install e d, and that the boot memory selection jumper is set correctly
•Ensure that all other wire jumpers are set correctly (DIP socket memory type and
size, boot device, system clock and on-board resets ???)
Warning!
Failure to set the wire jumpers correctly may cause damage or
malfunctionning to your board. Please refer to the Hardware
Configuration section in this manual for any details on jumper
settings.
•Install the board in an appropriate slot and engage the retaining mechanism
•Connect external interfacing cables to the board as required
•Ensure that the board and interfacing cables are properly secured.
•Ensure that the safety requir ements indi cated above are ob served
•Disconnect any interfacing cables that may be connected to the board
•Disengage the board retaining mechanism by pressing down on the board release
handle disengaging the board from the backplane connector and pull the board out
of the slot.
3.1.1External Serial Interface Module
Being a combined system and serial communications controller board, the VSBC -32(E)
is designed for a possible combined use together with the CXM-SIO3 external serial
interface module. If such an interface module is used, all communication signals
between the mainboard and the module are transmitted via the CXC bus. For this purpose, the external interface module must be “sandwiched” with the VSBC-32(E) mainboard.
3.2 Software Installation
There are no special requirements for software installation. However, many components
of the VSBC-32(E) are controlled by the MC68(EN)360 processor. Due to this fact, the
controller requires a special initialization sequence before any other software can be
started.
For any details on the initialization sequence and the address list of involved registers
please refer to the relevant description in t he User’s Manual included with your operating system.
The VSBC-32(E) has fifteen jumpers fitted to the board. The list of default jumper settings is shown below. A board layout with all jumper locations and pinouts is supplied in
the Board Layouts section of the Introduction chapter of this manual.
4.1.1W ire Jumpers
The following parameters are selected via wire jumpers:
•Boot device selection (J9)
•CXC/Enhanced CXC selection (J10)
•Connection of SYSCLK to VMEbus (J11)
•Connection of on-board reset to VMEbus (J12)
•DIP socket memory type and size (J13/J14)
Note...
Jumpers J9 to J14 are normal wire jumpers that can be configured by the user. The other jumpers are solder jumpers and are
factory set.
Table 4-1: ACFAIL, (e)CXC and Boot Device Selection, General Purpose Jumper
JumperSettingsDescription
J9
J10
J11
J12
OpenBoot from flash on DRAM/Flash piggyback enabled
ClosedBoot from flash/EPROM DIP sockets enabled
OpenCXC enabled
ClosedEnhanced CXC enabled
OpenSYSCLK disconnected from VMEbus
ClosedSYSCLK connected to VMEbus
OpenOn-b oard RESET generator no t to VMEbus
ClosedOn-board RESET generator to VMEbus
Table 4-2: DIP Socket Memory Selection
J13J14Description
OpenOpenEPROM 256kB/512kB (2x 27C010 or 2x 27C020)
The following parameters are selected via solder jumpers:
•CPU/bus clock frequency (J1/J2/J3)
•Communications clock frequency (J4)
•Serial EEPROM write protection (J5)
•Connection of protective and signal Ground (J6)
•CXC interface connector pin A5 function assignment (J11)
•SRAM size (J7/J8)
Warning!
All solder jumpers are factor y set. Alteration of their settings can
result in damage to the board. Therefore, customers must not
alter the settings of these jumpers .
Table 4-3: CPU/Bus Clock Frequency Selection
J3J2J1Description
ClosedClosedOpen25M Hz(VSBC-32 and VSBC-32E)
OpenClosedOpen33.3MHz(VSBC-32E only)
Table 4-4: Clock Frequencies, EEPROM Write Protection and GND Connection
JumperSettingsDescriptio n
Open24MHz commun ica tion s c lock not conn ecte d to M C68( EN)36 0
J4
Closed
OpenEEPROM write p rotection disabled
J5
ClosedEEPROM write protection enabled
OpenSignal GND no t co nnec ted to P rotec tive GND
J6
Closed
24MHz communications clock connected to MC68(EN)360
Note: This jumper must be set to op en if the RCL K2 signal
(CXM pin C16) i s requ ired .
Signal GND connec ted to Protec tive GN D
Note: If this jumper is set, care must be taken to avoid any
grounding curre nts.
Table 4-5: SRAM Size Selection
J7J8Description
1-21-21MB(VSBC-32E only)
1-31-3256kB (VSBC-32 and VSBC-32E)
Software applications may require to configure data in the VSBC-32(E) registers. For this purpose, the configurab le m e m ory is described in the follow ing . T he a dd r es s m a p in th e ta ble
below is base d on the r ecommended defaul t initi alization of th e MC68(EN) 360 chip select l ogic.
Figure 4-1: VSBC-32(E) Memory Map
AddressM emory Dev iceMC68(EN)360
0x 00 xx xx xx
0x 04 xx xx xx
0x 07 00 0x xx
0x 09 xx xx xx
0x 0A xx xx xx
0x 0B F7 xx xx
0x 0C xx xx xx
0x 0D xx xx x1
0x 0D xx xx x5
0x 0D xx xx x7
0x 82 xx xx xx
0x 83 xx xx xx
0x 85 00 xx xx
0x 87 xx xx xx
DRAM on DRAM/Flash piggybackCS1
FLASH on DRAM/Flash pigg ybackCS0
MC68(EN)360 internal RAM registe r—
Flash/EPROM sockets
SRAMCS4
2
CXC
Real-time clockCS6
VMEbus IRQ mask registerCS7+1
VMEbus control / s tatu s regi sterCS7+5
Board control / st atus reg isterC S7+7
VMEbus user-defin ed AM codeCS2
VMEbus user-defin ed AM codeCS2
VMEbus short I/O AM codeCS2
VMEbus standard AM codeCS2
1
CS3
CS5
1
If the ROM sockets are selected as the default boot device, then the address 0x 09 xx xx xx, i.e. CS3 of the
MC68[EN[360, is automatically selected as the base address for the flash on the memory piggyback.
2
See the “CXC” appendix of this manual for further addressing information.
Note...
The above shown memory map is
PEP
do not cause CS0..CS7 signals. Therefore access to them leads to
bus errors (BERR).
Furthermore, in order to determine the base of the internal memory
map of the MC68[EN]360 controller, 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 on the recommended MC68(EN)360 initialization sequence,
please refer to the Software Installation section in this manual.
Address:CS7 + 0x7
Format:Byte
Access:Read/write
Value after HW Res et:0PEP Default Address:0x 0D 00 00 07
Figure 4-2: CS7 + 0x7 Bitmap
01234567
WDGEN_WDGBERR1BERR2
Table 4-6: Register Description
Name
WDG
bit 7
BERR2
bit 6
BERR1
bit 5
EN_WDG
bit 4
TR_WDG
bit 3
EN_BERR1
bit 2
Register
Value
1Read/Write
1Read/WriteTriggers the watchdog timer. Watchdog timeout = 512ms.
1Read/Write
AccessDescription
Read/Write
Read/Write
Read/Write
EN_BERR1TR_WDGACFAILLED_G
Set by watchdog timer when timout has been reached. Used to
differentiate between resets caused by the watchdog and
resets caused by the reset button (power up resets can be
identified w ith in the MC 68(EN )360) .
Set by VMEbus error timer on timeout to identify bus errors
caused by this ti mer.
(See also VME bus stat us/c ontr ol r egiste r)
Set by on-bo ard b us error time r on timeou t to id entify bus
errors caused by this ti mer.
Enables the watchdog timer. It can only be set once, and
remains enabled until the next reset.
Enables the o n-boa rd bus erro r timer. It also moni tors a ll
on-board I/O cycl es, incl udin g th e ti me fr om t he VM Ebus
request to th e VMEb us gran t. Time out = 8µs.
ACFAIL
bit 1
LED_G
bit 0
1Read/Write
1Read/WriteEnables the green ‘gen eral p urpos e’ front pan el LE D.
VME ACFAIL signal latched when active in order to distinguish
a level 7 NMI from an ABORT or ACFAIL.
Warning!
The correct functionality of your equipment may be jeopardized
due to a loss of information, if bit 7 is written to. Therefore, the
customer should not write an y data to bit 7.
The Memory Piggy backs described herein provide main memory capability for the storage of progam code and data either in DRAM or flash memory. Various configurations of
DRAM and flash memory as indicated in the table below are available for a wide variety
of PEP CPU boards. All configurations have 32-bit access and a maximum address
range of 64 MB. In addition jumpers are available for providing write protection.
Table A-1: Memory Pi ggyback Types and Configurations
The serial interface (SI) piggybacks described herein adapt the multi-protocol serial
channels of the 68EN360 controller chip to one of the following physical interfaces:
•10Base2 (thin or cheapernet) Ethernet,
•10Base5 (AUI) Ethernet,
•10BaseT (twisted pair) Ethernet,
•RS-232 modem compatible,
•RS485 optoisolated (PROFIBUS),
and are available for a wide variety of PEP CPU boards.
The SI-10B2 is a physical cheapernet (10Base2) interface to the 68EN360 Controller
chip. It connects one of the range of PEP CPU boards to a 50 ohm coax cable via an
RG58 BNC ‘T’ connector.
The SI6-10B2 has two LEDs fitted; a red LED indicates collision detection and a yellow
LED for data transmission.
B.2.1Specifications
On-board termination:
Max. Baudrate:
None (Cheapernet cable is terminated at both ends)
10Mbit/s according to Ethernet specification
The SI-10B5 is a physical AUI interface to the 68EN360 Controller chip.
B.3.1Specifications
On-board termination:
Max. Baudrate
None
10Mbit/s according toEthernet specification
B.3.2Front Panel View and Pinout
Figure B-2: SI-10B5 Serial Interface Piggyback
Pin 1
Pin 8
Pin 9
15-pin D-Sub
female connector
Pin 15
Table B-2: SI-10B5 Connector Pinout
PinSignalPinSignal
1Control IN circuit shield9Control IN circuit shield
2Control IN circuit A10Data OUT circuit B
3Data OUT circuit A11Data OUT circuit shield
4Con tro l IN circ uit shiel d12Data IN circuit B
5Dat a IN circ uit A13+12V*
6Voltage common14GND
7N/C15N/C
8N/C
*The SI-10B5 requires an external +12V from the base board. For further details please refer to the
The SI-10BT is a physical twisted pair (10BaseT) interface to the 68EN360 Controller
chip. It connects one of the range of PEP CPU boards to an unshielded 100ohm
twisted-pair cable via an RJ45 telephone jack.
The SI-10BT has two LEDs fitted: a red LED indicates collision detection and a yellow
LED for data.
B.4.1Specifications
On-board termination:
Max. Baudrate:
100ohm
10Mbit/s according to Ethernet specification
The SI-PB232 provides two RS-232 serial interfaces to th e 68EN360 Controller chip. It
connects one of the range of PEP CPU boards via two RJ45 telephone jacks.
B.5.1Front Panel View and Pinout
Figure B-4: SI-PB232 Serial Interface Piggy back
Pin 8
Pin 1
Pin 8
Pin 1
RJ45
Connecto
(SCC1)
RJ45
Connecto
(SCC4)
Table B-7: SI-PB232 Connectors SER1 and SER2 Pinouts
The SI-PB485-ISO is an RS-485 optoisolated interface piggyback for 2-wire half-duplex
(PROFIBUS) connection. It has one LED fitted indicating data transmission.
B.6.1Specifications
On-board termination:
Isolation voltage
Max. baudrate
150ohm, jumper selectable
Optocoupler specified up to 2.5kV
1.5MBaud
B.6.2Front Panel View, Jumper Layout, and Pinout
Figure B-5: SI-PB485-ISO Serial Interface Piggy back
9-pin D-Sub
female
connector
(SCC1)
Pin 1
Pin 5
Transmit
Yellow
Tx
Pin 6
Pin 9
J5
2
1
3
J1
J2
J3
J4
2
J6
1
3
Table B-8: SI-PB485-ISO Connector Pinout
PinSignalDescription
1N/C—
2N/C—
3RxD+/TxD+Receive/Transmit Data plus
4N/C—
5DGNDData Ground (GND 5V)
6VPVoltage Plus (+5V)
7N/C—
8RxD-/TxD-Receive/Transmit minus
9N/C—
The Controller eXtension Connector (CXC) is the local interface. It contains a 16-bit
data bus, seven address lines and eight decoded chip select lines. Each select line has
256 Bytes. In total, there are eight select signals.
C.1 CXC Address Ranges
The following tables provide address range information for both the CXC standard backplanes as well as the enhanced CXC backplanes (ECXC) for the CPU boards indicated.
1IRQ_1SER1_RCLKU ser-d efin ed
2IRQ_2SER1_TCLK_DMA_ACK
3IRQ_3GND_DMA_REQ
4IRQ_4SER1_TXDUser-defin ed
5User-definedSER1_ RTS
6User-definedGNDSER3_RCLK
7VCCSER3_RTS
8User-definedSER3_ CD