EFM32G200F16 Energy Micro, EFM32G200F16 Datasheet - Page 223

• Manufacturer Part Number: EFM32G200F16
• Description: MCU 32BIT 16KB FLASH 32-QFN
• Manufacturer: Energy Micro
• Series: Geckor

Specifications of EFM32G200F16

• Core Processor: ARM® Cortex-M3™
• Core Size: 32-Bit
• Speed: 32MHz
• Connectivity: EBI/EMI, I²C, IrDA, SmartCard, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, DMA, POR, PWM, WDT
• Number Of I /o: 24
• Program Memory Size: 16KB (16K x 8)
• Program Memory Type: FLASH
• Ram Size: 8K x 8
• Voltage - Supply (vcc/vdd): 1.8 V ~ 3.8 V
• Data Converters: A/D 4x12b, D/A 1x12b
• Oscillator Type: External
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 32-VQFN Exposed Pad
• Processor Series: EFM32G200
• Core: ARM Cortex-M3
• Data Bus Width: 32 bit
• Data Ram Size: 8 KB
• Interface Type: I2C, UART
• Maximum Clock Frequency: 32 MHz
• Number Of Programmable I/os: 24
• Number Of Timers: 2
• Operating Supply Voltage: 1.8 V to 3.8 V
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• Minimum Operating Temperature: - 40 C
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Eeprom Size: -
• Lead Free Status / Rohs Status: Details

18.3.5.2 Blocking Incoming Data
18.3.5.3 Data Sampling
2010-09-06 - d0001_Rev1.00
Figure 18.4. LEUART Receiver Overview
When using hardware frame recognition, as detailed in Section 18.3.5.6 (p. 224) , Section 18.3.5.7 (p.
225) , and Section 18.3.5.8 (p. 225) , it is necessary to be able to let the receiver sample
incoming frames without passing the frames to software by loading them into the receive buffer. This is
accomplished by blocking incoming data.
Incoming data is blocked as long as RXBLOCK in LEUARTn_STATUS is set. When blocked, frames
received by the receiver will not be loaded into the receive buffer, and software is not notified by the
RXDATAV bit in LEUARTn_STATUS or the RXDATAV interrupt flag in LEUARTn_IF at their arrival.
For data to be loaded into the receive buffer, RXBLOCK must be cleared in the instant a frame is fully
received by the receiver. RXBLOCK is set by setting RXBLOCKEN in LEUARTn_CMD and disabled
by setting RXBLOCKDIS also in LEUARTn_CMD. There are two exceptions where data is loaded into
the receive buffer even when RXBLOCK is set. The first is when an address frame is received when
in operating in multi-processor mode as shown in Section 18.3.5.8 (p. 225) . The other case is when
receiving a start-frame when SFUBRX in LEUARTn_CTRL is set; see Section 18.3.5.6 (p. 224)
Frames received containing framing or parity errors will not result in the FERR and PERR interrupt flags
in LEUARTn_IF being set while RXBLOCK is set. Hardware recognition is not applied to these erroneous
frames, and they are silently discarded.
Note
The receiver samples each incoming baud as close as possible to the middle of the baud-period. Except
for the start-bit, only a single sample is taken of each of the incoming bauds.
The length of a baud-period is given by 1 + LEUARTn_CLKDIV/256, as a number of 32.768 kHz clock
periods. Let the clock cycle where a start-bit is first detected be given the index 0. The optimal sampling
point for each baud in the UART frame is then given by the following equation:
LEUART Optimal Sampling Point
LEUn_RX
If a frame is received while RXBLOCK in LEUARTn_STATUS is cleared, but stays in the
receive shift register because the receive buffer is full, the received frame will be loaded into
the receive buffer when space becomes available even if RXBLOCK is set at that time.
The overflow interrupt flag RXOF in LEUARTn_IF will be set if a frame in the receive shift
register, waiting to be loaded into the receive buffer is overwritten by an incoming frame
even though RXBLOCK is set.
RXENS
Receive shift register
d0-d8
status
! RXBLOCK
...the world's most energy friendly microcontrollers
223
d0
d1
d2
RXDATA
d3
(RXDATAXP)
d4
RXDATAX
d5
d6
d7
d8
www.energymicro.com
status
Receive buffer