Installing the Moose Perl Module for Object-Oriented Programming

 

Welcome back to Tech Simplified TV, where we bring you tutorials on tech topics made simple! In today’s blog post, we’ll guide you through installing the Moose Perl module, a powerful framework for object-oriented programming in Perl. Whether you’re using your personal computer or need help from your Unix administrator at work, this guide will help you set up Moose quickly and easily.

What is Moose?

Moose is a modern Perl module designed to make object-oriented programming easier and more efficient. It provides robust tools and a simplified syntax for building classes, attributes, and methods in Perl.

If you’re exploring object-oriented programming in Perl, Moose is a must-have. Let’s walk through the installation process!

Installation Prerequisites

• Perl Installed: Make sure Perl is installed on your system.
• Internet Connection: Required for downloading the module.
• Admin Permissions: For work computers, you may need to ask your Unix administrator to handle the installation.

Step-by-Step Guide to Installing Moose:

• Visit the CPAN Page .The Moose module is hosted on CPAN (Comprehensive Perl Archive Network). The URL will typically be provided in related tutorials or documentation.Choose Your Installation Method

• There are two common ways to install modules from CPAN:

• CPAN Shell: A built-in tool for managing Perl modules.
• cpanm: A more modern and user-friendly alternative.

For this guide, we’ll use the CPAN Shell.

Installing Moose Using CPAN Shell:

• Open a Terminal
• Launch a terminal on your system.

• Invoke the CPAN Shell and check 

  if the CPAN shell is available by typing:  cpan

• If it’s your first time running CPAN, you may be prompted to configure it. Most configurations can be handled automatically by choosing "yes."
• Run the Installation Command

• In the CPAN shell, execute the following command to install Moose: 

  install Moose

• Provide Sudo Permissions
• For Linux or Unix systems, you’ll need to run the CPAN shell with root permissions (sudo) to install the module system-wide: sudo cpan
• If prompted, enter your system password to proceed.
• Monitor Installation Progress: The CPAN shell will download, compile, and install the Moose module. Ensure your system remains connected to the internet throughout this process.

• Verify Successful Installation. Once the process is complete, look for a confirmation message, such as: Result: PASS

---

Things to Note

• Office Computers: If you’re installing on a work machine, consult your Unix admin for permissions and assistance.
• System-wide vs. User Installation:
  • Installing with sudo allows all users on the system to access the module.
  • Without sudo, the module will only be available for the current user.

---

Wrapping Up:

That’s it! You’ve successfully installed the Moose Perl module and are ready to start leveraging its powerful object-oriented programming capabilities. For a live demonstration or more detailed explanations, check out our video tutorials on Tech Simplified TV.

Don’t forget to like, share, and subscribe for more tech tutorials. Got questions? Drop them in the comments below.

Until next time, happy coding!

Watch the video lecture : 

Coutesy: Image by www.pngegg.com

Read More

Installing the File::Tee Perl Module for VLSI Log Management

Welcome back to another installment of Free and Open Source VLSI Software Installation! In today’s post, we’re diving into the installation process for a key Perl module, File::Tee. This module is invaluable for anyone working with VLSI EDA tools, as it enables efficient log file management within your Perl scripts.

Understanding File::Tee and Log Files in VLSI Tools

Before we jump into the installation, let’s briefly discuss what File::Tee does and why it’s important.

When using VLSI EDA tools, log files are generated to capture various outputs during execution. Typically, these logs fall into two categories:

• General Logs: Contain all standard outputs and command results.
• Error Logs: Record errors or warnings encountered during execution.

While most VLSI tools automatically generate these logs, there may be scenarios where you want your Perl script to manage similar logging functionality. That’s where the File::Tee module comes in handy—it allows you to seamlessly create and manage log files within your Perl programs.

Installation Guide for File::Tee

Let’s walk through the installation process step by step.

# Prerequisites:

• Perl Installed: Ensure Perl is installed on your system.
• Internet Connection: Required for downloading the module from the CPAN repository.

Steps to Install File::Tee Using CPAN Shell

• Access the CPAN Shell
• Open a terminal and launch the CPAN shell by typing: cpan

• Verify CPAN Accessibility. Ensure that the CPAN shell is functioning correctly. You should see a prompt indicating the shell is active.

• Install the File::Tee Module
  Run the following command within the CPAN shell:

  install File::Tee
  

• Provide Root Permissions. During the installation, you might be prompted for the root or sudo password to complete the process. Enter the password to proceed.

• Monitor Installation Progress .The installation process will download and compile the module from CPAN. You can observe the log messages to confirm the progress.

• Verify Installation Success .Once completed, you should see a message indicating the installation passed successfully:

  Result: PASS
  

Post-Installation Check:

Review the log output to ensure there are no warnings or errors. If all looks good, you’re ready to use the File::Tee module in your Perl scripts!

Exploring More About File::Tee

The File::Tee module comes with a detailed synopsis, API documentation, and usage examples, all available on its CPAN page. You can explore these resources to understand its full capabilities and integrate it effectively into your projects.

Wrapping Up

Congratulations! You’ve successfully installed the File::Tee module and are now equipped to enhance your Perl scripts with robust log management. If you have any questions or run into issues, feel free to leave a comment below.

For more VLSI software tips and tutorials, stay tuned to our blog. Don’t forget to like, share, and subscribe to keep up with the latest updates.

Happy coding!

Watch the video here:

Courtesy:  Image by www.pngegg.com

Read More

Installing the Perl Modules for Excel File Operations

 

Welcome to Tech Simplified TV! Today, we’re diving into the process of installing three essential Perl modules from CPAN repositories that make working with MS Excel files seamless. Whether you're automating data processes or analyzing spreadsheets, these modules are indispensable. Let’s get started!

In this informative article, we delve into various topics centered around Perl module installation, specifically focusing on three essential modules: Spreadsheet::WriteExcel, Spreadsheet::ParseExcel, and Excel::Writer::XLSX. Our aim is to equip you with the necessary knowledge and skills to seamlessly install these modules from the CPAN network repository onto your local machine. These modules play a crucial role in enabling efficient Excel file manipulation through Perl programming. The video is structured into three chapters, commencing with an introduction and an overview of the three modules, followed by a comprehensive tour of their functionalities. Finally, we guide you step-by-step through the installation processes of Spreadsheet::ParseExcel and Excel::Writer::XLSX, ensuring you gain a solid understanding of each module's setup.

Step 1: Preparing Your Environment

Before diving in, ensure that Perl is installed on your system. To verify, open your terminal and run:

If CPAN is already installed, you're good to go! If not, you'll need to install it before proceeding.

Step 2: Installing the Modules:

Here are the three modules we’ll install:

1. Spreadsheet::ParseExcel

2. Spreadsheet::WriteExcel

3. Excel::Writer::XLSX

Module 1:

Spreadsheet::ParseExcel

This module lets you read Excel files in Perl, making it ideal for parsing spreadsheet data. Follow these steps to install it:

1. Visit the [Spreadsheet::ParseExcel] : https://metacpan.org/release/Spreadsheet-ParseExcel 

page on CPAN.

2. Open the CPAN shell by running:

install Spreadsheet::ParseExcel

Provide your root password if prompted and wait for the installation to complete.

Module 2:

Spreadsheet::WriteExcel

This module enables you to create and write data to Excel files. It supports Excel 97 to 2007 formats but is currently in maintenance mode.

1. Visit the [Spreadsheet::WriteExcel] https://metacpan.org/release/Spreadsheet-WriteExcel page on CPAN.

2. Open the CPAN shell and run: 

install sreadsheet::WriteExcel 

3. Wait for the installation to finish. Once done, you’re ready to write Excel files with Perl.

Module 3:

Excel::Writer::XLSX

This advanced module is perfect for creating modern Excel files with rich formatting options.

1. Go to the [Excel::Writer::XLSX]   https://metacpan.org/release/Excel-Writer-XLSX  page on CPAN.

2. Install the module using the CPAN shell:

install Excel::Writer::XLSX 

3. The installation might take longer due to its extensive features. Once complete, you’re all set to work with advanced Excel files.

Summary:

In this guide, we installed three powerful Perl modules for working with Excel files:

Spreadsheet::ParseExcel for reading Excel files.

Spreadsheet::WriteExcel for writing basic Excel files.

Excel::Writer::XLSX for advanced Excel file creation.

With these tools, you can automate and streamline Excel-related tasks directly from your Perl scripts. That’s all for today’s episode! Stay tuned for more tech tips, and feel free to leave your questions or suggestions in the comments below.

Watch the video tutorial here : 

Courtesy : Image by pngegg.com

Read More

Exploring VLSI Domains and Skill Sets : Test Chip & CAD Automation

In this episode, we’ll dive into two lesser-known but crucial domains in the VLSI  industry: Test Chip and CAD Automation. These domains don’t receive as much attention as others, such as STA (Static Timing Analysis), Physical Design (PD), or Verification. However, they are indispensable for the seamless functioning and progress of VLSI technology.  

Let’s explore why these domains are essential and how they contribute to the IC design process.  

Why These Domains Are Unique :

Test Chip and CAD Automation domains differ from more popular ones as they:  

• Require a mix of technical, inter-domain knowledge, and management skills.  
• Don’t follow a narrowly focused approach but instead interact with multiple stages of the design process.  
• Play behind-the-scenes roles that are critical for validating and optimizing IC designs.  

So, let’s begin our exploration!  

Test Chip Domain :

The Test Chip domain is fundamental for validating and bench marking the performance of designs, IPs, or innovative technologies.  

What Are Test Chips? 

Test chips, also called prototype chips, are created to ensure the design fulfills its specifications both in simulations (software) and physical silicon (hardware). These chips can include digital, analog, or mixed-signal designs, and even IPs, to evaluate their functionality against key performance metrics.  

Where Test Chip Units Operate in VLSI :

1. ASIC Design Flow:  

• In the RTL to GDS2 flow, SoCs (System on Chips) are designed with multimillion gates.  
• Test chips here are smaller K-chip designs reused across technology nodes and fabrication processes. 

2. Analog Design Flow: 

• Test chips in analog design are smaller, focusing on innovations to improve power, timing, and functionality.  
• These chips validate improvements across technology nodes and new fabrication techniques.  

3. Whole Chip Verification:  

•  A rigorous verification process encompassing analog, digital, and mixed-signal components. 
• Advanced EDA tools and verification techniques are required.  

4. DFT (Design for Testability):  

• Engineers troubleshoot testability issues, bridging gaps between software simulations and silicon validations.  

5. Post-Silicon Validation:  

• Involves hands-on testing of physical chips using advanced lab equipment.  
• Practical knowledge of tools like oscilloscopes and specialized instruments from vendors like Agilent is essential.  

6. Silicon Reporting:  

• The final step, where software-to-silicon results are compared and compiled into detailed reports for customers.  
• This is a high-responsibility role, requiring years of experience.  

CAD Automation Domain :

Computer-Aided Design (CAD) Automation ensures seamless tool integration and workflow efficiency across the VLSI design process.  

What Is CAD Automation?  

CAD engineers develop and maintain automation frameworks to support various design stages. These frameworks optimize time and resources, allowing designers to focus on creating innovative chips.  

Subdomains in CAD Automation:  

1. Frontend CAD:  

•  Covers RTL to synthesis and schematic design flows.  
•  Requires understanding of EDA tools and continuous updates to automate bug fixes and enhancements.  

2. DFT CAD:  

• Focuses on automation for smooth DFT inspections and testing.  

3. PNR (Place and Route) CAD:  

• Automates layout mechanisms for both digital and analog designs.  
• Requires knowledge of TCL scripting and proprietary languages like SKILL.  

4. Physical Verification CAD:  

•  Handles DRC (Design Rule Check), LVS (Layout vs. Schematic), and EMIR (Electromigration and IR drop) checks.  
•  Requires expertise in tools like ICV, PVS, and Calibre.  

5. IP View CAD:  

• Maintains consistency across multiple views of IPs, ensuring compatibility with various EDA tools and foundry requirements.  

6. Design Environment CAD:  

•  Develops user-friendly interfaces (GUIs) that streamline design workflows, saving designers significant time.  

 Core Skills for CAD Engineers : 

• Scripting Knowledge: Proficiency in scripting languages such as Python, Perl, TCL, and Bash.  
• Version Control: Familiarity with systems like CVS or SVN for managing automation repositories.  
• Resource Management: Expertise in tools like Univa Grid Engine (UGE) or IBM Load Sharing Facility (LSF) for computational resource optimization.  
• Communication and Troubleshooting: Cross-team collaboration and problem-solving skills are critical in resolving complex design challenges.  

Conclusion :

Both Test Chip and CAD Automation are pivotal to the VLSI industry’s progress. While these domains might not always be in the spotlight, they are integral to ensuring design accuracy, efficiency, and innovation.  

We hope this episode sheds light on these hidden gems of VLSI and helps you explore potential career paths in these exciting fields.  

Watch the Video here:

Courtesy: Image by www.pngegg.com

Read More

Exploring VLSI Domains and Skill Sets: IP Design & Characterization

In this episode, we’ll dive into the types of IPs (Intellectual Property) used in the VLSI domain and explore what makes this field so crucial in modern electronics. If you’re curious about how technology progresses and evolves, this is an episode you won’t want to miss. Let’s get started!

What is IP in VLSI?

In the world of VLSI, IP (Intellectual Property) refers to a self-contained design block with clearly defined inputs and outputs, capable of performing a specific function. The idea behind IP is simple: design once, reuse multiple times. This approach speeds up the development process and ensures consistency across projects.

What is Characterization?

Characterization in VLSI is the process of analyzing and recording the electrical properties of an IP (such as current, voltage, power variations, etc.) under different conditions. This step ensures the IP functions reliably across a range of environments and applications.

Types of IPs in VLSI:

Here’s a look at the major types of IPs designed in the VLSI domain:

1. Standard Cell IPs

These are the building blocks of any digital design, such as an ASIC or SoC. Standard cell libraries include:

• Logic cells (e.g., AND, OR gates)
• Sequential cells (e.g., flip-flops, latches)
• Power management cells
• Special cells (e.g., filler cells, decap cells)

Standard cell characterization is a key focus area, as variations in PVT (Process, Voltage, and Temperature) and threshold voltage impact their performance.

2. Memory IPs

Memory is integral to modern devices. Common types include:

• SRAM (Static RAM)
• DRAM (Dynamic RAM)
• NVM (Non-Volatile Memory), such as Flash
• BRAM (Battery-Backed RAM)

Memory IPs are designed at two levels:

• Unit Memory Cell Design
• Memory Array Design

Characterization ensures reliable storage and retrieval of data under varying conditions.

3. Analog IPs

These IPs perform specific analog functions and are critical in applications like power management, audio, and signal generation. Examples include:

• DC-DC Converters
• Phase-Locked Loops (PLLs)
• Audio IPs

4. SerDes IPs

SerDes (Serializer/Deserializer) IPs convert parallel data to serial and back, enabling high-speed data transfer in modern devices. They are particularly popular in handheld gadgets.

5. Mixed Signal IPs (e.g., USB, MIPI, PHY)

Mixed signal IPs, such as USB, MIPI, and PHY, bridge the analog and digital worlds. With the rise of plug-and-play devices, these IPs are in high demand.

6. IO Pad IPs

IO Pads manage the interface between the silicon chip and external circuitry. These are essential in any chip design.

Design Views and Skill Sets in IP Characterization

At the core of IP design and characterization lies the need for highly specialized skill sets. Here’s a breakdown:

1. HDL Representation

For digital IPs, you’ll use:

• Verilog/System Verilog
• VHDL

For analog IPs:

• Verilog-A
• Verilog-AMS

2. Timing Library Characterization

This involves performing dynamic timing analysis to record parameters like:

• Delay
• Slew
• Rise/Fall times

Tools: Liberate, Silicon Smart  

Format: Liberty (.lib)

3. Layout Design:

Layouts are handcrafted at the unit cell level, where components like diffusion layers, poly, and metal layers are meticulously designed.

Tools: Virtuoso, Custom Compiler  

Free Option: Magic Layout

4. Parasitic Extraction

Extracting parasitic resistance and capacitance ensures accurate simulation of the physical design. Tools like StarRC or QRC are used for this purpose.

5. Physical Verification

Tools like Calibre, ICV, and PVS are used for:

• DRC (Design Rule Checks)
• LVS (Layout vs. Schematic)
• EM/IR Checks

6. Schematic Design

For analog IPs, schematic design involves:

• Interconnecting components (active and passive)
• Simulating using AC, DC, or transient analysis

Free Tool: LTSpice

The Evolution of IP Design:

As technology advances, the need for innovative IPs grows. The scaling of technology nodes, increasing device complexity, and new applications in AI, IoT, and high-speed computing have spurred the creation of novel IPs.

The IP design and characterization field promises a future rich with opportunities for skilled professionals.

Conclusion:

The IP Design and Characterization domain is the backbone of VLSI innovation. Whether you're drawn to standard cells, memory, analog, or mixed-signal IPs, each offers a unique blend of challenges and rewards.

Thanks for reading! See you soon!

Watch the Video Here:

Courtesy : Image by www.png.com

Read More

Exploring VLSI Domains and Skill Sets: Analog & Analog Mixed Signal (AMS)

In this episode, we delve into two fascinating VLSI domains: Analog Design and Analog Mixed Signal (AMS) Design. While their names might sound similar, these domains require distinctly different skill sets. If you're curious about the differences and the expertise needed for each, stick around until the end!

Setting the Stage:

This episode is part of our ongoing series answering a question from our viewer. As previously mentioned, the detailed answer spans multiple episodes. In this second installment, we'll be focusing on the Analog Design and AMS Design domains. Let's get started!

Domains Inside Analog Design:

Analog design is rooted in concepts many of you may have encountered during your college days. If you've worked with SPICE or explored circuits like operational amplifiers (op-amps), phase-locked loops (PLLs), or oscillators, you're already on familiar ground.

Let's break down the key aspects:

1.Schematic Design :  

• Why It Matters: In the industry, manual SPICE-based node labeling isn't practical for complex designs. Instead, schematic capture tools like Cadence Virtuoso and Synopsys Custom Compiler streamline the process. These tools provide graphical interfaces to design and simulate circuits efficiently.  
• Skills Needed:  
• Strong foundation in analog electronics.  
• Familiarity with schematic capture tools like Virtuoso and LTspice (a free option to start with).  
• Knowledge of analysis methods such as transient, AC, DC, and noise analysis.  

2. Layout Design  

• Process: Analog layout design often employs semi-custom or full-custom techniques, particularly for unique blocks. Tools like Virtuoso and Custom Compiler are essential for this stage.  
• Skills Needed:  Expertise in analog layout methodologies.   Ability to optimize for performance metrics like noise, power and parasitics.  

3. Physical Verification  

• Verification Steps:  
• Using tools like Calibre DRC, LVS, and ICV to ensure design rule compliance and layout correctness.  
• DSPF Extraction with tools like StarRC to check parasitic effects.  
• Running EMIR (Electromigration and IR drop) checks and making necessary corrections.  
• Skills Needed:  
• Mastery of verification tools and scripting languages like Tcl for custom rule coding.  

4. Post-Layout Functional Verification  

• Objective: Incorporating parasitic effects into the design and ensuring performance remains within permissible limits.  
• Tools Used: Industry-standard SPICE simulators like HSPICE, Spectre, and CustomSim for efficient simulations.  

Domains Inside AMS Design:

AMS design combines analog and digital blocks, leveraging the best of both worlds. The scaling down of technology nodes below 10nm has made AMS designs increasingly relevant.

1. System-Level Modeling  

• Approach: Design begins with a top-down or bottom-up methodology. Tools like C++, Simulink, and SystemVerilog are used for system-level modeling.  
• Skills Needed: Proficiency in system-level modeling and simulation tools.  

2. Behavioral Design  

• Analog Behavioral Modeling:  
• Verilog-A is used for analog components.  
• Verilog-AMS allows seamless integration of analog and digital components.  
• Digital Behavioral Modeling: Verilog or SystemVerilog.  
• Skills Needed: Expertise in Verilog, Verilog-A, and Verilog-AMS.  

3. Mixed-Signal Verification  

• Process:  Concurrent simulation of analog and digital blocks using SPICE (for analog) and Verilog (for digital).  Proper configuration of A-to-D and D-to-A converters to facilitate smooth signal transactions.  
• Tools Used: Virtuoso AMS, CustomSim AMS, and Vista IDMS simulators.  

4. AMS Layout and Physical Verification  

• Layout Tools: AMS-specific layout capabilities in tools like Virtuoso AMS and Custom Compiler AMS Layout.  
• Verification: Standard DRC, LVS, ERC checks, and EMIR analysis.  
• Additional Skills:  
• Coding DRC rules with Tcl or tool-specific languages.  
• Deep understanding of silicon fabrication processes.  

Conclusion:

The Analog and AMS domains offer exciting opportunities, but they require dedicated learning and practice. From foundational tools like SPICE to advanced simulators like HSPICE and Virtuoso AMS, mastering these skills can open doors to rewarding VLSI careers.  

Watch the video here:

Courtesy: Image by www.png.com

Read More

Exploring VLSI Domains and Skill Sets: ASIC & FPGA

 

In this, we’ll explore the various domains in VLSI (Very Large Scale Integration) where you can build a career. Additionally, we’ll break down the specific skill sets needed for each domain. This topic stems from a viewer's request to clarify what professionals do in different VLSI domains like design, verification, and physical design. 

Since this is a broad topic, we’re dividing it into multiple posts. This blog is part one, so stay tuned for future installments!

Introduction to VLSI Domains: A Bird's Eye View

The VLSI ecosystem is vast and can be broadly divided into several domains:

1. Digital Design:

Digital design caters to various chip technologies like ASIC (Application-Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and SoC (System-on-Chip).  The digital design flow typically starts with RTL (Register Transfer Level) coding and ends with a GDSII (Graphic Data System) file for fabrication.

2. Analog Design :

In analog design, engineers work on components like PLLs (Phase-Locked Loops), op-amps, and oscillators. These components are crucial for circuits that process analog signals.

3. Analog Mixed-Signal (AMS) Design

AMS design combines analog and digital techniques, widely used in technologies like USB, SerDes, and IP cores. This domain bridges the gap between digital and analog design.

4. IP Design and Characterization :

IP (Intellectual Property) design involves creating reusable design blocks, such as:

• Digital IP: Logic gates, sequential elements.
• Analog IP: Converters (ADC/DAC), PLLs, memory cells.

5. Test Chip Development :

Test chips are prototypes that test designs on actual silicon. They validate performance by comparing test outcomes with simulation results, providing critical feedback for final production.

6. CAD and Automation :

CAD (Computer-Aided Design) automation tools form the backbone of all VLSI domains. Proficiency in these tools is essential across the board.

Domains Within Digital Design:

Let’s dive deeper into digital design, which spans multiple specialized domains:

1. RTL Design :

•  What It Entails: Writing hardware description languages (HDLs) like Verilog, VHDL, or SystemVerilog to define the chip’s behavior.
• Skills Needed: 
•  Advanced expertise in HDLs.
•  Strong problem-solving skills to design complex circuits.

2. Verification :

• What It Entails: Ensuring the chip design meets its specifications through methodologies like UVM (Universal Verification Methodology) and OVM (Open Verification Methodology).
• Skills Needed: 
• System Verilog assertions.
• Knowledge of LRMs (Language Reference Manuals) to stay updated with industry changes.

3. DFT (Design for Testability) : 

• What It Entails: Designing chips with built-in testing features for post-manufacturing validation.
• Skills Needed: Familiarity with tools like Tetramax and concepts like ATPG (Automatic Test Pattern Generation), BIST (Built-In Self-Test), and JTAG (Joint Test Action Group).

4. Physical Design :

• What It Entails: Translating RTL designs into layouts for fabrication. This stage includes:
• PNR (Place and Route).
• CTS (Clock Tree Synthesis).
• ECO (Engineering Change Order).
• Skills Needed: Tools like Cadence Encounter or Synopsys ICC2.

5. Physical Verification

• What It Entails: Verifying the layout with checks like:
• DRC (Design Rule Check).
• LVS (Layout vs. Schematic).
• ERC (Electrical Rule Check).
• Skills Needed: Tools such as IC Validator and PERC.

6. STA (Static Timing Analysis)

• What It Entails: Analyzing timing paths to ensure designs meet speed and performance goals.
• Skills Needed: Mastery of tools like PrimeTime and ETS

 7. Sign-Off :

• What It Entails: Finalizing the design for tape-out (fabrication). Engineers in this domain require comprehensive knowledge of the RTL-to-GDSII flow.
• Skills Needed: Tools like LEC (Logical Equivalence Check) and IREM.

Final Thoughts:

Each VLSI domain offers unique challenges and opportunities. While large companies often have specialized teams for each domain, startups may require engineers to handle multiple responsibilities. The choice of domain depends on your interest and expertise.

Stay tuned for upcoming blogs where we’ll discuss analog design, AMS design, and other key domains in detail. 

Let’s simplify VLSI, one domain at a time. Until next time, happy learning! 😊

Watch the video here:

Courtesy: Image by www.pngegg.com

Read More