Home/Glossary/IoT ASIC Solutions
Semiconductor knowledge

IoT ASIC Solutions

Custom chips for connected devices that combine some mixture of sensing, processing, security, power management and communication. The required integration depends on the device's purpose and network environment.

← All glossary termsTechnical guide · 5 min read
In this article

Custom chips for connected devices that combine some mixture of sensing, processing, security, power management and communication. The required integration depends on the device's purpose and network environment.

Connect the ASIC to its product
Conceptual system boundaries. Component evidence contributes to, but does not replace, complete product evaluation.

Design for the connected device

An IoT ASIC supports functions in a connected product, potentially combining sensing, control, processing, interfaces and security. The useful architecture depends on how often the device measures, computes and communicates. A sensor that transmits occasionally has different priorities from a continuously connected controller. Describe the operating cycle before selecting hardware. Include startup, sleep, communication retries and maintenance activity, because those states can influence energy and responsiveness more than the nominal active-mode performance of an individual processing block.

Energy and connectivity together

Local processing can reduce the amount of data transmitted, but it also consumes energy and may require additional memory. Evaluate the complete tradeoff under realistic traffic and signal conditions. Communication availability can vary, so define buffering, retry and data-loss behavior. The chip may connect an external radio rather than integrating one; that boundary affects power, interfaces and flexibility. Do not equate the broad IoT label with a particular wireless technology or assume that every protocol can be supported by the same fixed implementation.

Security through the lifecycle

Connected devices need a plan for identity, authenticated updates, access control and recovery. Manufacturing provisioning must be connected to the deployed security model. Decide how debug access changes between development, production and field service. If the device stores data while disconnected, consider how that data is protected and eventually synchronized. Hardware security blocks can support the architecture, but the surrounding firmware, cloud service and operating procedures remain important. A secure boot block alone does not establish the security of the complete connected product.

Support deployed units

Plan how software identifies hardware capabilities, reports errors and handles interrupted updates. Diagnostics should be sufficient to investigate common failures without exposing unnecessary access. Long-lived deployments may experience changes in connectivity services, software dependencies or user expectations. The architecture should preserve appropriate flexibility for those changes and identify what cannot be changed after fabrication. Compare an ASIC with available programmable solutions using the intended production volume, battery objective and lifecycle requirements rather than assuming custom integration is automatically the best option for every connected device.

Questions about IoT ASICs

Must an IoT ASIC contain a radio?

No. It can provide sensing, processing or control while using an external communications component. The integration boundary should follow the product's technical and lifecycle requirements.

Does low sleep current prove long battery life?

No. Active work, wake-up frequency, communication retries, leakage elsewhere in the system and battery behavior also matter. Evaluate the complete operating cycle under realistic conditions.

Derive chip requirements from system behavior

Begin with the product's intended tasks, users and environment. Describe the signals it receives, decisions it makes and outputs it produces. Include timing, energy and operating limits where they matter. Distinguish requirements that the chip can satisfy directly from those that depend on software, sensors, power supplies or other components. This prevents a good component specification from being mistaken for complete product performance. A useful system review identifies the boundaries and assigns an owner to each assumption that crosses them.

Allocate integration and flexibility

Choose which functions belong in fixed logic, software or external devices. Integration can reduce board complexity and communication overhead, but it also connects the functions' revision and manufacturing lifecycles. Preserve flexibility for plausible product changes without assuming that every requirement can remain open indefinitely. Consider configuration, firmware and interface compatibility alongside area and power. The architecture should explain why each function is integrated and what evidence supports the choice. A custom chip is most useful when it addresses a concrete product constraint rather than simply increasing the amount of circuitry on one die.

Exercise realistic operating cases

Test normal use, startup, interrupted power, invalid inputs and the relevant error or recovery sequences. Use representative workloads and environmental assumptions. Include software-visible behavior so the complete product can detect and respond to important conditions. Measurements should state the setup, configuration and product boundary. A chip-only benchmark can answer a narrow question, but it may not represent what a customer experiences. Preserve reproducible tests and distinguish measured results from estimates while the design and evaluation platform are still evolving.

Plan manufacturing and support

Include package, test access, diagnostics and expected production life in the development plan. Discuss traceability and change control according to the application's actual needs. If qualification or regulatory requirements apply to the finished product, coordinate them with the responsible product team; the presence of an ASIC does not establish compliance. Consider how firmware, supplier changes and field issues will be managed over time. A supportable design connects technical behavior with the information and responsibilities needed to manufacture, evaluate and maintain the product after the first successful demonstration.

A practical cross-discipline review

Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.

Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.

Explore the related Avnet offering or discuss your project requirements.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →