DFI - ddr-phy.org

DFI Contributors

 

 

Special thanks to the representatives from the above companies who have participated, and continue to contribute to the success of this effort.

 

About DFI (DDR PHY Interface)

... Simplify DDR PHY

The DFI specification defines an interface protocol between memory controller logic and PHY interfaces, with a goal of reducing integration costs while enabling performance and data throughput efficiency. The protocol defines the signals, timing, and functionality required for efficient communication across the interface. The specification is designed to be used by developers of both memory controllers and PHY designs, but does not place any restrictions on the how the memory controller interfaces to the system design, or how the PHY interfaces to the memory devices.


The DFI specification is being developed by expert contributors from recognized leaders in the semiconductor, IP and electronic design automation (EDA) industries.


Learn more about DFI here ...

DFI News

DFI Group Releases Final Version DFI 3.1 and Preliminary DFI 4.0 Addendum of its High-Speed Memory Controller and PHY Interface Specification

San Jose, CA , April 8th: Today the DDR PHY Interface (DFI) Group, consisting of leading IP and product companies including ARM, Cadence, Intel, LSI, Samsung, ST and Synopsys, released the final version of the DFI 3.1 specification.

The standard defines an interface protocol between DDR memory controllers and PHY interfaces. It is intended to be used by developers of both memory controllers and PHY designs, but does not place any restrictions on the how the memory controller interfaces to the system design, or how the PHY interfaces to the memory devices. The standard replaces the preliminary DFI 3.1 specification which was available since mid 2012.

In addition the group released a new – preliminary – DFI 4.0 addendum specifically addressing the requirements to support LPDDR4 memories.

The DFI 4.0 addendum includes the following features:

  • Necessary command interface signaling and timing changes to support all LPDDR4 memory commands
  • New channel architecture defined on DFI interconnect to align with the LPDDR4 channel architecture.
  • CA training extensions necessary to extend the existing CA training to support LPDDR4.
  • Changes to Read Data Eye Training and Write Leveling to accommodate differences in LPDDR4 training definitions.
  • Addition of Write DQ training for LPDDR4 and extended to all other memory classes.
  • Addition of DB training to support DDR4 data buffer training.
  • Addition of Geardown support.
  • Modifications of DFI specific features and definitions including
    1. new slice width parameter
    2. modified data chip select definition
    3. new PHY master handshake protocol
    4. new frequency value indicator
    5. new DFI disconnect protocol
    6. modified data bit disable function.

“Mobile consumer devices continue to demand both increased memory performance and power efficiency, requiring the use of the latest available technologies like LPDDR4 memory”," said John MacLaren, Senior Member of Consulting Staff at Cadence Design Systems and chairman of the DFI Group. "We are excited to add LPDDR4 mobile memory support to the DFI standard, enabling the benefits of this technology for the rapidly growing mobile computing market.”

Both the final DFI 3.1 specification as well as the DFI 4.0 addendum is available now for download at www.ddr-phy.org

 
 
 

Latest Activity

venkatesh g replied to venkatesh g's discussion Regarding training modes
"Thank you Jonh :)"
yesterday
Profile IconGary Nichols, Qingjun Bu, Ravi and 7 more joined DFI - ddr-phy.org
Wednesday
John MacLaren replied to venkatesh g's discussion Regarding training modes
"Hi Venkatesh, DFI supports two training modes - DFI training and PHY independent training - the terminology may be slightly different, but the meaning is the same.  For DFI training, the MC cooperates with the PHY to execute training algorithms…"
Wednesday
John MacLaren replied to varma Devaganugula's discussion dfi_init_complete signal transition after dfi_init_start
"This situation is not discussed in the DFI specification, so it is outside of the scope of the interface definition.  It does not mean that an issue will necessarily occur; but it would be good to discuss this behavior with the MC IP developer…"
Wednesday

© 2014   Created by Denali Software, Inc..   Powered by

Badges  |  Report an Issue  |  Terms of Service