Spectrum Signal ProcessingMonaco Technical Reference
Preface
Preface
About
Spectrum
Contacting
Spectrum
Spectrum Signal Processing offers a complete line of DSP hardware, software and I/O
products for the DSP Systems market based on the latest DSP microprocessors, bus
interface standards, I/O standards and software development environments. By delivering
quality products, and DSP expertise tailored to specific application requirements,
Spectrum can consistently exceed the expectations of our customers. We pride ourselves
in providing unrivaled pre- and post-sales support from our team of application
engineers. Spectrum’s excellent relationships with third party vendors provide customers
with a diverse and top quality product offering.
In 1994, Spectrum achieved ISO 9001 quality certification.
Spectrum’s Applications Engineers are available to provide technical support Monday to
Friday, 8:00 AM to 5:00 PM, Pacific Standard Time.
Telephone1-800-663-8986 or (604) 421-5422
Fax(604) 421-1764
Emailsupport@spectrumsignal.com
Internethttp://www.spectrumsignal.com
To help us assist you better and faster, please have the following information ready:
• A concise description of the problem
• The names of all Spectrum hardware components
Customer
Feedback
• The names and version numbers of all Spectrum software components
• The minimum amount of code that demonstrates the problem
• The versions of all software packages, including compilers and operating systems
At Spectrum, we know that accurate and easy to use manuals are important to help you
develop your applications and products. If you wish to comment on this manual, please
e-mail us at documentation@spectrumsignal.com or fax us at (604) 421-1764. Please
include the following information:
• The full name, document number, and version of the manual
• A description of any inaccuracies you may have found
• Comments about what you liked or did not like about the manual
It may be helpful for us to call you to discuss your comments. If this would be acceptable
please include your name, organization, and telephone number with your comments.
Note: Spectrum board products are static sensitive and can be damaged by electrostatic
discharges if not properly handled. Use proper electrostatic precautions whenever
handling Spectrum board products.
Part Number 500-00191
Revision 2.00
iii
Monaco Technical ReferenceSpectrum Signal Processing
Preface
Document
Change
History
Rev.DateChangesSection
2.00Sept 1999Updated for TMS320C6201B and TMS320C6701
n.a.
DSPs
iv
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Monaco Technical ReferenceSpectrum Signal Processing
Table of Contents
xii
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Introduction
1 Introduction
This manual describes the features, architecture, and specifications of the Monaco Quad
'C6x VME64 Board. You can use this information to program the board at a driver level,
extend the standard hardware functionality, or develop custom configurations.
1.1. Features
Spectrum’s Monaco VME64 board consists of four TMS320C6x processing nodes. It is
available with either fixed-point or floating-point TMS320C6x processors.
Monaco Technical ReferenceSpectrum Signal Processing
Introduction
1.2. Interfaces
In addition to the VME bus which provides the primary interface to the host computer,
the Monaco board features PMC, PEM, serial port, DSP~LINK3 and JTAG interfaces.
1.2.1. VME
Two VMEbus interfaces are provided on the Monaco board. The primary dataflow
interface supports VME64 master and slave modes for fast data transfer through the
SCV64 interface chip.
A secondary interface gives the VME A24 bus direct access to the Host Port Interface
(HPI) of each ‘C6x. This provides direct control and data transfer to and from the DSP
without interfering with dataflow on the Monaco’s Global Shared Bus.
1.2.2. PMC
The Spectrum Hurricane PCI bridge chip supports high-speed data transfer from an onboard PMC site to the shared memory. The industry-standard IEEE-1386 PMC module
site allows developers to select from a wide variety of third-party modules.
1.2.3. PEM
Four independent high-speed, full-bandwidth, bi-directional, dataflow channels between
standard mezzanine boards (Processor Expansion Modules, or PEMs) and the ‘C6x
processors are supported. Application-specific interfaces, mounted to the PEM, are
available for computer telephony, digital radio as well as customer-specified interfaces.
1.2.4. Serial Ports
Two serial ports from each ‘C6x are available at each PEM site for on-board I/O
expansion. For each ‘C6x, one of the serial ports is always routed to the PEM site, the
second can be routed to either the PEM site or the VME P2 connector.
1.2.5. JTAG
The secondary VME interface allows access to the on-board JTAG Test Bus Controller
(TBC) from a host single-board computer for diagnostic purposes.
2
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Introduction
1.3. Reference Documents
Monaco Installation Guide from Spectrum
Monaco Programming Guide from Spectrum
DSP~LINK3 Specification from Spectrum
PEM Specification from Spectrum
TMS320C6000 Peripherals Reference Guide from Texas Instruments
SCV64 User Manual from Tundra Semiconductor Corporation
Hurricane Data Sheet from Spectrum
Draft Standard Physical and Environmental Layers for PCI Mezzanine Cards: PMC
IEEE P1386.1/Draft 2.0 available from IEEE
VME64 ANSI/VITA 1-1994 available from ANSI
Part Number 500-00191
Revision 2.00
3
Monaco Technical ReferenceSpectrum Signal Processing
Introduction
1.4. General Bus Architecture
The following block diagram shows the main components of the Monaco board.
'C6x Host Port Inteface (HPI)
DSP~LINK3 Interface
SBSRAM
128K x 32
PMC
Site
PCI
Bus
Hurricane
Node A
'C6x
PEM Site
Address Buffer
and
Data Latches
Global Shared
SRAM
512K x 32
VME P2 Connector
SDRAM
4M x 32
Node B
'C6x
Address Buffer
and
Data Latches
SBSRAM
128K x 32
SDRAM
4M x 32
SBSRAM
128K x 32
SDRAM
4M x 32
Global Shared Bus
Node C
'C6x
Address Buffer
and
Data Latches
Node D
PEM Site
Address Buffer
Data Latches
SCV64
VME64
Interface
VME P1 Connector
'C6x
and
JT A G
SBSRAM
128K x 32
SDRAM
4M x 32
Test Bus
Controller
A24 VME
Slave
Interface
Figure 1 Block Diagram
1.5. On-Board Power Supply
There is an on-board high-efficiency DC-DC power converter that supplies +2.5V and
+3.3V power to the board from the VME 5V supply. The circuit efficiency is
approximately 90%. The +3.3V supply is available to the PEM and PMC sites, as well as
+5V and ±12V. Up to 16.5 Watts is available from the +3.3V supply for the PEM and
PMC sites. The combined +3.3V current consumption of modules on these sites must not
exceed 5 Amps.
When adding modules to the Monaco board, ensure that the power requirements for the
modules are within the specified limits, and that the system power supply and cooling are
sufficient to meet the added requirements.
4
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Introduction
1.6. Reset Conditions
The Monaco board responds to three types of reset conditions:
• VME SYSRESET (VME bus /SYSRESET line)
• VME A24 Slave Interface Reset (VME A24 Control Register bit D0)
• JTAG reset (JTAG chain /TRST line)
The following table indicates which hardware components are reset by the specific reset
condition.
A VME SYSRESET is initiated when the /SYSRESET line on the VME bus is driven
low. All devices and registers on the Monaco board are reset to their default conditions.
1.6.2. VME A24 Slave Interface Reset
The VME A24 slave interface reset is initiated from the VME bus by setting bit D0 of
the VME A24 Control Register to “0”. All devices and registers on the Monaco board
are reset to their default conditions except for the SCV64 VME interface chip. The
VME A24 Control Register is located at VME A24 Base Address + 1004h. The base
address for the VME A24 slave interface is set by jumper block JP1.
1.6.3. JTAG Reset
The JTAG path can be reset by asserting the /TRST line of the JTAG chain by an
EMURST from the XDS or TBC. Only the JTAG path of the DSPs is reset by this
action; no other devices or registers on the board are affected.
5
Monaco Technical ReferenceSpectrum Signal Processing
Introduction
1.7. Board Layout
The following diagram shows the board layout of the Monaco board.
JP10JP8JP9JP7
JN6
JN8JN9
JN10JN11
JN12
JN7
JN13
PEM Site
Nodes C and D
PEM Site
Nodes A and B
JP4 JP5
Node D
‘C6x
Node C
‘C6x
Node B
‘C6x
Node A
‘C6x
JP3
JP2
JP1
12
34
56
78
89
10 11
12 13
VME
P1
JN1JN2
JN5
VME
P2
J1
JTAG IN
Connector
J2
JTAG OUT
Connector
PMC Site
J3
DSP~LINK3 Ribbon Cable Connector
J8
JN4
Figure 2 Board Layout
6
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Introduction
1.8. Jumper settings
Table 2 Jumper Settings
JumperDescriptionINOUT
JP1 Pins 1-2VME A24 slave interface base address bit A2301*
JP1 Pins 3-4VME A24 slave interface base address bit A220*1
JP1 Pins 5-6VME A24 slave interface base address bit A210*1
JP1 Pins 7-8VME A24 slave interface base address bit A200*1
JP1 Pins 9-10VME A24 slave interface base address bit A190*1
JP1 Pins 11-12VME A24 slave interface base address bit A180*1
JP1 Pins 13-14VME A24 slave interface base address bit A170*1
JP2Node A boot modePEMHPI*
JP3Node B boot modePEMHPI*
JP4Node C boot modePEMHPI*
JP5Node D boot modePEMHPI*
JP7Node A Serial Port 1 RoutingVME P2PEM*
JP8Node B Serial Port 1 RoutingVME P2PEM*
JP9Node C Serial Port 1 RoutingVME P2PEM*
JP10Node D Serial Port 1 RoutingVME P2PEM*
* Default position
Note:
The default VME A24 slave interface base address is set to 80 0000h.
Part Number 500-00191
Revision 2.00
7
Monaco Technical ReferenceSpectrum Signal Processing
Introduction
8
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Processor Nodes
2 Processor Nodes
The Monaco board supports one, two or four embedded ‘C6X processor nodes shared
across the Global Shared Bus. The three possible processor configurations are described
in the following figure.
Table 3 Processor Configurations
Populated
ConfigurationNode ANode BNode CNode D
One NodeY
Two NodesYY
Four NodesYYYY
Each DSP node consists of:
• One TMS320C6201 DSP operating at 200 MHz for Monaco, or one TMS320C6701
DSP operating at 167 MHz for Monaco67
• 128K of 32-bit Synchronous burst SRAM (SBSRAM)
• 4M of 32-bit Synchronous DRAM (SDRAM)
• Processor Expansion Module (PEM) interface
• A slave Host Port Interface to VME A24 bus
• Two serial ports
• A DSP~LINK3 interface (DSP node A only)
Part Number 500-00191
Revision 2.00
9
Monaco Technical ReferenceSpectrum Signal Processing
Processor Nodes
JT A G Test Bus
‘C6x Host Port
Interface (HPI) Bus
Node Local
Resources
Serial
Port 0
Serial
Port 1
DSP-LINK3
Interface
Node A
Only
PEM Site
Shared with
Node Pair
DSP
DSP
Local
Bus
‘C6x
128K x 32
SBSRAM
4M x 32
SDRAM
Address Buffer
and
Data Latches
Global Shared Bus
Figure 3 Processor Node Block Diagram
10
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Processor Nodes
2.1. Processor Memory Configurati on
Each ‘C6X DSP processor implements a 4 Gigabyte (full 32-bit) address space. This
address space is partitioned into internal memory space and external memory space.
External memory space is accessed through four memory select lines (CE0, CE1, CE2
and CE3).
2.1.1. Internal Memory
Internal memory space is further separated into three distinct regions:
• internal program RAM (64Kbytes)
• internal peripheral registers (2 Mbytes)
• internal data RAM (64 Kbytes)
These three regions define memory space which is implemented in the DSP processor.
2.1.2. External Memory
External memory is segmented into 4 regions:
• external memory interface CE0 (16 Mbytes)
• external memory interface CE1 (4 Mbytes)
• external memory interface CE2 (16 Mbytes)
• external memory interface CE3 (16 Mbytes)
External memory (CE0, CE1, CE2 and CE3) consists of node local memory resources
which are accessed on the DSP Local Bus, but are external to the DSP processor. The
type of memory in each of the four CE regions is determined by settings in the internal
peripheral registers. All remaining memory in the 4 GB address space is reserved.
The internal peripheral registers for Monaco must be initialized to the values in the
following table upon reset for the board to operate.
Part Number 500-00191
Revision 2.00
11
Monaco Technical ReferenceSpectrum Signal Processing
Processor Nodes
Table 4 'C6x Internal Peripheral Register Values
Register
Global Control Register
Address
0x0180 0000
EMIF CE0 Control Register
0x0180 0008
EMIF CE1 Control Register
0x0180 0004
EMIF CE2 Control Register
0x0180 0010
EMIF CE3 Control Register
(Used for PEM. Must be
reconfigured for individual
PEM)
0x0180 0014
EMIF SDRAM Control
0x0180 0018
EMIF SDRAM Timing
0x0180 001C
ValueComments
0x0000 3078NOHOLD (External HOLD disable) off
SDCEN (SDRAM clock enable) on
SSCEN (SBSRAM clock enable) on
CLK1EN (CLKOUT1 enable) on
CLK2EN (CLKOUT2 enable) on
SSCRT (SBSRAM clock rate select) 1/2x CPU clock
RBTR8 off (requester controls EMIF until a high priority request
occurs..
0xFFFF 3F43MTYPE = 32 bit wide SBSRAM
No other bits are used.
0x30E4 0421MTYPE = 32 bit wide asynchronous interface
write setup = 3 cycles
write strobe = 3 cycles
write hold = 2 cycles
read setup = 4 cycles
read strobe = 4 cycles
read hold = 1 cycle
all cycles are clockout1 cycles
0xFFFF 3F33MTYPE = 32 bit wide SDRAM
No other bits are used.
0x72B7 0A23MTYPE = 32 bit wide asynchronous interface
address = 0x01800004
value = 0x30E40421
MTYPE = 32 bit wide asynchronous interface
write setup = 7 cycles
write strobe = 10 cycles
write hold = 3 cycles
read setup = 7 cycles
read strobe = 10 cycles
read hold = 3 cycle
all cycles are clockout1 cycles
refresh can be used.
SDWID = 1 (SDRAM width select) two 16 bit SDRAMs
Other timing parameters are SDRAM specific and should not be
modified by the user.
0x0000 061ARefresh timer implemented in external hardware. This register is
not used.
12
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Processor Nodes
‘C6x AddrMemory ContentsMemory Size
0000 0000Internal-Program RAM64 KB
0000 1000
Reserved4 MB - 64KB
0040 0000Local SBSRAM512 KB
0048 0000
0140 0000
0180 0000
01A0 0000
0200 0000
0300 0000
External-Memory Space
Upon Reset
PEM EEPROM
Boot Mode
Internal-Peripheral Space2 MB
Local SDRAM
Processor Expansion Module (PEM)
Reserved
CE1
CE0
External-Memory Space
After TOUT0 is toggled
DSP~LINK3
Shared SRAM
SCV64 Registers
(see the following CE1
memory map)
Reserved6 MB
CE2
CE3
CE1
16 M - 512 KB
4 MB
16 MB
16 MB
Part Number 500-00191
Revision 2.00
0400 0000
Reserved2 GB - 64 MB
8000 0000Internal-Data RAM64 KB
8001 0000
Reserved2GB -
(2GB - 64 KB)
FFFF FFFF
Figure 4 DSP Memory Map
13
Monaco Technical ReferenceSpectrum Signal Processing
Processor Nodes
External Memory Space CE1 is dedicated to accessing registers, global shared RAM and
DSP~LINK3 (Node A only). Node A differs from nodes B, C and D since it is the only
node with access to the DSP~LINK3. The following figure shows the memory map for
this region.
AddressNode ANodes B, C, and D
0140 0000
Global Shared SRAM
512K x 32
015F FFFC
0160 0000
DSP~LINK3 Standard Access
0163 FFFC
0164 0000
DSP~LINK3 Standard Fast AccessReserved
0167 FFFC
0168 0000
DSP~LINK3 RDY Controlled Access
016B FFFC
016C 0000
Hurricane RegistersHurricane Registers
016C 1FFC
016D 0000
Global Shared SRAM
512K x 32
016D 7FFC
016D 8000
016D FFFC
016E 0000
016E 7FFC
016E 8000
016E FFFC
016F 0000
016F FFFC
0170 0000
017F FFFC
Node A VPAGE RegisterNode B, C, or D VPAGE Register
Shared Bus RegistersShared Bus Registers
SCV64 Register Set (R/W)SCV64 Register Set (R/W)
ReservedReserved
IACK Cycle Space (Read Only)IACK Cycle Space (Read Only)
One Mbyte window to the
VME Address Space
VME base address set by VPAGE register
DSP as VME Master (R/W)
VME base address set by VPAGE register
One Mbyte window to the
VME Address Space
DSP as VME Master (R/W)
Figure 5 DSP Memory Map for External-Memory Space CE1
14
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Processor Nodes
2.2. Synchronous Burst SRAM
The board provides 128K of 32-bit synchronous burst SRAM (SBSRAM) on each ‘C6x
local bus. The Monaco board supports 1 wait state operation.
2.3. Synchronous DRAM
The board provides 4M of 32-bit synchronous DRAM on each ‘C6x bus. The Monaco
board supports 1 wait state operation. An additional 4M of 32-bit synchronous DRAM
per DSP can also be supported on a PEM module.
Burst data transfer rates from CPU to SDRAM are 400 Mbytes/s on a Monaco with
200 MHz TMS320C6201 chips.
2.4. Processor Expansion Module
The Processor Expansion Module (PEM) provides a simple and flexible interface from
the DSP to I/O. It is similar to a PMC module, although physically narrower.
The Monaco board is designed to support two DSPs per PEM site, with a pair of
connectors for each DSP. While both DSP devices share the same PEM, the two DSP
buses are kept separate to allow very fast PEM data transfer rates.
The PEM is capable of booting the DSPs from local ROM, with up to 4 MBytes of
addressable boot space available to each DSP.
Refer to the PEM Specification for mechanical and functional details of the PEM
interface.
2.5. Host Port
A separate A24 VMEbus Slave interface is used for direct access to the DSP’s Host Port
Interface. This interface can be used for downloading code and as a control path from the
host to the DSP. Data transfer rates depend upon both the code executing in the DSP and
the VMEbus Master performing the transfers, but can be as high as 30 Mbytes/second.
Jumper block JP1 selects the VME A24 base address for this slave interface.
2.6. Interrupt Lines
There are four external interrupt inputs on each ‘C6x. They are INT4, INT5, INT6, and
INT7. All four must be configured as rising-edge triggered interrupts upon initialization.
See the Interrupt Handling chapter for further information.
Part Number 500-00191
Revision 2.00
15
Monaco Technical ReferenceSpectrum Signal Processing
Processor Nodes
2.7. Processor Booting
The ‘C6x can boot from either the VME bus (via its Host Port Interface (HPI) port) or
from an 8-bit EEPROM on an installed PEM module. The jumpers listed in the following
table select the booting method for each node.
The Monaco board uses the CE1 memory space of the ‘C6x memory map 1 for the boot
space upon power up or reset. Immediately after booting, the ‘C6x cannot access the
resources in its CE1 space such as the Hurricane registers, Global Shared SRAM, and
SCV64 Registers. In order to access these CE1 resources, the ‘C6x must toggle the state
of its Timer 0 pin (TOUT0). The state of this pin is controlled by the DataOut bit of the
‘C6x Timer 0 Control Register. Once TOUT has been toggled, the CE1 resources are
available to the ‘C6x until the ‘C6x is reset.
16
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Processor Nodes
2.8. Serial Port Routing
Each ‘C6x has two serial ports. Serial Port 0 of each DSP is routed to the PEM connector
associated with the DSP node.
Routing for Serial Port 1 on nodes A, B, C and D is determined by jumpers J7 to J10 as
shown in the figure and following tables. The jumper setting selects routing either to the
PMC JN5 and VME P2 connectors, or to the PEM connector associated with the DSP
node.
Serial Port routing for the Monaco board is shown the figure. Complete pinouts for the
connectors are given in the Connector Pinouts chapter.
Serial
Port 0
Serial
Port 1
Serial
Port 0
Serial
Port 1
Serial
Port 0
Serial
Port 1
Serial
Port 0
Serial
Port 1
Node D
C6x
Node C
C6x
Node B
C6x
Node A
C6x
VME
P1
Node
D
PEM
1
Node
C
PEM
1
Node
B
PEM
1
Node
A
PEM
1
Node
D
PEM
2
Node
C
PEM
2
Node
B
PEM
2
Node
A
PEM
2
OUT
OUT
JP7
IN
OUT
JP8
IN
OUT
JP9
IN
JP10
IN
Figure 6 Serial Port Routing
Part Number 500-00191
Revision 2.00
Node D Serial Port 0
Node C Serial Port 0
Node B Serial Port 0
Node A Serial Port 0
PMC
Connector
JN5
Node D
Node C
Node B
Node A
VME
P2
17
Monaco Technical ReferenceSpectrum Signal Processing
Processor Nodes
Pin assignments for the serial ports are given in the following tables.
Table 6 PEM Connections for Serial Port 0 and 1
SignalPEM 1 Port 0PEM 2 Port 1*
CLKSExternal clock5617
CLKRReceive clock5213
CLKXTransmit clock423
DRReceived serial data489
DXTransmitted serial data467
FSRReceive frame synchronization5011
FSXTransmit frame synchronization445
*The serial port routing jumper corresponding to the node (J7, J8, J9, or J10) must be
OUT for port 1 to be routed to the node’s PEM 2 connector.
Table 7 VME and PMC Connections for Serial Port 1
Node A (J7 IN)Node B (J8 IN)Node C (J9 IN)Node D (J10 IN)
DXTransmitted serial data13D-1233D-2614Z-1134Z-25
FSRReceive frame synchronization15D-1435D-2816Z-1336Z-27
FSXTransmit frame synchronization17D-1637D-3018Z-1538Z-29
18
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Global Shared Bus
3 Global Shared Bus
The Global Shared Bus provides access between devices on the Monaco board as shown
in the following table.
Table 8 Global Shared Bus Access
Source
3.1. Memory
Target‘C6x
Nodes
Internal program & data RAMR/W own nodeNo AccessNo Access
Local SDRAMR/W own nodeNo AccessNo Access
Local SBSRAMR/W own nodeNo AccessNo Access
Global Shared RAMR/W (32-bit only)R/WR/W
Hurricane RegistersR/WR/WR/W
PMC SiteHurricane DMA
access only
SCV64 RegistersR/WNo AccessNo Access
Global Shared Bus RegistersR/WNo AccessNo Access
VMEbus as masterR/WNo Access-
PMC
Site
-No Access
VME Bus
via SCV64
512K of 32-bit Asynchronous RAM, implemented in four 512K x 8-bit Asynchronous
RAM devices, is provided on the Global Shared Bus. The ‘C6x DSPs can only perform
32-bit accesses to the Global Shared RAM. Byte accesses are not supported.
3.2. Arbitration
Arbitration of the Global Shared Bus is implemented using a next bus owner token that is
passed serially from one device to the next. Token passing follows a strict hierarchical
sequence, ordered by bus servicing priority. There are six devices participating in the
process. These are, in decreasing priority:
• SCV64
• Hurricane
• DSP Node A
• DSP Node B
• DSP Node C
• DSP Node D
Part Number 500-00191
Revision 2.00
19
Monaco Technical ReferenceSpectrum Signal Processing
Global Shared Bus
Bus ownership is cycled between the two highest priority devices (SCV64 and
Hurricane) until neither device requires the bus. Then the DSP Nodes are processed
round robin. After one pass through the DSP chain, the cycle loops back to include the
SCV64 and Hurricane. This eliminates any arbitration latency as bus ownership is
transferred between devices, and grants the highest priority to those devices interfacing
to external buses (VME and PCI), which require the fastest response. The arbitration
cycle is shown in the following figure.
Note:
Because there is no ownership timer for either Hurricane or SCV64 chip
the system designer must ensure that processors are not held off from the shared
resources for unreasonable lengths of time.
Highest PriorityLowest priority
Node AHurricaneSCV64Node DNode CNode B
Round Robin
DSPVME & PCI Bus
Round Robin
Figure 7 Global Bus Arbitration
Access to the Global Shared Bus can use single, burst, or locked cycles.
20
3.2.1. Single Cycle Bus Access
For single cycle accesses a device requests the global shared bus by simply initiating a
read or write access to the bus. When the bus is free, the device acquires it and performs
the single cycle access. The bus is then released.
3.2.2. Burst Cycle Bus Access
Burst cycles are used during DMA transfers from a ‘C6x processor to the Global Shared
Bus. A 6-bit bus ownership timer on each node prevents a ‘C6x from owning the bus for
more than 640 ns when another device is requesting the bus. When the burst cycles are
begun, the timer is started. If another device requests the bus when the timer expires, the
bus is released; otherwise ownership is maintained and the timer is reset and started
again.
If multiple DSPs request the bus, this scheme allocates time to them fairly so that none
are locked out.
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Global Shared Bus
Although this is a non-prioritized scheme, the back-off function of the SCV64 interface
resolves collisions between a bus master and the VMEbus if there is contention for the
VMEbus.
Note:
There are no ownership timers for the Hurricane or SCV64. If the
Hurricane holds the bus too long the VME bus could timeout.
3.2.3. Locked Cycles
A ‘C6x can lock the Global Shared Bus in order to perform Read-Modify-Write (RMW)
or other atomic accesses to it, by driving its Timer 0 (TOUT0) low. After the TOUT0 is
driven low, the next access to the Global Shared Bus acquires the bus. The bus is not
released until the ‘C6x drives the Timer 0 (TOUT0) pin high.
Caution:
be used carefully because other devices will not acquire the bus once it is locked.
This capability is intended for read-modify-write accesses to the Global Shared
RAM and registers. It is highly recommended that Bus locking not be used. It
can lead to a deadlock condition, and in particular, result in debugger timeouts.
The following precautions should be observed when locking the Global Shared Bus:
1. VME bus timeouts can occur because the SCV64 cannot access the board while a
‘C6x has locked the bus.
The capability of locking the Global Shared Bus from a ‘C6x should
2. If node A accesses the DSP~LINK3 interface while it has locked the Global Shared
Bus by asserting TOUT0, the bus will be released. Node A’s next access to the bus
will re-lock it to node A, providing that TOUT0 is still asserted.
3. Some SCV64 inbound cycles can occur while the bus is locked. If a ‘C6x has locked
the bus and is performing a VME outbound cycle while a VME inbound cycle is in
progress, the ‘C6x will be temporarily backed off and the SCV64 cycle will proceed.
The Global Shared Bus will be returned to that ‘C6x node after the SCV64 cycle
finishes. No other ‘C6x will get ownership of the bus.
4. If a debugger is being used when one processor has the bus locked for an extended
time while another processor is trying to get the bus, the debugger may timeout.
Part Number 500-00191
Revision 2.00
21
Monaco Technical ReferenceSpectrum Signal Processing
Global Shared Bus
22
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
VME64 Bus Interface
4 VME64 Bus Interface
There are two separate VMEbus slave interfaces on the Monaco board. One is
implemented by the SCV64 and provides A32 and A24 VMEbus masters access to the
global shared bus. The second slave interface provides direct access to the Test Bus
Controller for debugging, and to the Host Port Interfaces (HPIs) of each ‘C6x. The HPI
provides support for code download, control, and data transfers from the VME64 bus.
4.1. VME Operation
The Monaco board requires a VME chassis (6U) with power supply. The board
automatically becomes VMEbus system controller (Syscon) if it resides at the top of the
VMEbus grant daisy chain. This capability is provided by the Tundra SCV64 interface
chip. Refer to the SCV64 User Manual for details.
The Monaco board has two VME backplane connectors: a 3 row P1 connector and a 5
row P2 connector.
The board may be installed in either a 5 row VME backplane or a 3 row backplane. The
two additional rows on the VME P2 connector (Z and D) only serve to route serial port
signals from DSP processor nodes A, B, C and D to the VME backplane, if the board is
configured for that option.
Note:
routing will be restricted to the PEM and PMC sites only.
If the Monaco board is installed in a 3 row VME chassis, serial port
4.2. SCV64 Primary Slave A32/A24 Interface
The primary interface to the VME64 bus is based on Tundra Semiconductor
Corporation’s SCV64 VME64 Interface chip. This chip enables the Monaco board to act
as a master or a slave on the VME64 bus, and also provides VME interrupt capabilities.
Transfer rates of 40 MBytes/sec are supported between the SCV64 and the Global
Shared Bus SRAM once the bus has been acquired. The SCV64 cannot be pre-empted
from the Global Shared Bus and it does not have a bus ownership timer.
A host on the VME64 bus can access both the lower half (1 Mbyte) of Global SRAM
and the Hurricane control registers on a Monaco board in either A24 or A32 addressing
modes as shown in the following memory map.
Part Number 500-00191
Revision 2.00
23
Monaco Technical ReferenceSpectrum Signal Processing
VME64 Bus Interface
VME Offset AddressAccess
0000 0000h
Global Shared SRAM
(lower 1Mbyte)
000F FFFFh
0010 0000h
Global Shared SRAM
(Upper 1 Mbyte)
001F FFFFh
0020 0000h
Hurricane Control Registers
002F FFFFh
0030 0000h
Reserved
003F FFFFh
Host
VMEDSP
accessibleand
Figure 8 Primary VME A24/A32 Memory Map
Note:
The full A24 memory map occupies one-quarter of the available A24
space. This can be reduced to the standard 512K (16M ÷ 32) of the available
A24 space by mapping only the lower 512 Kbytes (128k x 32) of the global
shared SRAM. This is entirely programmable in the SCV64 base address
registers. Only SCV64 A21 and A20 are used for decode on SCV64 VME slave
accesses to the board. D16 and D08E0 writes are not supported on the primary
A32/A24 interface.
Hurricane
accessible
4.3. A24 Secondary Slave Interface
Jumper block JP1 sets address bits A23..A17 of the VME A24 slave interface. This base
address defines a 128K byte addressed memory space accessed by the VME bus. Access
to this space from the VME bus bypasses the SCV64 VME bus interface chip.
All A24 VME transfer types are accepted except for LOCK, and MBLT types.
As shown in the following memory map, the A24 slave interface provides the VME bus
direct access to:
• The Host Port Interface (HPI) registers of each ‘C6x processor
• The Test Bus Controller (TBC) for JTAG debugging operation
• Control and Status registers of the Monaco board
D16 and D08E0 accesses are not supported on the slave A24 secondary interface.
24
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
VME64 Bus Interface
VME Offset Address
00 0000h
Test Bus Controller Registers (JTAG)
00 0FFFh
00 1000h
FPGA
‘C6x
‘C6x
00 1003h
00 1004h
00 1007h
00 1008h
00 1FFFh
00 2000h
00 2FFFh
00 3000h
00 3FFFh
00 4000h
00 4FFFh
00 5000h
00 5FFFh
00 6000h
00 FFFFh
01 0000h
01 3FFCh
01 4000h
01 3FFCh
01 B000h
01 3FFCh
01 C000h
01 FFFCh
VME A24 Status Register (Read Only)
VME A24 Control Register (Read/Write)
Reserved
Node A HPI Registers
Node B HPI Registers
Node C HPI Registers
Node D HPI Registers
Reserved
Node A HPID DMA Space (HPIA incremented)
all addresses mapped to 00 2008h
Node B HPID DMA Space (HPIA incremented)
all addresses mapped to 00 3008h
Node C HPID DMA Space (HPIA incremented)
all addresses mapped to 00 4008h
Node D HPID DMA Space (HPIA incremented)
all addresses mapped to 00 5008h
16 KB
16 KB
16 KB
16 KB
Figure 9 A24 Secondary Interface Memory Map
Refer to the JTAG Debugging chapter for information on using the Test Bus Controller
for JTAG operation. The VME A24 Status Register and the
VME A24 Control Register are described in the Registers chapter.
Part Number 500-00191
Revision 2.00
25
Monaco Technical ReferenceSpectrum Signal Processing
VME64 Bus Interface
The Host Port Interface (HPI) allows a VME host to access the memory map of any
‘C6X. The board transfers 32-bit VME accesses automatically through the 16-bit Host
Port Interface as two 16-bit words. The interface consists of three read/write, 32-bit
registers that are accessed through the VME A24 slave interface:
• HPI Address register (HPIA)
• HPI Control register (HPIC). A ‘C6x can also read and write to its HPI Control
register (HPIC) at address 0188 0000h.
• HPI Data register (HPID)
VME address bits A[3:2] select which register is being accessed in each node’s HPI
register address space. These bits are mapped to the HCNTRL[1:0] control pins of the
‘C6x. The following table shows how the HPI interface is addressed.
Table 9 HPI Register Addresses
VME address
‘C6x
Register
HPIC00 2000h 00 3000h 00 4000h00 5000hState for reading/setting the Control Register value.
HPIA00 2004h 00 3004h 00 4004h00 5004hUsed to read/set the HPI address pointer. The HPIA
HPID00 2008h 00 3008h 00 4008h00 5008hA VME host reads and writes data to this address for
HPID00 200Ch 00 300Ch 00 400Ch00 500ChA VME host reads and writes data to this address for
HPID
DMA
Space
Node
A
01 0000h 01 4000h 01 8000h 01 C0000h VME hosts which increment their target address can use
Node
B
Node
C
Node
DDescription
points into the C6x memory space.
DMA transfers to the HPID register. The HPIA register
automatically increments by 4 bytes as each word is
transferred through the HPID register.
single cycle transfers to the HPID register. The HPIA is
not incremented for this HPI access mode.
this address space for DMA transfers to the HPID
register. Up to 4K of 32-bit data can be transferred in this
space. Data written to this space is automatically
transferred to the HPID register, and the HPIA register
automatically increments by 4 bytes as each word is
transferred.
26
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
VME64 Bus Interface
Before a host can transfer data through a node’s HPI, the VME host must set the HWOB
bit of the node’s HPIC register to “1”. This only has to be done once after the Monaco
board is reset. To access an address within a ‘C6x’s memory space, the VME host loads
the address into the HPIA register. Data is then transferred through the HPID register.
• The HPID at offset “8h” auto-increments four bytes after every cycle, allowing it to
be used for burst DMA data transfers.
• The HPID at offset “Ch” does not auto-increment, and is therefore intended for
single cycle accesses only.
• The HPID DMA Space offers a 16K address space to VME hosts which increment
their target address during DMA transfers. This allows them to transfer data in
blocks of 16K 32-bit words to the HPID register used for DMA transfers.
4.4. Master A32/A24/A16 SCV64 Interface
As a VME master, the Monaco board supports A16, A24, or A32 transactions from any
node to the VME64 bus through the SCV64 chip. Any node can program the SCV64’s
DMA Controller for VME Master Accesses, and can directly master the VMEbus. Each
node has its own VPAGE Register to support the KFC, KSIZE, and upper 12 and
lower 2 address bits to the SCV64. The upper 11 bits extend the 20-bit address space of
the ‘C6x to the full 32-bit address space of the VME bus. Any node can monitor the
status of the /KIPL interrupt lines, BUSERRORs for each node, and KAVEC line by
reading the VSTATUS Register.
The Monaco board supports Auto-Syscon capabilities allowing it to become the System
Controller board when placed in the leftmost slot of the VME backplane. If it is to be the
System Controller it should typically be booted from a PEM module equipped with a
boot PROM.
Upon reset, the SCV64 is in Bus-Isolation Mode (BI-Mode) which isolates the SCV64
from the VME64 bus. The SCV64 is released from BI-Mode by a write to the SCV64
Location Monitor from any node of the Monaco board.
Part Number 500-00191
Revision 2.00
27
Monaco Technical ReferenceSpectrum Signal Processing
VME64 Bus Interface
28
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
DSP~LINK3 Interface
5 DSP~LINK3 Interface
The Monaco board provides a DSP~LINK3 interface through a ribbon cable connector.
The interface supports up to 4 slave DSP~LINK3 devices. The ribbon cable can be up to
12 inches (30 cm) long.
The DSP~LINK3 interface is accessed from node A’s local bus only; it is not accessible
from any other node nor from the VME bus. Accesses to the DSP~LINK3 interface do
not require the Global Shared Bus. As a result, DSP~LINK3 accesses can happen
concurrently with Global Shared Bus access by other devices (such as the other
processors or the SCV64 chip).
If a DSP~LINK3 access is interleaved within global shared SRAM accesses, node A
acquires the Global Shared Bus, performs the SRAM access, releases the Global Shared
Bus, performs the DSP~LINK3 access, acquires the Global Shared Bus, and then
performs the next Global Shared Bus SRAM access using a control register.
5.1. DSP~LINK3 Data Transfer Operating Modes
The Monaco board supports four data transfer operating modes.
• Standard Access
• Standard Fast Access
• Address Strobe Control
• Ready Control Access
The three “access” data transfer operating modes (Standard, Standard Fast and Ready
Control) of the DSP~LINK3 interface use three 64K address spaces accessed from node
A. Each of the three “access” modes is assigned its own 64K memory space. Address
Strobe Control cycles are multiplexed with the Standard Fast Access mode space.
The following table shows how the DSP~LINK3 data transfer operating modes are
supported.
Part Number 500-00191
Revision 2.00
29
Monaco Technical ReferenceSpectrum Signal Processing
DSP~LINK3 Interface
Table 10 DSP~LINK3 Data Transfer Operating Modes
Mode
Standard
Access
Standard
Fast
Access
Address
Strobe
Control
Ready
Control
Access
Base
Address
0160 0000h
0164 0000h0For DSP~LINK3 slave boards that have fast,
0164 0000h1For slave boards that require more than the
0168 0000h
ASTRB_EN
BitDescription
x
x
For slave boards that are similar to DSP~LINK1
slave boards and operate with a fixed access
time.
fixed access time. This memory space is
shared with the Address Strobe Control
operating mode.
16 KWords of addressing provided by the
standard DSP~LINK3 address lines. The bus
master uses the /ASTRB cycle to place the
page address onto the DSP~LINK3 data lines.
It determines which address page is accessed
on the slave board. This allows access to up to
14
address pages with each address page
2
having an address depth of 2
Cycle has the same timing as the Standard
Fast transfer cycle.
For DSP~LINK3 slave boards that require
variable length access times. /DSTRB is active
until the slave asserts the DSP~LINK3 ready
signal (/RDY) to end the cycle.
14
. The /ASTRB
5.2. Address Strobe Control Mode
The Address Strobe Control mode uses the same node A 64K address space as the
Standard Fast Access mode. The Address Strobe Control mode is enabled for this space
by setting bit D1, the ASTRB_EN bit, of the DSP~LINK3 register to “1”. This register is
located at address 016D 8018h of node A. Standard Fast Access mode writes will now
generate /ASTRB cycles. The DSP~LINK3 slave attached to the Monaco board should
then latch the lower addresses.
30
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
DSP~LINK3 Interface
5.3. Interface Signals
The DSP~LINK3 interface consists of two 16-bit bi-directional buffers for data, a 16-bit
address latch, and a control signal buffer. The control signals are terminated via a SCSI
terminator. The DSP~LINK3 interface signals are:
• 32 data I/O lines: D[31..0]
• 16 address outputs: A[15..0] A15 and A14 are used for slave device (board)
selection.
• /DSTRB, /ASTRB, R/W and /RST outputs
• Tri-state ready (/RDY) input
• 4 open-collector interrupt inputs (IRQ0 to IRQ3). These interrupt are logically
OR’ed and routed to the INT7 line of node A’s ‘C6x.
Refer to DSP~LINK3 specification for details (available from Spectrum’s internet web
site at http://www.spectrumsignal.com)
5.4. DSP~LINK3 Reset
Bit D0 of the DSP~LINK3 register controls the DSP~LINK3 reset line. This register is
located at address 016D 8018h of node A. Setting bit D0 to “1” asserts the DSP~LINK3
reset line; setting it to “0” releases the reset. DSP~LINK3 resets must be at least 1 µs
long. This reset is entirely under software control.
The DSP~LINK3 reset line will also be asserted during /SYSRESET or secondary
control register board reset conditions.
Part Number 500-00191
Revision 2.00
31
Monaco Technical ReferenceSpectrum Signal Processing
DSP~LINK3 Interface
32
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
PCI Interface
6 PCI Interface
The Hurricane chip provides the interface between the Global Shared SRAM on the
Global Shared Bus and the PMC site which supports a 32 bit, 33 MHz PCI bus. Although
the DSPs cannot directly master the PCI bus, the Hurricane’s DMA controller provides
flexible data transfer between the Global Shared Bus SRAM and the PMC.
Pre-emptive arbitration is not used. If a node requests the Global Shared bus when the
bus is not currently in use, then it will be granted the bus. It is up to the bus ownership
timers of the Hurricane and PMC devices to prevent bus hogging.
PMC modules can directly master the Global Shared SRAM.
The memory map of the Monaco seen by a PMC module is shown in the following
figure.
PCI Offset AddressAccess
0000 0000h
001F FFFFh
0020 0000h
002F FFFFh
0030 0000h
003F FFFFh
Figure 10 PCI Memory Map
6.1. Hurricane Configuration
Before the PMC site can be accessed, the Monaco initialization software must configure
the Hurricane registers with the values shown in the following table. Only the indicated
values should be initialized, all other values should be left alone. As can be seen, these
registers can be accessed from a ‘C6x, the PMC’s PCI bus, and a host on the VME bus.
Global Shared SRAM
Hurricane Control Registers
Reserved
Part Number 500-00191
Revision 2.00
33
Monaco Technical ReferenceSpectrum Signal Processing
The Hurricane PCI-to-DSP Bridge Data Sheet should be read in order to understand
how it is used with the Monaco board.
On the DSP port of the Hurricane, only bank 0 is used to access the Global Shared Bus.
All other Hurricane DSP banks are unused.
There are two devices on the PMC site’s PCI bus: the Hurricane chip and the PMC
device. The IDSEL line from each of the two PCI devices is connected to the following
Address/Data lines:
PCI DeviceIDSEL Connection
HurricaneAD16
PMC ModuleAD17
36
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
r
d
l
o
JTAG Debugging
7 JTAG Debugging
The Monaco board supports JTAG in-circuit emulation from a built in 74ACT8990 Test
Bus Controller. The 74ACT8990 Test Bus Controller permits the VME interface to
operate the JTAG chain. There are also two JTAG connectors for an XDS510 or White
Mountain debugger, JTAG IN (J1) and JTAG OUT (J2), which can route the JTAG
chain off-board.
JTAG in-circuit emulation is fed to the Test Bus Controller from the VME A24
secondary interface. C source debugging using an emulator board running a debug
monitor on an adjacent computer is supported through the JTAG IN connector. If a
JTAG IN connection with a clock signal is present the Test Bus Controller is
automatically disconnected.
JTAG data lines are routed to each available ‘C6x node. The full JTAG chain is shown
in the following diagram. Unpopulated processor nodes are bypassed.
TDO
JTAG OUT
TDI
The Test Bus Controlle
(TBC) is disable
(bypassed) if an externa
debugger is connected t
the JTAG IN connector.
Figure 11 JTAG Chain
Routed back
to JTAG IN if
nothing is
connected to
JTAG OUT
TDO
JTAG IN or TBC
TDO
TDI
Node D
‘C6x
TDI
TDO
Node C
‘C6x
TDI
TDO
Node B
‘C6x
TDI
TDO
Node A
‘C6x
The JTAG IN input is buffered to reduce the load on an external JTAG device. The
JTAG OUT output is buffered to guarantee enough drive to external JTAG loads. Up to
three Monaco boards can be chained together through JTAG.
Part Number 500-00191
Revision 2.00
37
Monaco Technical ReferenceSpectrum Signal Processing
JTAG Debugging
For multiple Monaco boards, the JTAG cable of the external debugger should be
connected to the JTAG IN of the first board. The JTAG OUT of the first board should be
connected to the JTAG IN of second board. The JTAG OUT of the second board should
be connected to the JTAG IN of third board and so on. The JTAG OUT connector of the
last board is not connected to anything.
Note:
All hardware must be powered off before the JTAG cable are connected
and the JTAG chain is set up.
38
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Interrupt Handling
8 Interrupt Handling
8.1. Overview
Each ‘C6x has four interrupt pins which are configurable as either leading or falling
edge-triggered interrupts. For the Monaco board, all ‘C6x interrupts are configured as
rising edge-triggered interrupts. The /NMI interrupts for the ‘C6x DSPs are not used;
they are tied high.
The following block diagram shows how interrupts are routed to these pins on the
Monaco board.
Part Number 500-00191
Revision 2.00
39
Monaco Technical ReferenceSpectrum Signal Processing
Interrupt Handling
KIPL D Enable
SCV64 Interrupt
BUSERR_D
VINTD
BUSERR_C
VINTC
BUSERR_B
VINTB
KIPL C Enable
KIPL B Enable
KIPL A Enable
PEM INT1
PEM INT2
PEM INT1
PEM INT2
PEM INT1
PEM INT2
VME Interrupt
PCI Interrupt
Hurricane
VME Interrupt
PCI Interrupt
Hurricane
VME Interrupt
PCI Interrupt
Hurricane
INT 4
INT 5
INT 6
INT 7
INT 4
INT 5
INT 6
INT 7
INT 4
INT 5
INT 6
INT 7
Node D
'C6x
Node C
'C6x
Node B
'C6x
BUSERR_A
VINTA
Hurricane
De-Bounce Logic
PCI Bus
Interrupts
DSP~LINK3
Interface
Interrupts
INTA
INTB
INTC
INTD
INT0
INT1
INT2
INT3
Figure 12 Interrupt Routing
8.2. DSP~LINK3 Interrupts to Node A
The four active-low interrupts from the DSP~LINK3 interface are logically OR’ed and
routed to the INT7 interrupt input of the node A ‘C6x. The open-collector signals are debounced. The interrupts are not latched on the Monaco board and must be cleared on the
DSP~LINK3 board that generated them.
VME Interrupt
PCI Interrupt
Hurricane
PEM INT1
PEM INT2
De-Bounce Logic
INT 4
INT 5
Node A
'C6x
INT 6
INT 7
Note
‘C6x interrupts
are rising edge-
triggered.
40
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Interrupt Handling
8.3. PEM Interrupts
There are two active-low, driven interrupts from the PEM connectors for each node.
These interrupts (/PEM INT1 and /PEM INT2) are OR’ed together. Their output is
routed to INT6 of each node’s DSP and inverted to create a rising-edge trigger.
The Monaco board does not latch the PEM interrupts. They must be cleared on the PEM
module that generated them.
8.4. PCI Bus Interrupts
The four active-low interrupt signals from the PCI bus (INTA#, INTB#, INTC#, and
INTD#) are physically tied together and routed to INT5 of each of ‘C6x DSPs. They are
also buffered through a de-bounce circuit because they are open-collector. On node A the
PCI bus interrupt is also shared with the Hurricane interrupt on INT5 of the ‘C6x through
an OR gate.
The interrupt is not latched, and its source must be cleared on the PMC module.
8.5. Hurricane Interrupt
The interrupt signal from the Hurricane chip is routed to each of the board’s ‘C6x
processors. On node A the PCI bus interrupt is also shared with the Hurricane interrupt
on INT5 of the ‘C6x through an OR gate. For nodes B, C, and D, the Hurricane interrupt
is routed to INT7 of the ‘C6x.
8.6. SCV64 Interrupt
An interrupt line from the SCV64 VME interface is routed to the INT4 interrupt input of
all four ‘C6x processors. The interrupt provides VME, SCV64 timers and DMA, and
other local interrupt capability. On-board logic routes VME bus error and the interprocessor VINTx interrupts to INT4 as well.
This interrupt can be individually enabled or disabled for each node using the
KIPL Enable Register (address 016D 8014h). Bits D0..D4 enable the interrupt for each
node when set to “1”. The SCV64 interrupt is disabled from reaching the node when the
corresponding bit is set to “0”.
BitInterrupted Node
D0Node A
D1Node B
D2Node C
D3Node D
Part Number 500-00191
Revision 2.00
41
Monaco Technical ReferenceSpectrum Signal Processing
Interrupt Handling
The /KIPL[2..0] status bits, D[2..0], in the VSTATUS Register indicate the priority
level of the SCV64 interrupt. These bits reflect the state of the /KIPL lines from the
SCV64. If all three active-low bits are set to “1” (inactive), then an SCV64 interrupt did
not cause the INT4 interrupt.
If the interrupt was due to an SCV64 interrupt, it is serviced by performing an IACK
cycle to the SCV64. An IACK cycle is a special type of VME read cycle to a specific
location in the IACK cycle space (base address 016F 0000h).
For an IACK read cycle, bits D[0..7] of the VPAGE Register must be initialized in the
following way:
• KADDR0 (bit D0) is set to “0”
• The value of the /KIPL0 bit in the VSTATUS Register is inverted and placed in
the KADDR1 bit (bit D1)
• KSIZE0 (bit D2) is set to “1”
• KSIZE1 (bit D3) is set to “0”
• All three KFC bits (bits D[6..4]) are set to “1”
The /KIPL[2..1] status bits, D[2..1], in the VSTATUS Register determine the offset of
the address to read within the IACK cycle space.
• /KIPL2 is inverted to determine IACK address bit A3
• /KIPL1 is inverted to determine IACK address bit A2
The following table summarizes how the /KIPL[2..1] bits in the VSTATUS Register
initialize the VPAGE Register and set the IACK cycle address.
Table 12 KIPL Status Bits and the IACK Cycle
/KIPL2/KIPL1/KIPL0VPAGE KADDR1IACK Address
Spectrum Signal ProcessingMonaco Technical Reference
Interrupt Handling
SCV64 interrupts can be generated from the VMEbus (vectored) or internally by the
SCV64 (auto-vectored).
• If the interrupt was caused by an external VMEbus interrupt the SCV64 initiates an
/IACK cycle on the VMEbus. The /IACK cycle is acknowledged by the interrupter
which puts its interrupt vector on the lower 8 data bits of the DSP’s data bus.
• If the /KIPL lines were set due to an internal (auto-vectored) interrupt source the
SCV64 initiates an /IACK cycle on the VMEbus, but no value is place on the lower
8 data bits. The SCV64 terminates the cycle by asserting the /KAVEC signal.
The KAVEC bit (bit D3) in the VSTATUS Register can be read to determine which
type of interrupt was generated. After an IACK cycle is performed, it is set to “0” if the
value on the lower 8 bits is a valid interrupt vector; or to “1” if the value is not a valid
interrupt vector.
Auto-vectored interrupt sources can be cleared by accessing the SCV64 register set.
Refer to the SCV64 User Manual for more information.
8.7. Bus Error Interrupts
Bus error interrupts (BUSERR_x) are generated whenever an access cycle from a node
or SCV64 DMA to the VME bus causes the SCV64 to generate a bus error.
This interrupt is routed only to INT4 of the ‘C6x responsible for causing the VME bus
error. On-board logic routes enabled SCV64 interrupts and the inter-processor VINTx
interrupts to INT4 as well.
Any node can also determine the status of the bus error interrupts by reading the
VSTATUS Register at address 016D 8000h. A “1” in any of the following bit
positions of the register indicates which nodes have pending bus error interrupts.
BitNode Whose Access Caused the Bus Error
D4Node A
D5Node B
D6Node C
D7Node D
To clear the interrupt, the interrupted ‘C6x writes a “1” to the same bit in the
VSTATUS Register. It must also clear the appropriate bits in the SCV64 DCSR
register before the board can access the VME bus again.
Part Number 500-00191
Revision 2.00
43
Monaco Technical ReferenceSpectrum Signal Processing
Interrupt Handling
8.8. Inter-processor Interrupts
The Inter-processor interrupts (VINTx) are shared with the SCV interrupt. They allow
any processor to interrupt any other processor through the VINTx registers. There are
four of these registers; one for each of the processors.
To generate an interrupt to a particular processor, a “1” is written to bit D0 of the VINT
register corresponding to the processor to be interrupted. These registers are accessible
from any of the four processors. Node C, for example, can interrupt node B by writing
“1” to the VINTB Register (address 016D 8008h).
The VSTATUS Register (address 016D 8000h) also indicates that a node has a
pending interrupt whenever any of the following bits is set to “1”:
BitInterrupted Node
D8Node A
D9Node B
D10Node C
D11Node D
A processor clears an interrupt by clearing its corresponding bit VINTx register. In the
case where node C interrupts node B, for example, node B would clear the interrupt by
writing “0” to the VINTB Register (address 016D 8008h).
8.9. VME Host Interrupts To Any Node
A VME host can interrupt a particular node on the Monaco board using DSPINT in the
HPIC register of the Host Port Interface (HPI). Refer to the TMS320C6x documentation
for further information on using DSPINT.
44
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
9 Registers
This section provides a reference to the registers that are unique to the Monaco board.
Information for the registers within the SCV64 bus interface chip, the ACT8990 Test
Bus Controller (TBC), and the Hurricane PCI interface chip can be found in their
respective data sheets.
Most of the registers described in this section are accessed from the processor nodes. Of
these, most are shared among nodes A, B, C, and D. A few, though, are unique to each
node. The registers that are not accessible from the processor nodes are part of the VME
A24 Host Port Interfaces and to the TBC.
The following table summarizes the registers described in this section.
Table 13 Register Address Summary
Access
Register
PrivilegeBusAddress
VPAGE Register (for node A)R/WNode A only016D 0000h
VPAGE Register (for node B)R/WNode B only016D 0000h
VPAGE Register (for node C)R/WNode C only016D 0000h
VPAGE Register (for node D)R/WNode D only016D 0000h
This register sets certain SCV64 address and control lines in order to extend the address
range of the ‘C6x processors and set up the type of VME cycle to be performed. Each
node has its own register. Except for D7 all other reserved bits are disconnected; D7 will
store what is written to it. These register is undefined upon reset and should be
initialized. Refer to the SCV64 User Manual for complete information on these signals.
KADDR[31..20]
Sets the upper 12 address bits that are latched to the SCV64 when the
‘C6x accesses the VME address space. This extends the 20 address bits
of the ‘C6x to the full 32 bits of the VME address space. This allows a
‘C6x access the entire VME bus as a master by setting these bits to
1 Mbyte region being accessed. A write to this register latches data lines
D19..8 and presents them to the SCV64 upper address lines
KADDR31..20 respectively. For example, a write to the VPAGE register
with data equal to 8 0000h causes the next outbound VME cycle (base
address 0170 0000h) with offset 0x0 to be addressed at VME address
8000 0000h.
KFC[2..0]
Sets the access type as User or Supervisor Program, or Data accesses.
Directly affects the address modifiers used for the VME Master cycle.
KSIZE[1..0]
Sets the number of bytes transferred for VME Master cycles. Directly
affects D32, D16, or D8 access type.
KADDR[1..0]
These bits allow the node, which is little endian in order to access the
PEM and PMCs, to access the SCV64, which is big endian.
Note:
Although access to VPAGE is local to each processor node, any read or
write to the register requires that the Global Shared Bus to be acquired. The
DSP’s cycles are extended until any current Global Shared Bus operations are
complete when accessing the VPAGE Register.
46
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
This register is used by a processor to identify the source of an INT4 interrupt.
VINTD
Status of the user defined interrupt to node D. Set to “1” when another
processor has set the VINTD interrupt register. Active High.
VINTC
Status of the user defined interrupt to node C. Set to “1” when another
processor has set the VINTC interrupt register. Active High.
VINTB
Status of the user defined interrupt to node B. Set to “1” when another
processor has set the VINTB interrupt register. Active High.
VINTA
Status of the user defined interrupt to node A. Set to “1” when another
processor has set the VINTA interrupt register. Active High.
BUSERRD
Status of the last bus cycle access made to the SCV64 by node D, including
SCV64 register and VME master accesses. Set to “1” if there was an error.
Cleared by writing“80h” to the VSTATUS register. All other interrupts are
cleared when the source of the interrupt is cleared. This interrupt is cleared
on reset.
BUSERRC
Status of the last bus cycle access made to the SCV64 by node C, including
SCV64 register and VME master accesses. Set to “1” if there was an error.
Cleared by writing“40h” to the VSTATUS register. All other interrupts are
cleared when the source of the interrupt is cleared. This interrupt is cleared
on reset.
BUSERRB
Part Number 500-00191
Revision 2.00
Status of the last bus cycle access made to the SCV64 by node B, including
SCV64 register and VME master accesses. Set to “1” if there was an error.
Cleared by writing “20h” to the VSTATUS register. All other interrupts are
cleared when the source of the interrupt is cleared. This interrupt is cleared
47
Monaco Technical ReferenceSpectrum Signal Processing
Registers
on reset.
BUSERRA
KAVEC
/KIPL2..0
Status of the last bus cycle access made to the SCV64 by node A, including
SCV64 register and VME master accesses. Set to “1” if there was an error.
Cleared by writing “10h” to the VSTATUS register. All other interrupts are
cleared when the source of the interrupt is cleared. This interrupt is cleared
on reset.
Status of the interrupt vector last received on the data bus. High if the
vector was not valid. During the IACK cycle, a non-vectored interrupt
source causes this bit to be set, denoting a non-valid vector value on the
bus. This bit is cleared on reset. The next SCV64 register, IACK, or
VMEOUT cycle updates KAVEC. This signal is active high.
The interrupt level of pending interrupts in the SCV64. These signals are
active low. For example, a value of 0x0 indicates that interrupt level 7 is
pending.
48
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
VINTA Register
Address: 016D 8004h
D31....D8
Reserved
D7....D1D0
ReservedInterrupt
This register allows any processor to generate or clear an interrupt to node A. Upon reset
this value is ‘0’.
• To generate an interrupt to node A, set bit D0 of this register to “1”.
• To clear an interrupt to node A, set bit D0 of this register to “0”.
Part Number 500-00191
Revision 2.00
49
Monaco Technical ReferenceSpectrum Signal Processing
Registers
VINTB Register
Address: 016D 8008h
D31....D8
Reserved
D7....D1D0
ReservedInterrupt
This register allows any processor to generate or clear an interrupt to node B. Upon reset
this value is ‘0’.
• To generate an interrupt to node B, set bit D0 of this register to “1”.
• To clear an interrupt to node B, set bit D0 of this register to “0”.
50
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
VINTC Register
Address: 016D 800Ch
D31....D8
Reserved
D7....D1D0
ReservedInterrupt
This register allows any processor to generate or clear an interrupt to node C. Upon reset
this value is ‘0’.
• To generate an interrupt to node C, set bit D0 of this register to “1”.
• To clear an interrupt to node C, set bit D0 of this register to “0”.
Part Number 500-00191
Revision 2.00
51
Monaco Technical ReferenceSpectrum Signal Processing
Registers
VINTD Register
Address: 016D 8010h
D31....D8
Reserved
D7....D1D0
ReservedInterrupt
This register allows any processor to generate or clear an interrupt to node D. Upon reset
this value is ‘0’.
• To generate an interrupt to node D, set bit D0 of this register to “1”.
• To clear an interrupt to node D, set bit D0 of this register to “0”.
52
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
KIPL Enable Register
Address: 016D 8014h
D31....D8
Reserved
D7....D4D3D2D1D0
ReservedKIPL_ENDKIPL_ENCKIPL_ENBKIPL_ENA
The KIPL Enable Register is used to enable interrupts generated from the SCV64 to be
sent to a particular processor node. The /KIPL lines represent VME interrupts, location
monitor interrupt, SCV64 DMA, and SCV64 timer interrupts. These enable bits do not
affect the individual KBERR interrupt bits.
KIPL_END
When set to “1”, interrupts to node D that are generated from the SCV64
/KIPL lines are enabled. Active high.
KIPL_ENC
When set to “1”, interrupts to node C that are generated from the SCV64
/KIPL lines are enabled. Active high.
KIPL_ENB
When set to “1”, interrupts to node B that are generated from the SCV64
/KIPL lines are enabled. Active high.
KIPL_ENA
When set to “1”, interrupts to node A that are generated from the SCV64
/KIPL lines are enabled. Active high.
These bits are set to “0” upon reset.
Note:
/KIPL interrupts must also be enabled by register writes to the SCV64.
Refer to the SCV64 data book for further information.
Part Number 500-00191
Revision 2.00
53
Monaco Technical ReferenceSpectrum Signal Processing
Registers
DSP~LINK3 Register
Address: 016D 8018h
D31....D8
Reserved
D7....D2D1D0
ReservedASTRB_ENDL3_RESET
Processor node A uses this register assert or release reset to the DSP~LINK3 interface its
local bus. It is also used to control the operation of DSP~LINK3 standard fast accesses.
DL3_RESET
• Setting this bit (D0) to “1” asserts reset to the DSP~LINK3.
• Setting this bit (D0) to “0” releases the DSP~LINK3 from reset.
Set to “1” upon reset. Application code must set it to “0” to release the
DSP~LINK3 from reset.
ASTRB_EN
• Setting this bit (D1) to “1” enables ASTRB accesses to DSP~LINK3.
Accesses to the standard fast region when ASTRB_EN is set will be
/ASTRB accesses.
• Setting this bit (D1) to “0” disables ASTRB accesses to
DSP~LINK3. Accesses to the standard fast region when ASTRB_EN
is cleared will be /DSTRB accesses.
Set to “0” upon reset.
This read/write register is not accessible from nodes B, C, or D.
54
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
ID Register
Address: 016D 801Ch
D31....D8
Reserved
D7....D4D3D2D1D0
ReservedNode DNode CNode BNode A
This register allows DSP software to identify which processor it is running on. Each of
the four bits in the register correspond to a particular processor node. A node can read
the status of all four bits but can only write to its own bit.
To identify its processor, the DSP program first locks the Global Shared Bus for its use
by asserting TOUT0. It then reads the value of this register and stores the result. This
value is toggled (inverted) and written back to the register. The register is read once
again and compared to the first reading to determine which bit was changed by the write
operation. Because only the bit corresponding to the node can be changed, this bit will
identify the node that the application is running on. TOUT0 should then be de-asserted to
release the Global Shared Bus.
Part Number 500-00191
Revision 2.00
55
Monaco Technical ReferenceSpectrum Signal Processing
Registers
VME A24 Status Register
VME A24 Secondary Base Address + 1000h
D31....D8
Reserved
D7....D4D3D2D1D0
ReservedHINT_DHINT_CHINT_BHINT_A
The VME host reads this register to determine the state of the HINT lines from each
processor node. Each bit corresponds to one of the four processor nodes. The state of the
bit is simply a reflection of the HINT bit value in the corresponding ‘C6x HPIC register.
A “1” in the bit position indicates that the corresponding ‘C6x processor has requested
an interrupt.
HINT_A
HINT_B
HINT_C
HINT_D
Bit D0 is set to “1” when node A is requesting a host interrupt.
Bit D1 is set to “1” when node B is requesting a host interrupt.
Bit D2 is set to “1” when node C is requesting a host interrupt.
Bit D3 is set to “1” when node D is requesting a host interrupt.
This read only register is accessed from the VME A24 bus. It is located at offset 1000h
from the base address set by jumper JP1 (A23..A17).
56
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Registers
VME A24 Control Register
VME A24 Secondary Base Address + 1004h
D31....D8
Reserved
D7....D1D0
Reserved/Reset
The VME host uses this register to reset all Monaco board devices except for the SCV64
bus interface chip.
• To reset the board, the VME host writes a “0” to bit D0.
This read/write register is accessed from the VME A24 bus. It is located at offset 1004h
from the base address set by jumper JP1 (A23..A17).
Part Number 500-00191
Revision 2.00
57
Monaco Technical ReferenceSpectrum Signal Processing
Registers
58
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Specifications
10 Specifications
10.1. Board Identification
Power, current, and data throughput specifications depend upon the type and version of
processors used on the board.
Monaco
Monaco boards currently use the TMS320C6201B
DSP.
Earlier Monaco versions used the TMS320C6201.
Monaco boards with this processor may have heat
sinks or fans installed over the DSPs due to the
higher power consumption of the earlier DSP.
Monaco67
Monaco67 boards use the TMS320C6701 DSP.
The processor type and version can be identified by examining the DSPs on the board;
earlier DSPs have the marking “C21”, while TMS320C6201B chips are marked “C31”.
Boards equipped with earlier TMS320C6201 revision 2.1 chips may also have heat sinks
or fans attached to the cover of the DSPs.
The board’s 600-level part number may also be used to determine which DSPs are used
on the board. The following table presents a partial list of Monaco part numbers.
-12 Volts0 Amps0 Amps0 Amps
Power18 Watts44 Watts15 Watts
Height6U
Width1 VME slot
Operating Temperature0° C to 50° C
Monaco
TMS320C6201
Monaco67
TMS320C6701
60
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Specifications
10.3. Performance and Data Throughput
The following table gives the data transfer rates between different memory, processor
and interface resources on the Monaco board. Monaco boards using the TMS320C6201
processor have a clock speed of 200 MHz; Monaco67 boards using the TMS230C6701
processor have a clock speed of 167 MHz.
Table 15 Data Access/Transfer Performance
Clock SpeedUnits
SourceTarget200167MHzComment
‘C6xLocal SBSRAM400333 MB/s
Local SDRAM400333 MB/s
PEM Site400333 MB/s
Global SRAM read8874 MB/s
Global SRAM write10083 MB/s
DSP~LINK3 Standard1512.5 MB/s
DSP~LINK3 Standard Fast2824 MB/s
Hurricane Registers115138 ns
VMEbus (master) read2 MB/sCoupled read. Typical value for a "real" slave, which is slower
than for an "ideal" VME slave.
VMEbus (master) write9 MB/sDe-coupled write. Typical value for a "real" slave, which is
slower than for an "ideal" VME slave.
VME HostGlobal SRAM40 MB/s
Hurricane Registers150 ns
HPI read14 MB/sMaximum speed from internal ‘C6x memory when the ‘C6x is
not accessing memory
HPI write28 MB/sMaximum speed to internal ‘C6x memory when the ‘C6x is not
Monaco Technical ReferenceSpectrum Signal Processing
Specifications
62
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
Connector Pinouts
11 Connector Pinouts
CBA
1 2
1 2
JN7
JN6
PEM1PEM
2
59 60
59 60
1 2
1 2
JN8JN9
PEM1PEM
2
59 60 59 60
1 2
1 2
JN10JN11
PEM1PEM
2
Node
D
Node
C
Node
B
Node D
‘C6x
Node C
‘C6x
Node B
‘C6x
1
VME
P1
CBA
32
59 60
1 2
JN12
PEM1PEM
59 60
13
14
JTAG IN
Connector
59 60
1 2
JN13
Node
A
2
59 60
1
13
2
14
J1
JTAG OUT
Connector
1
J3
2
J2
2
1
DSP~LINK3 Ribbon Cable Connector
J8
1 2
JN5
49 50
Node A
‘C6x
1 2
JN1JN2
63 64
68
67
1 2
63 64
1 2
JN4
63 64
DCBAZ
1
VME
P2
DCBAZ
32
Figure 13 Connector Layout
Part Number 500-00191
Revision 2.00
63
Monaco Technical ReferenceSpectrum Signal Processing
Connector Pinouts
11.1. VME Connectors
VME connector P1 is a standard 96-pin DIN 3-row connector. VME connector P2 is
standard 160-pin DIN 5-row connector. The Monaco board will be factory configured to
route either the PMC or DSP~LINK3 connector to P2. Refer to the appropriate pinout for
your board for this.
Spectrum Signal ProcessingMonaco Technical Reference
Connector Pinouts
11.4. JTAG Connectors
Both JTAG connectors use 2 x 7, 0.1” x 0.1” bare pin headers.
Table 25 JTAG IN Connector Pinout
Pin #SignalPin #Signal
1TMS2/TRST
3TDI4GND
5PD6key (no pin)
7TDO8GND
9TCK_RET10GND
11TCK12GND
13EMU014EMU1
Table 26 JTAG OUT Connector
Pin #SignalPin #Signal
1TMS2/TRST
3TDO4key (no pin)
5PD6GND
7TDI8GND
9TCK_RET10GND
11TCK12GND
13EMU014EMU1
Part Number 500-00191
Revision 2.00
73
Monaco Technical ReferenceSpectrum Signal Processing
Connector Pinouts
74
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference
SCV64 Register Values
Appendix A: SCV64 Register Values
This appendix briefly describes the default register settings for the SCV64 on the
Monaco board. The following table shows the default values that are programmed into
the registers by the initialization code supplied with the Monaco board.
Table 27 SCV64 Register Initialization
‘C6x Address RegisterValue
016E 0000hDMA Local Address00000000h
016E 0004hDMA VMEbus Address00000000h
016E 0008hDMA Transfer Count00000000h
016E 000ChControl and Status00000000h
016E 0010hVMEbus Slave Base AddressSee notes
016E 0014hRx FIFO DataRead only
016E 0018hRx FIFO Address RegisterRead only
016E 001ChRx FIFO Control RegisterRead only
016E 0020hVMEbus/VSB Bus Select00000000h
016E 0024hVMEbus Interrupter Vector00000000h
016E 0028hAccess Protect Boundary00000000h
016E 002ChTx FIFO Data Output LatchRead only
016E 0030hTx FIFO Address Output LatchRead only
016E 0034hTx FIFO AM Code and Control Bit LatchRead only
016E 0038hLocation Monitor FIFO Read PortRead only
016E 003ChSCV64 Mode Control24000005h
016E 0040hSlave A64 Base Address00000000h
016E 0044hMaster A64 Base Address00000000h
016E 0048hLocal Address GeneratorRead only
016E 004ChDMA VMEbus Transfer CountRead only
016E 0050h
toReserved
016E 007Ch
016E 0080hStatus Register 000000000h
016E 0084hStatus Register 100000080h
016E 0088hGeneral Control Register0000001Ch
016E 008ChVMEbus Interrupter Requester00000000h
016E 0090hVMEbus Requester Register000000CFh
016E 0094hVMEbus Arbiter Register00000034h
016E 0098hID RegisterRead only
016E 009ChControl and Status Register00000002h
016E 00A0hLevel 7 Interrupt Status RegisterRead only
Part Number 500-00191
Revision 2.00
75
Monaco Technical ReferenceSpectrum Signal Processing
SCV64 Register Values
Table 27 SCV64 Register Initialization
‘C6x Address RegisterValue
016E 00A4hLocal Interrupt Status RegisterRead only
016E 00A8hLevel 7 Interrupt Enable Register00000001h
016E 00AChLocal Interrupt Enable Register00000000h
016E 00B0hVMEbus Interrupt Enable Register00000000h
016E 00B4hLocal Interrupts 1 and 0 Control Register 00000089h
016E 00B8hLocal Interrupts 3 and 2 Control Register 000000A8h
016E 00BChLocal Interrupts 5 and 4 Control Register 000000CBh
016E 00C0hMiscellaneous control register00000000h
016E 00C4hDelay line control registerDynamically configured by SCV64 initialization routine
016E 00C8hDelay line status register 1Dynamically configured by SCV64 initialization routine
016E 00CChDelay line status register 2Dynamically configured by SCV64 initialization routine
016E 00D0hDelay line status register 3Dynamically configured by SCV64 initialization routine
016E 00D4hMailbox register 0Not used
016E 00D8hMailbox register 1Not used
016E 00DChMailbox register 2Not used
016E 00E0hMailbox register 3Not used
016E 00E4h
toReserved
016E 01FCh
76
Part Number 500-00191
Revision 2.00
Spectrum Signal ProcessingMonaco Technical Reference