HD6417750SBP200 Renesas Electronics America, HD6417750SBP200 Datasheet - Page 859

• Manufacturer Part Number: HD6417750SBP200
• Description: IC SUPERH MPU ROMLESS 256BGA
• Manufacturer: Renesas Electronics America
• Series: SuperH® SH7750r

Specifications of HD6417750SBP200

• Core Processor: SH-4
• Core Size: 32-Bit
• Speed: 200MHz
• Connectivity: EBI/EMI, FIFO, SCI, SmartCard
• Peripherals: DMA, POR, WDT
• Number Of I /o: 28
• Program Memory Type: ROMless
• Ram Size: 24K x 8
• Voltage - Supply (vcc/vdd): 1.8 V ~ 2.07 V
• Oscillator Type: External
• Operating Temperature: -20°C ~ 75°C
• Package / Case: 256-BGA
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Eeprom Size: -
• Program Memory Size: -
• Data Converters: -

Section 16 Serial Communication Interface with FIFO (SCIF)
SCK2/MRESET: As the manual reset pin is multiplexed with the SCK2 pin, a manual reset must
not be executed while the SCIF is operating in external clock mode.
When Using the DMAC: When using the DMAC for transmission/reception, inhibit output of
RXI and TXI interrupt requests to the interrupt controller. If interrupt request output is enabled,
interrupt requests to the interrupt controller will be cleared by the DMAC without regard to the
interrupt handler.
Serial Ports: Note that, when the SCIF pin value is read using a serial port, the value read will be
the value two peripheral clock cycles earlier.
Overrun Error Flag (SH7750): SCIF overrun error flag is not set in the case that overrun error
and flaming error occurred simultaneously in receiving data, that means 17th byte data which
overrun was accompanying with flaming error. In such case, only SCFSR2. ER flag which shows
occurrence of flaming error is set. Receive FIFO stores data received before the overrun and does
not store (i. e. lose) overrun data. SCIF has no bit which corresponds to SCFSR2. FER for the lost
data.
In addition to the overrun error handling software routine, exception handler should check co-
occurrence of overrun error when a flaming error is occurred and when a co-occurrence is found,
it should handle also overrun error (When (i) a overrun error solely occurred without
accompanying with other receive error and (ii) when a parity error is accompanied with overrun
error, usual overrun error handling can be used. Overrun error handling should rather be done
primarily).
Rev.7.00 Oct. 10, 2008 Page 773 of 1074
REJ09B0366-0700