MC68HC11E0CFNE3 Freescale Semiconductor, MC68HC11E0CFNE3 Datasheet - Page 83

• Manufacturer Part Number: MC68HC11E0CFNE3
• Description: IC MCU 8BIT 3MHZ 52-PLCC
• Manufacturer: Freescale Semiconductor
• Series: HC11r

Specifications of MC68HC11E0CFNE3

• Core Processor: HC11
• Core Size: 8-Bit
• Speed: 3MHz
• Connectivity: SCI, SPI
• Peripherals: POR, WDT
• Number Of I /o: 38
• Program Memory Type: ROMless
• Ram Size: 512 x 8
• Voltage - Supply (vcc/vdd): 4.5 V ~ 5.5 V
• Data Converters: A/D 8x8b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 52-PLCC
• Controller Family/series: 68HC11
• No. Of I/o's: 38
• Ram Memory Size: 512Byte
• Cpu Speed: 3MHz
• No. Of Timers: 1
• Embedded Interface Type: SCI, SPI
• Digital Ic Case Style: LCC
• Rohs Compliant: Yes
• Processor Series: HC11E
• Core: HC11
• Data Bus Width: 8 bit
• Data Ram Size: 512 B
• Interface Type: SCI, SPI
• Maximum Clock Frequency: 3 MHz
• Number Of Programmable I/os: 38
• Number Of Timers: 8
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 8 bit, 8 Channel
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Program Memory Size: -
• Lead Free Status / Rohs Status: Details

8.5 SPI Registers
TECHNICAL DATA
indicates that an attempt was made to write data to the SPDR while a transfer was in
progress.
When the SPI system is configured as a master and the SS input line goes to active
low, a mode fault error has occurred — usually because two devices have attempted
to act as master at the same time. In cases where more than one device is concurrent-
ly configured as a master, there is a chance of contention between two pin drivers. For
push-pull CMOS drivers, this contention can cause permanent damage. The mode
fault attempts to protect the device by disabling the drivers. The MSTR control bit in
the SPCR and all four DDRD control bits associated with the SPI are cleared. An in-
terrupt is generated subject to masking by the SPIE control bit and the I bit in the CCR.
Other precautions may need to be taken to prevent driver damage. If two devices are
made masters at the same time, mode fault does not help protect either one unless
one of them selects the other as slave. The amount of damage possible depends on
the length of time both devices attempt to act as master.
A write collision error occurs if the SPDR is written while a transfer is in progress. Be-
cause the SPDR is not double buffered in the transmit direction, writes to SPDR cause
data to be written directly into the SPI shift register. Because this write corrupts any
transfer in progress, a write collision error is generated. The transfer continues undis-
turbed, and the write data that caused the error is not written to the shifter.
A write collision is normally a slave error because a slave has no control over when a
master initiates a transfer. A master knows when a transfer is in progress, so there is
no reason for a master to generate a write-collision error, although the SPI logic can
detect write collisions in both master and slave devices.
The SPI configuration determines the characteristics of a transfer in progress. For a
master, a transfer begins when data is written to SPDR and ends when SPIF is set.
For a slave with CPHA equal to zero, a transfer starts when SS goes low and ends
when SS returns high. In this case, SPIF is set at the middle of the eighth SCK cycle
when data is transferred from the shifter to the parallel data register, but the transfer
is still in progress until SS goes high. For a slave with CPHA equal to one, transfer be-
gins when the SCK line goes to its active level, which is the edge at the beginning of
the first SCK cycle. The transfer ends in a slave in which CPHA equals one when SPIF
is set. For a slave, after a byte transfer, SCK must be in inactive state for at least 2 E-
clock cycles before the next byte transfer begins.
The three SPI registers, SPCR, SPSR, and SPDR, provide control, status, and data
storage functions. Refer to the following information for a description of how these reg-
isters are organized.
Freescale Semiconductor, Inc.
For More Information On This Product,
SERIAL PERIPHERAL INTERFACE
Go to: www.freescale.com
8-5