PNX1502E,557 NXP Semiconductors, PNX1502E,557 Datasheet - Page 720

IC MEDIA PROC 300MHZ 456-BGA

PNX1502E,557

Manufacturer Part Number
PNX1502E,557
Description
IC MEDIA PROC 300MHZ 456-BGA
Manufacturer
NXP Semiconductors
Datasheets

Specifications of PNX1502E,557

Applications
Multimedia
Core Processor
TriMedia
Controller Series
Nexperia
Interface
I²C, 2-Wire Serial
Number Of I /o
61
Voltage - Supply
1.23 V ~ 1.37 V
Operating Temperature
0°C ~ 85°C
Mounting Type
Surface Mount
Package / Case
456-BGA
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Program Memory Type
-
Ram Size
-
Lead Free Status / Rohs Status
Not Compliant
Other names
935274744557
PNX1502E
PNX1502E

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
PNX1502E,557
Manufacturer:
NXP Semiconductors
Quantity:
10 000
Philips Semiconductors
Volume 1 of 1
PNX15XX_SER_3
Product data sheet
been reached and the status of the third fragment is written. The third fragment’s
status word will have the Last bit set to 1 and the EntryLevel equal to 2 (for a value of
3, because of –1 encoding).
The next packet received from the MII interface will be written to the fourth fragment
buffer, therefore five bytes of the third buffer will be unused.
The Rx DMA manager checks to make sure receive data and status data have been
committed to memory. Only if memory acknowledges that the data has been
committed to memory will the RxProduceIndex be updated and the interrupt flags be
forwarded to the IntStatus register. The LAN100 tags receive data and statuses
continuously but does not necessarily tag every data and every status individually.
After committing status of the fragments to memory the LAN100 will trigger a
RxDoneInt interrupt, which triggers the device driver to inspect the status information.
In this example all descriptors have the Interrupt bit set in the Control word, so all
descriptors will generate an interrupt after committing data and status to memory.
In this example, the receive function of the LAN100 cannot read new descriptors as
long as the device driver does not increment the RxConsumeIndex because the
descriptor array is full (even though one descriptor is not programmed yet, see
Section 5.2.4 on page
data to application software and after the device driver has updated the
RxConsumeIndex by incrementing it by the number of received fragments (3 in this
case) can the LAN100 continue reading descriptors and receive data.
Rev. 3 — 17 March 2006
23-35). Only after the device driver has forwarded the receive
Chapter 23: LAN100 — Ethernet Media Access Controller
© Koninklijke Philips Electronics N.V. 2006. All rights reserved.
PNX15xx Series
23-51

Related parts for PNX1502E,557