Dual symmetric 600 MHz high performance Blackfin cores
328K bytes of on-chip memory (see memory information
on Page 3)
Each Blackfin core includes:
Two 16-bit MACs, two 40-bit ALUs, four 8-bit video ALUs,
40-bit shifter
RISC-like register and instruction model for ease of program-
ming and compiler-friendly support
Advanced debug, trace, and performance monitoring
0.8 V – 1.2 V core V
3.3 V and 2.5 V tolerant I/O
256-ball mini-BGA and 297-ball PBGA package options
IRQ CONTROL/
WATCHDOG
TIMER
VOLTAGE
REGULATOR
DD
B
PERIPHERALS
Two parallel input/output peripheral interface units support-
ing ITU-R 656 video and glueless interface to analog front
end ADCs
Two dual channel, full duplex synchronous serial ports sup-
porting eight stereo I2S channels
Dual 16-channel DMA controllers and one internal memory
DMA controller
12 general-purpose 32-bit timer/counters, with PWM
capability
SPI-compatible port
UART with support for IrDA
Dual watchdog timers
48 programmable flags
On-chip phase-locked loop capable of 1× to 63 × frequency
multiplication
B
IRQ CONTROL/
WATCHDOG
TIMER
®
JTAG TEST
EMULATION
UART
®
IrDA
L1
INSTRUCTION
MEMORY
BOOT ROM
Blackfin and the Blackfin logo are registered trademarks of Analog Devices, Inc.
Rev. 0
Information furnished by Analog Devices is believed to be accurate and reliable.
However, no responsibility is assumed by Analog Devices for its use, nor for any
infringements of patents or other rights of third parties that may result from its use.
Specifications subject to change without notice. No license is granted by implication
or otherwise under any patent or patent rights of Analog Devices. Trademarks and
registered trademarks are the property of their respective owners.
The ADSP-BF561 processor is a high performance member of
the Blackfin family of products targeting a variety of multimedia
and telecommunications applications. At the heart of this device
are two independent Analog Devices Blackfin processors. These
Blackfin processors combine a dual-MAC state-of-the-art signal
processing engine, the advantage of a clean, orthogonal RISClike microprocessor instruction set, and single instruction, multiple data (SIMD) multimedia capabilities in a single instruction
set architecture. The ADSP-BF561 device integrates a generalpurpose set of digital imaging peripherals.
The ADSP-BF561 processor has 328K bytes of on-chip memory.
Each Blackfin core includes:
• 16K bytes of Instruction SRAM/Cache
• 16K bytes of Instruction SRAM
• 32K bytes of Data SRAM/Cache
• 32K bytes of Data SRAM
• 4K bytes of Scratchpad SRAM
ADDRESS ARITHMETIC UNIT
Additional on-chip memory peripherals include:
• 128K bytes of Low Latency On-Chip L2 SRAM
• Four-Channel Internal Memory DMA Controller
• External Memory Controller with Glueless Support for
SDRAM, Mobile SDRAM, SRAM, and Flash.
PORTABLE LOW POWER ARCHITECTURE
Blackfin processors provide world-class power management
and performance for embedded signal processing applications.
Blackfin processors are designed in a low power and low voltage
design methodology and feature Dynamic Power Management.
Dynamic Power Management is the ability to vary both the voltage and frequency of operation to significantly lower the overall
power dissipation. This translates into an exponential reduction
in power dissipation, providing longer battery life to portable
applications.
BLACKFIN PROCESSOR CORE
As shown in Figure 2, each Blackfin core contains two multiplier/accumulators (MACs), two 40-bit ALUs, four video ALUs,
and a single shifter. The computational units process 8-bit, 16bit, or 32-bit data from the register file.
LD032BITS
LD132BITS
SD 3 2 BI TS
SP
FP
P5
P4
P3
P2
P1
P0
R7.L
R7.H
R7
R6
R5
R4
R3
R2
R1
R0
R6.H
R5.H
R4.H
R3.H
R2.H
R1.H
R0.H
R6.L
R5.L
R4.L
R3.L
R2.L
R1.L
R0.L
I3
I2
I1
I0
BARREL
SHIFTER
L3
B3
L2
L1
L0
16
A0A1
DATA ARITHMETIC UNIT
M3
B2
M2
B1
M1
B0
M0
8888
4040
DAG0DA G 1
16
SEQUENCER
ALIGN
DECODE
LOOP BUFFER
CONTRO L
UN IT
Figure 2. Blackfin Processor Core
Rev. 0 | Page 3 of 52 | January 2005
Page 4
ADSP-BF561
Each MAC performs a 16-bit by 16-bit multiply in every cycle,
with accumulation to a 40-bit result, providing eight bits of
extended precision. The ALUs perform a standard set of arithmetic and logical operations. With two ALUs capable of
operating on 16- or 32-bit data, the flexibility of the computation units covers the signal processing requirements of a varied
set of application needs.
Each of the two 32-bit input registers can be regarded as two
16-bit halves, so each ALU can accomplish very flexible single
16-bit arithmetic operations. By viewing the registers as pairs of
16-bit operands, dual 16-bit or single 32-bit operations can be
accomplished in a single cycle. By further taking advantage of
the second ALU, quad 16-bit operations can be accomplished
simply, accelerating the per cycle throughput.
The powerful 40-bit shifter has extensive capabilities for performing shifting, rotating, normalization, extraction, and
depositing of data. The data for the computational units is
found in a multiported register file of sixteen 16-bit entries or
eight 32-bit entries.
A powerful program sequencer controls the flow of instruction
execution, including instruction alignment and decoding. The
sequencer supports conditional jumps and subroutine calls, as
well as zero overhead looping. A loop buffer stores instructions
locally, eliminating instruction memory accesses for tight
looped code.
Two data address generators (DAGs) provide addresses for
simultaneous dual operand fetches from memory. The DAGs
share a register file containing four sets of 32-bit Index, Modify,
Length, and Base registers. Eight additional 32-bit registers provide pointers for general indexing of variables and stack
locations.
Blackfin processors support a modified Harvard architecture in
combination with a hierarchical memory structure. Level 1 (L1)
memories are those that typically operate at the full processor
speed with little or no latency. Level 2 (L2) memories are other
memories, on-chip or off-chip, that may take multiple processor
cycles to access. At the L1 level, the instruction memory holds
instructions only. The two data memories hold data, and a dedicated scratchpad data memory stores stack and local variable
information. At the L2 level, there is a single unified memory
space, holding both instructions and data.
In addition, half of L1 instruction memory and half of L1 data
memory may be configured as either Static RAMs (SRAMs) or
caches. The Memory Management Unit (MMU) provides memory protection for individual tasks that may be operating on the
core and may protect system registers from unintended access.
The architecture provides three modes of operation: user mode,
supervisor mode, and emulation mode. User mode has
restricted access to certain system resources, thus providing a
protected software environment, while supervisor mode has
unrestricted access to the system and core resources.
The Blackfin instruction set has been optimized so that 16-bit
op-codes represent the most frequently used instructions,
resulting in excellent compiled code density. Complex DSP
instructions are encoded into 32-bit op-codes, representing fully
featured multifunction instructions. Blackfin processors sup-
port a limited multi-issue capability, where a 32-bit instruction
can be issued in parallel with two 16-bit instructions, allowing
the programmer to use many of the core resources in a single
instruction cycle.
The Blackfin assembly language uses an algebraic syntax for
ease of coding and readability. The architecture has been optimized for use in conjunction with the VisualDSP C/C++
compiler, resulting in fast and efficient software
implementations.
MEMORY ARCHITECTURE
The ADSP-BF561 views memory as a single unified 4G byte
address space, using 32-bit addresses. All resources including
internal memory, external memory, and I/O control registers
occupy separate sections of this common address space. The
memory portions of this address space are arranged in a hierarchical structure to provide a good cost/performance balance of
some very fast, low latency memory as cache or SRAM very
close to the processor, and larger, lower cost and performance
memory systems farther away from the processor. The ADSPBF561 memory map is shown in Figure 3.
The L1 memory system in each core is the highest performance
memory available to each Blackfin core. The L2 memory provides additional capacity with lower performance. Lastly, the
off-chip memory system, accessed through the External Bus
Interface Unit (EBIU), provides expansion with SDRAM, flash
memory, and SRAM, optionally accessing more than
768M bytes of physical memory. The memory DMA controllers
provide high bandwidth data movement capability. They can
perform block transfers of code or data between the internal
L1/L2 memories and the external memory spaces.
Internal (On-chip) Memory
The ADSP-BF561 has four blocks of on-chip memory providing
high bandwidth access to the core.
The first is the L1 instruction memory of each Blackfin core
consisting of 16K bytes of four-way set-associative cache memory and 16K bytes of SRAM. The cache memory may also be
configured as an SRAM. This memory is accessed at full processor speed. When configured as SRAM, each of the two 16K
banks of memory is broken into 4K sub-banks which can be
independently accessed by the processor and DMA.
The second on-chip memory block is the L1 data memory of
each Blackfin core which consists of four banks of 16K bytes
each. Two of the L1 data memory banks can be configured as
one way of a two-way set-associative cache or as an SRAM. The
other two banks are configured as SRAM. All banks are accessed
at full processor speed. When configured as SRAM, each of the
four 16K banks of memory is broken into 4K sub-banks which
can be independently accessed by the processor and DMA.
The third memory block associated with each core is a 4K byte
scratchpad SRAM which runs at the same speed as the L1 memories, but is only accessible as data SRAM (it cannot be
configured as cache memory and is not accessible via DMA).
RESERVED
ASYNC MEMORY BANK 3
ASYNC MEMORY BANK 2
ASYNC MEMORY BANK 1
ASYNC MEMORY BANK 0
RESERVED
SDRAM BANK 3
SDRAM BANK 2
SDRAM BANK 1
SDRAM BANK 0
0xFF80 0000
0xFF70 1000
0xFF70 0000
0xFF61 4000
0xFF61 0000
0xFF60 4000
0xFF60 0000
0xFF50 8000
0xFF50 4000
0xFF50 0000
0xFF40 8000
0xFF40 4000
0xFF40 0000
EXTERNAL MEMORY
INTERNAL MEMORY
Figure 3. Memory Map
The fourth on-chip memory system is the L2 SRAM memory
array which provides 128K bytes of high speed SRAM operating
at one half the frequency of the core, and slightly longer latency
than the L1 memory banks. The L2 memory is a unified instruction and data memory and can hold any mixture of code and
data required by the system design. The Blackfin cores share a
dedicated low latency 64-bit wide data path port into the L2
SRAM memory.
Each Blackfin core processor has its own set of core Memory
Mapped Registers (MMRs) but share the same system MMR
registers and 128K bytes L2 SRAM memory.
External (Off-Chip) Memory
The ADSP-BF561 external memory is accessed via the External
Bus Interface Unit (EBIU). This interface provides a glueless
connection to up to four banks of synchronous DRAM
(SDRAM) as well as up to four banks of asynchronous memory
devices, including flash, EPROM, ROM, SRAM, and memory
mapped I/O devices.
The PC133-compliant SDRAM controller can be programmed
to interface to up to four banks of SDRAM, with each bank containing between 16M bytes and 128M bytes providing access to
up to 512M bytes of SDRAM. Each bank is independently programmable and is contiguous with adjacent banks regardless of
the sizes of the different banks or their placement. This allows
Rev. 0 | Page 5 of 52 | January 2005
Page 6
ADSP-BF561
flexible configuration and upgradability of system memory
while allowing the core to view all SDRAM as a single, contiguous, physical address space.
The asynchronous memory controller can also be programmed
to control up to four banks of devices with very flexible timing
parameters for a wide variety of devices. Each bank occupies a
64M byte segment regardless of the size of the devices used so
that these banks will only be contiguous if fully populated with
64M bytes of memory.
I/O Memory Space
Blackfin processors do not define a separate I/O space. All
resources are mapped through the flat 32-bit address space. Onchip I/O devices have their control registers mapped into memory mapped registers (MMRs) at addresses near the top of the
4G byte address space. These are separated into two smaller
blocks, one which contains the control MMRs for all core functions, and the other which contains the registers needed for
setup and control of the on-chip peripherals outside of the core.
The core MMRs are accessible only by the core and only in
supervisor mode and appear as reserved space by on-chip
peripherals. The system MMRs are accessible by the core in
supervisor mode and can be mapped as either visible or reserved
to other devices, depending on the system protection model
desired.
Booting
The ADSP-BF561 contains a small boot kernel, which configures the appropriate peripheral for booting. If the ADSP-BF561
is configured to boot from boot ROM memory space, the processor starts executing from the on-chip boot ROM.
Event Handling
The event controller on the ADSP-BF561 handles all asynchronous and synchronous events to the processor. The ADSPBF561 provides event handling that supports both nesting and
prioritization. Nesting allows multiple event service routines to
be active simultaneously. Prioritization ensures that servicing of
a higher priority event takes precedence over servicing of a
lower priority event. The controller provides support for five
different types of events:
• Emulation—An emulation event causes the processor to
enter emulation mode, allowing command and control of
the processor via the JTAG interface.
• Reset—This event resets the processor.
• Non-Maskable Interrupt (NMI)—The NMI event can be
generated by the software watchdog timer or by the NMI
input signal to the processor. The NMI event is frequently
used as a power-down indicator to initiate an orderly shutdown of the system.
• Exceptions—Events that occur synchronously to program
flow, i.e., the exception will be taken before the instruction
is allowed to complete. Conditions such as data alignment
violations or undefined instructions cause exceptions.
• Interrupts—Events that occur asynchronously to program
flow. They are caused by timers, peripherals, input pins,
and an explicit software instruction.
Each event has an associated register to hold the return address
and an associated “return from event” instruction. When an
event is triggered, the state of the processor is saved on the
supervisor stack.
The ADSP-BF561 event controller consists of two stages: the
Core Event Controller (CEC) and the System Interrupt Controller (SIC). The Core Event Controller works with the System
Interrupt Controller to prioritize and control all system events.
Conceptually, interrupts from the peripherals enter into the
SIC, and are then routed directly into the general-purpose
interrupts of the CEC.
Core Event Controller (CEC)
The CEC supports nine general-purpose interrupts (IVG15–7),
in addition to the dedicated interrupt and exception events. Of
these general-purpose interrupts, the two lowest priority interrupts (IVG15–14) are recommended to be reserved for software
interrupt handlers, leaving seven prioritized interrupt inputs to
support the peripherals of the ADSP-BF561. Table 1 describes
the inputs to the CEC, identifies their names in the Event Vector
Table (EVT), and lists their priorities.
The System Interrupt Controller provides the mapping and
routing of events from the many peripheral interrupt sources to
the prioritized general-purpose interrupt inputs of the CEC.
Rev. 0 | Page 6 of 52 | January 2005
Page 7
ADSP-BF561
Although the ADSP-BF561 provides a default mapping, the user
can alter the mappings and priorities of interrupt events by writing the appropriate values into the Interrupt Assignment
Registers (SIC_IAR7–0). Table 2 describes the inputs into the
SIC and the default mappings into the CEC.
The ADSP-BF561 provides the user with a very flexible mechanism to control the processing of events. In the CEC, three
registers are used to coordinate and control events. Each of the
registers is 16 bits wide, while each bit represents a particular
event class.
• CEC Interrupt Latch Register (ILAT)—The ILAT register
indicates when events have been latched. The appropriate
bit is set when the processor has latched the event and
cleared when the event has been accepted into the system.
Rev. 0 | Page 7 of 52 | January 2005
Page 8
ADSP-BF561
This register is updated automatically by the controller, but
may be written only when its corresponding IMASK bit is
cleared.
• CEC Interrupt Mask Register (IMASK)—The IMASK register controls the masking and unmasking of individual
events. When a bit is set in the IMASK register, that event is
unmasked and will be processed by the CEC when asserted.
A cleared bit in the IMASK register masks the event
thereby preventing the processor from servicing the event
even though the event may be latched in the ILAT register.
This register may be read from or written to while in supervisor mode. (Note that general-purpose interrupts can be
globally enabled and disabled with the STI and CLI
instructions.)
• CEC Interrupt Pending Register (IPEND)—The IPEND
register keeps track of all nested events. A set bit in the
IPEND register indicates the event is currently active or
nested at some level. This register is updated automatically
by the controller but may be read while in supervisor mode.
The SIC allows further control of event processing by providing
six 32-bit interrupt control and status registers. Each register
contains a bit corresponding to each of the peripheral interrupt
events shown in Table 2.
• SIC Interrupt Mask Register
(SIC_IMASK0, SIC_IMASK1)—
This register controls the masking and unmasking of each
peripheral interrupt event. When a bit is set in the register,
that peripheral event is unmasked and will be processed by
the system when asserted. A cleared bit in the register
masks the peripheral event thereby preventing the processor from servicing the event.
• SIC Interrupt Status Register
(SIC_ISR0, SIC_ISR1)—
As multiple peripherals can be mapped to a single event,
this register allows the software to determine which peripheral event source triggered the interrupt. A set bit indicates
the peripheral is asserting the interrupt; a cleared bit indicates the peripheral is not asserting the event.
• SIC Interrupt Wakeup Enable Register
(SIC_IWR0, SIC_IWR1)—
By enabling the corresponding bit in this register, each
peripheral can be configured to wake up the processor,
should the processor be in a powered-down mode when
the event is generated.
Because multiple interrupt sources can map to a single generalpurpose interrupt, multiple pulse assertions can occur simultaneously, before or during interrupt processing for an interrupt
event already detected on this interrupt input. The IPEND register contents are monitored by the SIC as the interrupt
acknowledgement.
The appropriate ILAT register bit is set when an interrupt rising
edge is detected (detection requires two core clock cycles). The
bit is cleared when the respective IPEND register bit is set. The
IPEND bit indicates that the event has entered into the processor pipeline. At this point the CEC will recognize and queue the
next rising edge event on the corresponding event input. The
minimum latency from the rising edge transition of the generalpurpose interrupt to the IPEND output asserted is three core
clock cycles; however, the latency can be much higher, depending on the activity within and the mode of the processor.
DMA CONTROLLERS
The ADSP-BF561 has multiple, independent DMA controllers
that support automated data transfers with minimal overhead
for the DSP core. DMA transfers can occur between the ADSPBF561 internal memories and any of its DMA-capable peripherals. Additionally, DMA transfers can be accomplished between
any of the DMA-capable peripherals and external devices connected to the external memory interfaces, including the
SDRAM controller and the asynchronous memory controller.
DMA-capable peripherals include the SPORTs, SPI port,
UART, and PPI. Each individual DMA-capable peripheral has
at least one dedicated DMA channel.
The ADSP-BF561 DMA controllers support both 1-dimensional (1D) and 2-dimensional (2D) DMA transfers. DMA
transfer initialization can be implemented from registers or
from sets of parameters called descriptor blocks.
The 2D DMA capability supports arbitrary row and column
sizes up to 64K elements by 64K elements, and arbitrary row
and column step sizes up to ± 32K elements. Furthermore, the
column step size can be less than the row step size, allowing
implementation of interleaved data streams. This feature is
especially useful in video applications where data can be deinterleaved on the fly.
Examples of DMA types supported by the ADSP-BF561 DMA
controllers include:
• A single linear buffer that stops upon completion.
• A circular autorefreshing buffer that interrupts on each full
or fractionally full buffer.
• 1D or 2D DMA using a linked list of descriptors.
• 2D DMA using an array of descriptors, specifying only the
base DMA address within a common page.
In addition to the dedicated peripheral DMA channels, each
DMA Controller has four memory DMA channels provided for
transfers between the various memories of the ADSP-BF561
system. These enable transfers of blocks of data between any of
the memories—including external SDRAM, ROM, SRAM, and
flash memory—with minimal processor intervention. Memory
DMA transfers can be controlled by a very flexible descriptorbased methodology or by a standard register-based autobuffer
mechanism.
Further, the ADSP-BF561 has a four channel Internal Memory
DMA (IMDMA) Controller. The IMDMA Controller allows
data transfers between any of the internal L1 and L2 memories.
WATCHDOG TIMERS
Each ADSP-BF561 core includes a 32-bit timer, which can be
used to implement a software watchdog function. A software
watchdog can improve system availability by forcing the processor to a known state, via generation of a hardware reset, nonmaskable interrupt (NMI), or general-purpose interrupt, if the
Rev. 0 | Page 8 of 52 | January 2005
Page 9
ADSP-BF561
timer expires before being reset by software. The programmer
initializes the count value of the timer, enables the appropriate
interrupt, then enables the timer. Thereafter, the software must
reload the counter before it counts to zero from the programmed value. This protects the system from remaining in an
unknown state where software, which would normally reset the
timer, has stopped running due to an external noise condition
or software error.
After a reset, software can determine if the watchdog was the
source of the hardware reset by interrogating a status bit in the
timer control register, which is set only upon a watchdog generated reset.
The timer is clocked by the system clock (SCLK) at a maximum
frequency of f
SCLK
.
SERIAL PORTS
The ADSP-BF561 incorporates two dual-channel synchronous
serial ports (SPORT0 and SPORT1) for serial and multiprocessor communications. The SPORTs support the following
features:
2
S capable operation.
•I
• Bidirectional operation—Each SPORT has two sets of independent transmit and receive pins, enabling eight channels
2
of I
S stereo audio.
• Buffered (8-deep) transmit and receive ports—Each port
has a data register for transferring data words to and from
other DSP components and shift registers for shifting data
in and out of the data registers.
• Clocking—Each transmit and receive port can either use an
external serial clock or generate its own, in frequencies
ranging from (f
/131,070) Hz to (f
SCLK
• Word length—Each SPORT supports serial data words
from 3 to 32 bits in length, transferred most significant bit
first or least significant bit first.
• Framing—Each transmit and receive port can run with or
without frame sync signals for each data word. Frame sync
signals can be generated internally or externally, active high
or low, and with either of two pulse widths and early or late
frame sync.
• Companding in hardware—Each SPORT can perform
A-law or µ-law companding according to ITU recommendation G.711. Companding can be selected on the transmit
and/or receive channel of the SPORT without additional
latencies.
• DMA operations with single-cycle overhead—Each SPORT
can automatically receive and transmit multiple buffers of
memory data. The DSP can link or chain sequences of
DMA transfers between a SPORT and memory.
SCLK
/2) Hz.
• Interrupts—Each transmit and receive port generates an
interrupt upon completing the transfer of a data word or
after transferring an entire data buffer or buffers through
DMA.
• Multichannel capability—Each SPORT supports 128 channels out of a 1,024-channel window and is compatible with
the H.100, H.110, MVIP-90, and HMVIP standards.
SERIAL PERIPHERAL INTERFACE (SPI) PORT
The ADSP-BF561 has one SPI-compatible port that enables the
processor to communicate with multiple SPI-compatible
devices.
The SPI interface uses three pins for transferring data: two data
pins (Master Output-Slave Input, MOSIx, and Master InputSlave Output, MISO) and a clock pin (Serial Clock, SCK). One
SPI chip select input pin (SPISS
) lets other SPI devices select the
DSP, and seven SPI chip select output pins (SPISEL7–1) let the
DSP select other SPI devices. The SPI select pins are reconfigured programmable flag pins. Using these pins, the SPI ports
provide a full duplex, synchronous serial interface, which supports both master and slave modes and multimaster
environments.
The baud rate and clock phase/polarities for the SPI port are
programmable (see SPI Clock Rate equation), and each has an
integrated DMA controller, configurable to support transmit or
receive data streams. The SPI DMA controller can only service
unidirectional accesses at any given time.
f
SCLK
SPI clock rate
-----------------------------------
=
2 SPIBAUD×
During transfers, the SPI port simultaneously transmits and
receives by serially shifting data in and out on its two serial data
lines. The serial clock line synchronizes the shifting and sampling of data on the two serial data lines.
UART PORT
The ADSP-BF561 provides a full duplex Universal Asynchronous Receiver/Transmitter (UART) port, fully compatible with
PC-standard UARTs. The UART port provides a simplified
UART interface to other peripherals or hosts, supporting full
duplex, DMA-supported, asynchronous transfers of serial data.
The UART port includes support for 5 to 8data bits; 1 or 2stop
bits; and none, even, or odd parity. The UART port supports
two modes of operation, as follows:
• PIO (Programmed I/O)—The processor sends or receives
data by writing or reading I/O-mapped UATX or UARX
registers, respectively. The data is double buffered on both
transmit and receive.
• DMA (Direct Memory Access)—The DMA controller
transfers both transmit and receive data. This reduces the
number and frequency of interrupts required to transfer
data to and from memory. The UART has two dedicated
Rev. 0 | Page 9 of 52 | January 2005
Page 10
ADSP-BF561
DMA channels, one for transmit and one for receive. These
DMA channels have lower priority than most DMA channels because of their relatively low service rates.
The baud rate (see UART clock rate equation), serial data format, error code generation and status, and interrupts for the
UART port are programmable. In the UART clock rate equation, the divisor (D) can be 1 to 65536.
f
SCLK
----------------
UART clock rate
=
16 D×
The UART’s programmable features include:
• Supporting bit rates ranging from (f
(f
/16) bits per second.
SCLK
/1048576) to
SCLK
• Supporting data formats from 7 to 12 bits per frame.
• Both transmit and receive operations can be configured to
generate maskable interrupts to the processor.
In conjunction with the general-purpose timer functions, autobaud detection is supported.
The capabilities of the UART are further extended with support
for the Infrared Data Association (IrDA
®
) Serial Infrared Physi-
cal Layer Link Specification (SIR) protocol.
PROGRAMMABLE FLAGS
The ADSP-BF561 has 48 bidirectional, general-purpose I/O,
programmable flag (PF47–0) pins. The programmable flag pins
have special functions for SPI port operation. Each programmable flag can be individually controlled by manipulation of the
flag control, status, and interrupt registers as follows:
• Flag Direction Control Register—Specifies the direction of
each individual PFx pin as input or output.
• Flag Control and Status Registers—Rather than forcing the
software to use a read-modify-write process to control the
setting of individual flags, the ADSP-BF561 employs a
"write one to set" and "write one to clear" mechanism that
allows any combination of individual flags to be set or
cleared in a single instruction, without affecting the level of
any other flags. Two control registers are provided, one
register is written-to in order to set flag values, while
another register is written-to in order to clear flag values.
Reading the flag status register allows software to interrogate the sense of the flags.
• Flag Interrupt Mask Registers—The Flag Interrupt Mask
Registers allow each individual PFx pin to function as an
interrupt to the processor. Similar to the Flag Control Registers that are used to set and clear individual flag values,
one Flag Interrupt Mask Register sets bits to enable an
interrupt function, and the other Flag Interrupt Mask Register clears bits to disable an interrupt function. PFx pins
defined as inputs can be configured to generate hardware
interrupts, while output PFx pins can be configured to generate software interrupts.
• Flag Interrupt Sensitivity Registers—The Flag Interrupt
Sensitivity Registers specify whether individual PFx pins
are level- or edge-sensitive and specify, if edge-sensitive,
whether just the rising edge or both the rising and falling
edges of the signal are significant. One register selects the
type of sensitivity, and one register selects which edges are
significant for edge sensitivity.
TIMERS
There are 14 programmable timer units in the ADSP-BF561.
Each of the 12 general-purpose timer units can be independently programmed as a Pulse Width Modulator (PWM),
internally or externally clocked timer, or pulse width counter.
The general-purpose timer units can be used in conjunction
with the UART to measure the width of the pulses in the data
stream to provide an autobaud detect function for a serial channel. The general-purpose timers can generate interrupts to the
processor core providing periodic events for synchronization,
either to the processor clock or to a count of external signals.
In addition to the 12 general-purpose programmable timers,
another timer is also provided for each core. These extra timers
are clocked by the internal processor clock (CCLK) and are typically used as a system tick clock for generation of operating
system periodic interrupts.
PARALLEL PERIPHERAL INTERFACE
The processor provides two Parallel Peripheral Interfaces (PPI0,
PPI1) that can connect directly to parallel A/D and D/A converters, ITU-R-601/656 video encoders and decoders, and other
general-purpose peripherals. Each PPI consists of a dedicated
input clock pin, up to three frame synchronization pins, and up
to 16 data pins.
General-Purpose Mode Descriptions
The general-purpose modes of the PPI are intended to suit a
wide variety of data capture and transmission applications. The
modes are divided into four main categories, each allowing up
to 16 bits of data transfer per PPI_CLK cycle:
• Data Receive with Internally Generated Frame Syncs
• Data Receive with Externally Generated Frame Syncs
• Data Transmit with Internally Generated Frame Syncs
• Data Transmit with Externally Generated Frame Syncs
These modes support ADC/DAC connections, as well as video
communication with hardware signaling. Many of the modes
support more than one level of frame synchronization. If
desired, a programmable delay can be inserted between assertion of a frame sync and reception/transmission of data.
ITU -R 656 Mode Descriptions
In ITU-R 656 mode, the PPI receives and parses a data stream of
8-bit or 10-bit data elements. On-chip decode of embedded preamble control and synchronization information is supported.
Three distinct ITU-R 656 modes are supported:
• Active Video Only Mode
• Vertical Blanking Only Mode
• Entire Field Mode
Rev. 0 | Page 10 of 52 | January 2005
Page 11
ADSP-BF561
Active Video Only Mode
In this mode, the PPI does not read in any data between the End
of Active Video (EAV) and Start of Active Video (SAV) preamble symbols, or any data present during the vertical blanking
intervals. In this mode, the control byte sequences are not stored
to memory; they are filtered by the PPI.
Vertical Blanking Interval Mode
In this mode, the PPI transfers vertical blanking interval (VBI)
data, as well as horizontal blanking information and control
byte sequences on VBI lines.
Entire Field Mode
In this mode, the entire incoming bitstream is read in through
the PPI. This includes active video, control preamble sequences,
and ancillary data that may be embedded in horizontal and vertical blanking intervals.
Though not explicitly supported, ITU-R 656 output functionality can be achieved by setting up the entire frame structure
(including active video, blanking, and control information) in
memory and streaming the data out of the PPI in a frame
syncless mode. The processor’s 2D DMA features facilitate this
transfer by allowing the static frame buffer (blanking and control codes) to be placed in memory once, and simply updating
the active video information on a per frame basis.
DYNAMIC POWER MANAGEMENT
The ADSP-BF561 provides four power management modes and
one power management state, each with a different performance/power profile. In addition, Dynamic Power
Management provides the control functions to dynamically
alter the processor core supply voltage, further reducing power
dissipation. Control of clocking to each of the ADSP-BF561
peripherals also reduces power consumption. See Table 3 for a
summary of the power settings for each mode.
Full-On Operating Mode—Maximum Performance
In the Full-On mode, the PLL is enabled and is not bypassed,
providing capability for maximum operational frequency. This
is the default execution state in which maximum performance
can be achieved. The processor cores and all enabled peripherals
run at full speed.
Active Operating Mode—Moderate Power Savings
In the Active mode, the PLL is enabled but bypassed. Because
the PLL is bypassed, the processor’s core clock (CCLK) and system clock (SCLK) run at the input clock (CLKIN) frequency. In
this mode, the CLKIN to CCLK multiplier ratio can be changed,
although the changes are not realized until the Full-On mode is
entered. DMA access is available to appropriately configured L1
and L2 memories.
In the Active mode, it is possible to disable the PLL through the
PLL Control Register (PLL_CTL). If disabled, the PLL must be
re-enabled before transitioning to the Full-On or Sleep modes.
Table 3. Power Settings
Core
PLL
ModePLL
Full-OnEnabled NoEnabled Enabled On
ActiveEnabled/
Disabled
SleepEnabled –Disabled Enabled On
Deep Sleep Disabled –Disabled Disabled On
HibernateDisabled –Disabled Disabled Off
Bypassed
YesEnabled Enabled On
Clock
(CCLK)
System
Clock
(SCLK)
Core
Power
Sleep Operating Mode—High Dynamic Power Savings
The Sleep mode reduces power dissipation by disabling the
clock to the processor core (CCLK). The PLL and system clock
(SCLK), however, continue to operate in this mode. Typically an
external event will wake up the processor. When in the Sleep
mode, assertion of wakeup will cause the processor to sense the
value of the BYPASS bit in the PLL Control register (PLL_CTL).
When in the Sleep mode, system DMA access is only available
to external memory, not to L1 or on-chip L2 memory.
Deep Sleep Operating Mode—Maximum Dynamic Power
Savings
The Deep Sleep mode maximizes power savings by disabling the
clocks to the processor cores (CCLK) and to all synchronous
peripherals (SCLK). Asynchronous peripherals will not be able
to access internal resources or external memory. This powereddown mode can only be exited by assertion of the reset interrupt
(RESET
). If BYPASS is disabled, the processor will transition to
the Full-On mode. If BYPASS is enabled, the processor will
transition to the Active mode.
Hibernate Operating State—Maximum Static Power
Savings
The Hibernate state maximizes static power savings by disabling
the voltage and clocks to the processor core (CCLK) and to all
the synchronous peripherals (SCLK). The internal voltage regulator for the processor can be shut off by writing b#00 to the
FREQ bits of the VR_CTL register. This disables both CCLK
and SCLK. Furthermore, it sets the internal power supply voltage (V
) to 0 V to provide the lowest static power
DDINT
dissipation. Any critical information stored internally (memory
contents, register contents, etc.) must be written to a nonvolatile
storage device prior to removing power if the processor state is
to be preserved. Since V
is still supplied in this mode, all of
DDEXT
the external pins three-state, unless otherwise specified. This
allows other devices that may be connected to the processor to
have power still applied without drawing unwanted current.
The internal supply regulator can be woken up by asserting the
RESET
pin.
Rev. 0 | Page 11 of 52 | January 2005
Page 12
ADSP-BF561
Power Savings
As shown in Table 4, the ADSP-BF561 supports two different
power domains. The use of multiple power domains maximizes
flexibility, while maintaining compliance with industry standards and conventions. By isolating the internal logic of the
ADSP-BF561 into its own power domain, separate from the I/O,
the processor can take advantage of Dynamic Power Management, without affecting the I/O devices. There are no
sequencing requirements for the various power domains.
Table 4. ADSP-BF561 Power Domains
Power DomainVDD Range
All internal logicV
I/OV
DDINT
DDEXT
The power dissipated by a processor is largely a function of the
clock frequency of the processor and the square of the operating
voltage. For example, reducing the clock frequency by 25%
results in a 25% reduction in dynamic power dissipation, while
reducing the voltage by 25% reduces dynamic power dissipation
by more than 40%. Further, these power savings are additive, in
that if the clock frequency and supply voltage are both reduced,
the power savings can be dramatic.
The Dynamic Power Management feature of the ADSP-BF561
allows both the processor’s input voltage (V
quency (f
) to be dynamically controlled.
CCLK
) and clock fre-
DDINT
The savings in power dissipation can be modeled using the
Power Savings Factor and % Power Savings calculations.
The Power Savings Factor is calculated as:
Power Savings Factor
f
CCLKRED
---------------------
=
f
CCLKNOM
V
DDINTRED
⎛⎞
--------------------------
×
⎝⎠
V
DDINTNOM
2
T
RED
⎞
⎛
------------ -
×
⎠
⎝
T
NOM
where the variables in the equations are:
•f
•f
•V
•V
•T
•T
is the nominal core clock frequency.
CCLKNOM
is the reduced core clock frequency.
CCLKRED
is the nominal internal supply voltage.
DDINTNOM
is the reduced internal supply voltage.
DDINTRED
is the duration running at f
NOM
is the duration running at f
RED
CCLKNOM
CCLKRED
.
.
The percent power savings is calculated as:
% Power Savings1 Power Savings Factor–()100%×=
VOLTAGE REGULATION
The ADSP-BF561 processor provides an on-chip voltage regulator that can generate processor core voltage levels 0.85 V to
1.25 V from an external 2.25 V to 3.6 V supply. Figure 4 shows
the typical external components required to complete the power
management system. The regulator controls the internal logic
voltage levels and is programmable with the Voltage Regulator
Control Register (VR_CTL) in increments of 50 mV. To reduce
standby power consumption, the internal voltage regulator can
be programmed to remove power to the processor core while
keeping I/O power (V
state V
can still be applied, eliminating the need for exter-
DDEXT
) supplied. While in the hibernate
DDEXT
nal buffers. The voltage regulator can be activated from this
power-down state by asserting RESET
, which will then initiate a
boot sequence. The regulator can also be disabled and bypassed
at the user’s discretion.
V
DDEXT
100µF
V
DDINT
100µF
1µF
VR
1–0
OUT
NOTE: VR
AND DESIGNER SHOU LD MINIMIZE T RACE LENGTH TO FDS9 431A.
1–0 SHOULD B E TIED TOGETHER EXTERNALLY
OUT
Figure 4. Voltage Regulator Circuit
10µH
0.1µF
ZHCS1000
EXTERNAL CO MPONENTS
2.25V TO 3.6V
INPUT VOLTAG E
RANGE
FDS9431A
CLOCK SIGNALS
The ADSP-BF561 can be clocked by an external crystal, a sine
wave input, or a buffered, shaped clock derived from an external
clock oscillator.
If an external clock is used, it should be a TTL-compatible signal
and must not be halted, changed, or operated below the specified frequency during normal operation. This signal is
connected to the processor CLKIN pin. When an external clock
is used, the XTAL pin must be left unconnected.
Alternatively, because the ADSP-BF561 includes an on-chip
oscillator circuit, an external crystal may be used. The crystal
should be connected across the CLKIN and XTAL pins, with
two capacitors connected as shown in Figure 5.
Capacitor values are dependent on crystal type and should be
specified by the crystal manufacturer. A parallel-resonant, fundamental frequency, microprocessor-grade crystal should be
used.
CLKIN
Figure 5. External Crystal Connections
CLKOUTXTAL
Rev. 0 | Page 12 of 52 | January 2005
Page 13
ADSP-BF561
3
3
As shown in Figure 6, the core clock (CCLK) and system
peripheral clock (SCLK) are derived from the input clock
(CLKIN) signal. An on-chip PLL is capable of multiplying the
CLKIN signal by a user-programmable 1× to 63× multiplication
factor. The default multiplier is 10×, but it can be modified by a
software instruction sequence. On the fly frequency changes can
be effected by simply writing to the PLL_DIV register.
“FINE” ADJUSTMENT
RE QUIRE S PL L SEQ UENCIN G
CLKIN
PLL
0. 5×−64×
Figure 6. Frequency Modification Methods
VCO
SCL K ≤ CC L K
SCLK≤ 1
“COARSE” ADJUSTMENT
ON-THE-FLY
÷1,2,4,8
÷1:15
MH z
CCL K
SCLK
All on-chip peripherals are clocked by the system clock (SCLK).
The system clock frequency is programmable by means of the
SSEL3–0 bits of the PLL_DIV register. The values programmed
into the SSEL fields define a divide ratio between the PLL output
(VCO) and the system clock. SCLK divider values are 1 through
15. Table 5 illustrates typical system clock ratios.
Table 5. Example System Clock Ratios
The core clock (CCLK) frequency can also be dynamically
changed by means of the CSEL[1–0] bits of the PLL_DIV register. Supported CCLK divider ratios are 1, 2, 4, and 8, as shown
in Table 6. This programmable core clock capability is useful for
fast core frequency modifications.
Table 6. Core Clock Ratios
Example Frequency
Signal Name
CSEL[1–0]
Divider Ratio
VCO/CCLK
Ratios (MHz)
VCOCCLK
001:1500500
012:1500250
104:120050
118:120025
The maximum PLL lock time when a change is programmed via
the PLL_CTL register is 40 µs. The maximum time to change
the internal voltage via the internal voltage regulator is also
40 µs. The reset value for the PLL_LOCKCNT register is 0x200.
This value should be programmed to ensure a 40 µs wakeup
time when either the voltage is changed or a new MSEL value is
programmed. The value should be programmed to ensure an
80 µs wakeup time when both voltage and the MSEL value are
changed. The time base for the PLL_LOCKCNT is the period of
CLKIN.
BOOTING MODES
The ADSP-BF561 has three mechanisms (listed in Table 7) for
automatically loading internal L1 instruction memory or L2
after a reset. A fourth mode is provided to execute from external
memory, bypassing the boot sequence.
Example Frequency
Signal Name
SSEL[3–0]
Divider Ratio
VCO/SCLK
Ratios (MHz)
VCOSCLK
00011:1100100
01106:130050
101010:150050
The maximum frequency of the system clock is f
. Note that
SCLK
the divisor ratio must be chosen to limit the system clock frequency to its maximum of f
. The SSEL value can be changed
SCLK
dynamically without any PLL lock latencies by writing the
appropriate values to the PLL divisor register (PLL_DIV).
Table 7. Booting Modes
BMODE1–0Description
00Execute from 16-bit external memory
(Bypass Boot ROM)
01Boot from 8-/16-bit flash
10Reserved
11Boot from SPI serial EEPROM
(16-bit address range)
The BMODE pins of the Reset Configuration Register, sampled
during power-on resets and software initiated resets, implement
the following modes:
• Execute from 16-bit external memory–
Execution starts from address 0x2000 0000 with 16-bit
packing. The boot ROM is bypassed in this mode. All configuration settings are set for the slowest device possible (3cycle hold time, 15-cycle R/W access times, 4-cycle setup).
• Boot from 8-/16-bit external flash memory–
The 8-/16-bit flash boot routine located in boot ROM
memory space is set up using Asynchronous Memory Bank
Rev. 0 | Page 13 of 52 | January 2005
Page 14
ADSP-BF561
0. All configuration settings are set for the slowest device
possible (3-cycle hold time; 15-cycle R/W access times;
4-cycle setup).
• Boot from SPI serial EEPROM (16-bit addressable)–
The SPI uses the PF2 output pin to select a single SPI
EPROM device, submits a read command at address
0x0000, and begins clocking data into the beginning of L1
instruction memory. A 16-bit addressable SPI-compatible
EPROM must be used.
For each of the boot modes, a boot loading protocol is used to
transfer program and data blocks from an external memory
device to their specified memory locations. Multiple memory
blocks may be loaded by any boot sequence. Once all blocks are
loaded, Core A program execution commences from the start of
L1 instruction SRAM (0xFFA0 0000). Core B remains in a heldoff state until Bit 5 of SICA_SYSCR is cleared. After that, Core B
will start execution at address 0xFF60 0000.
In addition, Bit 4 of the Reset Configuration Register can be set
by application code to bypass the normal boot sequence during
a software reset. For this case, the processor jumps directly to
the beginning of L1 instruction memory.
INSTRUCTION SET DESCRIPTION
The Blackfin processor family assembly language instruction set
employs an algebraic syntax that was designed for ease of coding
and readability. The instructions have been specifically tuned to
provide a flexible, densely encoded instruction set that compiles
to a very small final memory size. The instruction set also provides fully featured multifunction instructions that allow the
programmer to use many of the processor core resources in a
single instruction. Coupled with many features more often seen
on microcontrollers, this instruction set is very efficient when
compiling C and C++ source code. In addition, the architecture
supports both a user (algorithm/application code) and a supervisor (O/S kernel, device drivers, debuggers, ISRs) mode of
operation—allowing multiple levels of access to core processor
resources.
The assembly language, which takes advantage of the processor’s unique architecture, offers the following advantages:
• Seamlessly integrated DSP/CPU features are optimized for
both 8-bit and 16-bit operations.
• A multi-issue load/store modified Harvard architecture,
which supports two 16-bit MAC or four 8-bit ALU plus
two load/store plus two pointer updates per cycle.
• All registers, I/O, and memory are mapped into a unified
4G byte memory space providing a simplified programming model.
• Microcontroller features, such as arbitrary bit and bit-field
manipulation, insertion, and extraction; integer operations
on 8-, 16-, and 32-bit data types; and separate user and kernel stack pointers.
• Code density enhancements, which include intermixing of
16- and 32-bit instructions (no mode switching, no code
segregation). Frequently used instructions are encoded as
16-bits.
DEVELOPMENT TOOLS
The ADSP-BF561 is supported with a complete set of
CROSSCORE
including Analog Devices emulators and the VisualDSP++
development environment. The same emulator hardware that
supports other Analog Devices processors also fully emulates
the ADSP-BF561.
The VisualDSP++ project management environment lets programmers develop and debug an application. This environment
includes an easy to use assembler that is based on an algebraic
syntax, an archiver (librarian/library builder), a linker, a loader,
a cycle-accurate instruction-level simulator, a C/C++ compiler,
and a C/C++ runtime library that includes DSP and mathematical functions. A key point for these tools is C/C++ code
efficiency. The compiler has been developed for efficient translation of C/C++ code to Blackfin assembly. The Blackfin
processor has architectural features that improve the efficiency
of compiled C/C++ code.
The VisualDSP++ debugger has a number of important features. Data visualization is enhanced by a plotting package that
offers a significant level of flexibility. This graphical representation of user data enables the programmer to quickly determine
the performance of an algorithm. As algorithms grow in complexity, this capability can have increasing significance on the
designer’s development schedule, increasing productivity. Statistical profiling enables the programmer to nonintrusively poll
the processor as it is running the program. This feature, unique
to VisualDSP++, enables the software developer to passively
gather important code execution metrics without interrupting
the real-time characteristics of the program. Essentially, the
developer can identify bottlenecks in software quickly and efficiently. By using the profiler, the programmer can focus on
those areas in the program that impact performance and take
corrective action.
Debugging both C/C++ and assembly programs with the
VisualDSP++ debugger, programmers can:
• View mixed C/C++ and assembly code (interleaved source
and object information).
• Insert breakpoints.
• Set conditional breakpoints on registers, memory, and
stacks.
• Trace instruction execution.
• Perform linear or statistical profiling of program execution.
• Fill, dump, and graphically plot the contents of memory.
• Perform source level debugging.
•Create custom debugger windows.
*
CROSSCORE is a registered trademark of Analog Devices, Inc.
†
VisualDSP++ is a registered trademark of Analog Devices, Inc.
®
*
software and hardware development tools,
®
†
Rev. 0 | Page 14 of 52 | January 2005
Page 15
ADSP-BF561
The VisualDSP++ IDE lets programmers define and manage
software development. Its dialog boxes and property pages let
programmers configure and manage all development tools,
including Color Syntax Highlighting in the VisualDSP++
editor. These capabilities permit programmers to:
• Control how the development tools process inputs and
generate outputs.
• Maintain a one-to-one correspondence with the tool’s
command line switches.
The VisualDSP++ Kernel (VDK) incorporates scheduling and
resource management tailored specifically to address the memory and timing constraints of embedded, real-time programming. These capabilities enable engineers to develop code more
effectively, eliminating the need to start from the very beginning
when developing new application code. The VDK features
include Threads, Critical and Unscheduled regions, Semaphores, Events, and Device flags. The VDK also supports
Priority-based, Pre-emptive, Cooperative, and Time-Sliced
scheduling approaches. In addition, the VDK was designed to
be scalable. If the application does not use a specific feature, the
support code for that feature is excluded from the target system.
Because the VDK is a library, a developer can decide whether to
use it or not. The VDK is integrated into the VisualDSP++
development environment, but can also be used with standard
command line tools. When the VDK is used, the development
environment assists the developer with many error prone tasks
and assists in managing system resources, automating the generation of various VDK-based objects, and visualizing the
system state when debugging an application that uses the VDK.
VCSE is Analog Devices’ technology for creating, using, and
reusing software components (independent modules of substantial functionality) to quickly and reliably assemble software
applications. Components can be downloaded from the Web
and dropped into the application. Component archives can be
published from within VisualDSP++. VCSE supports component implementation in C/C++ or assembly language.
The Expert Linker can be used to visually manipulate the placement of code and data in the embedded system. Memory
utilization can be viewed in a color-coded graphical form. Code
and data can be easily moved to different areas of the processor
or external memory with the drag of the mouse. Runtime stack
and heap usage can be examined. The Expert Linker is fully
compatible with existing Linker Definition File (LDF), allowing
the developer to move between the graphical and textual
environments.
Analog Devices emulators use the IEEE 1149.1 JTAG test access
port of the ADSP-BF561 to monitor and control the target
board processor during emulation. The emulator provides fullspeed emulation, allowing inspection and modification of memory, registers, and processor stacks. Nonintrusive in-circuit
emulation is assured by the use of the processor’s JTAG interface—the emulator does not affect target system loading or
timing.
In addition to the software and hardware development tools
available from Analog Devices, third parties provide a wide
range of tools supporting the Blackfin processor family. Third
party software tools include DSP libraries, real-time operating
systems, and block diagram design tools.
DESIGNING AN EMULATOR-COMPATIBLE
PROCESSOR BOARD (TARGET)
The Analog Devices family of emulators are tools that every system developer needs to test and debug hardware and software
systems. Analog Devices has supplied an IEEE 1149.1 JTAG
Test Access Port (TAP) on the ADSP-BF561. The emulator uses
the TAP to access the internal features of the processor, allowing the developer to load code, set breakpoints, observe
variables, observe memory, and examine registers. The processor must be halted to send data and commands, but once an
operation has been completed by the emulator, the processor is
set running at full speed with no impact on system timing.
To use these emulators, the target board must include a header
that connects the processor’s JTAG port to the emulator.
For details on target board design issues, including mechanical
layout, single processor connections, multiprocessor scan
chains, signal buffering, signal termination, and emulator pod
logic, see EE-68: Analog Devices JTAG Emulation Technical Reference on the Analog Devices website (www.analog.com)—
use site search on “EE-68.” This document is updated regularly
to keep pace with improvements to emulator support.
ADDITIONAL INFORMATION
This data sheet provides a general overview of the ADSP-BF561
architecture and functionality. For detailed information on the
Blackfin DSP family core architecture and instruction set, refer
to the ADSP-BF561 Hardware Reference and the Blackfin Family
Instruction Set Reference.
Rev. 0 | Page 15 of 52 | January 2005
Page 16
ADSP-BF561
PIN DESCRIPTIONS
ADSP-BF561 pin definitions are listed in Table 8. Unused
inputs should be tied or pulled to V
currents for each driver type are shown in Figure 22 through
Figure 29.
Table 8. Pin Descriptions
BlockPin NameType Signals Function
EBIUADDR[25:2]O24Address Bus for Async/Sync Access Anone
DATA[31:0]I/O32Data Bus for Async/Sync AccessAnone
ABE
TCKI1JTAG Clockinternal pull-down
TDOO1JTAG Serial Data OutCnone
TDII1JTAG Serial Data Ininternal pull-down
TMSI1JTAG Mode Selectinternal pull-down
TRST
or GND. Output drive
DDEXT
Driver
Type Pull-Up/Down Requirement
Anone
Async/Sync Access
O1Bus GrantAnone
I1Bus Requestpull-up required if function not used
O1Bus Grant HangA none
O1Row Address StrobeAnone
O1Column Address StrobeAnone
O1Write EnableA none
O4Bank SelectA none
O4Bank SelectA none
O1Write EnableA none
O1Read EnableAnone
O1Emulation OutputCnone
I1JTAG Resetexternal pull-down necessary
if JTAG not used
Rev. 0 | Page 16 of 52 | January 2005
Page 17
ADSP-BF561
Table 8. Pin Descriptions (Continued)
Driver
BlockPin NameType Signals Function
UARTRX/PF27I/O1UART Receive/
Programmable Flag
TX/PF26I/O1UART Transmit/
Programmable Flag
SPIMOSII/O1Master Out Slave InCsoftware configurable,
VDDINTP14Power SupplyN/A
GNDG41Power Supply ReturnN/A
No ConnectionNC2NCN/A
Tota l pins256
Type Pull-Up/Down Requirement
ADSP-BF561
Rev. 0 | Page 19 of 52 | January 2005
Page 20
ADSP-BF561
SPECIFICATIONS
Note that component specifications are subject to change
without notice.
RECOMMENDED OPERATING CONDITIONS
ParameterMinimum Nominal Maximum Unit
1
V
DDINT
2
V
DDINT
3
V
DDINT
V
DDEXT
V
IH
V
IL
T
AMBIENT
1
Internal Voltage Regulator tolerance:
ADSP-BF561SKBCZ500, ADSP-BF561SKBCZ600: V
2
Internal Voltage Regulator tolerance:
ADSP-BF561SBB600: V
3
Internal Voltage Regulator tolerance:
ADSP-BF561SBB500: V
4
The ADSP-BF561 is 3.3 V tolerant (always accepts up to 3.6 V maximum VIH), but voltage compliance (on outputs, VOH) depends on the input V
approximately equals V
Internal Supply Voltage ADSP-BF561SKBCZ600, ADSP-BF561SKBCZ5000.81.251.375V
Internal Supply Voltage ADSP-BF561SBB6000.81.351.43V
Internal Supply Voltage ADSP-BF561SBB5000.81.251.375V
External Supply Voltage2.252.5 or 3.3 3.6V
High Level Input Voltage4, @ V
Low Level Input Voltage, @ V
=maximum
DDEXT
=minimum–0.3+0.6V
DDEXT
2.03.6V
Ambient Operating Temperature
Industrial–40+ 85ⴗC
Commercial070ⴗC
= –5% to +10%
DDINT
= –7% to +12%
DDINT
= –7% to +12% except at 1.25 V: V
DDINT
(maximum). This 3.3 V tolerance applies to bidirectional and input only pins.
DDEXT
= –5% to +10%
DDINT
, because VOH (maximum)
DDEXT
ELECTRICAL CHARACTERISTICS
ParameterTest ConditionsMinimumMaximumUnit
V
OH
V
OL
I
IL
I
IH
I
IH
I
OZH
I
OZL
C
IN
1
Applies to output and bidirectional pins.
2
Applies to all input pins.
3
Applies to all input pins except TCK, TDI, TMS, and TRST.
4
Applies to TCK, TDI, TMS, and TRST.
5
Applies to three-statable pins.
6
Applies to all signal pins.
7
Guaranteed, but not tested.
High Level Output Voltage1 @ V
Low Level Output Voltage
1
@ V
Low Level Input Current2 @ V
6, 7
3
4
@ V
@ V
5
@ V
5
@ V
fIN = 1 MHz, T
High Level Input Current
High Level Input Current
Three-State Leakage Current
Three-State Leakage Current
Input Capacitance
=3.0 V, IOH = –0.5 mA2.4V
DDEXT
=3.0 V, IOL = 2.0 mA0.4V
DDEXT
=maximum, VIN = 0 V–10V
DDEXT
=maximum, VIN = VDD maximum10µA
DDEXT
=maximum, VIN = VDD maximum50µA
DDEXT
= maximum, VIN = VDD maximum10µA
DDEXT
= maximum, VIN = 0 V–10µA
DDEXT
= 25ⴗC, VIN = 2.5 VTBDpF
AMBIENT
Rev. 0 | Page 20 of 52 | January 2005
Page 21
ABSOLUTE MAXIMUM RATINGS
ADSP-BF561
ParameterValue
Internal (Core) Supply Voltage
External (I/O) Supply Voltage
Input Voltage
1
– 0.5 V to +3.6 V
Output Voltage Swing
Load Capacitance
Core Clock (CCLK)
1, 2
1
1
(V
)
DDINT
1
(V
)–0.3 V to +3.8 V
DDEXT
1
–0.3 V to +1.45 V
–0.5 V to V
DDEXT
+ 0.5 V
200 pF
ADSP-BF561SKBCZ600/ADSP-BF561SBB600 600 MHz
ADSP-BF561SKBCZ500 500 MHz
System Clock (SCLK)
Storage Temperature Range
1
1
133 MHz
–65ⴗC to + 150ⴗC
Junction Temperature Under Bias125ⴗC
1
Stresses greater than those listed above may cause permanent damage to the device. These
are stress ratings only. Functional operation of the device at these or any other condit ions
greater than those indicated in the operational sections of this specification is not implied.
Exposure to absolute maximum rating conditions for extended periods may affect device
reliability.
2
For proper SDRAM controller operation, the maximum load capacitance is 50 pF (at
3.3 V) or 30 pF (at 2.5 V) for ADDR25–2, DATA31–0, ABE3–0/SDQM3–0, CLKOUT,
SCKE, SA10, SRAS, SCAS, SWE, and SMS.
ESD SENSITIVITY
CAUTION
ESD (electrostatic discharge) sensitive device. Electrostatic charges as high as 4000 V readily accumulate
on the human body and test equipment and can discharge without detection. Although the ADSP-BF561
features proprietary ESD protection circuitry, permanent damage may occur on devices subjected to
high energy electrostatic discharges. Therefore, proper ESD precautions are recommended to avoid
performance degradation or loss of functionality.
pp
Rev. 0 | Page 21 of 52 | January 2005
Page 22
ADSP-BF561
TIMING SPECIFICATIONS
Table 9 and Table 12 describe the timing requirements for the
ADSP-BF561 clocks. Take care in selecting MSEL, SSEL, and
CSEL ratios so as not to exceed the maximum core clock, system
clock, and Voltage Controlled Oscillator (VCO) operating
Table 9. Core and System Clock Requirements—ADSP-BF561SKBCZ500 and ADSP-BF561SBB500
ParameterMinimumMaximumUnit
t
t
t
t
t
CCLK
CCLK
CCLK
CCLK
CCLK
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
=1.1875 Vminimum)2ns
DDINT
=1.045 Vminimum)2.25ns
DDINT
=0.95 Vminimum)2.86ns
DDINT
=0.855 Vminimum)3.33ns
DDINT
=0.8 V minimum)4.00ns
DDINT
Table 10. Core and System Clock Requirements—ADSP-BF561SKBCZ600
ParameterMinimumMaximumUnit
t
t
t
t
t
CCLK
CCLK
CCLK
CCLK
CCLK
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
=1.1875 Vminimum)1.66ns
DDINT
=1.045 Vminimum)2.10ns
DDINT
=0.95 Vminimum)2.35ns
DDINT
=0.855 Vminimum)2.66ns
DDINT
=0.8 V minimum)4.00ns
DDINT
frequencies, as described in Absolute Maximum Ratings on
Table 11. Core and System Clock Requirements—ADSP-BF561SBB600
ParameterMinimumMaximumUnit
t
CCLK
t
CCLK
t
CCLK
t
CCLK
t
CCLK
t
CCLK
1
External voltage regulator required to ensure proper operation at 600 MHz 1.35 V nominal.
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
Core Cycle Period (V
=1.2825 Vminimum)
DDINT
=1.14 Vminimum)2.0ns
DDINT
=1.045 Vminimum)2.25ns
DDINT
=0.95 Vminimum)2.86ns
DDINT
=0.855 V minimum)3.33ns
DDINT
=0.8 Vminimum)4.00ns
DDINT
1
1.66ns
Table 12. Phase-Locked Loop Operating Conditions
ParameterMinimumMaximumUnit
Voltage Controlled Oscillator (VCO) Frequency50Maximum CCLKMHz
Rev. 0 | Page 22 of 52 | January 2005
Page 23
ADSP-BF561
Clock and Reset Timing
Table 13 and Figure 7 describe clock and reset operations. Per
Figure 7, combinations of CLKIN and clock multipliers must
not select core/peripheral clocks in excess of 600/133 MHz.
Table 13. Clock and Reset Timing
ParameterMinMaxUnit
Timing Requirements
t
CKIN
t
CKINL
t
CKINH
t
WRST
Switching Characteristics
t
SCLK
1
Applies to bypass mode and non-bypass mode.
2
Applies after power-up sequence is complete. At power-up, the processor’s internal phase-locked loop requires no more than 2,000 CLKIN cycles, while RESET is asserted,
assuming stable power supplies and CLKIN (not including startup time of external clock oscillator).
3
The figure below shows a ⴛ2 ratio between t
ADSP-BF561 Hardware Reference.
4
t
must always also be larger than t
SCLK
CLKIN Period25.0100.0ns
CCLK
1
1
2
3
and t
CKIN
, but the ratio has many programmable options. For more information, see the System Design chapter of the
Table 17 and Figure 11 describe external port bus request and
bus grant operations.
Table 17. External Port Bus Request and Grant Cycle Timing
Parameter
1, 2
Timing Requirements
t
BS
t
BH
BR Asserted to CLKOUT High Setup4.6ns
CLKOUT High to BR Deasserted Hold Time0.0ns
Switching Characteristics
t
SD
t
SE
t
DBG
t
EBG
t
DBH
t
EBH
1
These are preliminary timing parameters that are based on worst-case operating conditions.
2
The pad loads for these timing parameters are 20 pF.
CLKOUT Low to SMS, Address and RD/WR Disable4.5ns
CLKOUT Low to SMS, Address and RD/WR Enable4.5ns
CLKOUT High to BG Asserted Setup3.6ns
CLKOUT High to BG Deasserted Hold Time3.6ns
CLKOUT High to BGH Asserted Setup3.6ns
CLKOUT High to BGH Deasserted Hold Time3.6ns
ADSP-BF561
MinMaxUnit
CLKOUT
BR
AMSx
ADDR25-2
ABE3-0
AWE
ARE
BG
BGH
t
BS
t
BH
t
SD
t
SD
t
SD
t
t
DBG
DBH
t
t
EBG
EBH
t
SE
t
SE
t
SE
Figure 11. External Port Bus Request and Grant Cycle Timing
PPIx_CLK Width
PPI_CLK Period
External Frame Sync Setup Before PPI_CLK3.0ns
External Frame Sync Hold After PPI_CLK3.0ns
Receive Data Setup Before PPI_CLK2.0ns
Receive Data Hold After PPI_CLK4.0ns
Switching Characteristics
t
DFSPE
t
HOFSPE
t
DDTPE
t
HDTPE
1
PPI_CLK frequency cannot exceed f
Internal Frame Sync Delay After PPI_CLK10.0ns
Internal Frame Sync Hold After PPI_CLK 0.0ns
Transmit Data Delay After PPI_CLK 10.0ns
Transmit Data Hold After PPI_CLK0.0ns
1
1
/2.
SCLK
6.0ns
15.0ns
PPI_CLK
PPI_FS1
PPI_FS2
PPIx
DRIVE
EDGE
t
DFSPE
t
HOFSPE
t
t
HDTPE
DDTPE
Figure 12. Timing Diagram PPI
t
PCLKW
t
SFSPE
t
SDRPE
SAMPLE
EDGE
t
HFSPE
t
HDRPE
Rev. 0 | Page 28 of 52 | January 2005
Page 29
ADSP-BF561
Serial Ports
Table 19 on Page 29 through Table 22 on Page 30 and Figure 13
on Page 31 through Figure 15 on Page 33 describe Serial Port
operations.
Table 19. Serial Ports—External Clock
ParameterMinMaxUnit
Timing Requirements
t
SFSE
t
HFSE
t
SDRE
t
HDRE
t
SCLKW
t
SCLK
TFS/RFS Setup Before TSCLK/RSCLK
TFS/RFS Hold After TSCLK/RSCLK
Receive Data Setup Before RSCLK
Receive Data Hold After RSCLK
TSCLK/RSCLK Width4.5ns
TSCLK/RSCLK Period15.0ns
Switching Characteristics
t
DFSE
t
HOFSE
t
DDTE
t
HDTE
1
Referenced to sample edge.
2
Referenced to drive edge.
TFS/RFS Delay After TSCLK/RSCLK (Internally Generated TFS/RFS)
TFS/RFS Hold After TSCLK/RSCLK (Internally Generated TFS/RFS)
Transmit Data Delay After TSCLK
Transmit Data Hold After TSCLK
1
1
1
1
1
1
3.0ns
3.0ns
3.0ns
3.0ns
2
1
0.0ns
10.0ns
10.0ns
0.0ns
Table 20. Serial Ports—Internal Clock
ParameterMinMaxUnit
Timing Requirements
t
SFSI
t
HFSI
t
SDRI
t
HDRI
t
SCLKW
t
SCLK
TFS/RFS Setup Before TSCLK/RSCLK
TFS/RFS Hold After TSCLK/RSCLK
Receive Data Setup Before RSCLK
Receive Data Hold After RSCLK
TSCLK/RSCLK Width4.5ns
TSCLK/RSCLK Period15.0ns
1
1
1
1
8.0ns
–2.0ns
6.0ns
0.0ns
Switching Characteristics
t
DFSI
t
HOFSI
t
DDTI
t
HDTI
t
SCLKIW
1
Referenced to sample edge.
2
Referenced to drive edge.
TFS/RFS Delay After TSCLK/RSCLK (Internally Generated TFS/RFS)
TFS/RFS Hold After TSCLK/RSCLK (Internally Generated TFS/RFS)
Transmit Data Delay After TSCLK
Transmit Data Hold After TSCLK
1
1
TSCLK/RSCLK Width4.5ns
2
1
–1.0ns
3.0ns
3.0ns
–2.0ns
Table 21. Serial Ports—Enable and Three-State
ParameterMinMaxUnit
Switching Characteristics
t
DTENE
t
DDTTE
t
DTENI
t
DDTTI
1
Referenced to drive edge.
Data Enable Delay from External TSCLK
Data Disable Delay from External TSCLK
Data Enable Delay from Internal TSCLK–2.0ns
Data Disable Delay from Internal TSCLK
1
1
1
0ns
10.0ns
3.0ns
Rev. 0 | Page 29 of 52 | January 2005
Page 30
ADSP-BF561
Table 22. External Late Frame Sync
ParameterMinMaxUnit
Switching Characteristics
t
DDTLFSE
t
DTENLFS
1
MCE = 1, TFS enable and TFS valid follow t
2
If external RFS/TFS setup to RSCLK/TSCLK > t
Data Delay from Late External TFS or External RFS with MCE = 1,
MFD = 0
1, 2
Data Enable from Late FS or MCE = 1, MFD = 0
DTENLFS
and t
SCLKE
DDTLFSE
/2, then t
.
DDTE/I
and t
apply; otherwise t
DTENE/I
1, 2
DDTLFSE
0ns
and t
DTENLFS
apply.
10.0ns
Rev. 0 | Page 30 of 52 | January 2005
Page 31
DATA RECEIVE— INTERNAL CLOCKDATA RECEIVE— EXTERNAL CLOCK
DRIVE EDGESAMPLE EDGE
t
SCLKIW
DRIVE EDGESAMPLE EDGE
t
SCLKW
ADSP-BF561
RSCLK
RFS
DR
TSCLK
TFS
DT
t
t
HOFSE
DATA TRANSMIT — INTERNAL CLOCK
DRIVE EDGESAMPLE EDGE
t
HOFSI
t
HDTI
DFSE
NOTE: EITHER THE RISING EDGE OR FALLING EDGE OF RSCLK CAN BE USED AS THE ACTIVE SAMPLING EDGE.
t
DFSI
NOTE: EITHER THE RISING EDGE OR FALLING EDGE OF TSCLK CAN BE USED AS THE ACTIVE SAMPLING EDGE.
t
SCLKIW
t
DDTI
t
t
t
SFSI
SDRI
SFSI
t
t
HFSI
t
HDRI
HFSI
RSCLK
RFS
DR
TSCLK
TFS
DT
t
t
HOFSE
DATA TRANSMIT — EXTERNAL CLOCK
DRIVE EDGESAMPLE EDGE
t
HOFSE
t
HDTE
DFSE
t
DFSE
t
SCLKW
t
DDTE
t
SFSE
t
t
SDRE
SFSE
t
HFSE
t
HDRE
t
HFSE
TCLK (EXT)
TFS (“LATE”, EXT)
DT
TCLK (INT)
TFS (“LATE”, INT)
DT
DRIVE EDGEDRIVE EDGE
TCLK/RCLK
t
DDTEN
DRIVE EDGE
t
DDTIN
TCLK/RCLK
t
DDTTE
DRIVE EDGE
Figure 13. Serial Ports
Rev. 0 | Page 31 of 52 | January 2005
t
DDTTI
Page 32
ADSP-BF561
EXTERNALRFS WITHMCE = 1,MFD = 0
DRIVEDRIVESAMPLE
RSCLK
RFS
DT
LATE EXTERNAL TFS
DRIVEDRIVESAMPLE
TSCLK
TFS
DT
Figure 14. External Late Frame Sync (Frame Sync Setup < t
t
SFSE/I
t
DTENLFS
t
DDTLFSE
t
DTENLFS
t
DDTLFSE
t
SFSE /I
t
HOFSE/I
t
HDTE/I
t
HOFSE/I
t
t
HDTE/I
t
DDTE/I
DDTE/I
SCLK
2ND BIT1ST BIT
2ND BIT1ST BIT
/2)
Rev. 0 | Page 32 of 52 | January 2005
Page 33
EXTERNAL RFS WITH MCE = 1, MFD = 0
ADSP-BF561
RSCLK
RFS
DT
LATE EXTERNAL TFS
TSCLK
TFS
DRIVESAMPLE
t
SFSE/I
t
DTENLSCK
1ST BIT
t
DDTLSCK
DRIVESAMPLE
t
SFSE/I
t
DTENLSCK
DRIVE
DRIVE
t
HOFSE/I
t
HDTE/I
t
HOFSE/I
t
HDTE/I
t
DDTE/I
t
DDTE/I
2ND BIT
DT
t
DDTLSCK
Figure 15. External Late Frame Sync (Frame Sync Setup > t
1ST BIT2ND BIT
SCLK
/2)
Rev. 0 | Page 33 of 52 | January 2005
Page 34
ADSP-BF561
Serial Peripheral Interface (SPI) Port—
Master Timing
Table 23 and Figure 16 describe SPI port master operations.
Table 23. Serial Peripheral Interface (SPI) Port—Master Timing
ParameterMinMaxUnit
Timing Requirements
t
SSPIDM
t
HSPIDM
Switching Characteristics
t
SDSCIM
t
SPICHM
t
SPICLM
t
SPICLK
t
HDSM
t
SPITDM
t
DDSPIDM
t
HDSPIDM
Data Input Valid to SCK Edge (Data Input Setup)7.5ns
SCK Sampling Edge to Data Input Invalid–1.5ns
SPISELx Low to First SCK Edge2t
Serial Clock High Period2t
Serial Clock Low Period2t
Serial Clock Period4t
Last SCK Edge to SPISELx High2t
Sequential Transfer Delay2t
–1.5ns
SCLK
–0.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
SCK Edge to Data Out Valid (Data Out Delay)06ns
SCK Edge to Data Out Invalid (Data Out Hold)–1.0+4.0ns
CPHA=1
CPHA=0
SPISELx
(OUTPUT)
SCK
(CPOL = 0)
(OUTPUT)
SCK
(CPOL = 1)
(OUTPUT)
MOSI
(OUTPUT)
MISO
(INPUT)
MOSI
(OUTPUT)
MISO
(INPUT)
t
SSPIDM
t
SDSCIM
MSB VALID
t
SPICHMtSPICLM
t
SPICLM
t
SSPIDM
MSB VALID
t
HSPIDM
t
SPICHM
t
DDSPIDM
t
HSPIDM
t
DDSPIDM
t
SPICLK
t
HDSPIDM
t
SSPIDM
LSB VALID
LSB VALID
t
HDSPIDM
LSBMSB
t
HDSM
LSBMSB
t
HSPIDM
t
SPITDM
Figure 16. Serial Peripheral Interface (SPI) Port—Master Timing
Rev. 0 | Page 34 of 52 | January 2005
Page 35
ADSP-BF561
Serial Peripheral Interface (SPI) Port—
Slave Timing
Table 24 and Figure 17 describe SPI port slave operations.
Table 24. Serial Peripheral Interface (SPI) Port—Slave Timing
ParameterMinMaxUnit
Timing Requirements
t
SPICHS
t
SPICLS
t
SPICLK
t
HDS
t
SPITDS
t
SDSCI
t
SSPID
t
HSPID
Serial Clock High Period2t
Serial Clock Low Period2t
Serial Clock Period4t
Last SCK Edge to SPISS Not Asserted2t
Sequential Transfer Delay2t
SPISS Assertion to First SCK Edge2t
Data Input Valid to SCK Edge (Data Input Setup)1.6ns
SCK Sampling Edge to Data Input Invalid1.6ns
Switching Characteristics
t
DSOE
t
DSDHI
t
DDSPID
t
HDSPID
SPISS Assertion to Data Out Active08ns
SPISS Deassertion to Data High Impedance08ns
SCK Edge to Data Out Valid (Data Out Delay)010ns
SCK Edge to Data Out Invalid (Data Out Hold)010ns
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
–1.5ns
SCLK
CPHA=1
CPHA=0
SPISS
(INPUT)
SCK
(CPOL = 0)
(INPUT)
SCK
(CPOL = 1)
(INPUT)
MISO
(OUTPUT)
MOSI
(INPUT)
MISO
(OUTPUT)
MOSI
(INPUT)
t
DSOE
t
DSOE
t
SDSCI
t
SPICHStSPICL S
t
SPICL S
t
DDSPID
t
SSPID
MSB VALID
t
MSB VALID
t
DDSPID
MSB
SPICHS
t
HDSPID
t
HSPID
t
SSPID
t
SPICLK
t
DDSPID
t
SSPID
LSB VALID
LSB VALID
LSB
t
HSPID
t
HDS
t
DSDHI
LSBMSB
t
DSDHI
t
HSPID
t
SPITDS
Figure 17. Serial Peripheral Interface (SPI) Port—Slave Timing
Rev. 0 | Page 35 of 52 | January 2005
Page 36
ADSP-BF561
Universal Asynchronous Receiver Transmitter (UART)
Port—Receive and Transmit Timing
Figure 18 describes UART port receive and transmit operations.
The maximum baud rate is SCLK/16. As shown in Figure 18,
there is some latency between the generation internal UART
interrupts and the external data operations. These latencies are
negligible at the data transmission rates for the UART.
CLKOUT
(SAMPLE CLOCK)
RECEIVE
TRANSMIT
RXD
INTERNAL
UART RECEIVE
INTERRUPT
TXD
INTERNAL
UART TRANSMIT
INTERRUPT
AS DATA
WRITEN TO
BUFFER
DATA8–5
START
DATA8–5
Figure 18. UART Port—Receive and Transmit Timing
STOP
STOP2–1
UART RECEIVE BIT SET BY DATA STOP;
CLEARED BY FI FO READ
UART TRANSMIT BIT SET BY PROGRAM;
CLEARED BY WRI TE TO TRANSMIT
Rev. 0 | Page 36 of 52 | January 2005
Page 37
ADSP-BF561
Timer Cycle Timing
Table 25 and Figure 19 describe timer expired operations. The
input signal is asynchronous in width capture mode and external clock mode and has an absolute maximum input frequency
of f
/2 MHz.
SCLK
Table 25. Timer Cycle Timing
ParameterMinMaxUnit
Timing Characteristics
t
WL
t
WH
Timer Pulse Width Input Low
Timer Pulse Width Input High
Switching Characteristics
t
HTO
1
The minimum pulse widths apply for TMRx input pins in width capture and external clock modes. They also apply to the PF1 or PPICLK input pins in PWM output mode.
2
The minimum time for t
CLKOUT
Timer Pulse Width Output
is one cycle, and the maximum time for t
HTO
1
1
2
equals (232–1) cycles.
HTO
1SCLK cycles
1SCLK cycles
1(2
t
HTO
32
–1)SCLK cycles
TMRx
(PWM OUTPUTMODE)
TMRx
(WIDTH CAPTURE AND
EXTERNAL CLOCK MODES)
t
WL
t
WH
Figure 19. Timer PWM_OUT Cycle Timing
Rev. 0 | Page 37 of 52 | January 2005
Page 38
ADSP-BF561
Programmable Flags Cycle Timing
Table 26 and Figure 20 describe programmable flag operations.
Table 26. Programmable Flags Cycle Timing
ParameterMinMaxUnit
Timing Requirements
t
WFI
Flag Input Pulse Widtht
Switching Characteristics
t
DFO
Flag Output Delay from CLKOUT Low6ns
CLKOUT
PF (OUTPUT)
PF (INPUT)
t
DFO
FLAG OUTPUT
t
WFI
FLAG INPUT
+ 1ns
SCLK
Figure 20. Programmable Flags Cycle Timing
Rev. 0 | Page 38 of 52 | January 2005
Page 39
ADSP-BF561
JTAG Test and Emulation Port Timing
Table 27 and Figure 21 describe JTAG port operations.
TCK Period20ns
TDI, TMS Setup Before TCK High4ns
TDI, TMS Hold After TCK High4ns
System Inputs Setup Before TCK High
System Inputs Hold After TCK High
TRST Pulse Width
2
1
1
4ns
5ns
4TCK cycles
TDO Delay from TCK Low10ns
System Outputs Delay After TCK Low
3
012ns
TCK
TMS
TDI
TDO
SYSTEM
INPUTS
SYSTEM
OUTPUTS
t
DSYS
t
DTDO
t
t
STAP
SSYS
t
TCK
t
HTAP
t
HSYS
Figure 21. JTAG Port Timing
Rev. 0 | Page 39 of 52 | January 2005
Page 40
ADSP-BF561
OUTPUT DRIVE CURRENTS
Figure 22 through Figure 29 show typical current voltage char-
acteristics for the output drivers of the ADSP-BF561 processor.
The curves represent the current drive capability of the output
drivers as a function of output voltage. Refer to Table 8 on
Page 16 to identify the driver type for a pin.
150
100
50
–50
SOURCE CURRENT (mA)
–100
–150
150
100
150
V
= 2.25V @ 95°C
DDEXT
= 2.50V @ 25°C
V
DDEXT
= 2.75V @ –40°C
V
DDEXT
0
0
50
0.51.01.52.02.53.0
SOURCE VOLTAGE (V)
Figure 22. Drive Current A (Low V
DDEXT
V
V
V
DDEXT
DDEXT
DDEXT
)
= 2.95V @ 95°C
= 3.30V@25°C
= 3.65V @ –40°C
V
OH
V
OL
100
–50
SOURCE CURRENT (mA)
–100
–150
150
100
50
0
0
0.51.01.52.02.53.0
SOURCE VOLTAGE (V)
Figure 24. Drive Current B (Low V
50
V
V
V
DDEXT
V
V
V
DDEXT
DDEXT
DDEXT
)
DDEXT
DDEXT
DDEXT
= 2.25V @ 95°C
= 2.50V @ 25°C
= 2.75V @ –40°C
V
OH
V
OL
= 2.95V @ 95°C
= 3.30V@25°C
= 3.65V @ –40°C
–50
SOURCE CURRENT (mA)
–100
–150
0
0
0.51.01.52.02.53.53.0
Figure 23. Drive Current A (High V
SOURCE VOLTAGE (V)
DDEXT
)
V
OH
V
OL
0
–50
SOURCE CURRENT (mA)
–100
–150
00.51.01.52.02.53.53.0
Figure 25. Drive Current B (High V
SOURCE VOLTAGE (V)
DDEXT
)
V
OH
V
OL
Rev. 0 | Page 40 of 52 | January 2005
Page 41
ADSP-BF561
150
100
50
0
–50
–100
–150
SOURCE CURRENT (mA)
V
OH
V
OL
00.51.01.52.02.53.53.0
SOURCE VOLTAGE (V)
V
DDEXT
= 2.95V @ 95°C
V
DDEXT
= 3.30V@25°C
V
DDEXT
= 3.65V @ –40°C
60
V
DDEXT
40
20
0
–20
–40
SOURCE CURRENT (mA)
–60
0
0.51.01.52.02.53.0
SOURCE VOLTAGE (V)
Figure 26. Drive Current C (Low V
100
80
60
40
20
0
–20
–40
SOURCE CURRENT (mA)
–60
–80
–100
00.51.01.52.02.53.53.0
SOURCE VOLTAGE (V)
V
V
DDEXT
V
V
V
DDEXT
DDEXT
)
DDEXT
DDEXT
DDEXT
= 2.25V @ 95°C
= 2.50V @ 25°C
= 2.75V @ –40°C
V
OH
V
OL
= 2.95V @ 95°C
= 3.30V@25°C
= 3.65V @ –40°C
V
OH
V
OL
100
–20
–40
SOURCE CURRENT (mA)
–60
–80
–100
V
= 2.25V @ 95°C
80
60
40
20
0
0
0.51.01.52.02.53.0
SOURCE VOLTAGE (V)
Figure 28. Drive Current D (Low V
DDEXT
V
DDEXT
V
DDEXT
DDEXT
)
= 2.50V @ 25°C
= 2.75V @ –40°C
V
OH
V
OL
Figure 27. Drive Current C (High V
)
DDEXT
Rev. 0 | Page 41 of 52 | January 2005
Figure 29. Drive Current D (High V
DDEXT
)
Page 42
ADSP-BF561
POWER DISSIPATION
Total power dissipation has two components, one due to internal circuitry (P
output drivers (P
internal circuitry (V
dent on the instruction execution sequence and the data
operands involved.
Table 28. Internal Power Dissipation
Parameter
2
I
DDTYP
3
I
DDSLEEP
I
DDDEEPSLEEP
I
DDHIBERNATE
1
IDD data is specified for typical process parameters. All data at 25 °C.
2
Processor executing 75% dual Mac, 25% ADD with moderate data bus activity.
3
See the ADSP-BF561 Blackfin Processor Hardware Reference Manual for defini-
4
Measured at V
3
4
tions of Sleep and Deep Sleep operating modes.
) and one due to the switching of external
INT
). Table 28 shows the power dissipation for
EXT
). Internal power dissipation is depen-
DDINT
Test Conditions1
f
=
CCLK
50 MHz
V
DDINT
0.8 V
=
f
=
CCLK
500 MHz
V
=
DDINT
1.25 V
f
=
CCLK
600 MHz
V
=
DDINT
1.25 VUnit
66450520mA
309191mA
278484mA
50µA
= 3.65 V with voltage regulator off (V
DDEXT
DDINT
= 0 V).
The external component is calculated using:
P
EXT
OC×V
2
×f×=
DD
The frequency f includes driving the load high and then back
low. For example: DATA31—0 pins can drive high and low at a
maximum rate of 1/(2 × t
) while in SDRAM burst mode.
SCLK
A typical power consumption can now be calculated for these
conditions by adding a typical internal power dissipation.
P
TotalPEXTIDDVDDINT
Note that the conditions causing a worst-case P
those causing a worst-case P
INT
×()+=
. Maximum P
differ from
EXT
cannot occur
INT
while 100% of the output pins are switching from all ones to all
zeros. Note also that it is not common for an application to have
100%, or even 50%, of the outputs switching simultaneously.
The external component of total power dissipation is caused by
the switching of output pins. Its magnitude depends on
• The number of output pins that switch during each
cycle (O).
• The maximum frequency at which they can switch (f).
• Their load capacitance (C).
• Their voltage swing (V
DDEXT
).
Rev. 0 | Page 42 of 52 | January 2005
Page 43
TEST CONDITIONS
The ac signal specifications (timing parameters) appear in Tim-
ing Specifications on Page 22. These include output disable
time, output enable time, and capacitive loading. The timing
specifications for the processor apply for the voltage reference
levels in Figure 32.
Output Enable Time
Output pins are considered to be enabled when they have made
a transition from a high impedance state to the point when they
start driving. The output enable time t
point when a reference signal reaches a high or low voltage level
to the point when the output starts driving, as shown in the
Output Enable/Disable diagram (Figure 30). The time
t
ENA_MEASURED
is the interval from when the reference signal
switches to when the output voltage reaches 2.0 V (output high)
or 1.0 V (output low). Time t
is the interval from when the
TRIP
output starts driving to when the output reaches the 1.0 V or
2.0 V trip voltage. Time t
t
ENAtENA_MEASUREDtTRIP
is calculated as:
ENA
–=
If multiple pins (such as the data bus) are enabled, the measurement value is that of the first pin to start driving.
is the interval from the
ENA
t
DIS
V
OH
(MEASURED)
V
OL
(MEASURED)
OUTPUT STOPS DRIVING
TO
OUTPUT
PIN
ADSP-BF561
REFERENCE
SIGNAL
t
DIS-MEASURED
V
(MEASURED) - ⌬V
OH
VOL(MEASURED) + ⌬V
t
DECAY
VOLTAGE T O BE APPROXIMATELY 1.5V.
Figure 30. Output Enable/Disable
t
ENA
OUTPUT STARTS DRIVING
HIGH IMPEDANCE STATE.
TEST CONDITIONS CAUSE THIS
50⍀
30pF
t
ENA-MEASURED
V
2.0V
(MEASURED)
1.0V
V
(MEASURED)
t
TRIP
1.5V
OH
OL
Output Disable Time
Output pins are considered to be disabled when they stop driving, go into a high impedance state, and start to decay from their
output high or low voltage. The time for the voltage on the bus
to decay by ∆V is dependent on the capacitive load, C
load current, I
. This decay time can be approximated by the fol-
L
, and the
L
lowing equation:
t
DECAY
The output disable time t
and t
, as shown in Figure 30.The time t
DECAY
CLV∆()IL⁄=
is the difference between t
DIS
DIS_MEASURED
DIS_MEASURED
is the
interval from when the reference signal switches to when the
output voltage decays ∆V from the measured output high or
output low voltage. t
is calculated with test loads CL and IL,
DECAY
and with ∆V equal to 0.5 V.
Example System Hold Time Calculation
To determine the data output hold time in a particular system,
first calculate t
using the equation given above. Choose ∆V
DECAY
to be the difference between the ADSP-BF561 output voltage
and the input threshold for the device requiring the hold time. A
typical ∆V will be 0.4 V. C
line), and I
is the total leakage or three-state current (per data
L
line). The hold time will be t
time (i.e., t
for an SDRAM write cycle).
DSDAT
is the total bus capacitance (per data
L
plus the minimum disable
DECAY
Capacitive Loading
Output delays and holds are based on standard capacitive loads
–30 pF on all pins (see Figure 31 on Page 43). Figure 33 on
Page 44 to Figure 40 on Page 45 show graphically how output
Figure 31. Equivalent Device Loading for AC Measurements (Includes All
Fixtures)
INPUT
1.5V1.5V
OR
OUTPUT
Figure 32. Voltage Reference Levels for AC Measurements (Except Output
Enable/Disable)
Rev. 0 | Page 43 of 52 | January 2005
Page 44
ADSP-BF561
delays and holds vary with load capacitance (note that these
graphs or deratings do not apply to output disable delays; see
Output Disable Time on Page 43). The graphs may not be linear
outside the ranges shown.
ABE_B[0] (133MHz DRIVER), EVDD
14
12
10
8
6
4
RISE AND FALLTIME ns (10%-90%)
2
0
050100150
LOAD CAPACITANCE (pF)
= 2.25V, TEMPERATURE = 85°C
MIN
RISE TIME
FALLTIME
200
Figure 33. Typical Output Delay or Hold for Driver A at EVDD
ABE0 (133MHz DRIVER), EVDD
12
10
8
6
4
RISE AND FALLTIME ns (10%-90%)
2
0
050100150200250
LOAD CAPACITANCE (p F)
= 3.65V, TEMPERATURE = 85°C
MAX
RISE TIME
FALLTIME
MIN
250
CLKOUT (CLKOUT DRIVER), EVDD
12
10
8
6
4
RISE AND FALLTIME ns (10%-90%)
2
0
050100150200250
LOAD CAPACITANCE (pF)
= 2.25V, TEMPERATURE = 85°C
MIN
RISE TIME
FALLTIME
Figure 35. Typical Output Delay or Hold for Driver B at EVDD
CLKOUT (CLKOUT DRIVER), EVDD
10
9
8
7
6
5
4
3
RISE AND FALLTIME ns (10%-90%)
2
1
0
050100150200250
LOAD CAPACITANCE (pF)
= 3.65V, TEMPERATURE = 85°C
MAX
RISE TIME
FALLTIME
MIN
Figure 34. Typical Output Delay or Hold for Driver A at EVDD
Rev. 0 | Page 44 of 52 | January 2005
MAX
Figure 36. Typical Output Delay or Hold for Driver B at EVDD
MAX
Page 45
ADSP-BF561
TMR0 (33MHz DRIVER), EVDD
30
25
20
15
10
RISE AND FALLTIME ns (10%-90%)
5
0
050100150200250
LOAD CAPACITANCE (pF)
= 2.25V, TEMPERATURE = 85°C
MIN
RISE TIME
FALLTIME
Figure 37. Typical Output Delay or Hold for Driver C at EVDD
TMR0 (33MHz DRIVER), EVDD
20
18
16
14
12
10
8
6
RISE AND FALLTIME ns (10%-90%)
4
2
0
050100150200250
LOAD CAPACITANCE (pF)
= 3.65V, TEMPERATURE = 85°C
MAX
RISE TIME
FALLTIME
SCK (66MHz DRIVER), EVDD
18
16
14
12
10
8
6
4
RISE AND FALLTIME ns (10%-90%)
2
0
050100150200250
MIN
Figure 39. Typical Output Delay or Hold for Driver D at EVDD
SCK (66MHz DRIVER), EVDD
14
12
10
8
6
4
RISE AND FALLTIME ns (10%-90%)
2
0
050100150200250
LOAD CAPACITANCE (pF)
LOAD CAPACITANCE (pF)
= 2.25V, TEMPERATURE = 85°C
MIN
RISE TIME
FALLTIME
= 3.65V, TEMPERATURE = 85°C
MAX
RISE TIME
FALLTIME
MIN
Figure 38. Typical Output Delay or Hold for Driver C at EVDD
Rev. 0 | Page 45 of 52 | January 2005
MAX
Figure 40. Typical Output Delay or Hold for Driver D at EVDD
MAX
Page 46
ADSP-BF561
ENVIRONMENTAL CONDITIONS
To determine the junction temperature on the application
printed circuit board use:
TJT
where:
T
= junction temperature (ⴗC).
J
= case temperature (ⴗC) measured by customer at top cen-
T
CASE
ter of package.
= from Table 29 and Table 30.
Ψ
JT
= power dissipation (see Power Dissipation on Page 42 for
P
D
the method to calculate P
Values of θ
are provided for package comparison and printed
JA
circuit board design considerations. θ
order approximation of T
TAθJAPD×()+=
T
J
where:
T
= ambient temperature (ⴗC).
A
In Table 29 and Table 30, airflow measurements comply with
JEDEC standards JESD51–2 and JESD51–6, and the junctionto-board measurement complies with JESD51–8. The junctionto-case measurement complies with MIL-STD-883
(Method 1012.1). All measurements use a 2S2P JEDEC test
board.
Thermal resistance θ
merit relating to performance of the package and board in a
convective environment. θ
under two conditions of airflow. θ
extracted from the periphery of the board. Ψ
correlation between T
package comparison and printed circuit board design
considerations.
ΨJTPD×()+=
CASE
).
D
can be used for a first
by the equation:
J
in Table 29 and Table 30 is the figure of
JA
represents the thermal resistance
JMA
and T
J
CASE
JA
represents the heat
JB
represents the
JT
. Values of θJB are provided for
Table 30. Thermal Characteristics for B-297 Package
ParameterConditionTypicalUnit
θ
JA
θ
JMA
θ
JMA
θ
JB
θ
JC
Ψ
JT
0 Linear m/s Airflow20.6ⴗC/W
1 Linear m/s Airflow17.8ⴗC/W
2 Linear m/s Airflow17.4ⴗC/W
Not Applicable16.3ⴗC/W
Not Applicable7.15ⴗC/W
0 Linear m/s Airflow0.37ⴗC/W
Table 29. Thermal Characteristics for BC-256 Package
ParameterConditionTypicalUnit
θ
JA
θ
JMA
θ
JMA
θ
JB
θ
JC
Ψ
JT
0 Linear m/s Airflow25.6ⴗC/W
1 Linear m/s Airflow22.4ⴗC/W
2 Linear m/s Airflow21.6ⴗC/W
Not Applicable18.9ⴗC/W
Not Applicable4.85ⴗC/W
0 Linear m/s Airflow0.15ⴗC/W
Rev. 0 | Page 46 of 52 | January 2005
Page 47
ADSP-BF561
256-BALL MBGA PINOUT
Table 31. 256-Ball MBGA Pin Assignment (Numerically by Ball Number)
Ball No. SignalBall No. SignalBall No. SignalBall No. Signal
Dimensions in the outline dimension figures are shown in
millimeters.
ADSP-BF561
a
A1 BALL
PAD CORNER
1.70
1.51
1.36
12.00 BSC SQ
TOP VIEW
SIDE VIEW
DETAIL A
256-BALL MINI BGA
(BC-256)
0.65 BSC
BALL PITCH
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
T
9.75 BSC SQ
CL
BOTTOMVIEW
34567891011121314151612
0.25 MIN
A1 BALL
PAD CORNER
CL
NOTES
1. DIMENSIONS ARE IN MILLIMETERS.
2. COMPLIES WITH JEDEC REGISTERED OUTLINE
MO-225, WITH NO EXACT PACKAGE SIZE AND
EXCEPTION TO PACKAGE HEIGHT.
3. MINIMUM BALL HEIGHT 0.25
0.10 MAX
COPLANARITY
BALL DIAMETER
0.45
0.40
0.35
Figure 41. 256-Ball Mini-Ball Grid Array
Rev. 0 | Page 51 of 52 | January 2005
DETAIL A
SEATING PLANE
Page 52
ADSP-BF561
a
A1 BALL
PAD CORNER
2.43
2.23
2.03SIDE VIEW
27.00 BSC SQ
TOP VIEW
DETAIL A
297-BALL PBGA
(B-297)
1.00 BSC
BALL PITCH
A
B
C
D
E
F
G
H
J
K
L
M
N
P
R
T
U
V
W
Y
AA
AB
AC
AD
AE
AF
25.00 BSC SQ
8.00
CL
BOTTOMVIEW
3456789101112131415161718192021222324252612
0.40 MIN
A1 BALL
PAD CORNER
8.00
CL
NOTES
1. DIMENSIONS ARE IN MILLIMETERS.
2. COMPLIES WITH JEDEC REGISTERED OUTLINE
MS-034, VARIATION AAL-1.
3. MINIMUM BALL HEIGHT 0.40
0.20 MAX
COPLANARITY
BALL DIAMETER
0.70
0.60
0.50
DETAIL A
SEATING PLANE
Figure 42. 297-Ball PBGA Grid Array
ORDERING GUIDE
Temperature
Range
Part Number
ADSP-BF561SKBCZ600
ADSP-BF561SKBCZ500
(Ambient)Package Description
1
0°C to +70°CBall Grid Array (Mini-BGA) BC-256600 MHz1.25 V Internal, 2.5 V or 3.3 V I/O
1
0°C to +70°CBall Grid Array (Mini-BGA) BC-256500 MHz1.25 V Internal, 2.5 V or 3.3 V I/O
ADSP-BF561SBB600–40°C to +85°C Plastic Ball Grid Array (PBGA) B-297600 MHz1.35 V Internal, 2.5 V or 3.3 V I/O
ADSP-BF561SBB500–40°C to +85°C Plastic Ball Grid Array (PBGA) B-297500 MHz1.25 V Internal, 2.5 V or 3.3 V I/O