MIPI UniPro: Comprehensive Verification Checklist
We at Arrow Devices are committed to help developers build happy and robust standard interface IP. We are starting with MIPI UniPro today.
As part of this initiative we have prepared the following actionable questionnaire and downloadable test plan that lists more than 600 test cases. All it takes is to answer the questionnaire and follow it up with five steps action plan of cross-referencing your verification plan with the test plan provided. The intent is to get to a single number (Verifcation Score), that will enable Managers, Technical leads, Verification engineers and those paranoid finger crossed designers to evaluate the strength of their verification plan. There by helping reduce the risk of new designs and increase the robustness of existing designs, by ensuring that none of the key items are missed.
Following verification checklist has been prepared for the MIPI UniPro Specification version 1.41. MIPI UniPro stack has 4 layers. Each layer requires its own verification strategy, which involves choosing the right combination of directed test cases and constrained random test cases. The following sections describe the verification strategy and focus areas for each layer.
Related Semiconductor IP
- RISC-V CPU IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
Related Blogs
- MIPI UniPro: Major Differentiating Features, Benefits and Verification Challenges
- Interface Standards Table - MIPI HSI, HSIC, UniPro, UniPort, LLI, C2C
- MIPI UniPro through eyes of PCI Express
- MIPI Unipro Transport Layer (L4) - An Introduction
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?