silicode · 2026-09-20 · 11 min

Oman's Foundry Push and the Realities of Gulf Silicon

Analysing Gulf fab ambitions, MPW shuttle economics, mature-node PDK requirements, and what regional RTL teams actually need to tape out locally.

Semiconductor cleanroom wafer processing line with lithography equipment under yellow cleanroom lighting

Regional forecasts now project the GCC wafer fabrication market toward $142 billion by 2031. Oman hosted the Semiconductor Ecosystem Forum to map out local manufacturing partnerships, and Saudi Arabia continues pushing its national mandate to seat 50 fabless design houses by 2030. These initiatives show an appetite to move past simply buying clusters of foreign compute.

Building physical foundry capacity in the Gulf presents hard engineering and economic hurdles. For a silicon team running linting runs, managing clock domain crossings, and watching tape-out budgets, political declarations do not close timing. A fab is not just a cleanroom building with concrete footings. It is an operational web of qualified Process Design Kits (PDKs), multi-project wafer (MPW) shuttle schedules, standard cell libraries, test structures, and packaging facilities.

Looking past the strategic press releases shows what it actually takes to build a viable regional semiconductor supply chain from scratch.

The Node Question: Trailing Nodes Over Leading-Edge Fantasies

Public discourse around chips often focuses on 3nm gate-all-around (GAAFET) processes and extreme ultraviolet (EUV) lithography scanners. For the Gulf, trying to enter the leading-edge logic market is a non-starter. A sub-5nm greenfield fab costs upwards of $20 billion, burns through millions of gallons of ultra-pure water daily, and requires hundreds of specialised suppliers within driving distance for specialty gases, precursor chemicals, and ultra-flat quartz photomasks.

Oman's stated strategy of building from the ground up points toward trailing and mature nodes. That is the only pragmatic technical path.

Mature nodes (180nm, 130nm, 65nm, 40nm, and 28nm planar CMOS or BCD) run the real world. A modern automotive ECU, industrial controller, smart meter, or satellite telemetry board relies on these processes. Power management ICs (PMICs), motor drivers, galvanic isolators, and RF front-ends do not benefit from 3nm geometries. In fact, high-voltage BCD (Bipolar-CMOS-DMOS) processes at 180nm or 130nm handle breakdown voltages up to 40V, 80V, or higher, which thin gate oxides on advanced nodes cannot tolerate.

Consider the economics of a 200mm (8-inch) or 300mm (12-inch) mature-node line in the Sultanate or elsewhere in the GCC:

+-----------------------+-------------------+--------------------+-----------------------+
| Process Category      | Target Geometry   | Typical Wafer Size | Primary Applications  |
+-----------------------+-------------------+--------------------+-----------------------+
| High-Voltage BCD      | 180nm - 130nm     | 200mm (8-inch)     | PMICs, Motor Drivers  |
| Mixed-Signal / RF     | 65nm - 40nm       | 300mm (12-inch)    | Transceivers, Baseband|
| Embedded Digital / MCU| 40nm - 28nm       | 300mm (12-inch)    | Edge MCUs, DSPs, ASICs|
| High-Power Discrete   | Planar / Trench   | 150mm - 200mm      | SiC / GaN Switches    |
+-----------------------+-------------------+--------------------+-----------------------+

A 65nm RF or 180nm BCD line relies on deep ultraviolet (DUV) immersion or dry argon fluoride (ArF) / krypton fluoride (KrF) excimer laser steppers. These tools are widely available on the secondary market, have documented maintenance procedures, and are not bound by the tightest geopolitical export embargoes.

If Oman or its regional peers fund a 180nm/65nm foundry, they target industrial IoT, energy grid metering, aerospace motor control, and automotive interfaces. These components represent high-volume, defensible segments that industrial firms across the Middle East purchase in high volumes from overseas vendors every quarter.

The PDK and EDA Tooling Problem

You cannot just run wafers; you must enable designers to target the silicon. A foundry without a mature, silicon-proven PDK is a pile of idle steel.

When a team designs an ASIC, they write RTL in SystemVerilog or Verilog. They need to synthesize that code into a gate-level netlist, place and route it, run static timing analysis (STA), extract parasitics, and verify design rules (DRC) and layout-versus-schematic (LVS). Every step in this flow depends entirely on files provided by the fab:

  1. Standard Cell Libraries: Liberty format (.lib) files characterizing propagation delays, transition times, setup/hold constraints, and power across operating corners (e.g., Slow-Slow 0.9V 125C, Typical-Typical 1.0V 25C, Fast-Fast 1.1V -40C).
  2. Physical Abstracts: Library Exchange Format (LEF) files defining cell bounding boxes, pin locations, and metal routing blockages.
  3. DRC/LVS Runsets: Complex rule decks for signoff physical verification tools (Siemens Calibre, Synopsys IC Validator, or Cadence Pegasus).
  4. Compact SPICE Models: BSIM3, BSIM4, or BSIM-CMG parameters fitted to actual silicon wafer measurements for corner and Monte Carlo simulations.
  5. Memory Compilers: Automated generators for synchronous single-port and dual-port SRAM blocks, ROMs, and register files.

Developing this IP stack takes years. Established foundries like TSMC, GlobalFoundries, or UMC have thousands of engineers maintaining PDKs over revisions spanning a decade. When a designer instantiates an I/O pad cell with 4kV ESD protection, they expect that pad to work without blowing up on the test bench.

For a regional Gulf foundry, building PDKs from zero is a massive software and metrology task. If the fab cannot hand a clean, bug-free PDK to a design team, the RTL cannot be reliably turned into masks.

Open-source PDK initiatives (like SkyWater's 130nm or IHP's 130nm BiCMOS) proved that open PDKs lower barriers for small teams. If Gulf initiatives want adoption from regional startups, adopting open or easily accessible PDK standards will matter far more than signing enterprise memorandums of understanding.

Multi-Project Wafer (MPW) Logistics

ASIC startups in the GCC do not have $1.5 million to drop on a dedicated mask set for an initial prototype run. A full mask set for a 28nm chip can easily run over $800,000, while a 180nm mask set might run $60,000 to $120,000.

Instead, design teams rely on MPW shuttles. Intermediaries like Europractice, CMP, Muse Semiconductor, or foundry-direct shuttle programs pool dozens of designs onto a single reticle. A startup buys a 5mm x 5mm or 2.5mm x 2.5mm tile on the reticle, paying a fraction of the mask cost ($10,000 to $40,000 depending on the node and area) and receives 50 to 100 unpackaged dies for bench testing.

+-------------------------------------------------------------------------+
|                        Full Reticle Field (e.g., 26mm x 33mm)           |
| +-----------------------+ +-----------------------+ +-----------------+ |
| | Startup A: Edge MCU   | | Startup B: PMIC Array | | Company C: DSP  | |
| | (5mm x 5mm)           | | (5mm x 10mm)          | | (10mm x 10mm)   | |
| +-----------------------+ +-----------------------+ +-----------------+ |
| +-----------------------+ +-----------------------+ +-----------------+ |
| | University Test Chip  | | Silicode IP Block     | | Startup D: ADC  | |
| | (2.5mm x 2.5mm)       | | (2.5mm x 5mm)         | | (5mm x 5mm)     | |
| +-----------------------+ +-----------------------+ +-----------------+ |
+-------------------------------------------------------------------------+

If Oman or regional players want to nurture domestic ASIC houses, the fastest operational lever is subsidising regular, quarterly MPW shuttles.

Waiting nine months for an overseas foundry shuttle kills hardware iteration. If an engineer misses a single timing constraint, miscalculates an asynchronous clock domain crossing (CDC), or has an uncharacterised voltage drop in the power distribution network (PDN), the fabricated silicon comes back non-functional. Finding that bug on an oscilloscope and waiting another nine months for a respin kills the company.

Predictable, fast-turnaround shuttle runs (10 to 14 weeks from GDSII signoff to bare die) would give regional teams the cycle speed they need to iterate.

Backend Bottlenecks: Packaging, Testing, and OSAT

Fabricating a wafer is only half the battle. Bare silicon die must be sliced, mounted, wire-bonded or bumped, packaged, and tested.

Data from the Rest-of-GCC semiconductor packaging materials market shows a baseline growing from $73.9 million in 2024 to $111.2 million by 2029. Yet, practical Outsourced Semiconductor Assembly and Test (OSAT) capacity within the region remains limited. Most regional projects ship wafers to Taiwan, Malaysia, or mainland China for packaging.

Packaging is not simple mechanical assembly. It directly dictates the thermal and electrical characteristics of the silicon:

  • Bond wire inductance: In high-frequency designs (RF or high-speed SerDes), bond wires introduce 1nH to 2nH of parasitic inductance per millimetre. A bad bond profile ruins high-speed signal integrity.
  • Thermal resistance: Gulf operational environments often involve ambient field temperatures exceeding 45C to 50C in industrial, energy, and defense installations. If a chip runs at 10W, packaging with high junction-to-case thermal resistance (Theta-JC) causes the silicon to hit thermal shutdown thresholds immediately.
  • Package selection: Moving from standard leadframe packages (QFN, TSSOP) to flip-chip Ball Grid Arrays (BGA) or Chip-Scale Packages (CSP) requires advanced substrate manufacturing, underfill dispensing, and tight planar alignment.

A regional packaging and testing facility focused on standard QFN, LQFP, and ruggedized ceramic packages would yield higher near-term ROI than a multi-billion-dollar wafer fab. Testing silicon on wafer probers (automated test equipment, or ATE) and packaging dies locally removes major logistical friction for regional defense, aerospace, and energy hardware builders.

The Design Verification Reality: What Silicon Teams Must Handle

While industrial planners debate fab capex, the actual bottleneck for chip teams is design verification. Fabricating wrong silicon is an expensive mistake. You cannot push a hotfix to a metal layer once the reticles are etched.

For a small design team operating in Riyadh, Muscat, or Abu Dhabi, the team structure rarely permits dedicating ten verification engineers per RTL designer. Teams have to be lean, relying on rigorous automated front-end workflows before spending money on layout and fabrication.

+-------------------------------------------------------------------------+
|                       Front-End Verification Flow                       |
+-------------------------------------------------------------------------+
                                     |
                                     v
                     +-------------------------------+ 
                     | SystemVerilog RTL Source      |
                     +-------------------------------+ 
                                     |
                                     v
                     +-------------------------------+ 
                     | Linting & CDC Checking        |
                     | (Syntax, Style, Metastability)|
                     +-------------------------------+ 
                                     |
                                     v
                     +-------------------------------+ 
                     | Formal Property Verification  |
                     | (SVA, Assertion Proving)      |
                     +-------------------------------+ 
                                     |
                                     v
                     +-------------------------------+ 
                     | UVM Dynamic Simulation        |
                     | (Constrained-Random Tests)    |
                     +-------------------------------+ 
                                     |
                                     v
                     +-------------------------------+ 
                     | Logic Synthesis (Gate Netlist)|
                     +-------------------------------+ 
                                     |
                                     v
                     +-------------------------------+ 
                     | Static Timing Analysis (STA)  |
                     | (Zero Slack, Setup/Hold Sign) |
                     +-------------------------------+ 

A small team must automate these steps aggressively. Static verification must catch structural issues before synthesis:

  • Clock Domain Crossing (CDC): Ensuring synchronisers (two-flip-flop or FIFO-based) protect against metastability between asynchronous clock domains (e.g., an AXI bus clock running at 200MHz interfacing with an SPI master running at 25MHz).
  • Reset Domain Crossing (RDC): Guaranteeing that asynchronous reset assertions and synchronous deassertions do not cause glitching or metastable states across flip-flops.
  • Lint Rules: Enforcing clean code that avoids inferred latches, combinational feedback loops, and width mismatches during arithmetic assignment.

In our work on Silicode, we see firsthand that AI assistance in silicon design only works when it operates strictly within these verification constraints. Generating Verilog without automated linting, formal verification property checking (SystemVerilog Assertions), and synthesisable standard-cell mapping creates unusable code. An LLM that outputs a syntactically correct module with hidden timing paths or race conditions is useless to an engineer who has to sign off on static timing analysis.

Verification engineers care about one metric: functional coverage closure without manual testbench exhaustion. Regional teams need to adopt modern constrained-random UVM (Universal Verification Methodology) environments, integrated formal verification, and automated regression pipelines. That is how a four-person RTL team achieves the verification coverage of a thirty-person team.

The Economics: Capex vs. Return for Regional Governments

Regional policymakers must avoid the "fab vanity trap." Building a physical silicon foundry requires high recurring capital expenditure. Semiconductor equipment depreciates across a five-to-seven-year window. Stepper optics degrade, vacuum chambers need continuous preventative maintenance, and gas scrubbers run around the clock.

If a fab runs at less than 80% capacity utilization, the cost per processed wafer rises dramatically. A 200mm fab running 20,000 wafer starts per month (WSPM) requires a massive, steady influx of design tape-outs to stay solvent.

Where does that volume come from?

It cannot come from domestic startups alone. A dozen regional hardware startups running prototype MPW runs consume barely a few dozen wafers a year. To fill a fab, a domestic foundry must win commercial contracts from global fabless companies, automotive Tier-1 suppliers, and consumer electronics brands.

To win those contracts, the fab must compete on price per good die, yield predictability (Defect Density per cm² below 0.1), and ISO/IATF automotive quality certifications.

+-------------------------------------------------------------------------+
|                     Foundry Viability Dependencies                      |
+-------------------------------------------------------------------------+
                                     |
          +--------------------------+--------------------------+
          |                                                     |
          v                                                     v
+-----------------------------------+ +-----------------------------------+
| Domestic / Regional Ecosystem     | | Global Commercial Competitiveness |
+-----------------------------------+ +-----------------------------------+
| - Government/Defense Anchor Demand| | - Price per Good Die vs. Rivals   |
| - University R&D & Test Shuttles  | | - Silicon-Proven Quality & Yield  |
| - Subsidised MPW Programs         | | - IATF 16949 / ISO Certifications |
| - Localised Packaging & ATE       | | - Established Third-Party IP Base |
+-----------------------------------+ +-----------------------------------+

Until global tier-1 customers see proven yield data, domestic government anchor tenancy is essential. Defense, national energy infrastructure (Aramco, ADNOC, Petroleum Development Oman), and smart utility meters can guarantee baseline volume for mature-node chips (microcontrollers, telemetry radios, power switches). This anchor demand protects the fab during early low-yield phases while process engineers dial in etch profiles, ion implantation depths, and chemical-mechanical planarization (CMP) recipes.

What Hardware Engineers Should Watch

For engineering leads and RTL designers in the Gulf, the broad national silicon push will matter only when it translates into specific engineering resources.

Watch for concrete, verifiable infrastructure rather than high-level ecosystem announcements:

  1. PDK Releases and EDA Tool Support: Look for announcements of calibrated foundry PDKs integrated into standard EDA flows (Synopsys, Cadence, Siemens, or open-source flows like OpenROAD). Check if standard cell libraries are characterized for industrial and automotive temperature ranges (-40C to 125C).
  2. Subsidised MPW Shuttle Schedules: Watch whether national tech programs establish funded MPW shuttle runs with published submission deadlines. A fixed annual calendar with 3 to 4 shuttle slots is the single clearest signal of real ecosystem support.
  3. Regional OSAT Operations: Track packaging developments. Having a domestic or regional assembly house that handles QFN, BGA, and power packages with fast turnarounds will accelerate physical prototyping far more quickly than waiting for a local fab to break ground.
  4. IP Core Availability: Check if common digital and mixed-signal hard IP blocks (PLLs, bandgaps, high-speed ADCs, LDO regulators, I/O pad rings) are validated on the targeted local nodes.

Moving the Gulf from a consumer of high-end compute to a builder of silicon is a multi-decade project. It will not be won by headline wafer projections, but by the practical work of qualifying libraries, tuning stepper parameters, passing formal verification proofs, and closing timing on real silicon.

ASICSemiconductorsPDKEDAGulf Tech