Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

MIPI DevCon 2016: Key Learnings in Creating the UFS Compliance Test Program

1,961 views

Published on

Of the many reasons driving development of standards, two of the most important are: 1) Enabling development of distinct yet "plug compatible" implementations; and 2) Encapsulating functionality to create a "building block" that can be used in a wide variety of systems. These two goals can conflict with each other in unexpected ways as the types of systems using the standard evolve. In this presentation, Perry Keller of the UFSA examines the UFSA's learnings in preparing to support logo certification testing of the recently adopted UFS card standard.

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

MIPI DevCon 2016: Key Learnings in Creating the UFS Compliance Test Program

  1. 1. Key Learnings in Creating the UFS Compliance Test Program Perry Keller Digital Applica+ons and Standards Program Lead and Memory Program Manager Chair – JEDEC JC64.5 UFS Measurement CommiDee Chair - UFSA Compliance CommiDee Member – JEDEC and UFSA Board of Directors MIPI / UFSA Liaison
  2. 2. UFS: A Very Different Animal ! New technical paradigms ! Microwave speed digital signaling ! Server class storage functions in fingernail sized packages on a battery budget (“SSD for Mobile”) ! New organizational and cultural paradigms ! Combines technology from at least four independent SSOs and trade associations targeting very different markets ! Serves both embedded and open systems ! First new consumer mass-market technology in 15-20 years (USB 1996, HDMI 2003) ! Ecosystem enablement is key to success 2
  3. 3. Compliance Program Requirements ! Assure devices and hosts interoperate reliably ! Maximize developer benefits, minimize cost ! Promote rapid advancement of underlying specifications and consistent procedures across the industry ! Assure ultimate integrity of the logo ! Utilize an open process from start to finish 3
  4. 4. Industry Best Practices ! Independent 3rd party testing (no “self certification”) !  Site and staff specific !  Physical audit and inspection !  Time limited !  Applies to test procedures and tools as well ! Multi-level certification !  IP, physical components for differentiation !  Complete hosts/devices for end-user confidence ! Balanced approach !  Certification by similarity focuses on distinctions that make a difference !  Compliance Test Matrix designed for high coverage while minimizing redundancy !  Monte Carlo interoperability testing covers the known and unknown ! Strict confidentiality !  Results for participant only !  Participant confidentiality until critical mass achieved 4
  5. 5. UFS Compliance Test Architecture 5 Opera+ng System File System Driver Stack UFS HCI UFS Device HCI Compliance Test Execu+ve Test Driver UFS HCI Emulated UFS Device Interop Test Execu+ve Emulated UFS Host UFS Device Test Execu+ve Device Test System Interop Test Host Test Verifies compliance with key elements of the UFS, UniPro and M-PHY specificaDons. Verifies overall system integrity and covers otherwise unreachable implicit requirements. CerDficaDon of instrumentaDon and independent 3rd party test centers Determinis+c coverage of func+on points Monte Carlo test of en+re system
  6. 6. Compliance Test Matrix Developed by the UFSA Compliance Committee, reviewed by MIPI 6 Test only the modes used by UFS Golden Devices Host DUTs Golden Hosts Device DUTs UFS UF S UF S UFS UFS Compliance Test Matrix for host and device tesDng Reduce test redundancy Interoperability test configuraDons
  7. 7. UFS Logo Certification Process 7 UFS Test Spec Compliance Certificate Logo License logo assures user that all compliance tests passed M-PHY/UniPro Test Procedures UFS Compliance Test Spec UFS Test Procedures Adopter Member Products Compliance CommiPee Board of Directors Plugfests & Accredited Labs * JEDEC, MIPI Alliance and UFSA logos are the property of their respective organizations
  8. 8. UFS Card Changes Everything 8 Page 8 Mobile & IoT Forum 9/15/16 Host and device integration by end user Upgraded phone or memory First purchase Host and device tested together at factory First purchase New host design New card design
  9. 9. Impact on Compliance Architecture 9 Opera+ng System File System Driver Stack UFS HCI UFS Device HCI Compliance Test Execu+ve Test Driver UFS HCI Emulated UFS Device Interop Test Execu+ve Emulated UFS Host UFS Device Test Execu+ve Device Test System Interop Test Host Test Verifies compliance with key elements of the UFS, UniPro and M-PHY specificaDons. Verifies overall system integrity and covers otherwise unreachable implicit requirements. CerDficaDon of instrumentaDon and independent 3rd party test centers Framework for Bench Characteriza+on OTen Sufficient Proves “UFS-ness” Increase coverage @ low cost Embedded: Exposed:
  10. 10. 2H 2014 Jedec Industry UFSA FPGA Prototype 2015 UFS Industry Timeline 10 21 UFS roadmap informa+ve only and no guarantee on schedules MIPI M-PHY 3.0 UFS CTS 1.0 UFS/HCI 2.0 CTS 0.56 2016 M-Phy Test 1.0 Golden Candidates Solicited 2017 Prototypes Solicited 2H 1H Unipro 1.61 1H 1st ATC UFS 2.1 Unipro Test 1.61 UFS Card 1.0 UFS CTS 2.0 UFS Compliance Test Matrix (CTM) 0.8 First Logo CerDficaDon 1H CTM 1.0 CTM 0.9 2013 2012 2011 2010 Workshops “Test the Tests” UFS CTS 2.1 UFS 3.0 Unipro 1.8 Unipro Test 1.8 eUFS UFS Card 1.0 ATC CerDficaDon “Test the Testers” M-PHY 4.0 CTM 1.0
  11. 11. Key Learnings ! Characterization procedures don’t necessarily map to compliance test ! Different goals ! Overlap ! Precision ! Test the tests ! DFT factoring requirements are different for ! Embedded vs. Open ! Module vs. System 11
  12. 12. Physical Layer Testing ! Typical platform components: !  Metrology grade test fixtures !  Oscilloscopes !  Bit Error Rate Testers !  Waveform generators !  Network Analyzers !  Time Domain Reflectometers ! Scope of testing !  M-Phy Tx !  M-Phy Rx !  UFS channel (Tx ball to Rx ball) !  Power integrity (future) 13
  13. 13. Protocol Testing ! Typical platform components: !  Host, Device, snoop test fixtures !  Oscilloscope protocol decoder !  Protocol analyzer !  Protocol generator/exerciser !  Instrumented “golden” hosts and devices ! Scope of testing !  Unipro !  UFS Transport Layer (UTP) 14
  14. 14. Interoperability Testing ! Typical platform components: !  Host, Device, snoop test fixtures !  Set of “Golden” hosts (for device test) !  Set of “Golden” devices (for host test) !  Host test application or procedures !  Phy/Protocol test equipment (for debugging) ! Scope of testing !  Complete UFS HW/SW stack !  Interoperation with defined set of “Golden” hosts/devices 15 UFS UF S UF S UFS
  15. 15. UFS Interoperability Universe 16 Standards Memory IP SoC Interconnect Hosts Reliable implementation of standards is essential Millions of possible combinaDons! Thousands of component designs…

×