Overview
The USB1.1 PHY is an IP version of USB transceiver designed in standard logic to interface the physical layer of Universal Serial Bus. It receives data via DP and DM and transfers data to USB1.1 core via RCV, VM and VP, capable of transmitting and receiving serial data at either full speed (12M bit/s) or low speed (1.5M bit/s) data rate. The serial interface engine (SIE) controls the state of USB1.1 PHY through the OEN signal. When in receiving mode, it receives data at the USB1.1 PHY output RCV, VM and VP; when in transmitting mode, it drives the USB1.1 PHY input VPO and VMO.
Learn more about Single-Protocol PHY IP core
UniversalFlash Storage (UFS) was created for mobile applications and computer systems requiring high performance and low power consumption. These systems typically use embedded Flash based on the JEDEC standard eMMC. UFS was defined by JEDEC as the evolutionary replacement for eMMC offering significantly higher memory bandwidth. The standard builds on existing standards such as the SCSI command set, the MIPI Alliance M-PHY and UniPro as well as eMMC form factors to simplify adoption and development.
In this paper, we introduce a new high-level, dataflow programming language called C~ (“C flow”) that further increases productivity by raising the level of abstraction from behavioral descriptions, while overcoming the limitations of C for hardware design. We present the syntax and semantics of this language, and the framework that provides hardware and software code generation. This paper illustrates the benefits of using C~ for hardware design of a IEEE 802.3 MAC, synthesized for FPGA and for 90nm CMOS technology.
Universal Flash Storage (UFS) was created for mobile applications and computer systems requiring high performance and low power consumption. These systems typically use embedded Flash based on the JEDEC standard eMMC. UFS was defined by JEDEC as the evolutionary replacement for eMMC offering significantly higher memory bandwidth. The standard builds on existing standards such as the SCSI command set, the MIPI Alliance M-PHY and UniProSM as well as eMMC form factors to simplify adoption and development.
Since MIPI and MDDI standards both target interfaces to cameras and displays on mobile devices, are two separate standards really needed?
Enter the Inner Sanctum of RapidIO: Part 1
Networking software key to PICMG 2.16 optimization
