Skip to main content

RTL Design Engineer at Skyroot Aerospace

Hello, Dear Readers, Skyroot Aerospace has a vacancy for the RTL Design Engineer role. About Skyroot Aerospace: A cutting-edge startup founded by ex-ISRO scientists. Dedicated to affordable space access, we're rewriting aerospace technology rules. Our dynamic team fosters inventiveness, collaboration, and relentless excellence. Join us on a transformative journey to redefine space possibilities. Welcome to the forefront of space innovation with Skyroot Aerospace! Purpose of role: Understand architectural requirements and Design micro-architecture, implement design blocks using VHDL/Verilog for FPGA based Avionics packages for orbital launch vehicles and ground infrastructure. Job Requirements: 2+ Years of RTL and system design experience. Strong knowledge on Digital System Design (DSD). Strong knowledge of RTL/SoC design/integration with VHDL/Verilog. Strong knowledge in problem solving and debugging skills. Ability to understand architectural requirements and Design micro-archite...

Inputs to the STA tool

Dear Readers,  

Today we will be discussing the inputs needed for the STA tool and the importance of each input file and its contents. This will be a lengthy and informative presentation. I hope this learning is enjoyable for you all.

Inputs for the STA tool

1. Gate level netlist

2. SDC (Synopsys Design Constraints)

3. .Lib

4. SPEF (Standard Parasitic Exchange Format)

5. SDF (Standard Delay format)


1. Gate level netlist: 

    The tool will receive the netlist after routing as input. Our design information and its connections, including metals and vias, can be found here.

2. SDC: 

    To ensure that the design meets its timing requirements, clock constraints are required in SDC. The contents of SDC include clock-related information such as clock period, clock latency, uncertainty, and transitions. And IO delay modelling like input and output delays, load, max fanout, max capacitance and max transition etc.., we will discuss the SDC contents in detail in the next post including the commands.

3. Lib:  

.Lib contains the following information.

  1. Cell Definitions:

    • Logical Cells: Information about logical standard cells (gates, flip-flops, latches, etc.) and their functionality.
    • I/O Cells: Definitions for input and output cells that interface with the external environment.
  2. Timing Information:

    • Cell Timing Models: Timing characteristics for each standard cell, including delays, transition times, setup times, hold times, etc.
    • Library Constraints: Maximum and minimum input/output arrival times, clock-to-Q delays, and other timing constraints.
  3. Power Information:

    • Power Models: Power consumption information for each standard cell, including dynamic power, leakage power, and total power.
  4. Physical Information:

    • Cell Area Models: Information about the physical size or area of each standard cell.
    • Pin Placement: Location and arrangement of pins for each cell.
  5. Voltage and Temperature Dependencies:

    • Voltage Scaling Information: How cell characteristics vary with different supply voltages.
    • Temperature Scaling Information: How cell characteristics vary with different temperatures.
  6. Library Constraints:

    • Maximum Capacitance: Maximum allowable load capacitance for each cell.
    • Maximum Fanout: Maximum number of loads a cell can drive.
  7. Other Information:

    • Library Version Information: Details about the library version and compatibility.
    • Corner Models: Different corners representing best-case, typical, and worst-case scenarios for process variations.
    • Please keep in mind that this is a simplified example for illustrative purposes, and the actual '.lib' files are much more detailed and complex.

# Header Information
library(example_lib) {
  technology (CMOS);
  voltage (3.3);
  time_unit : ns;
  capacitance_unit (1e-15);
  current_unit : mA;
  leakage_power_unit : nW;
  library_features (cell);

  # Logical Cell Definitions
  cell(nand2) {
    area : 4.5;   # Cell area in square micrometers
    cell_leakage_power : 10;   # Leakage power in nW
    cell_footprint : "AND2_X1";   # Physical footprint

    # Timing Models
    cell_fall(delay_template) {
      values(1.0, 2.0, 3.0);   # Timing values for falling transition
    }
    cell_rise(delay_template) {
      values(1.5, 2.5, 3.5);   # Timing values for rising transition
    }

    # Power Models
    cell_power(dynamic) {
      when : "A";
      values(0.5, 1.0, 1.5);   # Dynamic power values
    }
    cell_power(leakage) {
      values(5.0);   # Static or leakage power value
    }

    # Pin Information
    pin(A) {
      direction : input;
      capacitance : 0.1;   # Input capacitance
    }
    pin(B) {
      direction : input;
      capacitance : 0.1;
    }
    pin(Y) {
      direction : output;
      capacitance : 0.2;   # Output capacitance
    }
  }
}
    • 4. SPEF :
    This file was extracted from the layout using Star RC extraction tool (Synopsys), which contains parasitic information of interconnects. These include resistances and capacitances associated with the wires and vias, which are essential for STA timing calculations and also for estimating signal integrity and power consumption. The capacitance affects the speed of the signal transition and is crucial for estimating dynamic power consumption. These values were generated at different temperatures for every corner (the best, worst, and typical values of R, C, and RC). Every net has a unique ID corresponding to R,C values.
  1. Here's a simplified example of what a SPEF file might look like:

    • * Unit: 1.0E-12 F, 1.0E+3 Ohms * Design Information Section D_NET 1 CLK * Node Information Section * Format: (node name) (node capacitance) (node resistance) * Units: F Ohms * Example: * R 1 1.0 * C 1 0.5 * Resistances and Capacitances Section * Format: (net name) (capacitance between nodes) (resistance between nodes) * Units: F Ohms * Example: * * 2 1.0 0.5
5. SDF :

    This contains back annotated information describes cell delays, interconnect delays, timing checks. The timing checks includes setup, hold, recovery time, removal time, minimum pulse width. Some engineers won't give SDF as an input to the STA tool, but this can be useful for DFT engineers then PD engineer has to generate SDF by using "write_sdf" command and give it to them.
  1. To get a sense of how the SDF file would look, the following example is very basic. The actual file will be vast and complex.

  2. ;; Cell Timing Section
  3. (cell (cell_name)
  4.   (cell_rise (condition) (timing_value))
  5.   (cell_fall (condition) (timing_value))
  6.   ; ... other cell timing information ...
  7. )

  8. ;; Pin Timing Section
  9. (pin (cell_name) (pin_name)
  10.   (rise_capacitance (condition) (capacitance_value))
  11.   (fall_capacitance (condition) (capacitance_value))
  12.   ; ... other pin timing information ...
  13. )

  14. ;; Timing Checks Section
  15. (check (cell_name) (check_type) (limit_value))
  16. ; ... other timing checks ...

  17. ;; Port Transition Section
  18. (port (port_name) (clock_transition (rise|fall) (transition_value)))
  19. ; ... other port transition information ...

  20. ;; Interconnect Timing Section
  21. (interconnect (from_pin) (to_pin)
  22.   (rise_delay (condition) (delay_value))
  23.   (fall_delay (condition) (delay_value))
  24.   ; ... other interconnect timing information ...
  25. )

  26. ;; Clock Section
  27. (clock (clock_name)
  28.   (clock_type (primary|generated))
  29.   (period (condition) (period_value))
  30.   ; ... other clock information ...
  31. )

  32. ;; Clock Network Section
  33. (clock_network (clock_name)
  34.   (hierarchical_pin_name (port_name))
  35.   ; ... other clock network information ...
  36. )

STA SERIES:




Connect with me 


Comments

Post a Comment

Popular posts from this blog

Exploring the Role of LEF Files in VLSI Chip Design: A Beginner's Guide

Hello Dear Readers,   Today in this post, I will provide some deep insight into the LEF file role during the VLSI Chip Design process. In VLSI (Very Large Scale Integration) design, a LEF file is a file that contains information about the physical geometry of the standard cells used in a circuit. LEF stands for Library Exchange Format. A standard cell is a pre-designed logic cell that contains a specific function, such as a flip-flop or an AND gate. Standard cells are designed to be easily combinable and scalable to create more complex circuits. The physical geometry of each standard cell is defined in the LEF file. The LEF file contains information such as the width, height, and position of the pins and metal layers of each standard cell. It also contains information about the physical design rules that govern the placement of these cells on the chip. LEF files are important in VLSI design because they enable the interoperability of different design tools from different vend...

Internship - SoC /IP Design at NXP India

Hello Dear Readers, Currently, at NXP India  vacancy for  Internship - SoC /IP Design   role.   We are looking for a Master degree student with Electronics and Communication Engineering, or related field, with an emphasis on SoC design. This is a full-time internship with a duration of about 11-12 months. Job Responsibility: Working with our experienced design team to design state of the art SoC hardware specific segment applications like Automotive, IoT, voice/object recognition, security, smart connectivity and touch sensing . Assisting experienced engineers with End-to-end ownership of SoC Design, Verification and implementation (Physical Design). Design and verify digital and Mixed-signal IPs. Document designs and present results. Job Qualification: Master student in electronic/computer engineering Creative and positive mindset Good knowledge on CMOS technologies Great communication skills, interpersonal skills, teamwork skills and can-do attitude Desire for a ca...

IC Design Engineer at Broadcom

  Hello Dear Readers, Currently, at Broadcom vacancy for an IC Design Engineer role. Job Description: Candidate would be required to work on various phases of SOC physical design activities. The job will include but not limited to block level – floor-planning, partitioning, placement, clock tree synthesis, route, physical verification (LVS/DRC/ERC/Antenna etc). Should be able to meet congestion, timing and area metrics.  Candidate would be required to do equivalence checks, STA, Crosstalk delay analysis, noise analysis, power optimization. Should be able to implement timing and functional ECOs. Should have excellent problem-solving skill to help through congestion resolution and timing closure. Should have experience formal verification and timing analysis and ECO implementation. Experience with tools such as Innovus/Encounter, ICC, Caliber, LEC, Primetime etc is highly desirable. Candidate should be able to work independently and guide other team members. Should be ...