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

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
Design Checklist
F-2
9. Chip Select, DTAC K Generation
10. Chip Select, Option Register
11. A0–A7, D0–D7, Initialize, Reset
12. BSET Instruction, Byte
13. Exception Vector Table, Initialize, Reset
14. Stack Pointer, Initialize, Reset
15. Parameter RAM, Initialize, Reset
16. EQU, Parameter RAM
spec (see spec 32), or the total system reset may not be terminated correctly and un-
usual behavior may occur. Also, when using the RESET instruction to reset the
MC68302 internal peripherals, a strong pullup (such as 1.2K ohms) may be required
for proper rise times.
If unexpected behavior is occurring on the DTACK line, such as early or late assertion
or negation, then often the problem is traced to another component on the board that
is generating DTACK at the same time as the IMP DTACK generator. An often over-
looked source for DTACK generation is the emulator overlay memory (if an emulator
is used), which may have been inadvertently configured to overlap with a chip-select
area of the IMP. Very unusual behavior can result, especially if the number of wait
states programmed for the chip select is different from that of the overlay memory.
When setting up the chip select option register to operate as an address mask, the val-
ue programmed into the base address mask field should normally have all ones at the
left end and all zeros at the right end. Any zeros mixed between ones in the option reg-
ister base address mask field will cause multiple responses of the chip-select pin
throughout the MC68302 address space. In most applications, this is undesirable and
confusing.
The M68000 registers A0–A7 and D0–D7 do not have predefined values upon a total
system reset. The use of uninitialized (or partially uninitialized) registers can cause in-
termittent and erratic software behavior since the initialized register values may vary
from reset to reset.
To use the bit set instruction (BSET) to set a bit in the lower half of a word-sized reg-
ister or memory location, one MUST perform a byte operation on the byte address, i.e.,
word_address + 1. For example, to set bit zero of a word address $3000, one must
issue BSET.B #0,#$3001. There is no BSET.W instruction available in the MC68000.
This also applies to the BTST instruction.
Failure to provide the M68000 core exception vector table with vectors can cause er-
ratic behavior when an exception (such as bus error) occurs. Make sure that the boot
ROM/EPROM has exception vectors initialized, and that the initial reset vector causes
the program to start at an address above the vector table.
The stack pointer must be initialized to an EVEN address; otherwise, address errors
will occur when the stack is first used.
To use SCCs with specific protocols, both general-purpose parameters and protocol-
specific parameters must be initialized. Failure to initialize the parameter RAM will re-
sult in erratic behavior since the parameter RAM does not have predefined values
upon a total system reset.
Very unusual problems with the SCCs are often traced to the fact that the source code
MC68360 USER’S MANUAL
MOTOROLA

Related parts for MC68000