Home: IP Portfolio > Verification IP > Memory Models > Memory Model for UFS

Memory Model for UFS

This Cadence® Verification IP (VIP) provides support for the JEDEC® Universal Flash Storage (UFS) standard. The VIP for UFS is compatible with the industry-standard Universal Verification Methodology (UVM), runs on all leading simulators, and leverages the industry-standard Cadence Memory Model core architecture, interface, and use model.

The Universal Flash Storage (UFS) standard is an emerging standard for storage devices tailored specifically for mobile applications and computing systems requiring high performance and low power consumption. The UFS standard adopts the well-known SCSI architecture model and command protocols supporting multiple commands with command queuing features and enabling a multi-thread programming paradigm. To achieve the highest performance and most power efficient data transport, JEDEC UFS aligns with industry-leading specifications from the MIPI® Alliance to form its Interconnect Layer.

Specification Support

Versions supported

UFS 3.0, UFS 2.1, UFS 2.0, and UFS 1.1.

The specifications are available here: 

Other related specifications

For UFS 3.0

  • MIPI Alliance Specification for M-PHY®, Version 4.1
  • MIPI Alliance Specification for Unified Protocol (UniProsm), Version 1.8
  • MIPI Alliance Specification for Device Descriptor Block (DDB), Version 1.0
  • INCITS/T10 draft standard: SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010
  • INCITS/T10 draft standard: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010
  • INCITS/10 draft standard: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010

For UFS 2.1

  • MIPI Alliance Specification for M-PHY, Version 3.0
  • MIPI Alliance Specification for Unified Protocol (UniPro), Version 1.6
  • MIPI Alliance Specification for Device Descriptor Block (DDB), Version 1.0
  • INCITS/T10 draft standard: SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010
  • INCITS/T10 draft standard: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010
  • INCITS/10 draft standard: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010

For UFS 2.0

  • MIPI Alliance Specification for M-PHY, Version 3.0
  • MIPI Alliance Specification for Unified Protocol (UniPro), Version 1.6
  • MIPI Alliance Specification for Device Descriptor Block (DDB), Version 1.0
  • INCITS/T10 draft standard: SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010
  • INCITS/T10 draft standard: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010
  • INCITS/10 draft standard: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010

For UFS 1.1

  • MIPI Alliance Specification for M-PHY, Version 2.0
  • MIPI Alliance Specification for Unified Protocol (UniPro), Version 1.41
  • MIPI Alliance Specification for Device Descriptor Block (DDB), Version 1.0
  • INCITS/T10 draft standard: SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010
  • INCITS/T10 draft standard: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010
  • INCITS/10 draft standard: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010

Product Highlights

Important supported features are listed in the table below.

Feature Name
Description

UTP layer - UPIUs

NOP IN, NOP OUT, Query Request/ Response, Task Management Request/ Response, Command, Response, Data Out, Data In

UCS layer - SCSI commands

READ (6, 10, 16), WRITE (6, 10, 16), Inquiry, Report LUNs, Read Capacity (10, 16), Test Unit Ready, Verify, Start Stop Unit, Mode Sense, Request Sense, Security Protocol In, Security Protocol Out, Send Diagnostic, Read Buffer, Write Buffer, Pre-Fetch (10, 16), Synchronize Cache (10, 16), Mode select, Unmap, and Format

UFS protocol features supported
  • Boot functionality
  • LUNS and W-LUNS supported
  • Interleaving of commands supported
  • Queue depth of over 32 commands
CPort signaling interface

As specified by UniPro Specification:

  • CPort connection to Device UniPro
  • Direct CPort connection to Host UniPro
Supported use cases
  • UFS standalone (Transaction mode or using CPort signaling interface)
  • Full-stack UFS (with UniPro+M-PHY over DPDN serial interface or with UniPro only over RMMI interface)
 UFS 3.0 support
  • Support for HS Gear 3 and HS Gear 4 
  • Initiator ID (IID) feature update in Task Management request UPIUs
  • Device Health Descriptor

Key Verification Capabilities

Key verification capabilities include: 

  • Boot and initialization sequence support; can be skipped to save simulation time

  • Error injection support by modifying transactions during callbacks
  • Full stack support (when used with UniPro) and UFS stand alone

  • Multiple interfaces: DPDN and RMMI (when used with UniPro VIP), CPort signaling pin interface, CPort message (using transactions)

  • Multiple logic unit support with interleaving and command queues

    • Backdoor loads to individual LUN memories
    • Backdoor access to flags, attributes and descriptors 
  • Transaction and memory callbacks for all protocol and device memory events (Read/Write)
  • Various latencies to verify different scenarios
  • Unlimited or restricted UniPro message capacity

Other Supported Features

Methodologies Unified Verification Methodology (UVM), OVM
Simulators IES, VCS, and MTI
Testbench Language Interfaces Verilog, VHDL, SystemVerilog, and SystemC®
Trace Debug Yes