MCF5270CAB100 Freescale Semiconductor, MCF5270CAB100 Datasheet - Page 80

• Manufacturer Part Number: MCF5270CAB100
• Description: MCU V2 COLDFIRE 64K SRAM 160-QFP
• Manufacturer: Freescale Semiconductor
• Series: MCF527xr

Specifications of MCF5270CAB100

• Core Processor: Coldfire V2
• Core Size: 32-Bit
• Speed: 100MHz
• Connectivity: EBI/EMI, Ethernet, I²C, SPI, UART/USART
• Peripherals: DMA, WDT
• Number Of I /o: 39
• Program Memory Type: ROMless
• Ram Size: 64K x 8
• Voltage - Supply (vcc/vdd): 1.4 V ~ 1.6 V
• Oscillator Type: External
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 160-QFP
• Processor Series: MCF527x
• Core: ColdFire V2
• 3rd Party Development Tools: JLINK-CF-BDM26, EWCF
• Development Tools By Supplier: NNDK-MOD5272-KIT, NNDK-MOD5270-KIT
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Program Memory Size: -
• Data Converters: -
• Lead Free Status / Rohs Status: Details

ColdFire Core
10 and 11, respectively. The V2 core does not provide illegal instruction detection on the extension
words on any instruction, including MOVEC.
3.7.4
Attempting to divide by zero causes an exception (vector 5, offset = 0x014).
3.7.5
The attempted execution of a supervisor mode instruction while in user mode generates a privilege
violation exception. See the ColdFire Programmer’s Reference Manual for lists of supervisor- and
user-mode instructions.
3.7.6
To aid in program development, all ColdFire processors provide an instruction-by-instruction
tracing capability. While in trace mode, indicated by the assertion of the T-bit in the status register
(SR[15] = 1), the completion of an instruction execution (for all but the STOP instruction) signals
a trace exception. This functionality allows a debugger to monitor program execution.
The STOP instruction has the following effects:
If the processor is not in trace mode and executes a STOP instruction where the immediate operand
sets SR[T], hardware loads the SR and generates a trace exception. The PC in the exception stack
frame points to the instruction after the STOP, and the SR reflects the value loaded in step 2.
Because ColdFire processors do not support any hardware stacking of multiple exceptions, it is the
responsibility of the operating system to check for trace mode after processing other exception
types. As an example, consider the execution of a TRAP instruction while in trace mode. The
processor will initiate the TRAP exception and then pass control to the corresponding handler. If
the system requires that a trace exception be processed, it is the responsibility of the TRAP
exception handler to check for this condition (SR[15] in the exception stack frame asserted) and
pass control to the trace handler before returning from the original exception.
3-14
1. The instruction before the STOP executes and then generates a trace exception. In the
2. When the trace handler is exited, the STOP instruction is executed, loading the SR with
3. The processor then generates a trace exception. The PC in the exception stack frame
exception stack frame, the PC points to the STOP opcode.
the immediate operand from the instruction.
points to the instruction after the STOP, and the SR reflects the value loaded in the
previous step.
Divide-By-Zero
Privilege Violation
Trace Exception
MCF5271 Reference Manual, Rev. 2
Freescale Semiconductor