DESIGN VERIFICATION of POWER MANAGEMENT UNIT and CLOCK GENERATION BLOCK of Wi-Fi Soc
Total Page:16
File Type:pdf, Size:1020Kb
ISSN: 2278 – 909X International Journal of Advanced Research in Electronics and Communication Engineering (IJARECE) Volume 5, Issue 2, February 2016 DESIGN VERIFICATION OF POWER MANAGEMENT UNIT AND CLOCK GENERATION BLOCK OF Wi-Fi SoC Chandrahas Reddy.M1 and Sugandhi.k2 1 M.Tech .Vlsi Design, SRM University, Chennai, India 2Asst.Professor (Sr.G), Department of Electronics and Communication SRM University, Chennai, India. Abstract variants during this execution flow. A typical SOC may contains the cores like a It is all about the importance of processor or processor sub-system, a the system on chip and the typical processor bus, a peripheral bus, a bridge intellectual property design verification between the two buses, and many flow that is followed in the industry, peripheral devices such as data motivation behind this project and the transformation engines, data ports (e.g. time plan that was followed in the UARTs, MACs) and controllers (e.g., execution of project. DMA). The sub-systems included in a specific SOC depend on the intended The term “system on a chip”, or device and a series of tradeoffs and SOC really implies two things, the requirements, such as cost, form factor, product itself and the methodology used power, performance, and functionality. to design it. A SOC product integrates several sub-systems, many or all of The verification methodology of an which would’ve been separate discrete SOC flow includes the stimulation of chips in the past into a single chip. design by providing input stimuli through Depending on how tightly you restrict Testbench setup and verify that it the definition, a SOC may be only a functioning as per intended specifications single silicon die, or possibly many dies and this input stimulus exercises through a inside a single package. Either way, a comprehensive set of test cases which SOC is rarely the entire system on that includes all scenarios those verifies the single chip, but it usually encompasses designed module for both functionality and the computing functions of the device. timing behavior. Index Terms : System on The primary focus in SOC chip(SOC),Silicon die. verification is on checking the integration between the various components. The Introduction underlying assumption is that each System On a Chip (SOC) is an component was already checked by itself. implementation technology and may have The combined complexity of the multiple many transformations and many different sub-systems can be huge, and there are 285 All Rights Reserved © 2016 IJARECE ISSN: 2278 – 909X International Journal of Advanced Research in Electronics and Communication Engineering (IJARECE) Volume 5, Issue 2, February 2016 many seemingly independent activities As shown in the design flow hardware part that need to be closely correlated. As a and software part will be segregated and result, we need a way to define they are developed in parallel. Design complicated test scenarios as well as engineers will develop RTL models from measure how well we exercise such specifications and also write test bench for scenarios and corner cases. their blocks. Verification engineers setup the verification environment like tool The reuse of many hardware IP blocks in a integration, scripts, etc. mix-and-match style suggests reuse of the verification components as well. Many Typical design verification flow consists companies treat their verification IP as a of following steps as design goes from valuable asset, sometimes valued even design entry to tapeout. more than the hardware IP. Typically, there are independent groups working on 1. Functional Verification the subsystems, thus both the challenges 2. Timing Verification and the possible benefits of creating 3. Physical Verification reusable verification components are 1.1.1 Functional Verification magnified. In functional verification, 1.1 TYPICAL SOC VERIFIACTION FLOW engineers checks correctness of all features specified in design and this is carry out by The SOC verification undergoes RTL simulations of design. In RTL many stages of verification during the simulations, set comprehensive test cases cycle of design. A typical flow of are driven through Testbench setup and verification starting from the specifications these test cases includes the sequences that to design sign off is shown in Figure 1.1. are required to verify the scenarios. After this the functionally verified design with error free is fed to synthesizer and this will generate gate level netlist for specified design technology. 1.1.2 Timing Verification RTL simulations are run without timing information and it is not capable of finding potential design issues due to timing violations. Timing verification is carryout on synthesized netlist and called gate level simulations with timing information files for different corner cases Figure 1.1 SoC Verification Flow called SDF. The netlist is nothing but gate 286 All Rights Reserved © 2016 IJARECE ISSN: 2278 – 909X International Journal of Advanced Research in Electronics and Communication Engineering (IJARECE) Volume 5, Issue 2, February 2016 level description of the design. False paths operating at higher speeds, the design has (FP) and multi-cycle-paths (MCP) are to be verify thoroughly for its timing exceptions that present a completeness and indeed functionality. So particularly difficult problem when trying it requires robust verification environment to achieve the timing closure for high- i.e. Testbench which need to be organize performance designs. Typically these to suit for most of the similar design i.e. exceptions (as well as all timing developing more generic environment constraints) are considered late in the gives the industry to produce more design cycle and are specified in response products in less time. to timing problems during verification. For optimum timing results, all timing The objective of work included: exceptions must be guaranteed to be 1.In a system-on-chip (SOC) design flow, correct. So any potential timing violations the designed behavioral model i.e. register those were not caught in STA can be transfer level (RTL) code undergoes caught in gate level simulations during several transformations before it goes to netlist verification. synthesis. During each transformation, the 1.1.3 Physical Verification design logical behavior needs to be verified for it‟s indeed functionality. Layout vs. Schematics (LVS), Design Rule Checking(DRC), Signal 2.The typical complex SoC contains integrity, etc. is covered in physical several components/blocks, that are having verification. In DRC all physical interconnection with each other and also measurements are verifies as per specified those will be used for the host interface. So design technology (e.g. TSMC 180nm, the functionality of these modules should UMC 65nm Technology, etc.). In LVS the be verified. developed layout is compared with 3.Perform gate level simulations with required schematic and their connections SDFs to verify any timing violations, with power supplies and interconnection functional aspects of synthesized design. between the cells. Finally designed RTL models are sent to fabrication and 4.Run the regressions periodically to know successive validation/testing will be percentage of verification coverage for carried out on raw chip to investigate the design. indeed functionality before sending them to customer. Deliverables included: 1. Development of comprehensive 1.2 MOTIVATION test scenarios for module level and chip As today SOC design technologies level to achieve zero bugs in design. becomes more and more complex design with more cores present on a single chip 287 All Rights Reserved © 2016 IJARECE ISSN: 2278 – 909X International Journal of Advanced Research in Electronics and Communication Engineering (IJARECE) Volume 5, Issue 2, February 2016 2. The developed test cases must functional aspects of block and also it cover/verify all the features specified in introduces the gate level simulation design requirement. methodology with SDF. 3. The test cases should ensure less Chapter 4 illustrates the basic debugging efforts with maximum functional behavior of PMU and Clock reusability for future IPs. Generation Block through obtained waveforms. The timing violations that Key tools to be used: were caught during GLS are also 1. Software: Linux, Cadence Ncsim explained though waveforms and the final simulator, Synopsys Novas debug regression status also presented in this Platform. chapter. 2. Languages: Perl, TCL, Verilog and Chapter 5 talks about the future VHDL. scope of the project and also the conclusions drawn from the results. 1.4 ORGANIZATION OF REPORT BACKGROUND THEORY This report is organized in to 5 chapters. This chapter gives a brief description Chapter 1 gives a brief introduction about Wi-Fi Technology and also gives about the importance of the system on chip brief introduction about 802.11 protocol and the typical intellectual property design standards and its classification. It also verification flow that is followed in the describes the typical architecture of a Wi- industry, motivation behind this project Fi SOC at chip level and briefly explains and the time plan that was followed in the about the components present in this chip execution of project. like MAC hardware, PHY core, JTAG, PMU, etc. Chapter 2 gives a brief description about Wi-Fi Technology and also gives Wi-Fi, known as a popular wireless brief introduction about 802.11 protocol networking technology uses radio waves to standards and its classification. It also provide high-speed