ASIC architecture
Interface partitioning, clock domains, memory hierarchy and power architecture defined before RTL.
Discuss thisLoading...
Some products outgrow standard parts: the interface is unusual, the volume makes custom silicon worthwhile, or the feature simply does not exist off the shelf. We design that logic — architecture, RTL, verification and physical implementation — and support you through tape-out.
Custom silicon is usually justified by one of three things: a feature no available part provides, a unit cost that only falls below a volume threshold, or a requirement such as size, power or interface timing that cannot be met by configuring an existing device.
It is also the most expensive commitment in electronics. We help you test the business case against alternatives first, and if custom is right, we design it so verification and physical implementation are planned from the start rather than retrofitted.
Custom silicon is compared against module, FPGA and configuration alternatives before you commit.
Interface, clocking, memory and power architecture decided up front, because these are expensive to change later.
Verification strategy, coverage and sign-off criteria agreed before implementation, not after.
Timing, power and area closure considered during design rather than discovered at the end.
Engagements range from an architecture study to a full flow through to tape-out and post-silicon bring-up.
Interface partitioning, clock domains, memory hierarchy and power architecture defined before RTL.
Discuss thisSynthesizable RTL written to a defined coding standard, with reusable and parameterised blocks.
Discuss thisSimulation, formal checks and coverage-driven verification with agreed sign-off criteria.
Discuss thisSynthesis, place and route, timing and power closure against the target process and constraints.
Discuss thisScan, test coverage and production test considerations built into the design from the start.
Discuss thisTape-out support, bring-up, debug and yield analysis once silicon returns.
Discuss thisScope is agreed in writing before work starts, so deliverables and responsibilities are clear.
The flow is planned as a whole, because the decisions that affect tape-out schedule are made at the start, not at the end.
Custom bus, protocol and mixed-signal interfaces where no standard controller fits.
Pipelines, filters, codecs, encryptors and data-path logic written as parameterised RTL.
Memory hierarchies, clock domain crossing and reset strategies planned up front.
Power domains, gating and clocking strategies considered from the architecture stage.
Coverage-driven verification, formal property checks and regression management.
Scan insertion, test coverage and production test planning built in from the start.
Synthesis, place and route with timing, power and area closure managed deliberately.
Bring-up, debug and yield analysis once first silicon is available.
Feasibility, architecture, implementation, verification, then physical design and tape-out.
Business case tested against alternatives and the design specification written and agreed.
Design specificationInterfaces, clocking, memory and power domains designed and reviewed before RTL begins.
Architecture specRTL implemented block by block against a verification plan with coverage tracking.
Verified RTLSynthesis, place and route, timing and power closure, then tape-out and bring-up.
Tape-out and siliconProcess and toolchain choices follow the target volume, performance and cost rather than familiarity.
Temperature, vibration, electrical transients and certification needs differ by sector, and they are captured during discovery rather than after the first build.
Equipment and connectivity for networks, access hardware and connected infrastructure.
Telecom & networkingControl panels, motor drives, gateways and automation hardware for continuous operation.
IndustrialIn-cabin electronics, LED drivers and control units designed around automotive electrical and thermal expectations.
AutomotiveMonitoring, metering, conversion and control electronics for energy and power systems.
Energy & powerDiagnostic and monitoring devices designed with patient safety and compliance in mind.
HealthcareRugged, secure and mission-critical systems with controlled supply and documentation.
DefenceThe scenarios below illustrate the kind of work we do — they are not published client case studies or measured results. Ask us about relevant experience for your product.
Challenge: A standard MCU could not meet the interface and cost targets at volume.
Approach: Architecture optimised for the exact interface, with power and area closed against the target process.
Explore electronics developmentChallenge: A flexible processor used far more power than the workload actually required.
Approach: Fixed-function logic designed for the specific data path, verified with coverage-based sign-off.
Explore electronics developmentChallenge: A controller was no longer available and could not be reordered.
Approach: Its function re-implemented as custom logic, verified against the original behaviour before tape-out.
Explore component sourcingWhat buyers usually want to know before scoping this kind of work.
Ask about your requirements →Typically when a required feature does not exist in an available part, when unit cost only falls below a threshold at your volume, or when size, power or interface timing cannot be met by configuring standard devices.
Yes. We compare custom against module, FPGA and configuration options and model the cost, so the decision is made on evidence rather than enthusiasm.
Feasibility and specification, architecture, RTL implementation, verification with coverage closure, physical design with timing and power closure, and tape-out and post-silicon support.
Architecture and the verification plan are agreed before implementation begins, design reviews happen at block level, and sign-off criteria are defined up front rather than negotiated at the end.
The process is selected against your expected volume, performance and cost targets, together with mask cost, NRE, tool availability and foundry yield record. We advise rather than default to one node.
Yes. We can review existing RTL for structure, coding standard compliance, verification quality and synthesizability, then continue the design or prioritise the changes needed.
Explore the rest of the programme, or get in touch about this service directly.
Tell us what the part needs to do, your expected volume and what is blocking the current solution. We will be direct if a module or FPGA makes more sense.
No complete specification needed. A short brief of your product and goals is enough to start.