Access Official Technical PDF

Share Summary:LinkedInEmail

For embedded systems that need a direct path between USB and a parallel device, the EZ-USB FX2LP combines the key interface and control functions in one chip. This USB 2.0 peripheral controller integrates a transceiver, serial interface engine (SIE), enhanced 8051 microcontroller, endpoint memory and programmable interface logic. The combination can simplify a design’s USB data path while leaving the microcontroller available for application-specific firmware.

Understanding how those blocks work together is important when selecting the device or planning a migration from the earlier FX2. The main design choices involve endpoint configuration, the GPIF or Slave FIFO interface, firmware boot and power requirements, and the package’s available signals.

How the EZ-USB FX2LP handles USB and firmware

The FX2LP supports USB full-speed signaling at 12 Mbps and high-speed signaling at 480 Mbps; it does not support low-speed USB. Its Smart SIE handles much of the USB protocol in hardware, reducing the amount of protocol work required from the embedded 8051. The device supports USB 2.0 high-speed certification and can transfer data at rates above 53 Mbytes per second under the conditions described in its datasheet.

The integrated 8051 runs at a selectable 12, 24 or 48 MHz and has 16 KB of on-chip program/data RAM. Firmware can be loaded into internal RAM over USB or from an EEPROM through the I2C boot process. In the 128-pin package, external memory can also be used. This range of boot options allows a design to choose how its firmware is supplied without requiring a separate USB transceiver or SIE.

USB configuration is also software-defined. With ReNumeration, the device first connects using its initial USB identity, receives firmware and descriptor information, and then reconnects as the device described by that configuration. This makes it possible for one chip to take on different USB device identities under firmware control.

Endpoint buffering and the USB data path

Endpoint RAM provides the working space between the USB engine and the device’s parallel interface. Endpoint zero handles control transfers, while endpoint one provides a 64-byte bulk or interrupt endpoint. Four additional endpoints—EP2, EP4, EP6 and EP8—can be configured for bulk, interrupt or isochronous transfers. Their buffers are built from eight 512-byte blocks, with supported configurations that include double, triple or quad buffering for selected endpoints.

Buffering helps manage data moving between USB transactions and an external interface. While some memory blocks exchange data with the USB SIE, others can be available to the 8051 or interface logic. The same physical RAM is switched between these operating domains rather than requiring software to copy each byte between separate USB and FIFO memories. Designers still need to choose endpoint types, packet sizes and buffer allocation to suit their transfer and firmware requirements.

Full-speed and high-speed operation use different maximum packet sizes for relevant endpoints: the documented endpoint tables specify 64-byte packets at full speed and, for applicable high-speed endpoints, up to 512 bytes. A buffer’s allocated capacity does not mean every operating mode can use that entire space for a single packet.

Choosing between GPIF and Slave FIFO

The FX2LP provides two approaches for connecting its endpoint buffers to external logic. The choice depends on which side should control the transfer and how much interface sequencing the design needs.

GPIF for programmable interface control

The General Programmable Interface (GPIF) is a hardware unit driven by a programmable finite-state machine. It can generate control waveforms and coordinate data movement with an external device, making it suitable for interfaces such as ATA, printer parallel port and UTOPIA. The interface supports an 8-bit or 16-bit data bus, programmable control outputs and ready inputs. GPIF waveform descriptors define the sequence of control states and conditions for advancing through a transfer.

In master mode, the GPIF selects endpoint FIFOs and controls transfer timing. It can use an internally derived interface clock or an external clock, and the documented interface-clock options support rates up to 48 MHz. With a 16-bit data path, the datasheet specifies a burst rate of up to 96 Mbytes per second. Actual system performance depends on the interface configuration and connected hardware.

Slave FIFO for externally controlled transfers

In Slave FIFO mode, external logic controls transfers using signals such as SLRD, SLWR, SLOE and PKTEND. The interface can use an internal or external clock and can operate synchronously or asynchronously. A selected endpoint can be configured for byte- or word-wide operation. This approach is useful when an FPGA, ASIC or processor already manages the external bus and should control access to the FX2LP’s FIFO buffers.

Package selection affects how much of the interface is available. The 100- and 128-pin packages expose more GPIF control and ready signals than the 56-pin versions. The 128-pin package also provides external 8051 address and data buses. Review the pin assignments early in the design, especially when selecting a compact package or combining GPIF, FIFO, GPIO and other functions.

Power, integration and design checks

The FX2LP operates at 3.3 V and has 5 V-tolerant inputs. The family is designed for low-power applications, with distinct variants for power-sensitive battery designs. The CY7C68014A and CY7C68016A have a typical suspend current of 100 μA, compared with 300 μA for the CY7C68013A and CY7C68015A. These are suspend-current figures, not a measure of total system power during active transfers.

Before committing to a design, engineers should verify the package pinout, endpoint configuration, clock source, reset timing, boot method and external pull-ups required by the I2C pins. Firmware developers should also account for the selected USB transfer types and the interface mode. The FX2LP is form-, fit- and function-compatible with the earlier FX2 in many respects, but a migration still calls for a bill-of-materials review and a check of memory allocation.

Practical implications for embedded designs

The EZ-USB FX2LP brings USB protocol handling, firmware execution and parallel data interfacing into a single controller. Its endpoint RAM supports buffered transfers, while GPIF and Slave FIFO modes offer different ways to connect external logic. For engineers and system integrators, the practical task is to match those capabilities to the required USB transfer types, external bus behavior, power budget and package pinout. Making those choices early helps establish a workable hardware and firmware architecture.

Access Official Technical PDF

About The Author