This material contains information of proprietary interest to BVM Ltd. It has been supplied in
confidence and the recipient, by accepting this material, agrees that the subject matter will not be
copied or reproduced, in whole or in part, nor its contents revealed in any manner or to any person
except to meet the purposes for which it was delivered.
This page is intentionally left blank.
i
DISCLAIMER
The information in this document has been checked and
is believed to be entirely reliable, however no
responsibility is assumed for inaccuracies. BVM Ltd.
reserves the right to mak e changes and/or im provements
in both the product and the product documentat ion without
notice. BVM Ltd. does not assum e any liability arising out
of the application or use of any produc t described herein;
neither does it convey any licenc e under its patent rights
or the rights of others.
USE OF PRODUCT
This product has been designed to operate in a VMEbus
and IndustryPack compatible electrical environment.
Insertion of the board into any s lot which is not VMEbus
compatible is likely to cause serious damage. Insertion
and removal of the board from the backplane or
IndustryPack(s) or cable(s) from the board must not be
done whilst in a powered condition.
Do not lever out any devices from the produc t, whic h us es
surface-mounted devices extensively, as these can be
fractured by excessive force.
This product uses devices sensitive to static electricity.
Ensure adequate static electricity precautions are
observed when handling the product and associated
devices.
RF. INTERFERENCE
This product complies with European Council Directive
89/336/EEC (EMC directive), and conforms to
EN55022:1995 Class B (Limits and methods of
measurement of radio interference characteristics of
information technology equipment) and EN50082-1:1992
(Electromagnetic compatibility - Generic immunity
standard, Part 1: residential, commercial and light
industry) when used in accordance with the BVM EMC
Guidelines Manual part number 454-77000 (available on
request from BVM Ltd.).
GENERAL NOTICES
UNPACKING AND INSPECT I ON
This product contains c omponents which are suscept ible
to static discharge, and should be handled with
appropriate caution.
Upon receipt of this product, visually inspec t the board for
missing, broken or dam aged com ponents and for phys ical
damage to the printed circuit board or connectors. This
product was shipped in perfect physical condition. Any
physical damage to the product is the responsibility of the
shipping carrier and should be reported to the carrier's
agent immediately.
RETURN OF GOODS
Before returning a product for repair, verify as well as
possible that the suspect ed unit is at f ault. Then call BVM
Ltd. for a Customer Return (CR) number. Carefully
package the unit, in the original shipping cart on if this is
available, and ship prepaid and insured, preferably by
courier, with the CR number written on the outside of the
package.
Include a return address and the telephone num ber of a
technical contact, and a detailed description of the
observed fault. For out-of-warranty repairs, a purchase
order for repair charges must accom pany the return. BVM
Ltd. will not be responsible for damage due to improper
packaging of returned items. Out of warranty repairs can
be arranged, and will be charged on a material and labour
basis, subject to a minimum repair charge. Return
transportation and insurance will be charged as part of t he
repair and is in addition to the minimum charge.
SOFTWARE LICENCE NOTICE
Any software that is provided as Copyright BVM Ltd. is
proprietary and confidential property of BVM Ltd., and
each single copy is given on the agreed understanding
that it is licensed for use on product combinations
supplied by BVM Ltd. or their appointed dist ributors only.
The software product may not be copied (except for
backup purposes), given away, rented, loaned,
reproduced, distributed or trans mitted in any way or form,
in whole or in part, without written permiss i on of BVM Ltd.
This applies to any merged, m odified or derivative version
of the software including, but not limited to, versions
produced by customising, translating, reverse
engineering, decompiling or disassem bly.
This licence may be automatically terminated without
notice if any of its provisions are breached. Reasonable
legal costs may be awarded to the prevailing party in
connection with this licence agreement. Use of, or
accepted delivery of these products shall constitute your
acceptance of the provisi ons of this licence agreement.
WARRANTY
A) BVM Ltd. warrants that the articles furnis hed hereunder
are free from defects in material and workm anship for one
year after the date of shipment.
B) All warranties and conditions, express and implied,
statutory and otherwise, as to the qualit y of the goods or
their fitness for any purpose are hereby excluded and with
the exception of liability for death or personal injury
caused by negligence as defined in the Unfair Contract
Terms Act 1977 the s eller shall not be liable for any loss,
injury or damage arising directly or indirectly f rom the us e,
application or storage of such goods.
C) Subclause (B) above shall not apply where the buyer
deals as a consumer as thi s expression is defined in the
Unfair Contract Terms A ct 1977.
D) The liability of BVM Ltd. hereunder shall be limited to
repair or replacement at the manufacturers discretion of
any defective unit. Equipm ent or parts which have been
subject to abuse, misuse, accident, alteration, neglect,
unauthorised repair or installat ion are not covered by this
warranty. BVM Ltd. shall have t he right of determination
as to the existence and cause of any def ect.
E) The warranty period of the replacement or a repaired
product or part shall term inate with the termination of the
warranty period with respect to the original product or part
for all replacement parts supplied or repairs made during
the warranty period.
F) Although BVM Ltd. offer a high level of technical
support and advice, due to the com plex nature and wide
application of product configurations it is the responsibility
of the purchaser to be satis fied at the time of purchase
that the products are suitable for the final applicati on.
G) The term 'Software' used herein is defined as 'any
program data or code in sourc e or binary format recorded
in or on any readable device or media'.
H) BVM Ltd. will effect all reasonable effort to resolve
accepted reproducible soft ware errors reported within 12
months of purchase. Acceptance of an error shall solely
be based on conformance to supporting specifications.
Proper operation of earlier releases is not guaranteed.
NOTICES
Copyright 1993,1995,1998,2001 by BVM Ltd.
OS-9 is a registered trademark of Microware Systems
Corporation.
VxWorks is a regi stered trademark of Wind River Systems
Inc.
IndustryPack is a registered trademark of Greenspring
Computers.
ii
WARNINGS
Do not lever out the EPROM's from the BVME4000/6000. The board
uses surface-mounted devices extensively, which can be fractured by
excessive force. Use proper EPROM extraction and insertion tools.
Damage may result if users attempt to remove or fit EPROM's
incorrectly.
Do not lever out the IP's from the BVME4000/6000. The board uses
surface-mounted devices extensively, which can be fractured by
excessive force. Damage may result if users attempt to remove or fit
IP's incorrectly.
Do not lever out memory modules from the BVME4000/6000. The
board uses surface-mounted devices extensively, which can be
fractured by excessive force. Memory modules are not a field-fit option.
Damage may result if users attempt to remove or fit memory
modules incorrectly.
Do not fit/remove the 68040/68060 device to/from the
BVME4000/6000. Special tools are required to fit and remove these
devices and the correct voltage settings must be selected. Return the
board to the factory if the 68040/68060 device requires changing.
Damage may result if users attempt to fit or remove the
68040/68060 device.
The BVME4000/6000 uses devices sensitive to static electricity.
Ensure adequate static electricity precautions are observed when
handling the BVME4000/6000, EPROM's, IP's and memory modules.
Ensure the correct polarity of connections to the BVME4000/6000.
In particular ensure the correct polarity of connections to the P2 I/O
connector, incorporating the SCSI connections. Damage may result if
users fail to observe correct connection polarity to the
BVME4000/6000.
A getting started guide.
Configuration details.
A user reference guide.
A memory map.
A map of all register locations.
A detailed description of all dedicated registers.
Details of implementation specific considerations for major devices.
General hardware description.
This manual does not provide:-
Detailed data on the operation of the major devices.
Details of VMEbus & IndustryPack™ Specifications.
Information is provided to allow the module to be integrated into a system and configured by the
system software. This User Manual is intended for use by system integrators, service personnel,
software engineers and end users.
Unless otherwise stated, address information is in hexadecimal notation.
The term "IP" is used as an abbreviation for "IndustryPack™" throughout this manual.
1.2 BVME4000 Part Numbers
452-40231/40331MC68EC040 25/33MHz, VMEbus I/F, ETHERNET, SCSI, IP I/F, 2Mb SRAM
452-42231/42331MC68040 25/33MHz, VMEbus I/F, ETHERNET, SCSI, IP I/F, 2Mb SRAM
Other versions of the BVME4000 are available to special order, where any of the VMEbus I/F,
ETHERNET, SCSI & IP I/F may be omitted or 512Kb SRAM fitted. Contact your supplier for details.
1.3 BVME6000 Part Numbers
452-40631MC68EC060 66MHz, VMEbus I/F, ETHERNET, SCSI, IP I/F, 2Mb SRAM
452-42531MC6806050MHz, VMEbus I/F, ETHERNET, SCSI, IP I/F, 2Mb SRAM
Other versions of the BVME6000 are available to special order, where any of the VMEbus I/F,
ETHERNET, SCSI & IP I/F may be omitted or 512Kb SRAM fitted. Contact your supplier for details.
1.4 Memory Module Part Numbers
453-82390/83390MEM390 25(50)/33(66)MHz 4Mbyte DRAM *
453-82403/83403MEM400 25(50)/33(66)MHz 16Mby te DRAM & 4Mbyte FLASH
453-82404/83404MEM400 25(50)/33(66)MHz 16Mby te DRAM & 8Mbyte FLASH
453-82482/83482MEM480 25(50)/33(66)MHz 48Mbyte DRAM *
453-85016/86016MEM4SD 25(50)/33(66)MHz 16Mbyte SDRAM
Other Memory Module types and options are available, * denotes type not recommended for new
designs. Some Memory Module types can also be "stacked" two high, to increase capacity or mix
memory types. Contact your supplier for details.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/60002
2. Overview
2.1 Board Layout
ABORT
RESET
STATUS LEDs
SERIAL
CH. B
SERIAL
CH. A
CHEAPER
NET
68040
or
68060
PRINTER
CONN.
LOW
PROM
MEMORY
MODULE
INTERFACE
VMEbus
P1 CONN.
HIGH
PROM
IP I/O CONN.
2 X 50 WAY
IndustryPack
Site A
IndustryPack
Site B
Figure 1 Board Layout
VMEbus
P2 CONN.
Copyright 1993,1995,1998,2001 BVM Ltd.
3BVME4000/6000
2.2 Features
!BVME4000 - MC68040 CPU (MC68EC040/68LC040 options).
" 25 MHz and 33 MHz clock speed variants.
" 4096 byte data and instruction caches.
!BVME6000 - MC68060 CPU (MC68EC060/68LC060 options).
" 50 MHz and 66 MHz clock speed variants (25 MHz or 33 MHz bus).
" 8192 byte data and instruction caches.
!32-bit wide burst fill Dual Ported (with Bus Snooping) memory module interface with NO
capacity limitations allowing many options, for example:
" 8Mbytes of FLASH EPROM (Erasable, Programmable non-volatile storage).
!Two 16-bit IP Compatible Sites (Double height 32-bit access supported).
!
!
!Bi-directional Parallel port including one further 24-bit interrupting Counter/timer (MC68230).
!
!VMEbus System Controller Functions.
!
!Available built as a single solution disc based module.
!
High Performance DMA driven Ethernet/Cheapernet (10BaseT option) (82596CA).
" Expansion Connector allowing 4 IP Compatible Site daughter board.
" 8MHz, 32MHz and proprietary high speed 'Source Synchronous Modes' supported.
Two Interrupt driven serial I/O ports - RS232, RS422 and RS485 options (Z85230).
Real Time Clock (Battery backed) Including Tick timer, 2 16-bit timers and non-volatile
Four level Arbiter (programmable ROR, RWD and SGL).
"
" RESET, SYSCLK generator.
Single slot, 6U form factor.
OS-9, VxWorks, Linux & debug monitor software support.
!Fully compatible to VMEbus specification revision C.1.
2.3 Applications
!VMEbus Main System Processor.
!
!
VMEbus Intelligent I/O Processor.
High Performance Embedded Processor.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/60004
&
3. Description
3.1 Block Diagram
50 way
Direct
Connector
SCSI
Controller
68040
or
68060
Memory
Module
P2
SCSI
EPROM
2Mb
16 Bit Wide
Front Panel
BNC or
RJ45
Cheapernet
or 10BaseT
Interface
Ethernet
Controller
Internal Bus
Arbiter
SRAM
512Kb/2Mb
32 Bit Wide
P2
AUI I/F
Dual Serial
Comms
Controller
VMEbus
SYSCON
VMEbus
Interrupter
VMEbus
Slave
VMEbus
Interrupt
Handler
VMEbus
Master
R.T.C.
2 x Timers
IP AIP B
Front Panel
50 way I/O
IP
Interface
Front Panel
50 way I/O
Serial
Buffers
WatchDog
Bus Timers
EEPROM
IP
Expansion
Interface
Parallel I/O
& Timer
Centronics
Buffers
Figure 2 Block Diagram
P2
Serial
14 way
Connector
JP1
14 way
Connector
JP2
P2
Parallel I/O
26 way
Connector
JP3
Copyright 1993,1995,1998,2001 BVM Ltd.
5BVME4000/6000
3.2 Processor
The BVME4000 is based on the MC68040 32-bit processor from Motorola running at 25 or 33MHz.
This virtual memory processor provides a MC68030 compatible integer processor running
concurrently with an IEEE754 compatible floating-point unit (FPU). In addition two f ully independent
data and instruction demand page m emory management units (MMU's ) and two independent 4Kbyte
caches provide efficient bus interface with a high degree of instruction execution parallelism.
The BVME6000 is similar to the BVME4000, but is based on the MC68060 32-bit processor from
Motorola running at 50MHz with a 25MHz bus. The MC68060 provides a MC68040 compatible integer
processor running concurrently with a MC68040 IEEE754 compatible floating-point unit (FPU). In
addition two fully independent data and instruction MC68040 compatible demand page memory
management units (MMU's) and two independent 8Kbyte caches.
The BVME4000 and BVME6000 are also available in lower cost versions with the
MC68LC040/68LC060, which provide the same functionality as the MC68040/68060, but without the
FPU, and with the MC68EC040/68EC060 which provide the same functionality, but without the MMU
or FPU. The MC68LC060/68EC060 can run at 50 or 66MHz with a 25 or 33MHz bus respectively.
3.3 Memory
The BVME4000/6000 may be fitted with a large variety of 32-bit wide, burst fill m emory devices. The
BVME4000/6000 uses the BVM memory module interface which provides a full 32-bit MC68040/68060
bus, and supports 2/1/1/1 (no wait state) accesses to a variety of standard BVM mem ory modules,
allowing use of memory modules which currently include:
! 8 to 48Mbytes DRAM (5/3/3/3 access at 33MHz bus clock).
! 16 to 512Mbytes DRAM (4/1/1/1 read, 3/2/2/2 write at 25 & 33MHz bus clock).
!16Mbytes DRAM plus 8Mbyte FLASH EPROM (4/2/2/2 DRAM, 5/2/2/2 FLASH access).
This memory can be dual ported allowing concurrent accesses by both the processor and other
VMEbus masters. These acc esses may be 'snooped' by the processor to maintain cac he coherency.
This, together with the onboard 'location monitor' allows full multipr ocessor comm unication with other
CPU (and DMA) VMEbus cards.
The BVME4000/6000 also provides 2Mbytes (512Kbytes to special order) of battery-backed 32-bit
wide Static RAM, providing a 5 CPU clock cycle access at 25MHz or 33MHz bus clock . This SRAM
may be used for non-volatile storage applications, or as main system mem ory in applications where a
memory module is not fitted. The SRAM can also be dual ported to the VMEbus.
A pair of 32-pin JEDEC pinout sockets provide up to 2Mbytes of 16-bit wide EPROM providing a 10
CPU clock cycle access at 25MHz or 33MHz bus clock. These sockets can support 512K, 1M, 2M, 4M
and 8Mbit EPROM devices, and up to 4Mbit 5V FLASH devices.
3.4 Real Time Clock
The BVME4000/6000 provides a battery backed Real Time Clock using the DP8570 device. This
device is battery backed, and maintains date and time data. The DP8570 can also generate an
interrupt from it's per iodic tim er f rom 1m S to 1 s econd, or f rom two other independent 16-bit tim er s on
chip. The timers offer a resolution of up to 500nS, and can be used in one-shot or periodic interrupt
mode. A small amount of non-volatile storage is also provided for system conf iguration purposes . The
DP8570 is battery backed using a lithium battery giving typically 10 years of non-volatile operation.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/60006
3.5 Serial Communications
Two serial communications interfaces ar e provided from a Z85230 SCC device. T he Z85230 provides
both synchronous (SDLC/HDLC) and asynchronous protocols. Asynchronous baud rates of up to
115.2Kbit/s (using the on-board crystal) are supported. Field changeable buff er m odules allow RS232,
RS422 or RS485 electrical interfaces to be selected for either (or both) channels. The two serial
interfaces are available on the front panel, or via the rear P2 connector. The synchronous clock
signals are also available via the P2 connector.
3.6 Parallel Port
An 8-bit, bi-directional I/O port with interrupt driven handshake is provided allowing direct connection to
Centronics devices. This is im plem ented in a 68230 which includes a fur ther 24- bit tim er with interr upt
capability. This device also provides part of the board control functions, and is used to control the
software watchdog function. The parallel port is connected to a dedicated connector near the front
panel, or via the P2 connector.
3.7 SCSI Interface
A SCSI interface is provided built around the NCR53C710. This provides asynchronous transfers of up
to 5Mbytes per second. The 32-bit DMA driven interface allows direct acc ess to the entire memory
map of the BVME4000/6000. The burst mode interface stacks up 16 bytes at a time and transfers
them as a line transfer at up to 4/2/2/2 access speeds at 25MHz bus clock. At 5Mbyte/s this gives a
400nS burst every 3.2µS or 12.5% bus bandwidth requirement. The 53C710 is an intelligent proces s or
in its own right, running SCSI SCRIPTS software. This enables very high level commands to be issued
to the SCSI interface further m inimising processor overhead. The SCSI interface is connected to a
dedicated 50-way connector and is also available via the P2 connector.
3.8 Ethernet Interface
An Ethernet Interface is provided built around the Intel 82596CA. T his provides a 32-bit DMA driven
interface to both Ethernet (via the AUI interface on the P2 connector) and either Cheapernet (via a
front panel BNC) or optionally 10BaseT (via a front panel RJ45). The 32-bit DMA driven interface
allows direct access to the entire memory map of the BVME4000/6000 allowing full packet
management by the 82596CA. Each 32-bit transfer requires 320nS m axim um ( including ar bitration) to
execute the cycle. A transfer will occur no more frequently than every 4µS (4 bytes at 1Mbyte per
second). Thus worst case bus bandwidth requirement is 8% at 25MHz bus clock.
3.9 IP I/O
Two standard IP compatible sites are provided. The IP interface complies fully with the IP
specification. The two sites may be used individually for single IP's which are ac ces s ed as 16-bit wide,
or as a pair for double IP's, which are accessed as 32-bit wide. IP
32MHz, and CPU synchronous speeds. The IP DMA function is not supported by these two sites , but
may be supported on an IP daughter board (see below). The IP ID and I/O s pac es ar e 256bytes each,
and the memory spaces are 8Mbytes. IP vectored interrupts are fully supported and the interrupt levels
may be individually programmed.
An IP expansion bus connector is provided to allow additional IP's to be supported. A further 4 IP's
may be added on a daughter board connected to this expansion interf ace. Two 'virtual IP' sites are
also available for controlling the daughter board IP interfac e. The daughter board m ay include a local
DMA controller and RAM which is accessed thr ough one of the 'virtual IP' s ites, thus s upporting the IP
DMA function.
operation is supported at 8MHz,
Copyright 1993,1995,1998,2001 BVM Ltd.
7BVME4000/6000
3.10 VMEbus Interface
Full VMEbus system controller functions are provided including SYSCLK drive, Bus tim e out monitor,
SYSRESET drive and an efficient 4 level bus arbiter working in prioritised (PRI), s ingle level (SGL), or
round robin (RRS) arbitration modes.
3.10.1 VMEbus Master
Byte or Word Master accesses may be made to the Standard (A24) and Short I/O (A16) address
spaces, Byte, Word and Longword Master accesses may be made to the Extended (A32) address
space. BVME4000/6000 Longword accesses to the A24 or A16 address space m ay be converted to
two Word cycles, or proceed as a Longword cycle dependant upon the BVME4000/6000 address
space accessed. Read Modify Write (RMW) cycles are supported for all of these accesses.
VMEbus arbitration is normally configured to be Release On Request (ROR) method. This may be
changed to Release When Done (RW D) with a PLD change. Both schemes use FAIR requesting,
ensuring each master has an equal chance of obtaining the bus. Digital bus busy filtering and
arbitration interleaving is used to ensure premium arbitration performance.
3.10.2 VMEbus Slave
The memory module and on-board SRAM are dual ported onto the VMEbus. The VMEbus base
address, size of window and local base address are programmable for the A24 and A32 address
spaces. The BVME4000/6000 responds to Byte and W ord and Longword Slave ac cesses to the A32,
A24 and A16 address spaces.
The BVME4000/6000 can snoop VMEbus slave acces ses if enabled to do so. T hus although the CPU
uses extensive caching, full c oherency is maintained by the CPU providing any data that is 'stale' in
the accessed memory - refer to "Appendix B CPU Cache Coherency and Bus Snooping (on page 62)".
A VMEbus location monitor is also supported in the A16 address space. This is a fixed 256byte
window size, and the VMEbus base address is programm able. A local interrupt can be enabled when
the A16 VMEbus window is accessed.
The BVME4000/6000 is compatible with VMEbus address pipelining and RMW cycles.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/60008
3.11 Interrupts
3.11.1 VMEbus Interrupt Handler
The BVME4000/6000 may be configured to respond to VMEbus interrupts on any of the 7 VMEbus
interrupt levels. Each interrupt level may be programmed to be enabled or disabled individually.
A User vectored VMEbus interrupt causes the CPU to reply with a VMEbus Master interrupt
acknowledge cycle. This cycle uses only the that is broadcast in a similar way to the addresses. The
A1,2,3 address lines indicate the address level being handled.
The interrupting device returns an ID vector on the odd data byte. This is used as the us er vector by
the CPU.
3.11.2 Internal Interrupts
Internal CPU interrupts are generated from a variety of sources, as detailed in the table below:
The BVME4000/6000 may generate VMEbus interrupts on any programmable single level 1-7 and
responds with a software programmable ID to the subsequent interrupt acknowledge cycle. Writing the
ID to the a vector register causes a VMEbus interrupt to be generated on the selected level. The
BVME4000/6000 VMEbus interrupt ID vector may be programmed to suit the application.
Copyright 1993,1995,1998,2001 BVM Ltd.
9BVME4000/6000
3.12 VMEbus System Controller Functions
The BVME4000/6000 provides a number of system controller functions that may be enabled by
programming the relevant registers, or by link selection.
RESET
Asserted if +5V falls below 4.65V and when a link is installed. VMEbus RESET has a minimum
asserted period of 200mS.
ARBITRATION
The BVME4000/6000 can be programmed/link selected to provide SGL, PRI or RRS arbitration.
SYSCLK
The BVME4000/6000 can be programmed/link selected to provide a 16MHz VMEbus SYSCLK.
BUS TIMER
The BVME4000/6000 can be programmed/link selected to provide a 128µS Bus Timeout BERR
signal.
3.13 Power Supply Monitor/Watchdog
A MAX791 provides power up/power down control for the battery switching for the non-volatile RAM
and processor RESET. It also provides a processor watchdog capability controlled via the Board
Control Register. If enabled, the processor will be reset if the software fails to m aintain pulses to the
watchdog circuit.
3.14 Local Bus Monitor
All bus cycles (including VMEbus arbitration requests) are timed by an on-board timer. If any cycle
takes longer than 64 CPU clock cycles a Transfer Error Abort signal and bus error exception vector
are generated. Thus the processor cannot simply hang-up as a result of invalid addresses being
generated from software. The exception to this is for VMEbus accesses - these are timed by the
VMEbus Timeout monitor.
3.15 Configuration Switch
A 4-bit configuration switch is provided for soft ware bootstrap detection. This switch does not affect
the hardware directly, but is normally used by the software to set up the BVME4000/6000's
configuration registers.
3.16 EEPROM
An NM24C02 serial I2C EEPROM device provides 2Kbits of EEPROM storage for configuration
settings. The NMC24C02 is accessed on the I
2
C serial bus via the Board Control Register.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600010
4. Installation
The BVME4000/6000 module is inserted into a vacant VMEbus slot. If it is to function as the system
controller, then it should be positioned in slot 1. It passes thr ough all VMEbus dais y chained ar bitr ation
signals.
IACK should be jumpered to IAKIN on the backplane at slot 1. All interrupt IAKIN to IAKOUT and BGIN
to BGOUT signals should be jumpered across vacant slots to the right of the module.
If it is not the system controller, it may be located in any of the VMEbus slots to the right of the
VMEbus system controller.
To install the BVME4000/6000:
1.Ensure all backplane jumpers associated with the slot for the BVME4000/6000 are removed.
2.Ensure the BVME4000/6000 module is correctly configured for the target system.
3.If the Parallel interface is to be used, plug in the parallel cable to JP3 (if not using the P2
connections).
4.Connect the SCSI cable to the 50 way SCSI connector on the BVME4000/6000 (if not us ing
the P2 connections), ensure the correct polarity.
5.Insert the BVME4000/6000 module into the rack pushing the VMEbus connector fully home.
6.Secure the BVME4000/6000 into the rack with the two fixing screws top and bottom.
7. Plug in serial cables to JP1 and/or JP2 (if not using the P2 connections).
8.If using Cheapernet, connect the Cheapernet BNC-T connec tor to the BVME4000/6000 BNC
connector or if using the optional 10BaseT, connect the RJ45 connector to the
BVME4000/6000 RJ45 connector.
9.Connect the IP I/O connections to the two 50 way front panel connectors.
10. Ensure that the configuration switch is set up correctly for the software installation.
11. Ensure the correct application EPROM's are fitted.
Removal is the reverse of assembly.
If the test or application software fails, ensure that all installation instructions have been correctly
carried out. Some typical reasons for incorrect operation are:-
1.Socketed components may become dis turbed in transit. Push hom e all soc keted com ponents
where suspect.
2.The BVME4000/6000 module uses the VMEbus Address modifier codes to determine address
significance. Ensure the host CPU module produces the correct address modifier codes.
3.Ensure that all links are conf igured to the default set-up or that any alterations to the default
are correctly configured.
4. Ensure that the VMEbus backplane (if used) is correctly configured with regard to the daisychain signal jumpers and the IACK termination jumpers (if any).
The BVME4000/6000 CPU requires adequate airflow across it to ensur e correct oper ation. A heatsink
may need to be fitted to the CPU - refer to "Appendix E Thermal Managem ent (on page 68)" for more
details.
Copyright 1993,1995,1998,2001 BVM Ltd.
5. Configuration
5.1 PCB Layout
ABORT
RESET
LEDS
SERIAL B
SERIAL A
1
1 2
2
Pin1
LK1
LK2
P
R
I
N
T
E
R
MC68040
OR
MC68060
IC 2
1 2 3
1 2 3
11BVME4000/6000
M4
M3 M2
VME BUS
CONTROLLER
21
LK5
3V5V
XM1
INTERRUPT
CONTROLLER
ADDRESS
MAP
CONTROLLER
M1
CHEAPERNET
CONFIG
SWITCH
IP A
CONNECTOR
IP B
CONNECTOR
3
2
1
LK6
LK7
2 4 6
1 3 5
2 4 6
1 3 5
LK8
2 4 6
1 3 5
LK9
82596
LANC
NCR53C710
SCSI
CONTROLLER
STATIC RAM
PERIPHERAL
CONTROLLER
L
1
1
2
1 1 1
2 2 2
3 3 3
1 2 3
LK14
1 2 3
LK15
BATTERY
INDUSTRY
PACK
CONTROLLER
LL
KKK
1
01
LOW
PROM
HIGH
PROM
LK21
LK22
1 2
1 2
1
21 2
LK3
LK4
DISK POWER
CONNECTOR
LK13
FUSES
1 2
IP EXPANSION
Figure 3 PCB Layout
Copyright 1993,1995,1998,2001 BVM Ltd.
SCSI
BVME4000/600012
5.2 Link and Switch Definitions
The following link definitions s how the links grouped in the sam e orientation as the layout drawing on
the previous page, i.e. with the VMEbus connectors to the right. Link positions m arked with a # show
the default configuration.
Some of the link numbers are not described here, these are for factory use only when configuring
different build variants of the BVME4000/6000 and are not available for user's.
5.2.1 LK1 Abort Switch Enable
LK1
ABORT
RESET
1
MC68040
OR
MC68060
2
IC 2
Figure 4 LK1 Abort Switch Enable
Location
Fitting this link enables the ABORT switch to generate interrupts.
These links allow selection between CHEAPERNET (via front panel BNC c onnector) and ET HERNET
AUI (via P2 connector). They must all be set in conjunction.
LK7,8,9Function
1 & 3, 2 & 4
#
CHEAPERNET via front panel BNC
3 & 5, 4 & 6ETHERNET AUI via P2 connector
Note: these links are not fitted for the optional 10BaseT operation as it is permanently selected.
5.2.8 LK10,11,12,14,15 EPROM Size & Type Select
LK12
SERIAL A
LK14
LK15
CHEAPERNET
CONFIG
SWITCH
LK11
XM1
PERIPHERAL
CONTROLLER
1 1 1
2 2 2
3 3 3
1 2 3
1 2 3
LK10
ADDRESS
MAP
CONTROLLER
Figure 11
LK10,11,12,14,15
EPROM Size & Type
Select Location
LOW
PROM
These links selects the size of EPROM in the IC44/45 32-pin EPROM sockets. A 27C512 (28-pin)
EPROM should be fitted to the lower 28-pins of the socket (pins 1, 2, 31 & 32 unused).
This link allows the SCSI bus terminators to be enabled on the BVME4000/6000. T his is necessary if
the BVME4000/6000 is at the end of the SCSI bus cable, otherwise the terminators should be
disabled.
LK13Function
1 & 2 Omitted #SCSI bus terminated on BVME4000/6000
1 & 2 FittedNO SCSI bus termination on BVME4000/6000
5.2.10 LK18,19 CPU 5/3.3V Selection
LK18
ABORT
RESET
LEDS
MC68040
OR
MC68060
IC 2
M3 M2
VME BUS
CONTROLLER
Figure 13
LK18,19 CPU
5/3.3V Selection
Location
SERIAL B
5V
1 2 3
1 2 3
3V
INTERRUPT
CONTROLLER
LK19
These are factory set links – when a 68040 series CPU is fitted, 5V is s elected, when a 68060 series
CPU is fitted 3.3V is selected. They must all be set in conjunction.
Setting these links incorrectly will cause damage to the CPU device.
LK18,19 (5V/3V)Function
1 & 25 VOLTS SELECTED FOR 68040 SERIES
2 & 33.3 VOLTS SELECTED FOR 68060 SERIES
Copyright 1993,1995,1998,2001 BVM Ltd.
5.2.11 LK21 SRAM Backup Selection
LK21
17BVME4000/6000
XM1
ADDRESS
MAP
CONTROLLER
Figure 14 LK21 SRAM
PERIPHERAL
CONTROLLER
LOW
PROM
HIGH
PROM
1
2
Backup Selection
Location
This link enables the SRAM to be back ed up by the on-board battery. The SRAM is always back ed up
by the 0.1F Memory Capacitor and the VMEbus STDBY supply.
LK21Function
1 & 2 FittedSRAM is backed up by battery or MEMCAP/VMEbus STDBY
1 & 2 Omitted #SRAM is only backed up by MEMCAP/VMEbus STDBY
5.2.12 LK22 VMEbus System Controller Enable
LK22
XM1
PERIPHERAL
CONTROLLER
This link forces the BVME4000/6000 to be the VMEbus System Controller, so the BVME4000/6000
performs as the VMEbus arbiter, drives VMEbus SYSCLK and VMEbus BCLR. The norm al selection
for this function is in the Board Control Register when not overridden by this link - refer to "7.13.3 Port
B Usage (on page 52)". Omitting this link is typically required to ensure that the VMEbus SYSCLK
signal is driven as the VMEbus RESET signal is de-asserted.
LK22Function
1 & 2 OmittedBVME4000/6000 VMEbus System Controller ENABLED
1 & 2 Fitted #BVME4000/6000 VMEbus System Controller set in BCR
ADDRESS
MAP
CONTROLLER
LOW
PROM
HIGH
PROM
Figure 15 LK22 VMEbus
System Controller
Enable Location
1 2
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600018
5.2.13 Configuration Switch
PERIPHERAL
CONTROLLER
LOW
CHEAPERNET
CONFIG
SWITCH
1
2
3
4
82596
LANC
PROM
Figure 16 Configuration
Switch Location
This switch can be read by software to indicate system configuration options to the boot strap routines.
A switch ON selects a logical 0 f or a bit and a switch OFF selects a logical 1 for a bit. Switch pole 1
relates to Bit 3, switch pole 2 to Bit 2, switch pole 3 to Bit 1, and switch pole 4 to Bit 0 in the
BVME4000/6000 Configuration Switch Register - refer to "7.11.2 Configuration Switch Register (on
page 49)".
5.3 Indicators
5.3.1 Green LED - RUNNING
The GREEN RUNNING LED indicates that the BVME4000/6000 is running valid code. When
extinguished, the processor is either halted or stopped. The LED will also dim when the pr ocessor is
executing an RTE instruction, stacking an exception frame or doing an MMU table search.
5.3.2 Red LED - VMEbus Master Access
The RED MASTER LED indicates that the BVME4000/6000 is currently an active VMEbus master.
Copyright 1993,1995,1998,2001 BVM Ltd.
19BVME4000/6000
6. Connector Pinouts
6.1 JP1 & JP2 Serial Port Connections
JP1 and JP2 carry the serial port signals for Serial Channel A and Serial Channel B respectively. JP1
(Serial Channel A) is the lower connector. T he layout is designed to connect dir ec tly to a s tandar d 25way connector as shown:
The pinout numbering conventions are
different for the two styles of connector (see
diagram). However, the pinout is arranged to
give a one to one connection to a 25-way Dtype connector when using Insulation
Displacement Connectors (IDC) and ribbon
cable.
Not all the RS232 signals defined for a 25
way connector are supported by the
BVME4000/6000. The cable assembly
should be built such that pin 1 on the 14 way
connector connects to pin 1 of the 25 way. A
14 way ribbon cable is used leaving pins 8 13 and 21 - 25 unconnected.
N/C
N/C
N/C
N/C
N/C
N/C
N/C
14
12
10
8
6
13
11
9
7
5
34
12
GND
DTR
RTS
CTS
TxD
RxD
GND
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
GND
7
DTR
6
RTS
5
CTS
4
TxD
3
RxD
2
GND
1
Figure 17 JP1 & JP2 Serial Port Connections
The above assumes standard RS232 driver s are fitted to the BVME4000/6000. If RS422 or RS485
interface modules are fitted refer to the RS422/RS485 INT ERFACE MODULE docum entation detailed
in the "A.9 RS422/485 Interface Module (on page 60)" section of this manual .
6.2 JP3 Parallel Port Connections
JP3 carries the parallel port signals, and the layout is designed to connect directly to a standard 36way connector as shown:
The pinout numbering conventions
are different for the two styles of
10
11
12
13
14
15
16
17
18
19
1
2
3
4
5
6
7
8
9
connector (see diagram). However,
20
the pinout is arranged to give a one
21
to one connection to a 36-way delta
22
printer connector when using
23
Insulation Displacement
24
Connectors (IDC) and ribbon cable.
25
26
Not all the signals defined for a 36
27
way connector are supported by
28
the BVME4000/6000. The cable
29
assembly should be built such that
30
pin 1 on the 26 way connector
31
connects to pin 1 of the 36 way. A
32
26 way ribbon cable is used leaving
33
pins 14 - 18 and 32 - 36
34
unconnected.
35
36
/STROBE
DATA1
DATA2
DATA3
DATA4
DATA5
DATA6
DATA7
DATA8
/ACKNOW
BUSY
N/C
N/C
11
13
15
17
19
21
23
25
GND
1
3
5
7
9
2
4
6
8
10
12
14
16
18
20
22
24
26
GND
GND
GND
GND
GND
GND
GND
GND
GND
GND
N/C
N/C
/STROBE
DATA1
DATA2
DATA3
DATA4
DATA5
DATA6
DATA7
DATA8
/ACKNOW
BUSY
Figure 18 JP3 Parallel Port Connections
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600020
6.3 JP4 Cheapernet Connector
JP4 provides a 50Ω BNC connection to a 'Cheapernet' (IEEE802.3 10Base2) network.
When connecting to a network it is important that the bus topology is preser ved. The Cheapernet bus
is a multidrop bus with 50Ω terminator s at each end. Ideally each station on the bus has a zero length
stub connecting from the cable to the transceiver in the s tation. In practice, connection to the c able is
made using a BNC T-piece connected to the BNC connector. The cable is broken at the point of
contact and each new end is connected to the T-piece.
If the BVME4000/6000 is to be removed from the network, this is simply accomplished by
disconnecting the BVME4000/6000 BNC connector (JP4) from the T-piece, leaving the T-piece
connected to the cable.
All cheapernet cabling should use RG-58 type cable. It is important to ensure that both ends of the
cable are terminated using 50Ω BNC terminators.
Note: JP4 may be replaced by an optional 10BaseT RJ45 connection.
6.4 JP4 Optional 10BaseT Connector
The BVME4000/6000 may be fitted with an optional 10BaseT (twisted pair) Ethernet m odule. In this
case the 10BaseT connection is permanently selected and the AUI is not available. The JP4 BNC
connection is replaced with an RJ45 connector with the standard IEEE802.3 10BaseT pinout as
shown:
TD+
TD-
RD+
RD-
Figure 19 JP4 Optional 10BaseT Connector
1
2
3
4
5
6
7
8
Copyright 1993,1995,1998,2001 BVM Ltd.
21BVME4000/6000
6.5 JP5A/B IP A/B Connections
Each of the 50 pins on each I/O connector for the two IP, slots A and B, connects to a lik e-num bered
pin on the two corresponding flat cable connectors, JP5A and JP5B on the BVME4000/6000 front
panel. The IP I/O connector, the BVME4000/6000 flat cable c onnectors, and the wires on the r ibbon
cables are all numbered identically from 1 to 50.
Pin 1 on IP and BVME4000/6000 connectors are marked with a square pad, observable from the
solder side of the respective board. Pin 1 is shown on JP5 by a triangle etched into the connector
body. Pin 1 is typically marked on ribbon cable with a red stripe and on ribbon cable connectors with a
manufacturer's mark, often a moulded textured triangle.
Caution: This consistent pin numbering system is not maintained with many mass-terminated
connectors. Each type of connector has its own intrinsic pin numbering system. Systems
integrators or users making their own cables must be certain which pin corresponds to which
signal.
The pin assignment of the IP I/O connector is f ixed by the connector manufacturer and repeated in the
IP Specification. This assignment is shown below.
25
50
135791113
246810121415161718192021222324
26283032343638
2729313335373940414243444546464849
Figure 20 IP Connector Pin Numbering
Viewed from solder side of BVME4000/6000
The pin assignment of the 50-way flat cable connectors JA and JB are shown below:
JP7 is a power connection for a CPU fan (if f itted). Nor mally this will not be required,
THERM1
THERM0
+12V
GND
+5V
but in environments where the air-flow is not sufficient, the airflow can be
supplemented in this way. When a 68060 series CPU is being used, it's thermal
output signals for variable-speed fans are also available on this connec tor. Refer to
"Appendix E Thermal Management (on page 68)" for more details.
Figure 22 JP7 CPU Fan Power
6.7 JP8 JTAG Connector
JP8 is a JTAG connection via a 2 x 5 way header, the pinout matching the
TCK
TDS
TDI
TDO
GND
GND
Vcc
GND
/ENBL/TRST
MACH programming lead. This is for factory use only, to program the
internal BVME4000/6000 logic devices.
J1 carries the SCSI interface signals. The connector pinout allows
a 50 way IDC and ribbon cable assembly to be directly
connected. If necessary a standard 50-pin to 68-pin SCSI-1 to
SCSI-3 adapter may be used to adapt to 68-pin SCSI devices.
Figure 24 J1 SCSI Connections
Copyright 1993,1995,1998,2001 BVM Ltd.
23BVME4000/6000
6.9 J14 SCSI Peripheral Power Connections
J14 provides a power pick up connection for SCSI devices integrated within
+12V
GND
+5V
GND
+12V+5V
a module with the BVME4000/6000. It can provide up to 2A of +5V and 2A
of +12V. The pinout is arranged to be symmetrical allowing the mating
connector to be plugged either way around.
Figure 25 J14 SCSI Peripheral Power Connections
6.10 P2 I/O Connections
P2 is a 96 way, DIN-41612 connector consisting of 3 rows of 32 pins . The centre row (Row b) ca rries
VMEbus 32-bit extension signals. The other two rows carry BVME4000/6000 specific I/O connections:
The connections on the BVME4000/6000 which provide output power are protected with fus es. T hese
are surface-mounted fus es, and the BVME4000/6000 should be returned to factory for repair if any of
these fuses blows. For ref erence, the following is a list of the fuses, their functions, positions, r ating
and type.
Location
(see below)
CHEAPERNET
CONFIG
SWITCH
FunctionRatingType
(LittleFuse)
F1 SCSI TERM PWR1.5AALF II 42901.5
F2 ETHERNET -9V200mAALF II 429.200
F3 J14 +5V2AALF II 429002
F4 J14 +12V2AALF II 429002
F5 IP A +12V1AALF II 429001
F6 IP B +12V1AALF II 429001
F7 IP B +5V2AALF II 429002
F8 IP A -12V1AALF II 429001
F9 IP B -12V1AALF II 429001
F10 IP A +5V2AALF II 429002
F2F9 F6 F1 F3 F4 F7 F10 F8 F5
PERIPHERAL
CONTROLLER
LOW
PROM
HIGH
PROM
FUSES
82596
LANC
Figure 26 Protection Fuse Positions
Copyright 1993,1995,1998,2001 BVM Ltd.
25BVME4000/6000
7. Programming
7.1 Address Map
The Address Map for the BVME4000/6000 is shown below. The BVME4000/6000 is byte addressed;
each location addresses an 8-bit value. The BVME4000/6000 supports full 32-bit addressing for all
four Local Bus Masters (the MC68040/68060 CPU, the 82596CA LANC, the 53C710 SCSI Controller
and the VMEbus Slave Interface).
Some devices (IP memory, EPROM, SRAM, VMEbus A24) are dual mapped. This is to allow the
Transparent Translation registers in the MC68040/68060 to provide alternative cache modes for
accesses to these devices. The Cache Mode column is suggested cache mode, the hardware
provides no implicit cache mode control.
Address RangeDeviceSizeWidthCache ModeNotes
00000000 - variableMemory Module or
SRAM
variable - CFFFFFFFVMEbus - A32:D32up to 3328MbD32write through2
D0000000 - DFFFFFFFVMEbus - A32:D16256MbD16write through
E0000000 - E7FFFFFFIP Memory
FA000000 - FCFFFFFFReserved48Mb
FD000000 - FDFFFFFFVMEbus - A24:D3216MbD32non-c ac hed serial5
FE000000 - FEFFFFFFVMEbus - A24:D1616MbD16non-cached serial5
FF000000 - FFFFFFFFI/O see I/O map16Mbnon-cached serial
variableD32copyback1,2,4,6
128MbD16:D32write through5
D16write through4,5
(2Mb valid)
D32write through3,5
(2Mb valid)
128MbD16:D32non-cached serial5
D16non-cached serial4,5
(2Mb valid)
D32non-cached serial3,5
(2Mb valid)
NOTES:
1If 'RAMLO' is set, then accesses to the bottom 512Kb/2Mb of this space access the Battery Backed SRAM.
2The boundary between these spaces depends on how muc h memory is fitted to the memory module. Any space
3If no memory module is fitted, this SRAM can be dual mapped, s ee note 1. The SRAM is always ac cessible at t his
4For the first two accesses after RESET the E PROM is dual mapped at 00000000.
5These spaces are dual mapped in order to allow different caching modes to be s et up using the MC68040/68060's
6The caching mode is programmable on 16Mb boundaries. Therefore if the amount of on board memory is not
down here that is not decoded by the SRAM (if 'RAMLO' is s et) or the memory module is decoded as a VMEbus
A32:D32 access. This can be overridden if 'VMELO' is c lear, in which case the bott om 256Mb are decoded as onboard (SRAM or memory modul e) accesses only.
location.
Transparent Translation Registers.
divisible by 16Mb, the bottom bit of the VMEbus A32:D32 space will have to be copy back c ached. THI S MAY GIVE
CACHE COHERENCY PROBLEMS as the processor is unable to s noop VMEbus space. In this case locate t he
VMEbus A32:D32 devices on a 16Mbyte boundary which will allow the transparent translation regist ers to be set up
to give a coherent caching m ode.
Base Address :00000000
Size:Memory Module Dependent.
The BVME4000/6000 provides a site for BVM Memory Modules - refer to "Appendix C Memory
Module Pinout (on page 66)" for details. These modules are available in various configurations
(DRAM, SRAM, FLASH) and sizes and access speeds. Refer to the relevant Memory Module
documentation detailed in the "Appendix A Data Sheet & Manual Referenc es (on page 60)" sec tion of
this manual for details of the configuration.
The Memory Module Interface is 32-bits wide (though byte addressed) and supports Cache LINE
transfers. Thus 'zero wait state' operation is supported; giving the MC68040/68060 optimum
performance of 2/1/1/1 clock cycles per transf er. Thus 16 bytes of data can be transfer red in 5 clock
cycles (80Mbyte/sec @ 25MHz bus clock). Refer to the relevant Memory Module Manual for actual
memory performance.
The Memory Module provides a 'mem ory present' (/MEMO K) signal during the firs t c ycle of an acces s
that it decodes. Thus the BVME4000/6000 address decoder automatically handles different size
Memory Modules. Any accesses (for addresses up to CFFFFFFF) that are not decoded by the
Memory Module, generate a VMEbus A32:D32 master access (except if VMELO is clear, in which
case the bottom 256Mb are decoded as on- board accesses only) - r efer to "7.3.6 A32:D32 ( on page
28)" for more details.
Copyright 1993,1995,1998,2001 BVM Ltd.
27BVME4000/6000
7.3 VMEbus Master Access
The BVME4000/6000 can access VMEbus as a bus mast er. Depending on the Address Range used,
different types of access are performed.
VMEbus specifies three basic Address Mode schemes - A16 (Short I/O), A24 (Standard) and
A32 (Extended). The BVME4000/6000 supports all of these modes.
VMEbus also specifies three basic Data Transfer schemes - D08(EO), D16 and D32. The
BVME4000/6000 supports all these modes.
The BVME4000/6000 does not support Block transfers or A64:D64.
7.3.1 A16:D16 (D08EO)
Base Address :FFFF0000.
Size:64Kbyte.
Accesses to this area perf orm a Short I/O access to VMEbus with LW ORD inactive. Line and Long
Word accesses are automatically broken down to Word (D16) cycles. Byte accesses produce a
D08(EO) cycle. These accesses only involve signals available on the P1 VMEbus Connector.
The following Address Modifier (AM) codes are generated:
CPU SupervisorData Access= $2D
CPU UserData Access=$29
7.3.2 A16:D32
Base Address :FFEF0000.
Size:64Kbyte.
Accesses to this area perf orm a Short I/O access to VMEbus with LWORD dependent on the acc ess
type. Line and Long Word accesses pr oduce a D32 ( LWORD active) cycle. Word ac ces s es pr oduc e a
D16 (LWORD inactive) cycle. Byte accesses produce a D08(EO) cycle. These accesses involve
signals on both P1 and P2, therefore, a 'P2' Backplane is required.
The following Address Modifier (AM) codes are generated:
CPU SupervisorData Access=$2D
CPU UserData Access=$29
7.3.3 A24:D16 (D08EO)
Base Address :FE000000 or EE000000.
Size:16Mbyte.
Accesses to this area perf or m a Standard Address access to VMEbus with LWORD inactive. Line and
Long Word ac cesses are autom atically broken down to W ord (D16) cycles. Byte access es produce a
D08(EO) cycle. These accesses only involve signals available on the P1 VMEbus Connector.
The following Address Modifier (AM) codes are generated:
CPU SupervisorProgram Access= $3E
Data Access= $3D
CPU UserProgram Access= $3A
Data Access= $39
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600028
7.3.4 A24:D32
Base Address :FD000000 or ED000000.
Size:16Mbyte.
Accesses to this area perf or m a Standard Address access to VMEbus with LWO RD dependent on the
access type. Line and Long Word ac cesses produce a D32 (LW ORD active) cycle. Word accesses
produce a D16 (LW ORD inactive) cycle. Byte accesses produce a D08(EO) cycle. These accesses
involve signals on both P1 and P2, therefore, a 'P2' Backplane is required.
The following Address Modifier (AM) codes are generated:
CPU SupervisorProgram Access= $3E
Data Access= $3D
CPU UserProgram Access= $3A
Data Access= $39
7.3.5 A32:D16
Base Address :D0000000.
Size:16Mbyte.
Accesses to this area perform an Ex tended Address access to VMEbus with LW ORD inactive. Line
and Long Word accesses are automatically broken down to Word (D16) cycles. Byte accesses
produce a D08(EO) cycle. These accesses involve signals on both P1 and P2, therefore, a 'P2'
Backplane is required.
The following Address Modifier (AM) codes are generated:
CPU SupervisorProgram Access= $0E
Data Access= $0D
CPU UserProgram Access= $0A
Data Access= $09
7.3.6 A32:D32
Base Address:Immediately above the Memory Module, or 10000000 (if VMELO is
clear).
Size:Maximum 3328Mbyte (Memory Module Dependent).
Accesses to this area perf or m a Standard Address access to VMEbus with LWO RD dependent on the
access type. Line and Long Word ac cesses produce a D32 (LW ORD active) cycle. Word accesses
produce a D16 (LW ORD inactive) cycle. Byte accesses produce a D08(EO) cycle. These accesses
involve signals on both P1 and P2, therefore, a 'P2' Backplane is required.
This address space c an follow on contiguously from the top of a memory module, or the SRAM (if
RAMLO is set), or can be set to star t at a fixed base address (if VMELO is clear ). This allows for a
fixed partitioning of on-board and off - boar d memory for operating systems with this requir ement. Refer
to "7.10 VMEbus Slave Access Controller (on page 45)" for RAMLO and VMELO settings.
The following Address Modifier (AM) codes are generated:
CPU SupervisorProgram Access= $0E
Data Access= $0D
CPU UserProgram Access= $0A
Data Access= $09
Copyright 1993,1995,1998,2001 BVM Ltd.
29BVME4000/6000
7.4 SRAM
Base Address: E9000000 or F9000000.
Size:512K/2Mby te.
The 512Kbytes or 2Mbytes of SRAM is 32-bits wide, and provides a 5 CPU clock cycle access . The
SRAM can be accessed at the above two locations, which provide f or different cache regions f or the
same mem ory. Normally the MC68040/68060 will be set-up so that accesses in the region E9000000 E9FFFFFF are write-through cached, and accesses in the region F9000000 - F9FFFFFF are noncached with bus-serialised access.
The SRAM is normally backed up by an on-board m emory storage capacitor , and typically is used for
non-volatile storage applications such as a RAM-disc. In this case, the SRAM can retain it's data for up
to 7 days. If link selected to enable backup from the on-board battery, then the data can be retained
for up to 2.5 years, allowing also for the supply to the Real Time Clock - see "5.2.11 LK21 SRAM
Backup Selection (on page 17)". T he SRAM is also backed-up fr om the VMEbus ST DBY line. W hen
using the VMEbus STDBY line, retention time is dependant on the external source.
The SRAM can also be mapped to appear at the bottom 512K/2Mbytes of the memory map for boards
without a memory module fitted by setting RAMLO. In this case the SRAM is used as main system
memory, and normally will be treated as copy-back c ached m em ory for m axim um perf orm ance. Refer
to "7.10 VMEbus Slave Access Controller (on page 45)" for RAMLO setting.
7.5 EPROM
Base Address: E8000000 or F8000000.
Size:2Mbyte.
The BVME4000/6000 provides 2 x 32-Pin EPROM JEDEC compatible sockets that may be link
selected to accept either 64K8, 128K8, 512K8 or 1024K8 EPROM devices (e.g. 27C512, 27C010,
27C020, 27C040 or 27C080), providing 64K-2Mbytes of EPROM or 512K8 AM29F040 s ingle-voltage
FLASH EPROM devices, providing 1Mbyte of on-board programmable FLASH EPROM memory.
The EPROM space is 16-bits wide, and provides a 10 CPU cloc k cycle access. 90nS or faster devices
must be used at 33MHz, 120nS devices may be used at 25MHz bus clock. The EPROM can be
accessed at the above two locations, which provide for different cac he regions for the s ame m emor y.
Normally the MC68040/68060 will be set-up so that accesses in the region E8000000 - E8FFFFFF are
write-through cached, and accesses in the region F8000000 - F8FFFFFF are non-cached with busserialised access.
The EPROM is also mapped at the bottom of the memory map for the firs t two cycles after a reset.
This is to allow for the MC68040/68060 to fetch the initial program counter and stack pointer from the
first two longword locations in the EPROM.
When AM29F040 devices are fitted in these sockets, they can be accessed word-wide for
programming, erasing etc.. This means that effec tively the sector sizes are 128Kbytes (64Kbytes per
device), and they can be programmed/erased in parallel. For full programming details, refer to the
AMD AM29F040 documentation detailed in the "A.10 AM29F040 (on page 60)" section of this manual.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600030
7.6 SCSI Controller
7.6.1 Overview
The SCSI Interface uses the NCR53C710. This provides asynchronous transfers of up to 5Mbytes per
second and synchronous transfers of up to 10Mbytes per second. The 32-bit DMA driven interface
allows direct access to the entire memory map of the BVME4000/6000. The burst mode interface
stacks up 16 bytes at a time and transfers them as a line transfer at up to 4/2/2/2 access s peeds at
25MHz bus clock. This gives a 400nS burst every 3.2µS (at 5Mbyte/s) or 12.5% bus bandwidth
requirement.
The 53C710 is an intelligent Processor in its own right, running SCSI SCRIPTS software. This enables
very high level commands to be issued to the SCSI interface further minimising processor overhead.
7.6.2 Programming
The 53C710 is controlled using the 64 registers defined in section "7.6.4 SCSI Controller Registers (on
page 31)". Transfers with the SCSI bus ar e conduc ted independently of the m ain CPU. T he main CPU
sets up various parameters in the 53C710's registers, points the 53C710 at the start of a SCSI
SCRIPTS routine and tells it to run. Upon term ination the 53C710 interrupts the main CPU and waits
for a new start address. The main CPU can examine the res ults of the operation by interrogating the
53C710 registers.
The 53C710 can access the entire BVME4000/6000 address space, including becoming VMEbus
master. It access es memory for two purposes: SCRIPT S code fetches and DMA accesses for SCSI
data transfers.
Note that the 53C710 is configured for Big Endian Mode. T his can affect addressing in f airly subtle
ways. For full programming details, refer to the 53C710 documentation detailed in the "A.4 53C710 (on
page 60)" section of this manual.
Refer to "Appendix B CPU Cache Coherency and Bus Snooping (on page 62)" for details on Cache
Coherency Implications (snooping) while the 53C710 is a bus master.
Refer to "7.8 Interrupt Controller (on page 35)" for details of Interrupt generation by the 53C710.
7.6.3 Hardware Specific Considerations
The raw SCSI clock (SCLK) is driven with 40MHz. Thus the CF(1-0) bits in the DCNTL register must
be set to 00 (default value). This gives a core clock of 20MHz and a SCSI-1 synchronous transf er rate
of 5Mb/s. Optionally, the SSCF(1-0) bits in the SBCL may be set to 01 to give a SCSI-2 synchronous
transfer rate of 10Mb/s.
The 53C710 is hardware configured for Bus Mode 2. The following need to be set for correct operation
of the bus interface:
The first access to the 53C710 must be to set EA bit in DCNTL (This enables the 53C710 to
generate TA for slave cycles).
The TT1 bit of CTEST7 must be set (indicates TT1 pin cleared when bus master).
The TT0 bit of DMODE must be clear (indicates TT0 pin cleared when bus master).
The FC(2-1) bits of DMODE should be set to 10 (indicates Supervisor Data Access).
The PD bit of DMODE should always be clear (indicating Supervisor Data for all accesses).
The SM bit of CTEST8 must be clear (snoop control only driven as master).
The FA bit of DCNTL should always be clear (no 'fast' arbitration).
The BVME4000/6000 does not support differential SCSI transf ers thus the DIFF bit of CT EST7 must
always be clear.
Copyright 1993,1995,1998,2001 BVM Ltd.
31BVME4000/6000
7.6.4 SCSI Controller Registers
AddressSizeRead WriteRegi sterDescription
FF000000BR/WSIENS CS I Interrupt Enable
FF000001BR/WSDIDSCSI Destination ID
FF000002BR/WSCNTL1SCSI Control 1
FF000003BR/WSCNTL0SCSI Control 0
FF000004BR/WSOCLSCSI Output Control Latch
FF000005BR/WSODLSCSI Output Data Latch
FF000006BR/WSXFERSCSI Trans fer
FF000007BR/WSCIDSCSI Chip ID
FF000008BR/WSBCLSCSI Bus Control Lines
FF000009BRSBDLSCSI Bus Data Lines
FF00000ABRSIDLSCSI Input Data Latch
FF00000BBR/W*SFBRSCSI First Byte Received (Wri te Restrictions apply)
FF00000CBRSSTAT2SCSI Status 2
FF00000DBRSSTAT0SCSI Status 1
FF00000EBRSSTAT0SCSI S tatus 0
FF00000FBRDSTATDMA Status
FF000010LWR/WDSAData Structure Address
FF000014BRCTE ST3Chip Test 3
FF000015BRCTE ST2Chip Test 2
FF000016BRCTE ST1Chip Test 1
FF000017BR/WCTEST0Chip Test 0
FF000018BR/WCTEST7Chip Test 7
FF000019BR/WCTEST6Chip Test 6
FF00001ABR/WCTES T5Chip Test 5
FF00001BBR/WCTES T4Chip Test 4
FF00001CLWR/WT E MPTemporary Stack
FF000020BR/WLCRCLongitudinal Parity
FF000021BR/WCTEST8Chip Test 8
FF000022BR/WISTATInterrupt Status
FF000023BR/WDFIFODMA FIFO
FF000024BR/WDCMDDMA Command
FF000025(B)R/WDBC (lsb)DMA Byte Counter (least signif i cant byte)
FF000026WR/WDBCDMA Byte Counter
FF000028LWR/WDNADDMA Next Address for Data
FF00002CLWR/WDSPDMA SCRIPTS Pointer
FF000030LWR/WDSPSDMA SCRIPTS Pointer Save
FF000034LWR/WSCRATCHGeneral Purpose Scratch Pad
FF000038BR/WDCNTLDMA Control
FF000039BR/WDWTDMA Watchdog Ti mer
FF00003ABR/WDIENDMA Int errupt Enable
FF00003BBR/WDMODEDMA Mode
FF00003CLWR/WA DDE RSum Output of Internal Adder
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600032
7.6.5 SCSI Electrical Interface
The output drivers for the SCSI interf ace fully conform to the electrical requirements of SCSI-1 and
SCSI-2.
The drivers are isolated from the power supply. This ensures that, when powered down, the
BVME4000/6000 does not affect the active SCSI bus.
The SCSI bus requires termination at both ends of the bus. It is important that terminators are f itted at,
and only at, both ends of the bus. The BVME4000/6000 uses active, cur rent-mode terminators that
provide high performance termination that allows the BVME4000/6000 to achieve 10Mb/s transfer
rates when connected to a SCSI-2 bus.
The BVME4000/6000 terminators are active when LK13 is omitted. When LK13 is fitted, then the
BVME4000/6000 terminators are completely disabled and provide no load to the SCSI bus.
The BVME4000/6000 drives TERMPWR and uses T ERMPWR for its onboard ter m inators. T hus even
when unpowered the BVME4000/6000 will provide correct termination, if enabled (LK13 omitted).
Connection to SCSI bus is achieved via two alternative connections:
1.J1 provides a direct connection to a 50-way standard IDC ribbon. The layout of this connector
is intended for direct connection to SCSI peripherals built into a module with the
BVME4000/6000.
2.P2 carries all the SCSI signals (including T ERMPWR). T his allows a transition module to be
connected behind the backplane to provide connection to SCSI peripherals outside the
BVME4000/6000 enclosure.
Refer to section "6 Connector Pinouts (on page 19)" for details of SCSI connector pinouts.
Copyright 1993,1995,1998,2001 BVM Ltd.
33BVME4000/6000
7.7 Ethernet Controller
7.7.1 Overview
The Ethernet Interface is built around the Intel 82596CA LANC. This provides a 32-bit DMA driven
interface to both Ethernet (via the AUI interface) and Cheapernet (via a front panel BNC). The 32- bit,
DMA driven interface allows direct acc ess to the entire m emory map of the BVME4000/6000 allowing
full packet management by the 82596CA. Each 32-bit transfer requires 320nS max (including
arbitration) to execute the cycle. A transfer will occur no more frequently than every 4µS (4 bytes at
1Mbyte per second). Thus worst case bus bandwidth requirement is 8% at 25MHz bus clock.
7.7.2 Programming
The CPU and the 82596CA do not communicate directly (by registers). Instead, they comm unic ate via
a shared memory model. That is, the CPU sets up command blocks in memory and activates the
82596CA's Channel Attention. The 82596CA then examines the command block and executes the
commands. When it has finished it generates an interrupt to the CPU.
The 82596CA is hardware configured for Big Endian operation. This has fairly subtle effects on
parameter ordering in mem ory command blocks; in partic ular, m os t address pointers have their words
swapped. For full programming details, refer to the 82596CA documentation detailed in the "A.3
82596CA (on page 60)" section of this manual.
Although the CPU and the 82596CA do not generally communicate directly, there is a 'virtual' register
that the CPU can access to assert Channel Attention and to write to an 82596CA internal register
(PORT).
Refer to "Appendix B CPU Cache Coherency and Bus Snooping (on page 62)" for details on Cache
Coherency Implications (snooping) while the 82596CA is a bus master.
Refer to "7.8 Interrupt Controller (on page 35)" for details of Interrupt generation by the 82596CA.
7.7.3 PORT Access
Accesses to the PORT register cons ist of tw o consecu tive 32-bit writes at location FF100000, with
bits D31..D16 of the command in the least s ignificant word and bits D15..D0 of the command in the
most significant word (i.e. the command is word-swapped). The PORT register is a write only register.
Writing to the 82596CA PORT allows the CPU to do four things:
1.Write an Alternative System Conf iguration Pointer (SCP) address. This needs to be done as
the 82596CA will, by default, access 00FFFFF6 for its initial command block after reset.
2.Perform a dump of the internal state of the 82596CA to a specified address.
3.Execute a software reset.
4.Execute a self-test and write the results to memory at the specified address.
FunctionD31D4D3D2D1D0
Reset0000
Self-TestA31 Self-test Results AreaA40001
SCPA31 Alternative SCP AddressA40010
DumpA31 Dump Area PointerA40011
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600034
7.7.4 Channel Attention Access
Reading from location FF100000 causes a pulse on the 82596CA Channel Attention input. This
causes the 82596CA to execute command blocks.
7.7.5 Bus Error Handling
The 82596CA cannot directly handle bus errors. If the 82596CA is the bus master and access es a
location from which a bus error is generated (e.g. accesses non-existent memory) then special
hardware on the BVME4000/6000 handles the error condition.
When a bus err or occurs, the 82596CA is removed from the bus and kept off the bus by asserting
BOFF. ETHERR is generated causing an Ethernet Interrupt and the ETHERR bit to be set in the
Interrupt Local Status Register - ref er to "7.8 Interrupt Controller (on page 35)" for details of interrupt
control and status. The 82596CA is held of f the bus until a reset PORT command is issued to the
82596CA.
7.7.6 SYSBUS Byte Requirements
The SYSBUS byte of the SCP controls various hardware bus operations and must be set up as
follows:
Bit 6Must be set.
INTBit 5Must be clear (active high interrupt).
LOCK Bit 4LOCKed cycles are supported on the BVME4000/6000. It is recommended
that the LOCK function be enabled (bit is clear).
TRGBit 3External Triggering is supported on the BVME4000/6000. It is r ecommended
that external triggering be used (bit is set).
M(1-0) Bit 2,1 Should only be used in Linear Addressing Mode (bit 2 is set, bit 1 is clear).
7.7.7 Electrical Interface
The BVME4000/6000 provides both a full 'Cheapernet' (IEEE802.3 - 10Base2) coaxial interface via the
front panel and an Attachment Unit Interface (AUI) port via P2. This allows a transition module to be
connected behind the backplane to provide connection to Thick Ethernet (IEE802.3 - 10Base5) or
other Ethernet standards (e.g. Twisted Pair IEE802.3 - 10BaseT) outside the BVME4000/6000
enclosure.
Selection between the on board Cheapernet interface or the P2 AUI connection is m ade by three links
- refer to "5.2.7 LK7,8,9 Ethernet AUI/Cheapernet Select (on page 15)" for details of the link settings.
An optional 10BaseT (twisted pair) module is available which replaces the Cheapernet connection.
The AUI port is not available when this module is fitted.
Copyright 1993,1995,1998,2001 BVM Ltd.
35BVME4000/6000
7.8 Interrupt Controller
7.8.1 Overview
The Interrupt Controller is responsible for two independent functions:
Processor Interrupter-T akes interrupts fr om all sourc es (including VMEbus IRQ's , IP IRQ's,
Timers, etc.) and generates an interrupt to the CPU.
VMEbus Interrupter - Generates Interrupts on the VMEbus.
8570 Timers6Auto-vectored
68230 Timer5Vectored
Memory Module4Auto-vectored
85230 DUART3Vectored
53C710 SCSI3Auto-vectored
68230 Parallel2Vectored
82596CA ENET2Auto-vectored
Location Monitor1Auto-vectored
IP A Int 0
IP A Int 1
IP B Int 0
IP B Int 1
IP Daughter Board
Interrupts, up to 12
sources
VMEbus IRQ 77
VMEbus IRQ 66
VMEbus IRQ 55
VMEbus IRQ 44
VMEbus IRQ 33
VMEbus IRQ 22
VMEbus IRQ 11
VMEbus ACFAIL7Auto-vectored
Program
ProgramVectored - Level Programmable on IP Daughter Board.
Vectored - Level Programmable in IP Interface see "7.9.6 IP Controller Registers (on page 42)".
Where multiple sources are generating interrupts on the same level, the acknowledge cycle is
prioritised as follows:
Highest Priority:Auto-vectored
Local vectored
VMEbus Interrupt
Lowest Priority:IP
The IP Interrupts are highly programm able. They are program med in the IP Inter face - refer to "7.9 IP
Controller (on page 39)" for details. The IP interface is responsible for prioritising any pending IP
interrupts. The Interrupt Controller combines the current state of IP inter rupts with all other sources to
generate an Interrupt code to the CPU. During acknowledge cycles, the Interrupt Controller prioritis es
between sources of active interrupts and generates the appropriate acknowledge signal. If it
acknowledges the IP interrupt, then the IP Interface prioritises between any active IP interrupts.
When a VMEbus Interrupt is acknowledged, the BVME4000/6000 becomes a VMEbus master and
initiates an Interrupt Acknowledge cycle over VMEbus. The BVME4000/6000 expects the VMEbus
interrupter to return a vector which is then used by the processor vectoring mechanism . If no VMEbus
interrupter responds within the VMEbus time-out period, then a 'spurious interrupt' vector is generated.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600036
7.8.3 VMEbus interrupter
The BVME4000/6000 can generate interrupts on the VMEbus. This function is c ompletely independent
of the processor Interrupter function. When acknowledged by the VMEbus interrupt handler, the
BVME4000/6000 returns a programmable 8- bit vector. The interr upter is implem ented as Release On
AcKnowledge (ROAK). Thus the interrupt is cleared by the interrupt acknowledge cycle.
The BVME4000/6000 may generate an interrupt on any of the seven VMEbus IRQ levels. However, it
can only generate on a single level at any one time. The level on which an interrupt is gener ated is
programmable - refer to "7.8.4.2 VMEIRQ Vector Register (below)" for details.
The interrupt is asserted by the processor writing to the VMEIRQ Vector Register - refer to "7.8.4.3
VMEIRQ Level Register (on page 37)" for details. The value written to the VMEIRQ Vector Regist er is
then used as the value returned in the subsequent acknowledge cycle.
7.8.4 Interrupt Controller Registers
The Interrupt Controller contains six byte wide registers in four I/O loc ations. The first three locations
are WRITE ONLY - DO NOT READ FROM THEM, the last location is READ ONLY.
When SET thes e bits enable the corresponding inter rupts from VMEbus. For exam ple setting
bits 7 and 3 enable VMEbus IRQ's 7 and 3 to generate interrupts to the processor.
After RESET these bits are CLEAR (i.e. all VMEbus interrupts disabled).
Bit 0:ACFEN: ACFAIL Interrupt Enable.
When SET this bit enables interrupts from the VMEbus ACFAIL signal - r efer to "7.8.4.6 Local
IRQ Status Register (on page 38)" for details on ACFAIL interrupt operation.
After RESET this bit is CLEAR (i.e. ACFAIL interrupts disabled).
7.8.4.2 VMEIRQ Vector Register
Bit 7-1: VEC(7-1): Interrupt Vector.
Writing to this register s ets bits 7 to 1 of the Interrupt ID vector that will be returned to the
VMEbus Interrupt Handler, bit 0 is always set to ZERO. The act of writing to this register also
causes the VMEbus interrupt line, selected by the LVL(2-0) bits in the VMEIRQ Level
Register, to become active.
Bit 0:Select Bit.
This bit is used to select between the VMEIRQ Level Register and the VMEIRQ Vector
Register. This bit must be written as a ZERO to select the VMEIRQ Vector Register.
Copyright 1993,1995,1998,2001 BVM Ltd.
37BVME4000/6000
7.8.4.3 VMEIRQ Level Register
Bit 7-4: Reserved.
For future compatibility these must be always written as zero.
Bit 3-1: VLVL(2-0): VMEbus Interrupter Level.
These bits select on which VMEbus Inter rupt level the board will act as an interrupter. The
binary code written selects the corresponding interrupt level (i.e. 101 selects level 5). W hen
set to 000 no interrupt can be generated on VMEbus.
After RESET these bits are CLEAR (i.e. VMEbus interrupt generation disabled).
Bit 0:Select Bit.
This bit is used to select between the VMEIRQ Level Register and the VMEIRQ Vector
Register. This bit must be written as ONE to select the VMEIRQ Level Register.
7.8.4.4 LOCIRQ Enable Register
Bit 7-2: Reserved.
For future compatibility these must be always written as zero.
Bit 1:LOCEN: Location Monitor Interrupt Enable.
When SET this bit enables interrupts from the VMEbus Location Monitor - refer to "7.10
VMEbus Slave Access Controller (on page 45)" for details of VMEbus Slave Operation.
After RESET this bit is CLEAR (i.e. location monitor interrupts disabled).
This bit is used to clear the Location Monitor Interrupt during interrupt service routines. T he
interrupt is cleared by disabling (CLEARing) and re-enabling (SET ting) the Location Monitor
Interrupt.
Bit 0:Select Bit.
This bit is used to select between the LOCIRQ Enable Register and the ETHIRQ Enable
Register. This bit must be written as ZERO to select the LOCIRQ Enable Register.
7.8.4.5 ETHIRQ Enable Register
Bit 7-2: Reserved.
For future compatibility these must be always written as zero.
Bit 1:ETHEN: Ethernet Interrupt Enable.
When SET this bit enables interrupts from the 85296 Ethernet Controller - refer to "7.7
Ethernet Controller (on page 33)" for details of Ethernet Controller Operation.
After RESET this bit is CLEAR (i.e. 82596CA interrupts disabled).
This bit is used to clear the 82596CA Interr upt during interrupt service routines. The interrupt
is cleared by disabling (CLEARing) and re-enabling (SETting) the Ethernet Interrupt.
Bit 0:Select Bit.
This bit is used to select between the LOCIRQ Enable Register and the ETHIRQ Enable
Register. This bit must be written as a ONE to select the ETHIRQ Enable Register.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600038
7.8.4.6 Local IRQ Status Register
Bit 7-4: Reserved.
These bits are unused. When read, their state is undefined.
Bit 3:ABORT: Abort Switch Interrupt.
This bit indicates the status of the ABORT switch. If this bit is SET the ABORT switch is
pressed. This will also generate an Auto-vector level 7 interrupt, so this bit can be used to
determine that the ABORT switch was the source of an Auto-vector level 7 interrupt.
Bit 2:ACFAIL: VMEbus ACFAIL Interrupt.
This bit indicates the status of the VMEbus ACFAIL signal. If this bit is SET the ACFAIL s ignal
is active. This will also generate an Auto-vector level 7 interrupt, s o this bit can be used to
determine that the ACFAIL signal was the source of an Auto-vector level 7 interrupt.
Bit 1:ETHERR: Ethernet ERROR Interrupt.
This bit indicates that a 82596CA Ethernet Controller BUS ERROR has occurred - refer to
"7.7.5 Bus Error Handling (on page 34)" for more details.
Bit 0:ETHIRQ: Ethernet Interrupt Level.
This bit indicates the status of the 82596CA Ethernet Controller interrupt signal. If this bit is
SET the 82596CA's interrupt signal is ac tive. Note: This does not indicate the s tatus of the
internal interrupt signal controlled by ETHEN, but indicates the status of the 82596CA's
interrupt signal directly. The 82596CA will pulse its interrupt line inactive whenever a 'new'
interrupt condition becomes true within the device. T hus to distinguish between an Ethernet
Error interrupt and a normal Ether net interrupt, the ETHERR bit should be interrogated; not
the ETHIRQ bit.
Copyright 1993,1995,1998,2001 BVM Ltd.
39BVME4000/6000
7.9 IP Controller
7.9.1 Overview
The IP interface supports two onboard IP sites (I P A & IP B) as well as up to a further 4 IP s ites via an
expansion interface on a separate daughter board (IP's C to F).
Double width (D32) pairs of IP's are supported. Support for D16 and D32 Memory IP's is included.
High speed operation is supported:
8 MHz:This is the standard clock speed that all IP's support.
32 MHz:This higher speed operation is def ined in the IP Specification. Many modern
IP designs offer this higher speed operation.
SYNC:In this m ode, the IP runs synchronously with the main CPU clock speed. This
can achieve much higher performance on compatible IP's as clock
synchronisation is not necessary.
7.9.2 IP Expansion Interface
The IP expansion interface allows for a low cost IP carrier daughter board to be added - refer to
"Appendix D IP Expansion Interface Pinout (on page 67)" for details. The BVME4000/6000 c ontains all
the state machine and multiplexing logic thus minim ising daughter board circuitry requirements. The
interface allows up to four additional IP sites on a daughter board at all speed selections. F or exam ple
the EXP100 Expansion Board can be used - refer to the EXP100 documentation detailed in the to
"A.16 EXP100 Quad IP Expansion User's Manual (on page 61)" section of this manual.
7.9.3 IP Interrupts
Each IP can generate interrupts on two separate IRQ lines, INT0 and INT1. The IP Interfac e contains
registers for setting, in s oftware, the level on which each IRQ source will generate interrupts. IRQ's
from the on board IP's (i.e. first two) are supported in the IP interface. The daughter board is
responsible for prioritising any pending interrupts fr om IP's on the daughter board. The IP interface
combines the current state of the daughter board with that of onboard IP's to generate an interrupt
code to the Interrupt Controller - refer to "7.8 Interrupt Controller (on page 35)" for details.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600040
7.9.4 Memory Space Address Map
The Address Map logic decodes two 128Mbyte regions for memory space accesses, generating
/IPMEMCS when the processor accesses either of the IP Memory regions. The IP mem ory is dual
mapped in two regions to provide for acc esses using different c aching modes. Refer to "Appendix B
CPU Cache Coherency and Bus Snooping (on page 62)" for mor e details. This region is then fur ther
decoded in the IP Interface.
Each IP can be accessed in two ways:
1.As a single, 16-bit wide device through an 8Mbyte window.
2.As a double-size, 32-bit wide device through a 16Mbyte window. In this mode, a pair of IP
sites are used to take the double-size IP.
Thus A26 to A0 are used by the IP's or IP Interface for memory space decoding as shown below.
For future compatibility these must be always written as zero.
Bit 2-0: A0L(2-0): IP A IntReq 0 Level.
These bits select on which Interrupt level the IP IntReq will act as an interrupter . The binary
code written selects the corresponding inter rupt level (e.g. 101 selects level 5). W hen set to
000 no interrupt can be generated.
After RESET these bits are CLEAR (i.e. interrupt generation disabled).
7.9.6.2 IRQ Level A1 Register
Bit 7-3: Reserved.
For future compatibility these must be always written as zero.
Bit 2-0: A1L(2-0): IP A IntReq 1 Level.
These bits select on which Interrupt level the IP IntReq will act as an interrupter . The binary
code written selects the corresponding inter rupt level (e.g. 100 selects level 4). W hen set to
000 no interrupt can be generated.
After RESET these bits are CLEAR (i.e. Interrupt generation disabled).
7.9.6.3 IRQ Level B0 Register
Bit 7-3: Reserved.
For future compatibility these must be always written as zero.
Bit 2-0: B0L(2-0): IP B IntReq 0 Level.
These bits select on which Interrupt level the IP IntReq will act as an interrupter . The binary
code written selects the corresponding inter rupt level (e.g. 011 selects level 3). W hen set to
000 no interrupt can be generated.
After RESET these bits are CLEAR (i.e. Interrupt generation disabled).
Copyright 1993,1995,1998,2001 BVM Ltd.
43BVME4000/6000
7.9.6.4 IRQ Level B1 Register
Bit 7-3: Reserved.
For future compatibility these must be always written as zero.
Bit 2-0: B1L(2-0): IP B IntReq 1 Level.
These bits select on which Interrupt level the IP IntReq will act as an interrupter . The binary
code written selects the corresponding inter rupt level (e.g. 010 selects level 2). W hen set to
000 no interrupt can be generated.
After RESET these bits are CLEAR (i.e. Interrupt generation disabled).
7.9.6.5 IP Clock Speed Select Register
The IP controller supports four different clock speeds to the IP sites: Two standard
frequencies; 8MHz and 32MHz and two 'Source Synchronous' frequencies that are derived
from the CPU clock. This register selects between the high speed (32MHz or CPU clock
frequency) and low speed (8MHz or CPU clock divided by four). It is set up in conjunction with
the IP Sync Clock Select Register to set the required IP frequency.
Bit 2:CLKX: IP Expansion Interface Clock Select.
When CLEAR the IP expans ion interface is clocked at 8MHz or CPU Clock divided by four
(depending on the setting of SYNCX bit of the IP SYNC Clock Select Regis ter). When SET
the IP expansion interface is clocked at 32MHz or CPU Clock (depending on the s etting of
SYNCX bit of the IP SYNC Clock Select Register).
After RESET this bit is CLEAR (i.e. 8MHz clock selected or CPU Clock divided by four).
Bit 1:CLKB: IP B Clock Select.
When CLEAR IP B is clocked at 8MHz or CPU Clock divided by four (depending on the setting
of SYNCX bit of the IP SYNCB Clock Select Register). W hen SET the IP expans ion interface
is clocked at 32MHz or CPU Clock (depending on the s etting of SYNCB bit of the IP SYNC
Clock Select Register).
After RESET this bit is CLEAR (i.e. 8MHz clock selected or CPU Clock divided by four).
Bit 0:CLKA: IP A Clock Select.
When CLEAR IP A is clocked at 8MHz or CPU Clock divided by four (depending on the setting
of SYNCX bit of the IP SYNCA Clock Select Register). W hen SET the IP expans ion interface
is clocked at 32MHz or CPU Clock (depending on the s etting of SYNCA bit of the IP SYNC
Clock Select Register).
After RESET this bit is CLEAR (i.e. 8MHz clock selected or CPU Clock divided by four).
7.9.6.6 IP SYNC Clock Select Register
The IP controller supports four different clock speeds to the IP sites. Two standard
frequencies: 8MHz and 32MHz and two 'Source Synchronous' frequencies that are derived
from the CPU clock. This r egister selects between the standar d speed (32MHz or 8MHz) and
Source Synchronous speed (CPU clock frequency or CPU clock divided by four). It is s et up in
conjunction with the IP Clock Speed Select Register to set the required IP frequency.
Bit 2:SYNCX: IP Expansion Interface SYNC Clock Select.
When CLEAR the IP expans ion interface is clock ed at 8 or 32MHz (dependent on the CLKX
bit see above). W hen SET the IP expansion inter face is clock ed synchronously with the main
CPU clock at either the CPU clock f requency or CPU clock divided by 4 (again dependent on
the CLKX bit).
After RESET this bit is CLEAR (i.e. 8/32MHz clock selected).
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600044
Bit 1:SYNCB: IP B SYNC Clock Select.
When CLEAR IP B is c locked at 8 or 32MHz (dependent on the CLKB bit see above). W hen
SET the IP expansion interface is clocked synchronously with the main CPU clock at either
the CPU clock frequency or CPU clock divided by 4 (again dependent on the CLKB bit).
After RESET this bit is CLEAR (i.e. 8/32MHz clock selected).
Bit 0:SYNCA: IP A SYNC Clock Select.
When CLEAR IP A is c locked at 8 or 32MHz (dependent on the CLKA bit see above). W hen
SET the IP expansion interface is clocked synchronously with the main CPU clock at either
the CPU clock frequency or CPU clock divided by 4 (again dependent on the CLKA bit).
After RESET this bit is CLEAR (i.e. 8/32MHz clock selected).
Copyright 1993,1995,1998,2001 BVM Ltd.
45BVME4000/6000
7.10 VMEbus Slave Access Controller
7.10.1 Overview
The BVME4000/6000 allows other VMEbus masters to access som e of its onboard address s pace. It
allows accesses via either A24 or A32 address spaces. The BVME4000/6000 also acts as a location
monitor for A16 accesses.
7.10.2 Standard (A24) & Extended (A32) Accesses
Both the size of the window and the base address of the window (from the VMEbus master's point of
view) are programmable. T he bas e address of the acc ess f rom the onboar d m em ory's point of view is
also programmable.
Thus the BVME4000/6000 can be set-up to 'dual m ap' a programm able amount of mem ory (64Kbyte
to 4Gbyte) onto the VMEbus. The local base address of the memory is programmable (on window size
boundaries). The address that the 'dual mapped' memory appears at on VMEbus is also
independently programmable. So, for example, 512Kbytes of memory module memory located at
00380000 could be accessed by another VMEbus master accessing location 00C00000-00C80000.
The address decoding for A24 and A32 accesses are separate from each other. There are two
decoders, one for A24 and one for A32. T hey both work by comparing the m ost significant byte of the
address with the programmed base address. Thus A24 space is programmable on 64Kbyte (2
24
boundaries, and the A32 space is programmable on 16Mbyte (2
) boundaries.
16
)
The window sizing operates by masking out address bits to the comparator. Thus f or A24 space the
smallest window size (when no bits are masked) is 64Kbyte and for A32 is 16Mbyte. The window sizes
available are powers of two up to the maxim um window size of the address space (A24 = 8Mbytes,
A32 = 512Mbytes).
A restriction on the window base address is that it m ust be on a window size boundary. Thus if the
window size is 128Kbytes, the window base address must be on a 128Kbyte boundary, e.g. 00000000,
00020000, 00040000, 00D00000 etc.
The BVME4000/6000 responds to the following A24 Address Modifiers (AM) codes:
CPU SupervisorProgram Access= $3E
Data Access= $3D
CPU UserProgram Access= $3A
Data Access= $39
The BVME4000/6000 responds to the following A32 Address Modifiers (AM) codes:
CPU SupervisorProgram Access= $0E
Data Access= $0D
CPU UserProgram Access= $0A
Data Access= $09
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600046
7.10.3 Short I/O (A16) Accesses
The BVME4000/6000 will respond to Short I/O (A16) accesses. The size of the window is fixed at
256bytes. The base address is programmable on 256byte boundaries.
Short I/O space accesses act as a location monitor only and do not access physical memory within the
BVME4000/6000. This space is used to allow 'mail box' interrupts to the processor on the
BVME4000/6000. This allows other bus mas ters to use semaphor e control with the BVME4000/6000
without the use of the VMEbus IRQ lines.
The BVME4000/6000 responds to the following A16 Address Modifiers (AM) codes:
CPU SupervisorData Access= $2D
CPU UserData Access=$29
7.10.4 Controlling The Window Size
The table below shows window sizes for valid combinations of the Mask Register:
Mask RegisterA24 Address Space Window SizeA32 Address Space Window Size
The two Local Base Address registers (A32LBA and A24LBA) contain the base address of the 'dual
mapped' memory window.
For A32 accesses, the unmasked (see A32MSK register description) A32 Local Base Address
(A32LBA) Register bits are used as the most significant address lines during the VMEbus slave
access to the onboard memory. All other local address lines are driven from the VMEbus Address bus.
For A24 accesses, The mos t significant eight local address lines are dr iven by the A32LBA register.
The unmask ed (see A24MSK register description) A24 Local Base Address (A24LBA) Register bits
are used as the next most s ignificant address lines during the VMEbus slave access to the onboard
memory. All other local address lines are driven from the VMEbus Address bus.
Thus for standard (A24) VMEbus accesses bot h the A32LBA and the A24LBA registers need to
be set up.
Copyright 1993,1995,1998,2001 BVM Ltd.
47BVME4000/6000
7.10.6 Address Control Registers
Slave accesses are controlled by eight byte wide registers. All registers are write only.
7.10.6.1 A32VBA - A32 VMEbus Base Address Register
This register contains an 8-bit value, against which extended (A32) VMEbus access es are m atched in
order to determine slave access. If VMEbus A[31..24] matches, then an access to the onboard
memory is performed.
This contains an 8-bit mask that is applied, on a bit by bit basis, to the VMEbus slave address
decoding for A32 (extended) accesses from another VMEbus master. If a bit is set (a 1) then the
corresponding address line is ignored. Thus the contents of this register control the s ize of the window
decoded by the BVME4000/6000 - refer to "7.10.4Controlling The W indow Size (on page 46)" for
more details.
7.10.6.3 A24VBA - A24 VMEbus Base Address Register
This contains an 8-bit value, against which st andard (A24) VMEbus acc esses ar e matc hed in order to
determine slave access. If VMEbus A[23..16] matches, then an access to the onboard memory is
performed.
This contains an 8-bit mask that is applied, on a bit by bit basis, to the VMEbus slave address
decoding for A24 (standard) accesses from another VMEbus master. If a bit is set (a 1) then the
corresponding address line is ignored. Thus the contents of this register control the s ize of the window
decoded by the BVME4000/6000 - refer to "7.10.4Controlling The W indow Size (on page 46)" for
more details.
7.10.6.5 A16VBA - A16 VMEbus Base Address Register
This contains an 8-bit value, against which A16 VMEbus accesses are m atched in order to determ ine
slave access. If VMEbus A[15..8] matches, then a Short I/O access is performed.
7.10.6.6 A32LBA - A32 Local Base Address Register
This contains an 8-bit value that is us ed to drive the onboard most significant address lines during an
access by another VMEbus master. In other words it contains the most significant part of the local
memory base address of the 'dual mapped' window - refer to "7.10.5 Local Addr ess Generation (on
page 46)" for more details.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600048
7.10.6.7 A24LBA - A24 Local Base Address Register
This contains an 8-bit value that is used to drive the onboard next most significant address lines during
an access by another VMEbus master. In other words it contains the next m ost significant part of the
local memory base address of the 'dual mapped' window - refer to "7.10.5 Local Addr ess Generation
(on page 46)" for more details.
7.10.6.8 ADDRCTL - Address Control Register
This contains some miscellaneous control bits, After RESET all bits are CLEAR.
Bit 7:VMELO: Map VMEbus Low.
When CLEAR accesses to the bottom 256Mbytes of the address map are c onfined to local
memory only; accesses to non existent m emory return a bus error. W hen SET accesses to
the bottom 256Mbytes of the address map will be to local memory (or memory module if fitted)
OR to VMEbus A32:D32 address space if there is no local memory at that address.
Bit 6:Reserved.
For future compatibility this must be always written as zero.
Bit 5:SCVME: VMEbus Snoop Control.
This bit enables snooping for VMEbus Slave Acces ses. When SET VMEbus slave accesses
are snooped by the CPU, so that the CPU will sink and source dirty data - refer to "Appendix B
CPU Cache Coherency and Bus Snooping (on page 62)" for a dis cussion on snooping and
cache coherency.
Bit 4:SCETH: Ethernet Snoop Control.
This bit enables snooping for Ethernet Controller Master Accesses. When SET Ethernet
Controller master acc esses are snooped by the CPU, so that the CPU will sink and source
dirty data - refer to "Appendix B CPU Cache Coherency and Bus Snooping (on page 62)" for a
discussion on snooping and cache coherency.
Bit 3:A32EN: VMEbus A32 Slave Access Enable.
When SET VMEbus A32 slave acces s es ar e enabled as spec if ied by the A32VBA, A32MSK &
A32LBA registers. When CLEAR VMEbus A32 slave accesses are disabled.
Bit 2:A24EN: VMEbus A24 Slave Access Enable.
When SET VMEbus A24 slave access es are enabled as specified by the A24VBA, A24MSK,
A24LBA & A32LBA registers. When CLEAR VMEbus A24 slave accesses are disabled.
Bit 1:A16EN: VMEbus A16 Slave Access Enable.
When SET VMEbus A16 slave accesses are enabled as specified by the A16LBA regis ter.
When CLEAR VMEbus A16 slave accesses are disabled.
Bit 0:RAMLO: Map RAM Low.
When SET the SRAM (located at E9000000 and F9000000) is also mapped at 00000000.
This is mainly intended to provide a common address map for systems with no memory
module fitted.
Copyright 1993,1995,1998,2001 BVM Ltd.
49BVME4000/6000
7.11 Configuration Switch
This is a bank of four switches that are available through the front panel. The switches have no
dedicated hardware function. They are provided to allow configuration selection within software
applications. The state of each switch can be read in the Configuration Switch Register.
These bits are unused. When read, their state is undefined.
Bit 3-0: SW1, SW2, SW3, SW4.
Reflects the state of each numbered switch. When the switch is ON (lower position) the
associated bit is read as ZERO. When switch is OFF (upper position) the associated bit is
read as ONE.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600050
7.12 Real Time Clock/Timers
7.12.1 Overview
The Real Time Clock and Timer f ac ilities on the BVME4000/6000 ar e provided by the DP8570A Timer
Clock Peripheral, which provides two 16-bit tim er/counters , calendar/cloc k, a f lexible interrupt s chem e
and 44 bytes of non-volatile RAM.
Two independent, multi-mode, 16 bit tim ers are provided. Thes e timers oper ate in four m odes. Each
has its own prescaler and can select any of 8 possible c lock sourc es. T hus, by program m ing the input
clocks and the timer counter values a very wide range of time duration's can be achieved. The range
is from 200nS (8MHz external clock) to 65,535 seconds (18hrs., 12min.).
A very flexible and powerful on-chip interrupt structure is provided. Three basic types of interrupts are
available: Periodic (from 1mS to 1 m inute), Alarm /Com par e (fr om the RT C) and T imer . Interrupt m as k
and status registers enable the masking and easy determination of each interrupt.
For full programm ing details, refer to the DP8570A docum entation detailed in the "A.5 DP8570A (on
page 60)" section of this manual.
7.12.2 Hardware Specific Considerations
INTR pin Configuration
The INTR pin is fed to the Interrupt Controller - refer to "7.8 Interrupt Controller (on page 35)"
for more details. It m ust be programm ed as an active low, push-pull output. This is set up in
the OUTPUT MODE REGISTER by programming bit 2 (INTR Active Hi/Low) CLEAR and bit 3
(INTR Push-pull/Open Drain) SET.
T1 pin Configuration
The T1 pin (tim er 1 output) is f ed to the T IN pin of the PI/T (MC68230) - ref er to "7.13 Parallel
Port/Timer (on page 52) " for mor e details. It must be programm ed as a push-pull output. The
output may be programmed as active high or low as the application requir es. T his is set up in
the OUTPUT MODE REGISTER by programming bit 1 (T1 Push-pull/Open Drain) SET.
MFO pin Configuration
The MFO pin is not currently connected on the BVME4000/6000.
RTC Crystal Oscillator Frequency
The BVME4000/6000 uses a 32.768 kHz crystal. This pr ovides lowest power dissipation. The
DP8570A needs to be programmed with the oscillator f requency used. This is set up in the
REAL TIME MODE REGISTER by programming bits 7&6 (XT1 and XT0) both CLEAR.
TCK - External Timer Clock Input
TCK is driven from a fixed 8 MHz clock source.
PFAIL - Power Fail Input
This input is driven from the MAX791 power fail signal.
G0 & G1 - Timer Gate Inputs
These pins are pulled low on the BVME4000/6000.
Copyright 1993,1995,1998,2001 BVM Ltd.
51BVME4000/6000
7.12.3 Programming
The register map of the DP8570A is shown below. The register map consists of two 31 byte pages
with a main status register that is common to both pages. A control bit (bit 7) in the Main Status
Register is used to select either page. Page 0 contains all the clock and timer functions, while page 1
has non-volatile RAM.
Page 0 is further sub-divided to provide two blocks of control registers. Again a bit in the Main Status
Register (bit 6) is used to select either register block.
The registers are all byte wide mapped on the least significant byte of long word boundaries.
AddressPage Select = 1Page Select = 0
Register Select = 1Register Select = 0
FF900003Main Status Register
FF900007RAMReal Time ModeTimer 0 Control
FF90000BRAMOutput ModeTimer 1 Control
FF90000FRAMInterrupt Control 0Periodic Flag
FF900013RAMInterrupt Control 1Interrupt Routing
FF900017RAM
FF90001BRAM Seconds Clock Counter
FF90001FRAM Minutes Clock Counter
FF900023RAM Hours Clock Counter
FF900027RAMDay of Month Clock Counter
FF90002BRAM Months Clock Counter
FF90002FRAM Years Clock Counter
FF900033RAM Units Julian Clock Counter
FF900037RAM100s Julian Clock Counter
FF90003BRAM Day of Week Clock Counter
FF90003FRAM Timer 0 LSB
FF900043RAM Timer 0 MSB
FF900047RAMTimer 1 LSB
FF90004BRAMTimer 1 MSB
FF90004FRAMSeconds Compare RAM
FF900053RAMMinutes Compare RAM
FF900057RAMHours Compare RAM
FF90005BRAMDay of Month Compare RAM
FF90005FRAMMonths Compare RAM
FF900063RAMDay of Week Compare RAM
FF900067RAMSeconds Time Save RAM
FF90006BRAMMinutes Time Save RAM
FF90006FRAMHours Time Save RAM
FF900073RAMDay of Month Time Save RAM
FF900077RAMMonths Time Save RAM
FF90007BRAMRAM
FF90007FRAMRAM/TEST
1
/
Second Counter
100
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600052
7.13 Parallel Port/Timer
7.13.1 Overview
The Parallel Interface/Tim er (PI/T) is based on the MC68230. T his block provides a bi-directional, 8bit, double-buffered, Centronics com patible parallel Interface. This interfac e is electrically buffered to
provide 48mA of drive. Connection can be m ade via the front panel connector JP3 or via a paddle
board connected to the backplane P2.
The PI/T provides internal Board Contr ol Register func tions to control SCC c lock s election, Watchdog
refresh and VMEbus Arbitration Selection.
The PI/T contains an independent, 24-bit timer with a 5-bit presc aler. The timer m ay be clocked from
the PI/T clock pin or from the T1 output pin of the RTC Timer 1 - refer to "7.12 Real Time
Clock/Tim ers (on page 50)" for more details. It can generate periodic interrupts or a s ingle interrupt
after programm ed time period. T he CLK pin is driven from CPUCLK divided by 4, thus with a 25MHz
bus clock, the PI/T CLK is driven at 6.25MHz.
For full programming details, ref er to the MC68230 documentation detailed in the "A.7 MC68230 (on
page 60)" section of this manual.
7.13.2 Port A Usage
The MC68230 port A is available for use as an 8-bit parallel I/O port. It is buffered using a bidirectional transceiver to give 48mA of dr ive. The direction control of the transceiver is via port C refer to "7.13.4 Port C Usage (on page 54)" for more details. Any of the port A sub-m odes may be
used. However, because the port is connected to an 8-bit wide transceiver, ALL the bits must be
programmed to be in the same direction; all inputs or all outputs. The direction programmed must
match that of the transceiver set up via port C.
7.13.3 Port B Usage
The MC68230 port B is dedicated as an internal Board Control Register. This port needs to be
configured for simple pin I/O. Theref ore the MC68230 m ust be conf igured for Port Mode 0. This is s et
up in the PORT GENERAL CONTROL REGISTER by program ming bits 7 & 6 both CLEAR. Port B
must be configured to Sub Mode 1X. This is set up in the PORT B CONTROL REGISTER by
programming bit 7 SET.
D7D6D5D4D3D2D1D0
OUTOUTOUTOUTOUTIN/OUTOUTOUT
/RRS/SYSCONRQLVL1RQLVL0SCLSDASCLKASCLKB
Bit 7:/RRS: Round Robin Select.
This must be programmed as an output pin. This bit controls the VMEbus arbitration
mechanism used by the BVME4000/6000 when enabled as a System Controller. When the bit
is SET straight prioritised (PRI) or single level (SGL) is used. When CLEAR Round Robin
Select (RRS) is used. See Section 3 of the VMEbus Specification for a full description - refer
to "A.8 VMEbus (on page 60)" for details of this documentation.
Bit 6:/SYSCON: System Controller Function Enable.
This must be pr ogramm ed as an output pin. This bit controls whether the BVME4000/6000 is
the VMEbus System Controller unless overridden by the System Controller Link - refer to
"5.2.12 LK22 VMEbus System Controller Enable (on page 17)" for more details. When
programmed as the VMEbus System Controller, the BVME4000/6000 performs as the
VMEbus arbiter, it drives VMEbus SYSCLK and VMEbus BCLR. When the bit is SET the
BVME4000/6000 is NOT the System controller. When CLEAR the BVME4000/6000 is the
VMEbus System Controller.
Copyright 1993,1995,1998,2001 BVM Ltd.
53BVME4000/6000
Bit 5,4: RQLVL1,RQLVL0: VMEbus Request Level Selec tion.
These must be programm ed as output pins. The BVME4000/6000 can request m astership of
the VMEbus on any of the four VMEbus request levels. These two bits select which level
VMEbus requests are made upon:
RQLVL1RQLVL0VMEbus Request Level
00Requests on level 0
01Requests on level 1
10Requests on level 2
11Requests on level 3
Bit 3:SCL: Serial Clock Line.
This must be programmed as an output pin. This bit controls the I
2
C Clock Line, used for
clocking data in and out of the NM24C02 EEPROM. When the bit is SET the clock line is
HIGH, when the bit is CLEAR the clock line is LOW. For f ull program m ing details, refer to the
NM24C02 documentation detailed in the "A.11 NMC24C02 (on page 61)" section of this
manual.
Bit 2:SDA: Serial Data Line.
This is the I
2
C Data Line, used for reading the data to/from the NM24C02 EEPROM. When
the set as an output pin, the data will be OUTPUT to the EEPROM, when s et as an input pin,
the data will be INPUT from the EEPRO M. The bit sets the data to the EEPROM in output
mode, and reflects the data from the EEPROM in input m ode. For full programm ing details,
refer to the NM24C02 documentation detailed in the "A.11 NMC24C02 (on page 61)" section
of this manual.
Bit 1:SCLKA: Serial Communications Controller Clock Select for Channel A.
This must be program med as an output pin. T his bit controls which clock sour ce is applied to
the RTxCA pin of the SCC. Refer to "7.14 Ser ial Communications Controller (on page 56)" for
details of Baud Rate generation for Serial channels. The clock source can be selected
between an onboard crystal and an external clock from the P2 connector.
SCLKA ValueClock Applied to RTxCA
0Onboard Crystal - 7.3728 MHz
1SCLKINA signal from P2 (pin 4c)
Bit 0:SCLKB: Serial Communications Controller Clock S elect for Channel B.
This must be program med as an output pin. T his bit controls which clock sour ce is applied to
the RTxCB pin of the SCC. . Refer to "7.14Ser ial Communications Controller (on page 56)"
for details of Baud Rate generation for Serial channels. The clock source can be selected
between an onboard crystal and an external clock from the P2 connector.
SCLKB ValueClock Applied to RTxCB
0Onboard Crystal - 7.3728 MHz
1SCLKINB signal from P2 (pin 8c)
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600054
7.13.4 Port C Usage
The MC68230 port C is nominally an 8 bit general purpose I/O port ( similar to Ports A & B). However
five of the pins carry special functions associated with interrupts and timer operation.
The PORT SERVICE REQUEST REGISTER s hould be set up to us e vec tor ed interr upts on PIRQ and
PIACK. Thus bits 4 & 3 should be set as: Bit 4 SET, Bit 3 SET. T he PORT INTERRUPT VECT OR
REGISTER should be set up with the required Interrupt vector.
The TIMER CONTRO L REGISTER should be s et up to use vectored inter rupts on T OUT and T IACK.
Thus bits 7 & 6 should be set as: Bit 7 SET , Bit 6 CLEAR. Bit 5 should be used as an interr upt enable
bit. The TIMER INTERRUPT VECTOR REGISTER should be set up with the required Interrupt vector.
The Interrupt Controller assumes that the MC68230 Timer Interrupter supports vectored
interrupts. This pin is connected to the Interrupt Controller's TIMIACK line.
Bit 6:/PIACK: Parallel Port Interrupt Acknowledge.
The Interrupt Controller assumes that the MC68230 Parallel Interrupter supports vectored
interrupts. This pin is connected to the Interrupt Controller's PARIACK line.
Bit 5:/PIRQ: Parallel Port Interrupt Request.
This output drives the 68230 Parallel Interrupt input to the Inter rupt Controller - refer to "7.8
Interrupt Controller (on page 35)" for more details.
Bit 4:WDOG: WatchDog Refresh.
This bit drives the input to the watchdog circuit. When this bit is configured as an INPUT , the
watchdog function is disabled. When c onf igured as an O UT PUT, the watchdog is enabled and
this bit must be toggled every second if a Watchdog time out is to be avoided. If the WDOG bit
is not toggled within the time out period (1 second m inimum) then a hardware reset will be
generated.
Bit 3:TOUT: Timer Output.
This output drives the 68230 Timer Interrupt input to the Interrupt Controller - refer "7.8
Interrupt Controller (on page 35)" for more details.
Bit 2:TIN: Timer Input.
This input is driven from the T1 output of the DP8570A - refer to "7.12 Real Time
Clock/Timers (on page 50)" for more details.
Bit 1:PADIR: Port A Direction.
This OUTPUT controls the DIRECTION of the transceiver. When SET the transceiver will
drive OUT from the BVME4000/6000 to the connector. When CLEAR the transceiver will
receive IN from the connector and drive into Port A.
Bit 0:PAEN: Port A Enable.
This OUTPUT controls the ENABLE to the tr ansceiver. When SET the tr ansceiver is disabled
and its outputs are hi-impedance. When CLEAR the transceiver is enabled and will drive in the
direction controlled by its DIRECTION input.
Copyright 1993,1995,1998,2001 BVM Ltd.
55BVME4000/6000
7.13.5 Handshake Pin Usage
H1:This must be configured as an input. It is connected to /PACKNOW signal via an inverting
buffer.
H2:T his must be configured as an output. It is connected to /PSTROBE signal via an inverting
buffer.
H3:This must be configured as an input. It is connected to PBUSY signal via an inverting buffer.
H4:This signal is currently not connected on the BVME4000/6000.
7.13.6 MC68230 PI/T Registers
The register map of the MC68230 is shown below. The register map consists of a bank of 32 byte
wide registers (of which som e are undefined). The registers are mapped on the least significant byte
of long words.
AddressRegisterAccessAffected by
Reset
FFA00003Port General Control RegisterR/WYesNo
FFA00007Port Service Request RegisterR/WYesNo
FFA0000BPort A Data Direction RegisterR/WYesNo
FFA0000FPort B Data Direction RegisterR/WYesNo
FFA00013Port C Data Direction RegisterR/WYesNo
FFA00017Port Interrupt Vector RegisterR/WYesNo
FFA0001BPort A Control RegisterR/WYesNo
FFA0001FPort B Control RegisterR/WYesNo
FFA00023Port A Data RegisterR/WNoYes
FFA00027Port B Data RegisterR/WNoYes
FFA0002BPort A Alternate RegisterRNoNo
FFA0002FPort B Alternate RegisterRNoNo
FFA00033Port C Data RegisterR/WNoNo
FFA00037Port Status RegisterR/WYesNo
FFA0003BReserved
FFA0003FReserved
FFA00043Timer Control RegisterR/WYesNo
FFA00047Timer Interrupt Vector RegisterR/WYesNo
FFA0004BReserved
FFA0004FCounter Preload Register HighR/WNoNo
FFA00053Counter Preload Register MiddleR/WNoNo
FFA00057Counter Preload Register LowR/WNoNo
FFA0005BReserved
FFA0005FCounter Register HighRNoNo
FFA00063Counter Register MiddleRNoNo
FFA00067Counter Register LowRNoNo
FFA0006BTimer Status RegisterR/WYesNo
FFA0006FReserved
Affected by
Access
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600056
7.14 Serial Communications Controller
7.14.1 Overview
The Serial Comm unications Controller (SCC) resource is based on the Z85230. This bloc k provides
two independent, full-duplex serial communication channels. Both channels handle asynchronous,
byte synchronous and bit synchronous protocols. Each channel has its own baud rate generator,
clocked from a variety of sources, including a Digital Phase Locked Loop (DPLL).
Each channel can be independently electrically buffered as RS232, RS422 or RS485. Connection can
be made via the front panel connectors JP1 and JP2 or via a paddle board connected via the P2
connector.
For full programm ing details, ref er to the Z85230 docum entation detailed in the "A.6 Z85230 (on page
60)" section of this manual.
7.14.2 Serial Clock Sources
PCLK This is the master Z85230 c lock pin. It is used to synchronise all internal signals. It is available
as a clock source to the baud rate generator. The BVME4000/6000 dr ives this signal with the
processor clock divided by 2. Thus with a 25MHz bus clock, the Z85230 is clocked at
12.5MHz. Because this pin is CPU clock dependent it is recom mended that it is not used f or
baud rate generation.
RTxCA This input pin can be programmed to supply any combination of: the receive clock, the
transmit clock, the baud rate generator and the DPLL. T he BVME4000/6000 drives this signal
from a multiplexer contr olled by the SCLKA bit of the BOARD CONTROL REGISTER. Refer
to "7.13 Parallel Port/Timer (on page 52)" for more details of this register. The clock sourc e
can be selected between an onboard 7.3728MHz crystal and an external clock from P2
Connector.
SCLKA ValueClock Applied to RTxCA
0Onboard Crystal - 7.3728 MHz
1SCLKINA signal from P2 (pin 4c)
RTxCB This input pin can be programmed to supply any combination of: the receive clock, the
transmit clock, the baud rate generator and the DPLL. T he BVME4000/6000 drives this signal
from a multiplexer contr olled by the SCLKB bit of the BOARD CONTROL REG ISTER. Refe r
to "7.13 Parallel Port/Timer (on page 52)" for more details of this register. The clock sourc e
can be selected between an onboard 7.3728MHz crystal and an external clock from P2
Connector.
SCLKB ValueClock Applied to RTxCB
0Onboard Crystal - 7.3728 MHz
1SCLKINB signal from P2 (pin 8c)
TRxCA This pin is connected to the SCLKOUTA signal on P2 pin 4a. It can be programmed to be
either an input or an output. When programmed as an input, a clock source is received and
can then supply the clock to the receiver and/or the transmitter. When programmed as an
output, it can supply a clock from; the RTxCA pin, the RxDPLL or the baud rate generator.
TRxCB This pin is connected to the SCLKOUTB signal on P2 pin 8a. It can be programmed to be
either an input or an output. When programmed as an input, a clock source is received and
can then supply the clock to the receiver and/or the transmitter. When programmed as an
output, it can supply a clock from; the RTxCB pin, the RxDPLL or the baud rate generator.
Copyright 1993,1995,1998,2001 BVM Ltd.
57BVME4000/6000
7.14.3 Programming
Each channel has a data register, when it is read, the receiver FIFO is read. W hen it is written, the
transmitter FIFO is written.
Each channel also has a number of W rite Registers and Read Registers that are used to control the
operation of the channel. These are generally accessed as a two step procedure. First the regis ter to
be accessed is written to the Control Register, then the next acc ess to the Control Register ac cesses
the referenced Read or Write Register.
AddressRegister Access
FFB00003Control Register - Channel B (JP2)
FFB00007Data Register - Channel B (JP2)
FFB0000BControl Register - Channel A (JP1)
FFB0000FData Register - Channel A (JP1)
The BVME4000/6000 supports vectored interr upts fr om the SCC - ref er to "7.8 Interr upt Controller (on
page 35)" for more details.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600058
8. Specifications
8.1 On-Board Functions
BVME4000: MC68040, MC68LC040 or MC68EC040 CPU at 25MHz/33MHz.
BVME6000: MC68060, MC68LC060 or MC68EC060 CPU at 50MHz/66MHz (25MHz/33MHz bus).
Z85230 Dual Serial interface controller, 7.3728MHz or external clock source,
RS232 buffers (RS422 & RS485 options), front panel and P2 connections.
DP8570A Timer Clock Peripheral (calendar-clock, 3 timers, 44 byte NVR).
MC68230 Parallel Interface/Timer, front panel and P2 printer connections.
NCR53C710-1 DMA SCSI Controller, header and P2 connections.
85296CA DMA Ethernet/Cheapernet Controller,
Front panel BNC Cheapernet and P2 AUI connections (RJ45 10BaseT option).
MAX791 Watchdog: refresh period = 1000mS (when enabled).
2 x 32-pin CPU PROM sockets, 16-bit wide, accept 512Kbit to 8Mbit EPROM's, 4Mbit FLASH,
(90ns @ 25MHz bus, 120ns @ 33MHz bus).
512K/2Mbytes CMOS SRAM, 32-bit wide, battery backed (up to 7 days or 2.5 years).
32-bit wide memory module interface with burst-fill up to 2/1/1/1.
2Kbit serial access EEPROM.
LOCAL BUS TIMEOUT period 64 CPU clocks (2.56µS @ 25MHz bus clock).
RED LED indicates VMEbus MASTER access.
GREEN LED indicates processor status.
Interrupt handler D08(O): I(1-7) all levels, software maskable.
8.6 IP Functions
Two IP compatible sites:
2 x Single IPs (16-bit) or 1 x Double IP (32-bit);
8MHz, 32MHz or CPU synchronous IP clocks, software selectable;
Software programmable IP interrupts;
Front panel IP I/O connections.
IP expansion connector:
Supports up to four additional IP compatible sites.
NATIONAL SEMICONDUCTOR DP8570A Timer Counter Peripheral (TCP) Data Sheet (May 1993,
TL/F/8638).
A.6 Z85230 User's Manual
ZILOG SCC User's Manual (Q4/1992).
A.7 MC68230 Data Sheet
MOTOROLA MC68230 PARALLEL INTERFACE/TIMER (PI/T) Data Sheet (Dec 1983).
A.8 VMEbus Specification
THE VMEbus SPECIFICATION (Sept 1987, VITA).
A.9 RS422/485 Interface Module User's Manual
BVM 453-62370/62371 RS422/RS485 INTERFACE MODULE User's Manual (BVM part num ber: 454-
68370).
A.10 AM29F040 Data Book
AMD Flash Memory Products Data Book/Handbook 1996.
Copyright 1993,1995,1998,2001 BVM Ltd.
61BVME4000/6000
A.11 NMC24C02 Data Sheet
NATIONAL SEMICONDUCTOR NMC24Cxx – Standard 2-W ire Bus Inter face Serial EEPROM Fam ily
(May 1996).
A.12 MEM390 Memory Module User's Manual
MEM390 4/8 Mbyte DRAM MEMORY MODULE User's Manual (BVM part number: 454-68391).
A.13 MEM400 Memory Module User's Manual
MEM400 16Mbytes DRAM 4/8 Mbytes FLASH MEMORY MODULE User's Manual (BVM part number:
454-61400).
A.14 MEM480 Memory Module User's Guide
MEM480 16/32/48Mbytes DRAM MEMORY MODULE User's Guide (BVM part number: 454-61480).
A.15 MEM4SD Memory Module User's Guide
MEM4SD 16 to 512Mbytes SDRAM MEMORY MODULE User's Guide (BVM part number: 454-
61490).
A.16 EXP100 Quad IP Expansion User's Manual
EXP100 Quad IP Expansion User's Manual (BVM part number: 454-44100).
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600062
Appendix B CPU Cache Coherency and Bus Snooping
B.1 BVME4000 (MC68040)
The MC68040 is a third generation 68000 series processor with separate data and instruction c aches
of 4Kbytes each. The cache unit supports full copyback cac hing, in addition to write-through caching
(as available on earlier processors), cache inhibited, and bus-serialised cache modes.
Copyback caching means that when data is written out by the program, it m ay only reach the cache,
and not the main memory. This poses cache coherency problems over those nor m ally associated with
earlier 68000 series processor s (e.g. 68030), as the main memory can contain s tale data, affecting
DMA operations transferring data from dual-ported memory as well as to
Bus serialisation is required as the 68040's internal architecture has a high degree of parallelism.
Reads and writes do not occur in the order in which they are defined by the programmer. Normally this
causes no problem as the 68040 will detect any clashes and synchronise them, but if access es are
being made to I/O areas for example, the ordering of reads and writes are very important. Bus
serialised regions cause correct ordering of the reads and writes.
It follows on from the above that it is im portant to be able to define regions of the addres s space as
operating in different caching modes. This isn't strictly a caching issue, but is very relevant to the
operation of system and user software.
dual ported memory.
Use is made of the 68040's "Transparent T rans lation Regis ter s" and MMU "Page Tables" to define the
caching mode for different regions of the address space. The 68LC040 also has an MMU, and
functions exactly the same way as a 68040 in this respect. O n the 68EC040 however, although the
MMU is not available, the Transparent Tr anslation Regist ers are s till present, and can be us ed f or this
function, although the strategy needs to be slightly different.
The 68040's Transparent Translation Registers contain an address and mask f ield to allow definition
of an address range to be used. They also contain fields to specif y the relevant caching m odes for the
defined region. There are four regis ters, two for data DTT0 and DTT1 and two for instructions ITT0
and ITT1.
The TT0 registers override the TT1 registers if there is any overlap, and undefined regions will be
accessed in the 68040's default mode (write-through caching enabled) if the MMU is disabled. If the
MMU is enabled (not on 68EC040) any regions undefined in the TT regis ters will be checked in the
Page Tables. The Page Tables relate to a 4 or 8KByte region, and the caching mode is specified in a
field of the page descriptor in a similar way to the TT registers.
On the BVME4000 with a 68040 or 68LC040 processor, a c ache-inhibited, bus-serialised region can
be defined from $F0000000 to $FFFFFFFF for access to IP Memory, EPROM, SRAM, VMEbus A24,
VMEbus A16 & on-board registers for supervisor access. The rest of the address space is defined as
write-through caching for instructions and copy-back caching f or data for supervisor m ode. The page
descriptors would be used to define the regions f or us er-s tate acces ses, alloc ated on a dynamic basis
(by operating system software). The values that need to be set into the 68040 TT registers to
implement this scheme are as follows:
DTT0 = $F00FA040, DTT1 = $00FFA020, ITT0 = NOT USED, ITT1 = $00FFA000
On the BVME4000 with a 68EC040 processor, a similar scheme as that for the 68040/68LC040 can
be set up. This gives an I/O region from $F0000000 to $FFFFFFFF for supervisor and user-state
access, with the rest of the address space defined as write-through caching for instructions and
copyback caching for data for s upervisor and user-state access . The values that need to be s et into
the 68EC040 TT registers to implement this scheme are as follows:
DTT0 = $F00FC040, DTT1 = $00FFC020,ITT0 = NOT USED, ITT1=$00FFC000
Copyright 1993,1995,1998,2001 BVM Ltd.
63BVME4000/6000
Note that instruction caching only functions in write-through mode, not copy-back m ode, as no writes
occur to the instruction address space. To use write-through cac hing in place of copyback, the "$20"
should be replaced by a "$00" in the above values for DTT1.
The DTT1 and IT T1 values could be changed to introduce a third region of write-through caching in
addition to copy-back caching as follows for the 68EC040:
DTT1 = $000FC020, ITT1 = $000FC000
Now the on-board RAM is defined as copy-back caching from $00000000 to $0FFFFFFF and the
region from $10000000 to $EFFFFFFF is defined as write-through caching (the 68EC040's default). A
similar mechanism may be used via the page descriptors when the MMU is used in the 68040 or
68LC040.
It is useful to have different regions def ined for the sam e address space, becaus e as the BVME4000
dual-maps some of the address space, it can be accessed in diff erent caching modes. If the above
scheme was adopted, then the VMEbus A24 space could be accessed at address $EE000000 as
write-through cached, and at address $FE000000 as cache-inhibited bus-serialised access.
The BVME4000 has three separate blocks capable of bus mas tership ( DMA) other than the pr ocess or
itself: the Ethernet Controller, SCSI Controller and the VMEbus Slave Inter face. When any of these
bus masters transfer data directly into a memory region (DMA), c ache coher ency problems c an occ ur,
as the processor may not know that data in it's internal caches is now invalid.
This problem can be approached in a number ways:
1.Normally main system memory resides on the BVME4000, and the 68040 can use "bussnooping" to monitor accesses to the memory by any of the other bus masters. The bussnooping must be enabled by programm ing the relevant bus-snoop enable bit(s) for the bus
master in question. For the Ethernet Controller and VMEbus Slave Interface, there is a
SNOOP ENABLE bit - refer to "7.10VMEbus Slave Access Controller (on page 45) " for m ore
details. For the SCSI Controller, there are SNOOP MODE bits in it's register set - ref er to the
53C710 documentation detailed in the "A.453C710 Data Manual & Programmers Guide (on
page 60)" section of this manual.
2.The 68040's internal caches can be "flushed" if it is known that their data m ay be invalid (e.g.
when an interrupt occurs after a DMA operation). It m ay also be necessary to do a "cache
push" if copyback caching is in us e. This can be very wasteful, as data not involved in the
transfers at all will also be purged from the caches.
3.Non-cached regions can be used to acc ess the memory. For example, the Ethernet Controller
can be set-up to DMA into a separate buffer region (e.g. the SRAM), which is acc essed via a
non-cached address. In this cas e, bus-snooping is not required, but the data, once DMAed
into memory, is not subject to the advantages of caching. This does also have a potential
performance advantage, as there is a tim ing overhead involved in bus-snooping by the 68040
processor.
Other schemes may be determined by the user, or a combination of the above may be used in
conjunction.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600064
B.2 BVME6000 (MC68060)
The MC68060 is a superscaler 68000 s eries processor with separate data and instruction caches of
8Kbytes each. The cache unit supports full copyback caching, in addition to write-through caching (as
available on earlier processors), cache-inhibited imprecise-mode and precise-mode (bus-serialised)
cache modes.
Copyback caching means that when data is written out by the program, it m ay only reach the cache,
and not the main memory. This poses cache coherency problems over those nor m ally associated with
earlier 68000 series processor s (e.g. 68030), as the main memory can contain s tale data, affecting
DMA operations transferring data from dual-ported memory as well as to
Cache-inhibited precise-mode is required as the 68060's internal architecture has a high degree of
parallelism. Reads and writes do not occ ur in the order in which they are defined by the programm er.
Normally this causes no problem as the 68060 will detect any clashes and synchronise them, but if
accesses are being made to I/O areas for example, the ordering of reads and writes are very
important. Cache-inhibited precise-mode regions cause correct ordering of the reads and writes.
It follows on from the above that it is im portant to be able to define regions of the addres s space as
operating in different caching modes. This isn't strictly a caching issue, but is very relevant to the
operation of system and user software.
dual ported memory.
Use is made of the 68060's "Transparent T rans lation Regis ter s" and MMU "Page Tables" to define the
caching mode for different regions of the address space. The 68LC060 also has an MMU, and
functions exactly the same way as a 68060 in this respect. O n the 68EC060 however, although the
MMU is not available, the Transparent Tr anslation Regist ers are s till present, and can be us ed f or this
function, although the strategy needs to be slightly different.
The 68060's Transparent Translation Registers contain an address and mask f ield to allow definition
of an address range to be used. They also contain fields to specif y the relevant caching m odes for the
defined region. There are four regis ters, two for data DTT0 and DTT1 and two for instructions ITT0
and ITT1.
The TT0 registers override the TT1 registers if there is any overlap, and undefined regions will be
accessed in the 68060's default m ode set in the "Translation Control Register" T CR (normally writethrough caching enabled) if the MMU is disabled. If the MMU is enabled (not on 68EC060) any regions
undefined in the TT registers will be check ed in the Page Tables. The Page Tables relate to a 4 or
8KByte region, and the caching mode is specified in a field of the page des criptor in a similar way to
the TT registers.
On the BVME6000 with a 68060 or 68LC060 processor, a cache-inhibited, prec ise-mode region can
be defined from $F0000000 to $FFFFFFFF for access to IP Memory, EPROM, SRAM, VMEbus A24,
VMEbus A16 & on-board registers for supervisor access. The rest of the address space is defined as
write-through caching for instructions and supervisor data access. The page descriptors would be
used to define the regions for user -s tate ac c ess es inc luding copyback r egions, alloc ated on a dynamic
basis (by operating system software). The values that need to be set into the 68060 T T registers to
implement this scheme are as follows:
DTT0 = $F00FA040, DTT1 = $00FFA000, ITT0 = NOT USED, ITT1 = $00FFA000
On the BVME6000 with a 68EC060 processor, a similar scheme as that for the 68060/68LC060 can
be set up. This gives an I/O region from $F0000000 to $FFFFFFFF for supervisor and user-state
access, with the rest of the address space defined as write-through caching for instructions and
supervisor data, and copyback caching for us er-state data ac cess . T he values that need to be set into
the 68EC060 TT registers to implement this scheme are as follows:
DTT0 = $F00FC040, DTT1 = $00FFC020,ITT0 = NOT USED, ITT1=$00FFC000
Copyright 1993,1995,1998,2001 BVM Ltd.
65BVME4000/6000
Note that instruction caching only functions in write-through mode, not copy-back m ode, as no writes
occur to the instruction address space. To use write-through cac hing in place of copyback, the "$20"
should be replaced by a "$00" in the above values for DTT1.
The DTT1 and IT T1 values could be changed to introduce a third region of write-through caching in
addition to copy-back caching as follows for the 68EC060:
DTT1 = $000FC020, ITT1 = $000FC000
Now the on-board RAM is defined as copy-back caching from $00000000 to $0FFFFFFF and the
region from $10000000 to $EFFFFFFF is defined as default caching set in the TCR (norm ally writethrough caching enabled). A similar m echanism m ay be used via the page descr iptors when the MMU
is used in the 68060 or 68LC060.
It is useful to have different regions def ined for the sam e address space, becaus e as the BVME6000
dual-maps some of the address space, it can be accessed in diff erent caching modes. If the above
scheme was adopted, then the VMEbus A24 space could be accessed at address $EE000000 as
write-through cached, and at address $FE000000 as cache-inhibited precise-mode access.
The BVME6000 has three separate blocks capable of bus mas tership ( DMA) other than the pr ocess or
itself: the Ethernet Controller, SCSI Controller and the VMEbus Slave Inter face. When any of these
bus masters transfer data directly into a memory region (DMA), c ache coher ency problems c an occ ur,
as the processor may not know that data in it's internal caches is now invalid.
This problem can be approached in a number ways:
1.Normally main system memory resides on the BVME6000, and the 68060 can use "bussnooping" to monitor accesses to the memory by any of the other bus masters. The bussnooping must be enabled by programm ing the relevant bus-snoop enable bit(s) for the bus
master in question. For the Ethernet Controller and VMEbus Slave Interface, there is a
SNOOP ENABLE bit - refer "7.10 VMEbus Slave Access Controller (on page 45)" for more
details. For the SCSI Controller, there is the SC0 SNOOP MODE bit in it's register s et - refer
to the 53C710 documentation detailed in the "A.4 53C710 Data Manual & Programmers Guide
(on page 60)" section of this manual. The m em or y must be acc essed in write- through cac hing
mode as the 68060 can only invalidate cache entries, unlike the 68040 which can source and
sink data from/to the cache. This means that supervisor accesses (i.e. operating system
software) are write-through, whereas user-state accesses would normally be copyback.
2.The 68060's internal caches can be "flushed" if it is known that their data m ay be invalid (e.g.
when an interrupt occurs after a DMA operation). It m ay also be necessary to do a "cache
push" if copyback caching is in us e. This can be very wasteful, as data not involved in the
transfers at all will also be purged from the caches.
3.Non-cached regions can be used to acc ess the memory. For example, the Ethernet Controller
can be set-up to DMA into a separate buffer region (e.g. the SRAM), which is acc essed via a
non-cached address. In this cas e, bus-snooping is not required, but the data, once DMAed
into memory, is not subject to the advantages of caching. This does also have a potential
performance advantage, as there is a tim ing overhead involved in bus-snooping by the 68060
processor.
Other schemes may be determined by the user, or a combination of the above may be used in
conjunction.
9A23A9SIZ1Transfer9D8
10A22D10SIZ0Size #10D9D
11A21D11GNDGround11D10A
12A20R12/TSTransf er S tart #12D11T
13A19E13/TIPTrans. In Prog. #13D12A
14A18S14/LOCKLocked (RMW) #14D13
15A17S15+5V5 Volt Power15D14L
16A1616/TATransfer Ac k. #16D15I
17A15L17SC1Snoop17D16N
18A14I18SC0Control #18D17E
19A13N19GNDGround19D18S
20A12E20CLKCPU Clock #20D19
21A11S21GNDGround21D20#
22A1022/MIRQModule IRQ22D21
23A9#23/ MIMemory Inhibit #23D22
24A824+5V5 Volt Power24D23
25A725GNDGround25D24
26A626CLK2CPU Clock2 #26D25
27A527GNDGround27D26
28A428MERRModule Error28D27
29A329N/CNo Connect29D28
30A230GNDGround30D29
31A131+5VSB5V Standby Power31D30
32A032+12V12 Volt Power32D31
NOTES:This allows connection to a BVM Memory Module. # indicates a direct connection to the
equivalent processor signal, see the MC68040 and MC68060 m anual or data sheet f or an
explanation. /RST is a general reset signal, /MIRQ is an interrupt signal fr om the m odule,
and MERR is a bus error signal from the module. The 12 volt power connection is not
switched, and is intended for FLASH memory programming on those modules that
support it. The 5 volt standby power supply is connected directly to the VMEbus +5STDBY
line, and is intended for non-volatile SRAM backup on those modules that support it.
The interface is not intended f or us er connec tion, the pinout is provided her e f or r ef erenc e
only.
Some mem ory modules pr ovide a JT AG progr am m ing strip to allow direc t progr am m ing f rom the hos t
module. This connec tor detail is k nown as M4, the connections are s hown below, and are for factory
NOTES:This allows connection to a BVM IP Expansion Daughter Board (e.g. EXP100). The
BVME4000/6000 architecture provides for a further 6 IP sites to be added via this
extension interface. The interface allows full capability sites to be added including Interrupt
Control, 32-bit operation 8MHz, 32MHz and CPU Synchronous speeds.
The interface is not intended f or us er connec tion, the pinout is provided her e f or r ef erenc e
only.
Copyright 1993,1995,1998,2001 BVM Ltd.
BVME4000/600068
Appendix E Thermal Management
BVME4000
25MHz
MC68EC/LC040
33MHz
MC68EC/LC040
25MHz
MC68040
33MHz
MC68040
BVME6000
50MHz
MC68EC/LC060
66MHz
MC68EC/LC060
50MHz
MC68060
66MHz
MC68060
NOTES:Temperatures shown above are for ambient air temperature.
If operation above 50 °C for extended periods is antic ipated, then it is recomm ended that
the airflow is doubled, or (where not already specified) a heatsink is fitted.
25 °C50 °C70 °C
No Heatsink
No Airflow
No Heatsink
No Airflow
No Heatsink
No Airflow
No Heatsink
Natural Airflow
25 °C50 °C70 °C
No Heatsink
No Airflow
No Heatsink
No Airflow
No Heatsink
No Airflow
No Heatsink
Natural Airflow
No Heatsink
No Airflow
No Heatsink
Natural Airflow
No Heatsink
Natural Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
No Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
Natural Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
0.5m/s Airflow
Heatsink
1.0m/s Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
1.0m/s Airflow
No Heatsink
0.5m/s Airflow
No Heatsink
1.0m/s Airflow
Where a heatsink is specified, fit AAVID part 3325 24 B 0 0032.
Copyright 1993,1995,1998,2001 BVM Ltd.
69BVME4000/6000
Appendix F Circuit Diagrams
NOTE:Circuit diagrams are provided here for customer reference only. This information was
current at the time this User Manual was last revised. This information is not necessarily
current or complete manufacturing data, nor is it part of the product specification.
Copyright 1993,1995,1998,2001 BVM Ltd.
This is the master sheet for the
BVME4000/6000 rev F.
87654321
D
Processor and Memory
pro_mem.sch
2
C
Ethernet
eth.sch
3
SCSI
scsi.sch
B
4
This sheet contains:
Processor socket
SRAM
EPROM
MM Interface
This sheet contains:
Ethernet Interface
- Takes CPUCLK1
This sheet contains:
SCSI Interface
- Takes CPUCLK1
Industry Pack Interface
ip.sch
5
VME Interface
vme.sch
6
Peripherals and Interrupts
periph.sch
7
This sheet contains:
Industry Pack Interface
IP Connectors
EXP100 Connector
- Takes CPUCLK1
This sheet contains:
VME Interface
P1 & P2 Connectors
This sheet contains:
Serial Port
Parallel Port
Real Time Clock
Peripheral Control PAL
Interrupt Control PAL
Power and Reset
pwr.sch
8
This sheet contains:
3.3 V Power Supply
Reset Circuit
Oscillator Circuit
Battery Circuit
General De-Couplers