Download as PDF, PPTX
Uploaded byMIPI Alliance
MIPI DevCon 2016: Effective Verification of Stacked and Layered Protocols
The document provides an overview of MIPI protocols (MIPI M-PHY, MIPI UniPro, and UFS), emphasizing their maturity and infrastructure support, as well as key features like low power consumption and guaranteed delivery. It discusses verification challenges and strategies for effective testing of these protocols, including mapping specifications to verification items and analyzing coverage. The importance of a well-planned verification environment and the use of flexible VIP interfaces to ensure compliance and thorough coverage is also highlighted.
MIPI DevCon 2016: Effective Verification of Stacked and Layered Protocols
- 1. Effective verification of stackedand layered protocols Ofir Michaeli MIPI VIP R&D Team Leader Cadence Design Systems, Inc.
- 2.
- 3. MIPI M-PHY overview • MIPI M-PHY is a mature Protocol. Current version is M- PHY 4.0 and the WG is working on version 4.1.
- 4.
- 5. MIPI UniPro overview • UniPro is a mature Protocol. Current version is UniPro 1.61 (bound to MPHY 3.1) and the WG is working on version 1.8. • Vast infrastructure support – • Application notes with Q&As. • CTS (Conformance Test Suite). • IOT (Interoperability) events. • IPs, VIPs, Test equipment and protocol analyzers. • Key Features – • Low footprint on power and area. • Bi-directional. • Application agnostic. • Easy to use! • Guaranteed and in-order delivery of payload.
- 6. UFS overview • UFSstands for Universal Flash Storage. • UFS is high performance storage interface designed for use in computing and mobile systems requiring low power consumption (smart phones, tablets, etc.)
- 7. VIP core Pre-Silicon Verification User feeds the DUT’s specific Configura:on through PureView GUI Configura)on File SOMA/UVM Class BFM Monitor PureSpec UI DUT TestSuite NativeCoverage e/SV NL Tests TL Tests DME Tests PA Tests DLL Tests DUT specific info is created VIP configured per SOMA, ready to test DUT vPlan, Coverage and TestSuite are filtered per SOMA parameters
- 8. • Interfaces –Verifying connection to Upstream/Downstream Layers: • RMMI – Physical Layer (M-PHY) • CPort interface – Application Layer (UFS/ CSI3) • UniPro DME interface. • Backward compatibility – Verifying compatibility with designs implementing older versions of the specification. • Verifying new features or features that changed between version. • Unclear/ Vague Spec. description (for example Deep SAVE state). • Running with different configurations or with different set of supported features. Verification Challenges
- 9. Capability Exchange • NewPACP introduced: • How does a device behave if no PACP_CAP_EXT1_ind is received or silently discarded. • TX_LCC_Enable and LINE-CFG behavior at the end of burst.
- 10. Interfaces • RMMI (ReferenceM-PHY MODULE Interface) – • Optional. Described in M-PHY Annex • UniPro SAPs (Service Access Points) VS. M-PHY Signaling Interface • CPort interface – • Informative. Described in UniPro Annex. • DME interface – SAPs only.
- 11. How can aVIP help? • Checks protocol compliance as per protocol specification. • Provides full coverage model. • Generates and drives test sequences. • VIP interface is flexible – • No constraints to vendor capabilities. • Can be configured with different feature support/ capability settings. • Developed independently from DUT. • Make vs. Buy: • man years of development. • reused across many designs. Test Sequences State Machines Protocol Checks Coverage Model Verifica)on Plan ConfigurationDebug Methodology-Independent I/F Mul:-Language Testbench I/F Core VIP DUT
- 12. So how dowe verify effectively? Test Plan Verification Plan Test And Debug Coverage AnalysisVerification Environment
- 13. Verification should start asearly as possible! 13
- 14. Verification Plan • Mappingeach line in the specification to a verification item. • Mapping each item in the plan to a coverage item in the model.
- 15. Understand what you wantto test and how to test it! 15
- 16. • How muchis enough? How much is too much? • PA Hibernate description – 3 pages, 32 Test scenarios, Thousands of Test cases. Test Plan
- 17.
- 18.
- 19. UniPro VIP Data Link(L2) PHY Adapter (L1.5) PHY (L1) Partial UniPro DUT connected to DLL+PA only UniPro VIP using RMMI DeviceManagementEntity (DME) UniPro DUT MP MP MP RMMI
- 20. UniPro VIP UFS MM Transport(L4) Network (L3) Data Link (L2) PHY Adapter (L1.5) PHY (L1) UniPro DUT connected to UFS Device VIP using RMMI and UniPro Application VIP using CPort DeviceManagementEntity (DME) UniPro DUT MP MP MP MP MP MP MP MP RMMI UniPro Application CPort
- 21. UniPro VIP UFS MM Transport(L4) Network (L3) Data Link (L2) PHY Adapter (L1.5) PHY (L1) UFS Host DUT connected to UFS Device VIP using RMMI DeviceManagementEntity (DME) UFS Host DUT (full stack)MP MP MP MP MP MP MP MP RMMI
- 22. UFS MM Transport (L4) Network(L3) Data Link (L2) PHY Adapter (L1.5) PHY (L1) UFS Host DUT connected to UFS Device VIP using Serial interface DeviceManagementEntity (DME) UFS Host DUT (full stack) UniPro VIP DPDN MP MP MP MP MP MP MP MP
- 23. M-PHY DPDN VIP M-PHYDUT connected to M-PHY VIP using RMMI and Serial interface MPHY DUT RMMI DPDN M-PHY RMMI VIP
- 24. Use a PASSIVEagent! 24
- 25.
- 26.
- 27.
- 28.
- 29. Always make sureyou’re covered! 29
- 30.
- 31. Effective verification of stackedand layered protocols Ofir Michaeli MIPI VIP R&D Team Leader Cadence Design Systems, Inc.