MSTSingapore
All

MPW buyer question

90nm, 55nm or 40nm MPW for embedded AI control chips

Compare the first screening questions for embedded AI control, sensor-interface and mixed-signal prototype chips before an MPW RFQ.

RFQ non-confidential firstHuman confirmed route

Direct answer

When should an embedded AI control chip use 90nm, 55nm or 40nm MPW?

An embedded AI control chip should not start with node alone. Buyers should first describe control-loop function, voltage, analog front end, embedded memory, RF/high-speed needs, die-size range, package/test assumptions and schedule pressure. MST can help screen whether a 90nm, 55nm or 40nm mature-node route is reviewable before confidential design exchange.

  • 90nm requests may be driven by power, voltage, embedded eFlash or mature analog/control assumptions.
  • 55nm requests may involve SiGe BiCMOS, BCD, logic/eFlash, RF, mixed-signal or sensor-interface context.
  • 40nm requests often need logic/eFlash fit, PDK/NDA readiness, package/test scope and partner acceptance review.

What to prepare

  1. Control-chip role: motor control, battery/power supervision, sensor fusion, actuator interface, RF companion, safety monitor or edge-control logic.
  2. Voltage domains, analog/RF blocks, embedded memory, digital logic density and package/test expectations.
  3. Estimated die size and expected number of prototype samples.
  4. Schedule target, procurement route, PDK/NDA status and non-confidential end-use description.

Public boundary

  1. Node examples are screening anchors, not a published process menu or availability promise.
  2. PDK access, shuttle acceptance, quotation and schedule are confirmed case by case.
  3. MST does not accept controlled design files through the public MPW topic page.

Internal route

Route this requirement into an executable path

Use this page as the technical answer, then move into the right MST entry point for screening, RFQ or scenario routing.

MPW hub

Review mature-node MPW positioning, buyer questions, node screening and readiness paths.

MPW RFQ intake

Submit a non-confidential MPW brief for MST review before any sensitive design exchange.

AI hardware prototype path

Route robotics, AI device, drone or emerging hardware needs across SKU, MPW, design and sourcing.

Next step

Turn this into a reviewable MPW RFQ

Share a short non-confidential brief first. MST screens node, process, PDK/NDA, package/test, schedule, country and end-use before any sensitive design-file path.

MPW hub →
MPW pricing factors

MPW pricing factors without public price promises

What drives MPW pricing before a formal quote?

PDK/NDA access path

PDK/NDA access path for MPW screening

How should buyers discuss PDK/NDA access before MPW?

package/test scope

MPW package/test scope before RFQ

What package/test details matter before an MPW RFQ?