MCIMX286CVM4B Freescale Semiconductor, MCIMX286CVM4B Datasheet - Page 1638

• 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

IP Accelerator Functions
If one of the errors occurs and the IP Accelerator function is configured to discard frames
(Register ipaccRxConf), the frame is automatically discarded. Statistics are maintained
normally and are not affected by this discard function.
26.3.11.5 IPv4 Fragments
When an IP (IPv4) fragment frame is received, only the IP header is inspected and its
checksum is verified. The 32-bit alignment operates on fragments as on normal IP frames,
as specified above.
The IP fragment frame payload is not inspected for any protocol headers, as such a protocol
header would only exist in the very first fragment. To assist in the protocol specific checksum
verification, the one's-complement sum is calculated on the IP payload (that is, all bytes
following the IP header) and provided with the frame status word.
26.3.11.6.1 Receive Processing
An Ethernet frame of type 0x86dd identifies an IP Version 6 frame (IPv6) Frame. If an IPv6
frame is received, the first IP header is inspected (first 10 words) which is available in every
IPv6 frame.
If the receive SHIFT16 function is enabled, the IP header is aligned on a 32-bit boundary
allowing more efficient processing (see 12.3 page 54).
For TCP and UDP datagrams, the pseudo-header checksum calculation is performed and
verified.
To assist in protocol specific checksum verification, the one's-complement sum is always
calculated on the IP payload (that is, all bytes following the IP header) and provided with
the frame status word. For example, if extension headers were present, their sum(s) can be
subtracted in software from the checksum to isolate the TCP/UDP datagram checksum if
required.
1638
The application software can take advantage of the payload
checksum delivered with the frame's status word to calculate the
protocol specific checksum of the datagram after all the fragments
have been received and reassembled.
For example, if a TCP payload is delivered by multiple IP
fragments, the application software can calculate the pseudo
header checksum value from the first fragment and add the payload
checksums delivered with the status for all fragments to verify
the TCP datagram checksum.
i.MX28 Applications Processor Reference Manual, Rev. 1, 2010
Note
Freescale Semiconductor, Inc.