MC68000 MOTOROLA [Motorola, Inc], MC68000 Datasheet - Page 59

no-image

MC68000

Manufacturer Part Number
MC68000
Description
Manufacturer
MOTOROLA [Motorola, Inc]
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
MC68000-10/BZAJC
Manufacturer:
MOT
Quantity:
26
Part Number:
MC68000-8BXAJ
Manufacturer:
MOT
Quantity:
9
Part Number:
MC680008FN8
Manufacturer:
FREESCALE
Quantity:
8 831
Part Number:
MC680008L8
Manufacturer:
AMD
Quantity:
42
Part Number:
MC68000FN10
Manufacturer:
MOT
Quantity:
5 510
Part Number:
MC68000FN10
Manufacturer:
MOTOROLA/摩托罗拉
Quantity:
20 000
Part Number:
MC68000FN12
Manufacturer:
MOT
Quantity:
5 510
Part Number:
MC68000L8
Manufacturer:
MOTOROLA/摩托罗拉
Quantity:
20 000
Part Number:
MC68000P10
Manufacturer:
MOT
Quantity:
1 000
Part Number:
MC68000P10
Manufacturer:
MOT
Quantity:
20 000
3.1.4 IDMA Operational Description
Every IDMA operation involves the following steps: IDMA channel initialization, data trans-
fer, and block termination. In the initialization phase, the M68000 core (or external proces-
sor) loads the registers with control information, address pointers and transfer count, and
then starts the channel. In the transfer phase, the IDMA accepts requests for operand trans-
fers and provides addressing and bus control for the transfers. The termination phase oc-
curs when the operation is complete and the IDMA interrupts the M68000 core, if interrupts
are enabled.
3.1.4.1 Channel Initialization
To start a block transfer operation, the M68000 core must initialize IDMA registers with in-
formation describing the data block, device type, request generation method, and other spe-
cial control options. See 3.1.2 IDMA Registers (Independent DMA Controller) and 3.1.5
IDMA Programming for further details.
3.1.4.2 Data Transfer
The IDMA supports dual address transfers only. Thus, each operand transfer consists of a
source operand read and a destination operand write. The source operand is read from the
address contained in the SAPR into the DHR. When the source and destination operand siz-
es differ, the operand read may take up to two bus cycles to complete. The operand is then
written to the address contained in the DAPR. Again, this transfer may be up to two bus cy-
cles long. In this manner, various combinations of peripheral, memory, and operand sizes
may be used.
Source Operand Read
Destination Operand Write
MOTOROLA
During this cycle, the SAPR drives the address bus, the FCR drives the source function
codes, and the CMR drives the size control. The data is read from memory or the periph-
eral and placed temporarily into the data holding register (DHR) when the bus cycle is ter-
minated with DTACK. When the complete operand has been read, the SAPR is
incremented by one or two, depending on the address and size information. See 3.1.2.2
Source Address Pointer Register (SAPR) for more details.
During this cycle, the data in DHR is written to the device or memory selected by the ad-
dress from the DAPR, using the destination function codes from the FCR and the size
from the CMR. The same options exist for operand size and alignment as for the source
operand read. When the complete operand is written, the DAPR is incremented by one or
two, and the BCR is decremented by the number of bytes transferred. See 3.1.2.3 Desti-
nation Address Pointer Register (DAPR) and 3.1.2.5 Byte Count Register (BCR) for more
details.
When the SAPR and DAPR are programmed not to increment
and the bus width is 16 bits, the SAPR and DAPR addresses
must be even.
MC68302 USER’S MANUAL
NOTE
System Integration Block (SIB)
3-9

Related parts for MC68000