MC68376BAMFT20 Freescale Semiconductor, MC68376BAMFT20 Datasheet - Page 114

• Manufacturer Part Number: MC68376BAMFT20
• Manufacturer: Freescale Semiconductor

Specifications of MC68376BAMFT20

• Cpu Family: 68K/M683xx
• Device Core: ColdFire
• Device Core Size: 32b
• Frequency (max): 20MHz
• Interface Type: QSPI/SCI
• Program Memory Type: ROM
• Program Memory Size: 8KB
• Total Internal Ram Size: 7.5KB
• # I/os (max): 18
• Number Of Timers - General Purpose: 2
• Operating Supply Voltage (typ): 5V
• Operating Supply Voltage (max): 5.25V
• Operating Supply Voltage (min): 4.75V
• On-chip Adc: 16-chx10-bit
• Instruction Set Architecture: RISC
• Operating Temp Range: -40C to 125C
• Operating Temperature Classification: Automotive
• Mounting: Surface Mount
• Pin Count: 160
• Package Type: PQFP
• Lead Free Status / Rohs Status: Not Compliant

5.6.5.1 Bus Errors
5.6.5.2 Double Bus Faults
5-36
MOTOROLA
The CPU32 treats bus errors as a type of exception. Bus error exception processing
begins when the CPU32 detects assertion of the IMB BERR signal (by the internal bus
monitor or an external source) while the HALT signal remains negated.
BERR assertions do not force immediate exception processing. The signal is synchro-
nized with normal bus cycles and is latched into the CPU32 at the end of the bus cycle
in which it was asserted. Because bus cycles can overlap instruction boundaries, bus
error exception processing may not occur at the end of the instruction in which the bus
cycle begins. Timing of BERR detection/acknowledge is dependent upon several fac-
tors:
Because of these factors, it is impossible to predict precisely how long after occur-
rence of a bus error the bus error exception is processed.
Exception processing for bus error exceptions follows the standard exception process-
ing sequence. Refer to 4.9 Exception Processing for more information. However, a
special case of bus error, called double bus fault, can abort exception processing.
BERR assertion is not detected until an instruction is complete. The BERR latch is
cleared by the first instruction of the BERR exception handler. Double bus fault occurs
in three ways:
• Which bus cycle of an instruction is terminated by assertion of BERR.
• The number of bus cycles in the instruction during which BERR is asserted.
• The number of bus cycles in the instruction following the instruction in which
• Whether BERR is asserted during a program space access or a data space ac-
1. When bus error exception processing begins and a second BERR is detected
2. When one or more bus errors occur before the first instruction after a reset ex-
3. A bus error occurs while the CPU32 is loading information from a bus error
BERR is asserted.
cess.
before the first instruction of the exception handler is executed.
ception is executed.
stack frame during a return from exception (RTE) instruction.
If DSACK or BERR remain asserted into S2 of the next bus cycle,
that cycle may be terminated prematurely.
The external bus interface does not latch data when an external bus
cycle is terminated by a bus error. When this occurs during an in-
struction prefetch, the IMB precharge state (bus pulled high, or $FF)
is latched into the CPU32 instruction register, with indeterminate re-
sults.
SYSTEM INTEGRATION MODULE
WARNING
CAUTION
USER’S MANUAL
MC68336/376