Verification Academy

Search form

My Account Menu

  • Register
  • Log In
  • Topics
  • Courses
  • Forums
  • Patterns Library
  • Cookbooks
  • Events
  • More
  • All Topics
    The Verification Academy offers users multiple entry points to find the information they need. One of these entry points is through Topic collections. These topics are industry standards that all design and verification engineers should recognize. While we continue to add new topics, users are encourage to further refine collection information to meet their specific interests.
    • Languages & Standards

      • Portable Test and Stimulus
      • Functional Safety
      • Design & Verification Languages
    • Methodologies

      • UVM - Universal Verification Methodology
      • UVM Framework
      • UVM Connect
      • FPGA Verification
      • Coverage
    • Techniques & Tools

      • Verification IP
      • Simulation-Based Techniques
      • Planning, Measurement, and Analysis
      • Formal-Based Techniques
      • Debug
      • Clock-Domain Crossing
      • Acceleration
  • All Courses
    The Verification Academy is organized into a collection of free online courses, focusing on various key aspects of advanced functional verification. Each course consists of multiple sessions—allowing the participant to pick and choose specific topics of interest, as well as revisit any specific topics for future reference. After completing a specific course, the participant should be armed with enough knowledge to then understand the necessary steps required for maturing their own organization’s skills and infrastructure on the specific topic of interest. The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization’s processes so that you can then reap the benefits that advanced functional verification offers.
    • Universal Verification Methodology (UVM)

      • Advanced UVM
      • Basic UVM
      • Introduction to UVM
      • UVM Connect
      • UVM Debug
      • UVMF - One Bite at a Time
    • Featured Courses

      • Introduction to ISO 26262
      • Introduction to DO-254
      • Clock-Domain Crossing Verification
      • Portable Stimulus Basics
      • Power Aware CDC Verification
      • Power Aware Verification
      • SystemVerilog OOP for UVM Verification
    • Additional Courses

      • Assertion-Based Verification
      • An Introduction to Unit Testing with SVUnit
      • Evolving FPGA Verification Capabilities
      • Metrics in SoC Verification
      • SystemVerilog Testbench Acceleration
      • Testbench Co-Emulation: SystemC & TLM-2.0
      • Verification Planning and Management
      • VHDL-2008 Why It Matters
    • Formal-Based Techniques

      • Formal Assertion-Based Verification
      • Formal-Based Technology: Automatic Formal Solutions
      • Formal Coverage
      • Getting Started with Formal-Based Technology
      • Handling Inconclusive Assertions in Formal Verification
      • Sequential Logic Equivalence Checking
    • Analog/Mixed Signal

      • AMS Design Configuration Schemes
      • Improve AMS Verification Performance
      • Improve AMS Verification Quality
  • All Forum Topics
    The Verification Community is eager to answer your UVM, SystemVerilog and Coverage related questions. We encourage you to take an active role in the Forums by answering and commenting to any questions that you are able to.
    • UVM Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • UVM Forum
    • SystemVerilog Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • SystemVerilog Forum
    • Coverage Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • Coverage Forum
    • Additional Forums

      • Announcements
      • Downloads
      • OVM Forum
  • Patterns Library
    The Verification Academy Patterns Library contains a collection of solutions to many of today's verification problems. The patterns contained in the library span across the entire domain of verification (i.e., from specification to methodology to implementation—and across multiple verification engines such as formal, simulation, and emulation).
    • Implementation Patterns

      • Environment Patterns
      • Stimulus Patterns
      • Analysis Patterns
      • All Implementation Patterns
    • Specification Patterns

      • Occurrence Property Patterns
      • Order Property Patterns
      • All Specification Patterns
    • Pattern Resources

      • Start Here - Patterns Library Overview
      • Whitepaper - Taking Reuse to the Next Level
      • Verification Horizons - The Verification Academy Patterns Library
      • Contribute a Pattern to the Library
  • All Cookbooks
    Find all the methodology you need in this comprehensive and vast collection. The UVM and Coverage Cookbooks contain dozens of informative, executable articles covering all aspects of UVM and Coverage.
    • UVM Cookbook

      • UVM Basics
      • Testbench Architecture
      • DUT-Testbench Connections
      • Configuring a Test Environment
      • Analysis Components & Techniques
      • End Of Test Mechanisms
      • Sequences
      • The UVM Messaging System
      • Other Stimulus Techniques
      • Register Abstraction Layer
      • Testbench Acceleration through Co-Emulation
      • Debug of SV and UVM
      • UVM Connect - SV-SystemC interoperability
      • UVM Versions and Compatibility
      • UVM Cookbook
    • Coding Guidelines & Deployment

      • Code Examples
      • UVM Verification Component
      • Package/Organization
      • Questa/Compiling UVM
      • SystemVerilog Guidelines
      • SystemVerilog Performance Guidelines
      • UVM Guidelines
      • UVM Performance Guidelines
    • Coverage Cookbook

      • Introduction
      • What is Coverage?
      • Kinds of Coverage
      • Specification to Testplan
      • Testplan to Functional Coverage
      • Bus Protocol Coverage
      • Block Level Coverage
      • Datapath Coverage
      • SoC Coverage Example
      • Requirements Writing Guidelines
      • Coverage Cookbook
  • All Events
    No one argues that the challenges of verification are growing exponentially. What is needed to meet these challenges are tools, methodologies and processes that can help you transform your verification environment. These recorded seminars from Verification Academy trainers and users provide examples for adoption of new technologies and how to evolve your verification process.
    • Upcoming & Featured Events

      • Low Power Verification - 4/29
      • Fault Campaign for Mixed-Signal - 5/4
      • User2User - 5/26
      • Webinar Calendar
    • On-Demand Webinars

      • CDC+RDC Analysis
      • Basic Abstraction Techniques
      • Safety Analysis Techniques
      • QVIP Workflow and Debug for PCIe
      • Writing a Proxy-driven Testbench
      • Achieving High Defect Coverage
      • Visualizer Features
      • All On-Demand Webinars
    • Recording Archive

      • Siemens EDA 2021 Functional Verification Webinar Series
      • Improving Your SystemVerilog & UVM Skills
      • Should I Kill My Formal Run?
      • Visualizer Debug Environment
      • Industry Data & Surveys
      • All Recordings
    • Conferences

      • DVCon 2021
      • DVCon 2020
      • DAC 2019
      • All Conferences
    • Mentor Learning Center

      • SystemVerilog Fundamentals
      • SystemVerilog UVM
      • View all Learning Paths
  • About Verification Academy
    The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization's processes so that you can then reap the benefits that advanced functional verification offers.
    • Blog & News

      • Verification Horizons Blog
      • Academy News
      • Academy Newsletter
      • Technical Resources
    • Verification Horizons Publication

      • Verification Horizons - March 2021
      • Verification Horizons - November 2020
      • Verification Horizons - July 2020
      • Issue Archive
    • About Us

      • Verification Academy Overview
      • Subject Matter Experts
      • Contact Us
    • Training

      • Questa Basic
      • Questa Advanced
      • Mastering Questa
  • Home
  • Verification Horizons
  • June 2017
  • Converting Legacy USB IP to a Low Power USB IP

Converting Legacy USB IP to a Low Power USB IP

Verification Horizons - Tom Fitzpatrick, Editor

Converting Legacy USB IP to a Low Power USB IP by Anand Paralkar and Pervez Bharucha - Silicon Interfaces

Two common queries that customers pose to a design house is whether an existing or new IP can be made "low power" or if "power aware" verification can be carried out on an IP. The IEEE standard – P1801 captures what one may call the syntax and semantics to express the intent of the power architecture of a design. Merely adopting the standard (commonly known as the Unified Power Format) doesn't help. What it really takes to successfully achieve a low power design is design team know-how and a simulation tool that is geared towards low power implementation. This article captures how we use Mentor's Questa® Simulator to lower the power usage of our legacy USB IP. We also share how to start a low power implementation and provide some examples from our current effort.

LOW POWER METHODOLOGY IN A NUTSHELL

When we decided to do a low power design implementation for our existing IP, we were not sure how to get started. We had the basic understanding that power is saved in a digital circuit when:

  1. The switching activity of the circuit is reduced (reducing dynamic power consumption).
  2. Low static current consumption cells are used for parts of the design that don't switch often (reducing static power consumption).

But the trick for creating a low power architecture lies in reading through the specification document using a "power aware lens"! This means having low power techniques in mind at the beginning of your design work. Don't wait until later in the flow.

CREATING THE LOW POWER DESIGN ARCHITECTURE

Our team initiated the process of converting a legacy USB 2.0 (supporting full speed, high speed, and low speed) function controller to low power by using several low power techniques. These include clock gating, power gating, multi threshold design, multi rail design (also known as multiple power domain design), logic-level power optimization, and dynamic voltage frequency scaling. For the purpose of this article, we will focus on clock and power gating.

Using these techniques, we created our first power architecture for our USB 2.0 function controller. The legacy IP had the following internal blocks.

  1. Host Interface: Essentially a FSM that interfaces with a standard microcontroller bus. This block reacts to the read and write cycles from the microcontroller and generates interrupts when configured to do so.
  2. The Configuration and Status Registers: A set of registers that capture the operating parameters and status of the IP.
  3. FIFO and FIFO Controller: A FIFO to store the end-point data.
  4. Tx-Rx Controller: The controller that interprets the serial data and lends the notion of "end points" to the device.
  5. Phy (Bus) Controller: This block interacts with the transceiver and interprets the bus state and generates the serial data for the use of the Tx-Rx controller.

When we started the low power implementation, a Power Manager block was added. This block captures the logic required to monitor and control the various power management aspects of the design.

USE OF POWER GATING

We had the first hint of implementing power savings using power gating from the specification document itself and we are quoting verbatim for reference.

Section 4.3.2 Power Management: A USB host may have a power management system that is independent of the USB. The USB System Software interacts with the host's power management system to handle system power events such as suspend or resume. Additionally, USB devices typically implement additional power management features that allow them to be power managed by system software.
The power distribution and power management features of the USB allow it to be designed into power sensitive systems such as battery-based notebook computers.

The changes to the original architecture that we reviewed were as follows:

Table 1.


Another reason to implement a separate power domain for the USB "core" is to run the core at 3.3V while the logic associated with the "bus" can run at 5V, which is the standard voltage supply on a USB bus. (The above discussion is not the complete perspective on the suspend state. The specification mentions dependencies on/from the suspend state which need to be handled carefully. See section "7.1.7.6 Suspending".)

USUE OF CLOCK SCALING

The USB standard defines an IDLE state as: a state that is entered at the end of a packet transmission and the bus is floated because no more transactions are expected for a given duration. Since no transactions are expected, we saw an opportunity to save power. One cannot consider power gating, because in Section "7.1.7.6 Suspending", the USB specification states:

All devices must support the Suspend state. Devices can go into the Suspend state from any powered state. They begin the transition to the Suspend state after they see a constant Idle state on their upstream facing bus lines for more than 3.0 ms. The device must actually be suspended, drawing only suspend current from the bus after no more than 10 ms of bus inactivity on all its ports.

Note: The Full Speed, High Speed and Low Speed specifications define the Idle state. However, the line conditions for the Idle state are different across the three speeds. A USB 2.0 implementation must take special care while interpreting the Idle state.

The specification implicitly states that the bus may exit from the idle state within 3 ms, and the suspend state will follow (a state where we have decided to implement power gating). Recovering from power gating is a lengthy process (due to the steps involved to restore from retention), and the blocks should be able to react if any transaction is detected. Thus, clock gating is preferred as compared to power gating. The following blocks were implemented using clock gating: FIFO and FIFO controller; and the Tx-Rx controller. The other blocks need to remain active so as to capture and react to the transactions on the bus. The "always-on" bus controller could further save power by using a lower clock frequency and return to its normal clock when a bus transaction is detected.

The changes to the original architecture that we reviewed were as follows:

Table 2.


• Note: The USB 2.0 specification states more implementation details of the Suspend and Resume state in other sections (notable sections 7.1.7.6 Suspending through 7.1.7.7 Resume). These parts have not been considered here because this article is limited to our IP which is a function controller. A host or hub controller would have to consider those sections in their power architecture.

POWER AWARE VERIFICATION

When a design team starts implementing a low power design, the design managers have a choice:

  1. Should the low power behavior be included as part of the RTL?
  2. Should the RTL be instrumented with a layer of the power intent captured in a UPF file?

The major disadvantage of using the first approach is that true low power verification can happen only after the gate-level netlist is available. This causes the low power verification to start late in the design cycle. Even after the gate-level netlist is available, simulation times, debug time, and error correction time is extremely high. The UPF provides the advantages of a modular approach coupled with early detection of low power implementation errors. We chose to use Questa's support for UPF and benefited from it.

We wrote targeted testcases to ensure:

  1. All power states were covered using assertions.
  2. Every power state was entered and exited correctly.
  3. The isolation and retention cells did not allow corruption of state information on critical signals.

The current set of testcases target the various coverage points captured in the verification plan. The next challenge is to create a verification infrastructure that can automatically generate low power scenarios without violating the power sequencing rules.

During verification, the most critical changes were in the Power Manager's FSM. It took us a while to get the power sequencing correct. The available literature suggests that there is scope for more power savings, especially in the "core" blocks where there is scope for clock scaling in low speed and full speed modes.

CONCLUSION

The techniques put forth here led to a successful implementation of a low power USB 2.0 IP.

Figure 1. Clock Scaling


Figure 2. Power Gating


The waveforms above show the two cases discussed earlier as they appeared in our design. The timeline has been artificially manipulated to fit the waveforms in the available space. The original simulation runs are much longer.

REFERENCES

  1. Low Power Design and Verification Techniques - Stephen Bailey, Gabriel Chidolue, Allan Crone; Mentor, a Siemens Business
  2. USB 2.0 Specification

Back to Top

Table of Contents

Verification Horizons Articles:

  • What Does Improving Your Golf Swing Have in Common with Verification?

  • Parallel Debug: A Path to a Better Big Data Diaspora

  • Portable Stimulus Modeling in a High-Level Synthesis User's Verification Flow

  • Smoothing the Path to Software-Driven Verification with Portable Stimulus

  • Verification Planning with Questa® Verification Management

  • MIPI® CSI2 TX IP Verification Using Questa® VIPs

  • Converting Legacy USB IP to a Low Power USB IP

  • Understanding the UPF Power Domain and Domain Boundary

  • Automation and Reuse in RISC-V Verification Flow

  • Emulation – A Job Management Strategy to Maximize Use

  • RTL CDC Is No Longer Enough — How Gate-Level CDC Is Now Essential to First Pass Success

  • Formal Verification: Not Just for Control Paths

Siemens Digital Industries Software

Siemens Digital Industries Software

##TodayMeetsTomorrow

Solutions

  • Cloud
  • Mendix
  • Siemens EDA
  • MindSphere
  • Siemens PLM
  • View all portfolio

Explore

  • Digital Journeys
  • Community
  • Blog
  • Online Store

Siemens

  • About Us
  • Careers
  • Events
  • News and Press
  • Newsletter
  • Customer Stories

Contact Us

USA:

phone-office +1 800 547 3000

See our Worldwide Directory

  • Contact Us
  • Support Center
  • Give us Feedback
©2021 Siemens Digital Industries Software. All Rights Reserved.
Terms of Use Privacy Cookie Policy