Mohamed O.Abouzeid

Question: How do decoupling capacitors help in maintaining signal integrity in digital circuits? Answer: Decoupling capacitors are used to filter out noise from the power supply and provide a stable voltage to digital ICs. They store charge and release it when there is a transient demand, thereby reducing voltage fluctuations and ensuring a clean power supply for consistent signal operation. #Capacitor #Electronics #PassiveComponents #Capacitance #ElectricalEngineering #Resistor #PassiveComponents #Resistance #Inductor #Inductance #ElectronicsDesign #CircuitDesign #PCBDesign #HardwareDesign #PCB #PCBLayout #CircuitLayout #ElectronicsLayout #ElectricalEngineering #EmbeddedSystems #TechDesign #Engineering

21

Proper layout of decoupling capacitors is crucial for ensuring their effectiveness in reducing noise, stabilizing voltage, and improving overall circuit performance. Here are some key guidelines for laying out decoupling capacitors in a PCB design: 1. Placement Close Proximity: Place decoupling capacitors as close as possible to the power supply pins of the IC they are intended to decouple. The shorter the distance between the capacitor and the IC, the lower the inductance and resistance of the connection. Direct Path: Ensure that the connections between the capacitor, the power pin of the IC, and the ground are as short and direct as possible. This minimizes parasitic inductance and resistance, which can degrade the capacitor's performance. Multiple Capacitors: For large or complex ICs, use multiple decoupling capacitors distributed around the IC. This helps to provide effective decoupling at various points around the IC. 2. Via and Trace Considerations Minimize Inductance: Use wide traces and multiple vias to connect the decoupling capacitors to the power and ground planes. This reduces inductance and ensures a low-impedance path. Ground Plane: Connect the capacitor directly to a solid ground plane rather than running long traces to the ground. This provides a low-impedance return path for high-frequency currents. Via Placement: Place vias close to the capacitor pads to minimize the inductance of the connection. If possible, use multiple vias to further reduce inductance. 3. Capacitor Values and Types Broad Frequency Range: Use capacitors with different values (e.g., 0.1 µF, 1 µF, 10 µF) in parallel to cover a wide range of frequencies. Smaller value capacitors are more effective at higher frequencies, while larger values are better for lower frequencies. Low ESR: Choose capacitors with low Equivalent Series Resistance (ESR) for better high-frequency performance. 4. Grounding Strategy Local Grounding: Ensure that each decoupling capacitor has a good connection to the local ground plane. This helps to provide a low-impedance return path for high-frequency currents. Avoid Ground Loops: Ensure that the ground connections of decoupling capacitors do not form large loops, which can act as antennas and pick up noise. 5. Power Distribution Power Planes: Use solid power planes instead of long traces for power distribution. This reduces the impedance of the power supply network and improves decoupling performance. Bypass Capacitors: Use bypass capacitors along with decoupling capacitors to further stabilize the power supply. Bypass capacitors are typically placed near voltage regulators and other power supply components. 6. Thermal Considerations Thermal Management: Ensure that decoupling capacitors are not placed in areas of the PCB that experience excessive heat, as this can affect their performance and reliability. #pcb #design #palcement #vias #plane #ESR #capacitor #inductor #traces #plane

20

How to understand UVM Testbench in detail needed in ASIC Verification in VLSI: There are multiple components and objects which build the UVM testbench hierarchy. Among them, one important block is Agent which has three components Sequencer, Driver and Monitor. Below concepts are useful in learning the structure in detail: ✓ Sequencer <--> Driver handshaking mechanism for a. Only for req Id. b. Both req and RSP c. Pipelined and Non Pipelined access d. Wait States ✓ Use of Non blocking assignment in Driver logic code why? ✓ How to use clockvar in Driver. ✓ Configuration mechanism in Driver. Can we use UVM resource db. ✓ Factory registration and factory override. ✓ Use of function new() ✓ How to start a sequence item and randomize. ✓ How to handle multiple sequence item through Sequencer --> Use of arbitration algorithm. ✓ How to handle interrupts ✓ What is user arbitration and need of it ✓ Use of analysis port and TLM port. How to connect analysis port to subscribers. ✓ Different types of Port export connection. ✓ Use of p / m sequencer. ✓ How write function needs to be implemented. ✓ Difference b/w active and passive agent. ✓ Why Monitor uses new() instead of create method. ✓ Difference b/w TLM1.0 and TLM2.0 #vlsi #asic #electronics #electricalengineering

209

5 Comments

📢 Understanding Power, Performance, and Area (PPA) Analysis in VLSI: Key to Efficient Chip Design(Part-4) 🎯What are the methodologies for PPA analysis in VLSI ? PPA analysis in VLSI involves a set of methodologies and techniques to optimize the power consumption, performance, and chip area of semiconductor devices. Here are the key methodologies used for PPA analysis in VLSI: 🎯Architectural Exploration: Architectural exploration is a crucial initial step in P PA analysis. It involves studying various chip architectures and design alternatives at the conceptual level to identify the most suitable trade-offs between power, performance, and area. Designers assess different architectural choices, such as pipelining, parallel processing, memory hierarchy, and cache sizes, to understand their impact on PPA metrics. The goal is to find an optimal architecture that meets the target performance while adhering to power and area constraints. 🎯 Power Estimation: Power estimation involves modeling and predicting the power consumption of a VLSI chip at different operational states and scenarios. Power estimation can be performed at various levels of abstraction, including gate level, RTL, and system level. Power estimation tools help designers identify power-hungry sections or modules within the chip. Understanding power consumption patterns aids in the implementation of targeted power optimization techniques, such as clock gating, power gating, and voltage scaling. 🎯 Performance Modeling: Performance modeling is used to predict the chip's performance under various workloads, clock frequencies, and environmental conditions. Simulation tools are employed to analyze critical paths, timing constraints, and potential bottlenecks that may limit the chip's maximum achievable performance. By understanding the chip's performance characteristics, designers can make informed decisions to optimize performance, ensuring that the chip operates at its full potential. 🎯Area Optimization: Area optimization focuses on reducing the physical footprint of the chip. It involves various design methodologies, such as layout synthesis, floorplanning, and logic synthesis, to achieve efficient use of silicon real estate. By minimizing the chip's area, more chips can be fabricated on a single wafer, leading to higher yield and reduced manufacturing costs. Area optimization also enables the integration of more functionalities on a chip without compromising on power and performance.

26

1 Comment

In UVM-based verification environments, understanding the distinction between Verification Components (VC) and Bus Functional Models (BFM) is crucial for effective testbench development. Let's break it down: What is a Verification Component (VC)? A Verification Component in UVM is a modular, reusable block that includes agents, drivers, monitors, and scoreboards to comprehensively verify a design under test (DUT). VCs encapsulate behavior, protocols, and data handling. How is it Different from a Bus Functional Model (BFM)? A BFM focuses on driving and sampling signals at the interface level, providing low-level transaction capabilities without higher-level control or checks. Advantages of VC over BFM: 1. Modularity: VCs are highly modular, allowing easy reuse and integration into different testbenches. 2. Scalability: VCs can handle complex protocols and behaviors, making them suitable for sophisticated designs. 3. Self-Checking: VCs often include built-in monitors and scoreboards for self-checking, reducing manual effort. 4. Configurability: VCs can be easily configured and customized using sequences and configuration objects. Driving & Monitoring Signals with Sequences and Tests: 1. Driving Signals: - Use sequences to generate transactions that the driver converts into signal-level activities. class my_sequence extends uvm_sequence; `uvm_object_utils(my_sequence) task body(); // Generate and send transactions my_transaction tr = my_transaction::type_id::create("tr"); start_item(tr); tr.data = 'hA5; // Example data finish_item(tr); endtask endclass 2. Monitoring Signals: - Monitors observe the DUT's signal activity and collect data for analysis. class my_monitor extends uvm_monitor; `uvm_component_utils(my_monitor) // Signal observation logic virtual interface my_if vif; task run_phase(uvm_phase phase); forever begin @ (posedge vif.clk); if (vif.sig) begin // Capture and analyze signal data end end endtask endclass 3. Configuring Behavior: - Use tests to configure and control the verification environment. class my_test extends uvm_test; `uvm_component_utils(my_test) task run_phase(uvm_phase phase); my_sequence seq; uvm_config_db#(virtual my_if)::set(this, "my_env.*", "vif", my_vif); seq = my_sequence::type_id::create("seq"); seq.start(my_env.my_sequencer); endtask endclass By utilizing VCs, you can build robust, reusable, and scalable verification environments that streamline the verification process and enhance testbench capabilities. #UVM #VerificationComponents #BFM #SystemVerilog #HardwareVerification #EDA #TechTips

1

Basic concepts needed to start learning SystemVerilog: [1] Event scheduling in SystemVerilog. Difference b/w Active and Reactive Region. Role of observed region, preponed and postponed region. [2] How to avoid Race condition in SystemVerilog. Use of program block, clocking block and Modport. [3] How to handle asynchronous signals in the design using SV. [4] Different types of arrays: Packed, unpacked, associative and Dynamic. Which arrays are used for which purpose. [5] Interprocess communication like Mailbox and Semaphore. What is the role of triggering and event control. [6] Difference b/w Mailbox and Queue. Implement a scoreboard using associative array or Queue or TLM Fifo. [7] Difference b/w Struct and union. Difference b/w using a struct or a class. [8] Object and handle in a class. Inheritance tree. How to hide a variable in a clss. How to call or access method or a function within different class of inheritance tree. Concept of upcast and downcast. [9] Concept of Polymorphism, abstract class, virtual function and pure virtual method. [10] Data types in SV, operators and Synthesizable constructs. [11] How to override a constraint. Difference b/w rand and randc. Concept of inline constraint, weighted distribution, inside operator and solve x before y. [12] Difference b/w hard and soft constraints. [13] Need of SV interfaces. Difference b/w physical and virtual interface. [14] Use of pre randomize, post randomize and std::randomize methods. How to on/off randomization and constraint. #vlsi #asic #semiconductorindustry #electronics

172

6 Comments

Headline: Designed a 5kW High-Current PCB Board with MasterGan1 ICs in Parallel for Balanced Power Control Description: "I'm thrilled to share my latest accomplishment! I successfully designed a high-power PCB board that can handle up to 5kW of power using 12 MasterGan1 ICs in parallel. This achievement ensures balanced power control and distribution. To achieve this, I employed several design techniques: - Symmetrical PCB Layout: I designed the PCB layout to be symmetrical, with identical trace lengths and widths for each IC. This ensures equal electrical characteristics and minimizes variability. - Strategic IC Placement: I carefully placed the ICs to maintain equal distances from input and output points, with a tolerance of 10mil. This reduces voltage drops and ensures equal current sharing. - Shared Input and Output Points: I designed the board to have three input supply points and three output points, with two ICs sharing each points. This configuration promotes balanced loading and reduces the risk of overheating.

19

2 Comments

Let's create a series to discuss Signal Integrity in a nutshell. Topic 1: Factors to Consider in Signal Integrity for a high-Speed Board: Here are some key points to consider in the signal integrity flow for high-speed board design: 1. System Requirements Analysis: Understand the high-speed requirements of the system, including data rates, signal frequencies, and communication protocols. 2. Topology Planning (Layout Design): Carefully design the board layout and interconnect topology to minimize signal degradation and interference. Consider factors like signal routing, layer stackup, and component placement. 3. Transmission Line Theory: Apply transmission line theory to design controlled impedance traces that match the characteristic impedance of the transmission medium (usually PCB traces) to minimize reflections and signal distortion. 4. Cross-talk Analysis: Analyze and mitigate cross-talk between adjacent signal traces by maintaining proper spacing, using ground planes, and implementing shielding techniques. 5. Signal Integrity Simulation: Utilize simulation tools such as ADS to model signal behavior and predict issues like reflections, overshoot, undershoot, and signal integrity violations. 6. Power Integrity Analysis: Ensure stable power distribution across the board by minimizing voltage drops, managing power plane impedance, and reducing noise from switching components. 7. Signal Termination: Implement proper termination techniques such as series termination, parallel termination, or AC termination to match the impedance of the transmission line and prevent signal reflections. 8. EMI/EMC Considerations: Design the board to minimize electromagnetic interference (EMI) and ensure compliance with electromagnetic compatibility (EMC) standards. This includes proper grounding techniques, shielding, and signal isolation. 9. High-Speed Connector Design: Pay attention to the design of high-speed connectors to maintain signal integrity at the interface between different board sections or external devices. 10. Signal Integrity Validation: Validate the design through signal integrity testing, including time-domain reflectometry (TDR), eye diagram analysis, and bit error rate (BER) testing to ensure that the system meets the required performance criteria. By following these steps and considering the intricacies of signal integrity throughout the design process, you can enhance the reliability and performance of high-speed boards. hashtag #signalintegrity #powerintegrity #boarddesign #vlsi

63

2 Comments

📢 Understanding Power, Performance, and Area (PPA) Analysis in VLSI: Key to Efficient Chip Design(Part-5) 📟 Power Management Techniques: Power management techniques aim to dynamically adjust power consumption based on the chip's workload and requirements. Clock gating involves selectively enabling clock signals to idle or inactive parts of the chip, reducing unnecessary switching and power consumption. Power gating, on the other hand, turns off power to entire sections of the chip when they are not in use, further reducing static power consumption. Voltage scaling involves adjusting the supply voltage to optimize power and performance trade-offs. 📟Thermal Analysis: Thermal analysis is an essential part of PPA analysis, especially for high-performance chips. As chips become more densely packed with transistors, managing heat dissipation becomes critical. Thermal analysis helps identify potential hotspots, where excessive heat can cause performance degradation or reliability issues. Proper heat dissipation techniques, such as adding thermal vias or spreading power-consuming components, are applied to ensure the chip's reliable operation. 📟 Yield Analysis and Design for Manufacturability (DFM): PPA analysis includes considerations for yield and manufacturability. Yield analysis assesses potential manufacturing defects and their impact on chip performance and power consumption. Design for Manufacturability (DFM) techniques aim to improve chip yield and reliability during the manufacturing process by optimizing layout and ensuring the design adheres to process constraints.

4

What is ESR in Capacitors? Equivalent Series Resistance (ESR) in capacitors is the sum of all the internal resistive losses within the capacitor. It represents the resistance that is in series with the ideal capacitor. ESR is an important parameter as it affects the performance of the capacitor, especially in high-frequency and high-current applications. Impact on Performance: Energy Dissipation: ESR causes power dissipation in the form of heat, which can be significant in high-current applications. High-Frequency Response: High ESR can limit the capacitor’s effectiveness in filtering and decoupling at high frequencies. Capacitors with lower ESR are more effective at high-frequency noise suppression. Stability: High ESR can affect the stability of power supply circuits and can lead to voltage drops, especially during rapid changes in load current. Selection Criteria: For applications requiring high-frequency performance, such as decoupling and bypassing in digital circuits, low-ESR capacitors are preferred. In power supply circuits, low-ESR capacitors help maintain voltage stability and improve overall efficiency. #capacitor #spi #espi #i2c #uart #esr #capacitor #voltage

35

1 Comment

One of the important aspect in Verifying a RTL design is to use Assertion Based Verification (ABV) techniques. Assertions are used as a check against a design. For VLSI, someone needs to provide equal emphasis to SystemVerilog Assertions (SVA) in addition to Verilog, SV, Digital Design, etc. Below are some of the advantages of using Assertions in both RTL design and Verification: [1] SVA has to be written by both RTL designers and Verification engineers. RTL assertions mostly deals with microarchitectural specification while verification engineers deals with interface and functionality based assertions. [2] SVA improves the Observability of the design and thereby reducing the overall debug effort. This can be achieved by inserting various check points within the specific areas of the design to check the effect of internal bug instead of waiting for the entire Testcase to complete and then to backtrace the signal to find out the bug. [3] SVA can be written at multiple places within the Testbench like interfaces, monitor, scoreboard and even using bind with the top module to improve the probability of catching bugs within the design. [4] SVA has the keyword called as “cover” which will make sure the assertions are covered and is also used as a key indicator to measure verification progress. [5] SVA reduces the time to bring up the code because a simple logic may became cumbersome while trying to implement with Verilog and hence it makes the code more readable. Property P1; @(posedge clk) abc |-> ##[1:2] cd; endproperty assert property (P1); [6] SVA has assertion directives like assume, expect and restrict apart from assert which can be used in coding several temporal assertion as per the requirement. [7] Assertions has the capability to capture specific scenarios to measure coverage which is a important parameter to close coverage. [8] Since assertions are by default always on, they are useful in tracking the Testcases faster in case of any error. #vlsi #asic #electronics #electricalengineering

151

🚨 **Ensuring Correct Power Down State in IC Designs Using Synopsys VSLP Tool** 🚨 ### **What is Corr Power Down State?** **Corr Power Down State** refers to the correct management and implementation of power down states in an IC design, ensuring that sections of the circuit can be powered down properly without affecting overall functionality. ### **Importance of Correct Power Down State** - **Power Efficiency**: Properly managing power down states reduces power consumption, enhancing energy efficiency and extending battery life in portable devices. - **System Stability**: Ensuring that power down states are correctly implemented prevents unintended power disruptions that could lead to system instability or data loss. - **Reliability**: Correct power down state management ensures that the IC operates reliably under different power conditions, improving overall system robustness. - **Thermal Management**: Reducing power consumption through effective power down state management helps in thermal management by lowering heat generation. ### **Detecting and Addressing Corr Power Down State Issues with Synopsys VSLP** The Synopsys VSLP tool provides advanced capabilities to detect and rectify issues related to power down states, ensuring reliable and efficient IC designs. #### **1. Static Analysis** - **Power Down Path Checks**: Analyze the design to ensure that power down paths are correctly implemented and that all necessary components can enter a power down state without issues. - **State Transition Verification**: Verify that transitions to and from power down states are managed correctly, preventing any functional disruptions. #### **2. Dynamic Simulation** - **Power Down Scenarios**: Simulate various power down scenarios to assess the impact on system functionality and ensure smooth transitions. - **Power Consumption Analysis**: Monitor power consumption during power down states to identify any irregularities or inefficiencies. ### **Best Practices for Managing Power Down State** 1. **Clear Power Management Strategy**: Develop a clear strategy for managing power down states, including guidelines for when and how components should enter and exit these states. 2. **Continuous Validation**: Regularly validate power down state implementation throughout the design process to catch and address issues early. 3. **Collaboration**: Work closely with power management and system design teams to ensure that power down states are integrated seamlessly into the overall design. 4. **Advanced Tool Utilization**: Use advanced tools like Synopsys VSLP for automated detection and correction of power down state issues. #icdesign #synopsys #workwithuppula Thanks, Vishnu

16

#fundamentalseries UVM Monitor Classes 7. uvm_monitor * Observes DUT signals and converts them into transactions. * Sends transactions to other components like scoreboards and coverage collectors. * Passive component, does not drive signals. Environment Classes 8. uvm_env * Container class for grouping related UVM components (e.g., agents, scoreboards). * Typically represents a complete verification environment for a specific DUT. Agent Classes 9. uvm_agent * Groups related driver, sequencer, and monitor components. * Can be active (contains a driver and sequencer) or passive (contains only a monitor). Reporting Classes 10. uvm_report_object * Provides reporting utilities for printing messages, warnings, and errors. * Base class for components that need reporting capabilities. 11. uvm_report_server * Centralized reporting mechanism. * Collects and processes messages from uvm_report_object instances. Scoreboard and Analysis Classes 12. uvm_scoreboard * Analyzes DUT outputs and compares them with expected results. * Receives transactions from monitors via analysis ports. 13. uvm_analysis_port * Used for broadcasting transactions to one or more analysis components. * Example: uvm_analysis_port #(T)where T is the transaction type. 14. uvm_analysis_imp * Implements the analysis export interface. * Used to connect analysis ports to scoreboards or other analysis components. #uvm #uvmmethodology #fundamentalseries #uvmconcepts #uvmsyntax #verification #testbenches #verificationengineer #training #mirafratechnologies

27

1 Comment

Starting ABCDE again for new evening batch tomorrow. Live sessions are more effective as compared to recorded stuff. I adjusted my schedule for working embedded system professionals. * 8:45PM - 9:45PM for those who don't get time during weekends. * Separate batches on Saturday and Sunday Morning Just finished regular Coding skills exercise with Premium club members. Learn in an environment with experienced embedded system professional and be ahead in competition always .... If your target is big , you need to come out of comfort zone. Learn from various sources until you get expertise and can face interviews with full confidence. Just learn it ... Have a Great Day ! #embedkari #embeddedsystem #opentowork #freshers #firmware

4

🔌 Project Completed: Designing a Switched Capacitive DAC 📊 Overview: I recently completed a project focused on designing and implementing a Switched Capacitive Digital-to-Analog Converter (DAC). This type of DAC is widely used in various applications due to its high linearity, low power consumption, and accuracy in analog signal generation. 🔍 Project Details: Single-Ended Op-Amp Design: I designed a single-ended operational amplifier (op-amp) to be used within the DAC circuit. The op-amp plays a crucial role in amplifying the analog signal and maintaining stability. Inverter Unit: As part of the DAC design, I created an inverter unit. The inverter ensures proper signal polarity inversion, which is essential for accurate analog output. Capacitive DAC Design: The heart of the project was the capacitive DAC itself. Using capacitors and switches controlled by a clock signal, I converted digital input codes into precise analog output voltages or currents. By toggling switches according to the input code, capacitors accumulated charge, resulting in the desired analog signal. Test Bench with 10-Bit ADC: To validate the DAC’s performance, I set up a test bench using a 10-bit Analog-to-Digital Converter (ADC). This allowed me to compare the DAC’s output with the expected values and fine-tune its operation. 🚀 Key Takeaways: Successfully implemented a switched capacitive DAC Designed an efficient single-ended op-amp Demonstrated understanding of inverter circuits Validated the DAC using a 10-bit ADC test bench 👏 Kudos to the My great team who supported me throughout this exciting journey! Radwa El-Harty Yara Ahmed Rahma M. Ibrahim  🙌 #engineering #electronics #DAC #ADC #analogdesign #projectcompleted #CND #AUC

45

Hi Folks, Why timing constraints are so important in FPGA design?? I have gone through some of the following pages and good for understanding of timing constraints. 1) From Lattice : https://lnkd.in/gUYgrE7G 2) From 01signals : https://lnkd.in/gx8Tkian 3) From silicloud : https://lnkd.in/gndzmq4G Hope it will be useful..!!! 0052@allaboutfpga #fpga #allaboutfpga #vhdl #verilog #vlsi #asic #digital #electronics #automation  #innovation #semiconductor #technology #intel #amd

74

1 Comment

Scripting Interview Question Role: Physical Design Company : Product Based Experience: 5+ years Write a program or suggest an algorithm that compares two files containing lines of code. The program should perform the following tasks: 1.Consider all possible solutions and identify the most efficient one. 2.Identify and report matching patterns between the two files. 3.Identify and report non-matching patterns between the two files. 4.Propose a solution for scenarios where the file sizes are small (hundreds of lines of code). 5.Propose a solution for scenarios where the file sizes are large (thousands of lines of code). 6.Discuss whether the same solution works for both small and large file sizes. Instructions for Submission: Please post your answers in the comment section below. For detailed explanations and solutions, check the answers later on website compile-vlsi.blogspot.com https://lnkd.in/gREKu3SE ---------------------------------------------------------------------- Below are the links to access other Physical Design related blogs : Port Punching in Physical Design VLSI: https://lnkd.in/gnTVRjqd Inputs required to start physical design https://lnkd.in/gstmuBYS Tcl program to find out unique/odd elements using XOR: https://lnkd.in/g7mE_c5X Area optimization : https://lnkd.in/gVav8EgE Transition: https://lnkd.in/g5_pKd5e LVS: https://lnkd.in/giDg6X4U Congestion: https://lnkd.in/g-xNkHUy Floorplan Part 1 : https://lnkd.in/gxpuhgU9 Floorplan Part 2: https://lnkd.in/gx_6wJ4e Floorplan Part 3: https://lnkd.in/gq47qyJH Placement - Part 1 https://lnkd.in/g9X2iXf9 Placement - Part 2 https://lnkd.in/g3C99c3i Placement - Part 3 https://lnkd.in/gVEKkGyg #scripting #coding #pd #physicaldesign #pv #semiconductor #vlsi #india #freshers #interview #timing #files #compare #dsa #python #perl #tcl #infineon #programming #design #physical #timing #placement #floorplan #jobs #entrylevel

133

2 Comments

UVM Testbench Components To understand UVM, you should know all UVM Components. These UVM Components are: 1. DUT 2. Interface 3. Sequences 4. Sequencer 5. Driver 6. Monitor 7. Subscriber 8. Agent 9.Scoreboard 10. Env 11. Test 12. Top Let's understand each of these components, their role in UVM testbench, what do they consist of, etc. Link in Comment.

64

1 Comment

How to fit in the "Time to Market" with this cycle? Chip Tape out Cycle as per this Paper. Worst Case - 24 Months. Best Case - 15 Months. How can we tapeout every 3-6 Months. Double your work!!! 😁

18