ExpertQuestion 159 of 161Source: Ansys RedHawk User Manual: Reliability and EM Analysis (Temperature Setting for Power EM Calculation, Technology File); Synopsys ICC2 Implementation User Guide: Thermal Analysis Using Kelvin

Why must EM limits account for temperature?

From PDVerse PnR Interview Handbook · pdVerse Mentor Guide

Short Answer

Electromigration speeds up sharply with temperature, so the current a wire can carry for its lifetime drops as it gets hotter. An EM check run at a nominal temperature passes wires that fail in the hot parts of the die. Run thermal analysis first, then set the EM temperature to the hot-region value, or check hot regions separately.

Technical Reference DiagramWhy must EM limits account for temperature?
A table pairing temperature with the allowed current density for one metal layer, next to a binned thermal map of the die with hot bins flagged in red, showing that a strap passing at the nominal temperature fails in the hot region.

Technical Explanation

  • Black's equation links mean time to failure to current density and temperature through an exponential in activation energy over temperature, so a modest rise in temperature cuts lifetime a lot at the same current.
  • RedHawk sets EM temperature separately from extraction temperature. Priority runs from TEMPERATURES_EM (RH) per layer in the GSR, to TEMPERATURE_EM (RH) globally, to T_EM (RH) in the tech file, then the extraction temperatures, and finally TNOM_EM (RH). The log records what was used.
  • EM_TEMP_RATING (RH) in the tech file gives the ratio of maximum current density at another temperature to the limit at TNOM_EM (RH), which is how a foundry limit is derated.
  • RMS limits are tied to self-heating: RMS polynomial EM uses a temperature rise term set by DELTA_T_RMS_EM (RH).
  • The EM temperature keywords TEMPERATURES_EM (RH) and TEMPERATURE_EM (RH) are per layer or global, not per region. On a die with a 20 C spread you either use the hot-spot temperature everywhere, which is safe but pessimistic, or run the hot region again at its own temperature. The exception is a tile-based THERMAL_PROFILE (RH) from Sentinel thermal modeling, which maps tile temperatures onto wires and vias and derates only the average EM limits through EM_TEMP_RATING (RH).
  • Kelvin inside ICC2 gives the temperature map: analyze_thermal (ICC2) with thermal.tech_file (ICC2), which is mandatory, and report_thermal_qor -threshold (ICC2), threshold in Celsius, lists grids or instances above a temperature.
  • Temperature also raises metal resistance, so the same hot region sees more IR drop. Check thermal, IR and EM together rather than in isolation.

What To Check

  • Temperature used by the EM run, from the RedHawk log.
  • Hottest regions from thermal analysis and their temperature.
  • EM ratio of straps in hot regions at the hot temperature.
  • RMS results for high-activity nets, which depend on self-heating.

Command Checks & Actions

ICC2 (icc2_shell)set_app_options -name thermal.tech_file -value thermal.tech

Mandatory thermal tech file for Kelvin; it is not generated in memory.

ICC2 (icc2_shell)analyze_thermal

Runs thermal analysis and loads the thermal profile map.

ICC2 (icc2_shell)report_thermal_qor -threshold 105 -scenario func_ss

Lists regions above 105 C in the named scenario.

ICC2 (icc2_shell)analyze_rail -voltage_drop static -electromigration -nets {VDD VSS}

PG EM check in Fusion, run with voltage drop, once the EM temperature is set.

RedHawk (redhawk)perform emcheck -mode all -net VDD

Standalone EM check in all modes after setting the EM temperature keywords.

Healthy, Suspicious & Hard-stop Results

  • Healthy (illustrative): EM run at the 110 C hot-spot temperature with worst ratio 88%, confirmed by the log.
  • Suspicious (illustrative): EM run at a nominal 85 C while thermal analysis shows 110 C in the compute cluster.
  • Hard stop: Straps over 100% at the hot-region temperature, or no record of the EM temperature used.

Common Mistake

The Trap: Running EM at the junction temperature in the datasheet summary while the compute cluster runs 25 C hotter. Every strap passes, and the ones over the cluster carry current that is over the limit for their real temperature.

What The Interviewer Is Testing

  • Understanding that allowed current drops with temperature.
  • Knowledge of how RedHawk sets EM temperature.
  • Linking thermal analysis to EM and IR.

Follow-up Question & Model Response

"Why not always run EM at the hottest temperature on the die?"

Candidate Model Response: It is safe, and many teams do that for a first pass. On a die with a wide spread, though, it over-constrains the cool regions and can drive wider straps and more tracks where they are not needed. A second pass per hot region, or layer temperatures that match the thermal map, keeps the margin where the heat is without paying for it everywhere.

Practical Example

Tapeout Scenario: A strap carries 30 mA against a limit of 36 mA at the 85 C nominal EM temperature, an 83% ratio (illustrative). Kelvin shows the region at 110 C, and the tech file derating gives 0.7 times the limit at that temperature, 25 mA. The ratio becomes 120%. Adding a parallel strap splits the current to 16 mA, a 64% ratio at 110 C.

PnR Flow Mentor Guide

Read the complete 8-chapter PnR Flow Mentor Guide free on the web — library setup through placement, clock tree synthesis, routing, chip finishing, hierarchical implementation, and ECO, all the way to stream-out.

PnR Flow Physical Design Mentor Guide — eight chaptersPnR Flow Mentor GuideEight chapters, library setup through to stream-out. →