Access Official Technical PDF

Share Summary:LinkedInEmail

An INICnet interface controller can take on much of the low-level work involved in connecting an automotive device to a shared network. Microchip’s OS81212/4/6 family is designed for 50 Mbit/s INICnet-based systems, combining a balanced media physical layer (bPHY), an embedded software stack and interfaces for streaming data, control messages and packets. For engineers designing infotainment nodes, the key consideration is how those integrated functions fit the responsibilities of the local controller and the requirements of each endpoint.

The devices are intended for automotive applications such as instrument clusters, amplifiers, microphones, acoustic processing units, headrest speakers and rear-seat entertainment. Their network physical layer is transformer-less and designed for unshielded twisted-pair copper wiring. The family supports network designs based on point-to-point, simplex daisy-chain and ring topologies.

What the INIC integrates into a network node

The Intelligent Network Interface Controller (INIC) handles low-level functions needed to make a device operate as a compliant network node. Its embedded INIC Software Stack provides real-time network behavior and manages protocols associated with activities such as startup, shutdown, error reporting and Plug-and-Play node positioning. This can reduce the amount of real-time network processing assigned to an External Host Controller (EHC).

That division of work matters when an application processor or microcontroller needs to focus on its own device-level tasks. The INIC can manage network-facing functions while the EHC handles mid- and high-level application responsibilities. When a host is present, communication with the INIC uses a message-based interface rather than a register-based interface. A unified network management software stack, UNICENS, is available for the EHC to build a system-level solution.

The INIC also supervises the application. It can enter a protection mode when the application is absent, such as during startup, or when the EHC malfunctions. This mode is intended to prevent application faults from affecting network and system integrity. Embedded management functions also include hardware and application watchdog timers, diagnostics, intelligent muting and an emergency response system (eCall).

Choosing an OS81212/4/6 interface controller

The three variants share the core role of connecting a node to a 50 Mbit/s automotive network, but their available interfaces address different endpoint needs. Selecting a variant therefore starts with the data types the node must handle, how it will be controlled and whether it has a local host.

  • OS81212: Intended for audio and video streaming applications, it includes dual streaming ports and a MediaLB interface. It can operate with an EHC or as a remote network node.
  • OS81214: Intended for audio applications, it supports a streaming port and packet exchange over SPI. It can also operate with a local EHC or remotely on the network.
  • OS81216: Intended for remotely configured microphone applications without a local EHC.

The family’s streaming port supports synchronous, fixed-latency data exchange for serial audio formats including time-division multiplexing (TDM) and pulse density modulation (PDM). The I2C control port supports inter-chip message exchange. SPI provides asynchronous and control packet support on the OS81212 and OS81214, while MediaLB is available on the OS81212 to support inter-chip communication and streaming. GPIO pins provide additional general-purpose control options.

Connecting streaming, control and packet traffic

A network node may need to carry data with different timing and handling requirements. Synchronous audio streams, for example, use the streaming interfaces, while asynchronous application packets can carry information such as graphics, system data or software downloads. The network also provides an Ethernet channel for packet data. Keeping these traffic types in view helps system designers map interfaces at each endpoint to the role that endpoint plays in the larger architecture.

In a system combining a head unit and remote nodes, the head unit’s host can manage the network and control devices elsewhere in the vehicle. Remote amplifiers can receive configuration and control while sourcing or receiving synchronous audio through interfaces such as I2S connected to codecs or DSPs. Microphones can be configured remotely over I2C; the OS81216 is designed for this type of remotely configured microphone use without a local EHC. Other nodes, including instrument panels and rear-seat entertainment units, can use network packet channels as well as synchronous streams, depending on their interfaces and system design.

Remote operation is also supported through I2C master message tunneling and GPIO port control. These functions allow control and configuration without a local External Host Controller, a relevant consideration when defining the electronics and software responsibilities of distributed nodes.

Design considerations beyond the data path

Integration does not remove the need to account for device-level hardware requirements. The controllers use 3.3 V and 1.8 V operating supplies and are offered in 56-pin or 48-pin QFN packages, depending on the variant. The exposed paddle is the primary ground connection and must be connected to ground on the printed circuit board for proper operation. Designers should also consult the applicable device documentation for pin-specific requirements, including pull-up or pull-down resistors and signals that must be left unconnected.

For system planning, it is useful to define the node’s role before selecting the controller: identify whether it handles audio, video, control or packet traffic; determine which local interfaces are needed; and decide whether an EHC will be present. Those decisions clarify whether MediaLB, SPI, streaming ports or remote I2C configuration are relevant to the design.

Practical implications for network design

The OS81212/4/6 family places network protocols, supervision and multiple data interfaces in a dedicated automotive network controller. That architecture can separate low-level network operation from application processing, while giving system designers options for streaming-oriented, packet-capable and remotely managed nodes. The practical task is to match each variant’s interfaces and operating model to the endpoint’s function, host arrangement and traffic requirements. Careful planning of those boundaries helps keep node responsibilities clear across an INICnet-based vehicle network.

Access Official Technical PDF

About The Author