Skip to content
Avecas

AMS VERIFICATION

AMS verification

Check interactions between continuous-time circuits and digital control.

Discuss your requirements
Oscilloscope and multimeter measuring an electronic circuit

Representative photograph · Oscilloscope and multimeter measuring an electronic circuit.

THE ENGINEERING SCOPE

Built around
your requirements.

Explore the approach ↓
01

Technical starting point

Analog models, digital interfaces, operating modes and mixed-signal requirements.

02

Acceptance evidence

Model assumptions, threshold behaviour, sequencing and analog settling.

03

Delivery package

Testbench, models within scope, scenarios and verification reports.

CLIENT GUIDE

Scope ams verification with the right evidence.

Use these technical checkpoints to make the first project review productive.

Provide before the review

  • Analog models
  • Digital interfaces
  • Operating modes and mixed-signal requirements

Review during execution

  • Model assumptions
  • Threshold behaviour
  • Sequencing and analog settling

Agree for delivery

  • Testbench
  • Models within scope
  • Scenarios and verification reports

HOW WE WORK

Clarity at each stage.

01

Plan mixed-signal scenarios

The initial review establishes the baseline using analog models, digital interfaces, operating modes and mixed-signal requirements. Record gaps and dependencies before implementation.

02

Select model fidelity

Carry out the agreed work against the reviewed baseline. For ams verification, keep the interfaces and configuration used by this stage visible to the receiving team.

03

Integrate simulation

Retain the intermediate artifacts and review model assumptions, threshold behaviour, sequencing and analog settling. Investigate failures before using these results as an input to the next stage.

04

Debug cross-domain interactions

Package testbench, models within scope, scenarios and verification reports. Review unresolved findings against the agreed acceptance criteria and assign ownership for follow-up.

PROJECT DECISIONS

Know what moves the work forward.

Use these gates to agree readiness, review evidence and responsibility at each stage.

  1. 01

    Baseline ready

    Are the starting inputs complete enough to proceed?

    Review method and evidence

    Analog models, digital interfaces, operating modes and mixed-signal requirements.

    Review evidence

    Record input revisions, missing material and who can resolve each dependency.

  2. 02

    Implementation reviewed

    Has the work addressed the agreed technical objective?

    Review method and evidence

    Check interactions between continuous-time circuits and digital control.

    Review evidence

    Keep the intermediate artifacts with review comments and the decisions that changed the design.

  3. 03

    Evidence checked

    Can the result be reproduced and interpreted?

    Review method and evidence

    Model assumptions, threshold behaviour, sequencing and analog settling.

    Review evidence

    Capture the configuration, expected result, observed result and unresolved findings.

  4. 04

    Handoff accepted

    Can the receiving team use the delivery package?

    Review method and evidence

    Testbench, models within scope, scenarios and verification reports.

    Review evidence

    Review build or execution instructions, known limitations and ownership of follow-up actions.

INPUTS & OUTPUTS

What the work involves.

The final statement of work defines the scope and acceptance criteria.

Client inputs
Analog models, digital interfaces, operating modes and mixed-signal requirements.
Engineering sequence
Plan mixed-signal scenarios; select model fidelity; integrate simulation; debug cross-domain interactions.
Outputs to agree
Testbench, models within scope, scenarios and verification reports.

TECHNICAL DECISIONS

Planning AMS verification.

Read the technical guide

The engineering objective

Check interactions between continuous-time circuits and digital control.

The work starts from analog models, digital interfaces, operating modes and mixed-signal requirements. The team should identify the authoritative revision of each input and record any assumptions needed to proceed. This prevents a later result from being interpreted against a different specification or configuration.

What needs technical attention

A behavioural model should state which effects it omits so results are interpreted correctly.

The review centres on model assumptions, threshold behaviour, sequencing and analog settling. Each finding should identify the input revision, observed behaviour and supporting evidence. Distinguish a confirmed defect from a configuration issue, an unsupported case or an open engineering question before deciding how to resolve it.

How the work is reviewed

The practical sequence is: plan mixed-signal scenarios; select model fidelity; integrate simulation; debug cross-domain interactions. Intermediate reviews allow the client to resolve decisions while changes are still manageable. If an input changes, identify the affected activities and repeat the checks that depend on it.

The expected package comprises testbench, models within scope, scenarios and verification reports. Acceptance criteria should specify what the receiving team needs to reproduce, inspect or integrate these artifacts. Include known limitations and outstanding actions in that package, rather than assuming that delivery of a file implies acceptance.

Preserve electrical intent through models and layout

Analog results depend on operating conditions and modelling assumptions. Establish supply ranges, loading, bias conditions, temperature and the selected process models before comparing simulations. Identify which requirements concern nominal performance and which concern variation, startup, noise or stability. The intended use of each result should be clear: an exploratory sweep and a release check have different evidence requirements.

Layout choices can change the circuit through parasitics, coupling and device environment. Review matching intent, sensitive nodes, return paths, guard structures and routing symmetry with the circuit owner. A geometrically tidy layout is not necessarily an electrically suitable layout. Device placement and extraction results should be discussed together, especially when an observed shift is close to an acceptance limit.

When a model and a measurement disagree, first check units, configuration, instrument setup and the model’s range of validity. Use controlled sweeps to separate possible causes. Record solver settings, convergence concerns and any simplified boundary conditions. Circuit verification, layout verification and physical characterisation should retain their own acceptance criteria rather than allowing one successful check to stand in for all three.

An illustrative review scenario

A reference circuit may meet a nominal output target yet settle too slowly after a supply ramp. Review the ramp profile, load and initial conditions, then compare startup behaviour across the intended operating envelope. If extraction changes the result, identify the sensitive parasitic contribution before changing devices. This is a planning example and does not imply qualification of a specific technology.

BEFORE WE BEGIN

Project questions.

A clear conversation is the start of a strong engineering relationship.

What inputs are needed for ams verification?

The starting review needs analog models, digital interfaces, operating modes and mixed-signal requirements. Share the current revision and known limitations so the scope reflects the actual design state.

What does the ams verification handoff include?

The statement of work can define testbench, models within scope, scenarios and verification reports. The final package should include review results and any open actions.

Which technical risks need particular attention?

A behavioural model should state which effects it omits so results are interpreted correctly.

Can we start with a focused technical review?

The first work package can be a review of the available inputs and the engineering questions that must be resolved. Agree its boundaries, access requirements and expected findings before committing to a larger implementation. A review should leave an actionable list of decisions, dependencies and next steps.

How are changes and unresolved findings handled?

Tie each finding to the relevant revision and supporting evidence. A change should identify the affected interfaces, activities and checks. Confirm its effect on scope and delivery with the responsible owner. At handoff, distinguish closed findings, accepted limitations and open work so that a file transfer is not mistaken for technical acceptance.

PUT THE WORKFLOW IN CONTEXT

Explore the engineering decisions.

Practical reading to help prepare your project discussion. Studies are illustrative; they do not report client results.

Reviewing custom IP before subsystem integration ↗

YOUR NEXT CHAPTER STARTS HERE

What will you
build next?

Bring us your engineering challenge.
Let’s define the path from idea to implementation.

Start a conversation