MCIMX286CVM4B Freescale Semiconductor, MCIMX286CVM4B Datasheet - Page 1637

• Manufacturer Part Number: MCIMX286CVM4B
• Description: IC MPU I.MX286 289MAPBGA
• Manufacturer: Freescale Semiconductor
• Series: i.MX28r

Specifications of MCIMX286CVM4B

• Core Processor: ARM9
• Core Size: 32-Bit
• Speed: 454MHz
• Connectivity: CAN, EBI/EMI, Ethernet, I²C, MMC, SmartCard, SPI, SSI, UART/USART, USB OTG
• Peripherals: DMA, I²S, LCD, POR, PWM, WDT
• Program Memory Size: 128KB (32K x 32)
• Program Memory Type: Mask ROM
• Ram Size: 32K x 32
• Voltage - Supply (vcc/vdd): 1.25 V ~ 5.25 V
• Data Converters: A/D 17x12b
• Oscillator Type: External
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 289-LFBGA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Number Of I /o: -
• Eeprom Size: -
• Lead Free Status / Rohs Status: Compliant

Receive Processing
When the SHIFT16 bit in ipaccRxConf register is enabled, each frame is received with two
additional bytes in front of the frame. The user application has to ignore these first two
bytes and has to find the first byte of the frame in bits 23:16 of the first word from the RX
FIFO.
Note that the SHIFT16 bit must be set during initialization and kept asserted during the
complete operation as it influences the FIFO write behavior.
Transmit Processing
When the SHIFT16 bit in ipaccTxConf register is enabled, the first two bytes of the first
word written (that is, bits 15:0) will be discarded immediately by the FIFO write logic.
The SHIFT16 bit can be enabled/disabled for each frame individually if required, but can
be changed only in-between frames.
26.3.11.4 Received Frame Discard
As the Receive FIFO must be operated in store and forward mode (Register
RX_SECTION_FULL must be set 0), received Frames can be discarded based on the
following errors:
Freescale Semiconductor, Inc.
1. The MAC function receives the frame with an error:
2. An IP frame is detected and the IP header checksum is wrong
3. An IP frame with a valid IP header and a valid IP header checksum is detected, the
Byte 13
protocol is known but the protocol specific checksum is wrong
...
• The Frame has an invalid payload length.
• Frame length is greater than MAX_FL.
• Frame received with a CRC-32 error.
• Frame truncated due to receive FIFO overflow.
• Frame is corrupted as PHY signaled an error (mii_rx_err asserted during reception).
Byte 12
i.MX28 Applications Processor Reference Manual, Rev. 1, 2010
Byte 11
Byte 10
Byte 9
Byte 8
Chapter 26 Ethernet Controller (ENET)
Byte 7
Byte 6
1637