Automotive IP

Automotive IP cores support a range of protocols critical to automotive applications, including CAN IP, CAN XL IP, CAN-FD IP, FlexRay IP, LIN IP, Safe Ethernet IP, and SafeSPI IP. CAN IP and CAN-FD IP facilitate reliable in-vehicle communication, while CAN XL IP extends bandwidth for high-performance data transfer. FlexRay IP is used for high-speed, fault-tolerant communication in safety-critical systems, and LIN IP supports cost-effective communication in simpler applications. Safe Ethernet IP and SafeSPI IP ensure secure and fault-tolerant data transmission, meeting stringent automotive safety standards.

Explore our vast directory of Automotive IP cores below.

All offers in Automotive IP
Filter
Filter

Login required.

Sign in

Login required.

Sign in

Login required.

Sign in

Compare 77 Automotive IP from 28 vendors (1 - 10)
  • IEEE 802.1AS Software Stack
    • The IEEE 802.1AS software stack implements the Timing and Synchronization protocol for time-sensitive applications over bridged and wireless networks.
    • Based on a profile of the Precision Time Protocol (PTP) as defined in IEEE 1588, 802.1AS provides precise synchronization of clocks across all network devices, enabling accurate time distribution for Time-Sensitive Networking (TSN) and other real-time applications.
    Block Diagram -- IEEE 802.1AS Software Stack
  • CAN 2.0/CAN FD IP core
    • The IP is compliant to the new ISO 11898-1:2015 standard, supporting both standard CAN and CAN FD. 
    • The IP is available for most Xilinx, Altera, Lattice and Microsemi FPGA devices, supporting native bus interfaces like AXI, Avalon and APB. Processor integration is available for SOC type of FPGAs.
    Block Diagram -- CAN 2.0/CAN FD IP core
  • UniPro℠ Controller IP Core
    • The UniPro Controller IP core is fully compliant with the UniPro specification version 1.6 and supports the physical adapter layer of the M-PHY® specification.
    • MIPI UniPro is a high-performance, chip-to-chip, serial interconnect bus for mobile applications. Designed to support up to 5Gbps per data lane, it is scalable from one to four bidirectional lanes.
    Block Diagram -- UniPro℠ Controller IP Core
  • Host / device LIN controller IP
    • The LIN Controllers IP– Local Interconnect Network Controllers IPs are compliant to LIN 2.0, 2.1 & 2.2A Specifications. Backward compliant to LIN 1.3 Specification as well.
    • These can be integrated into systems through various simple AMBA-APB, AMBA-AHB or SRAM like interfaces that require LIN connectivity commonly used in automotive and industrial applications.
    Block Diagram -- Host / device LIN controller IP
  • CAN-XL Bus Controller IP
    • The CAN-XL Bus Controller Core performs serial communication as per CAN 2.0, CAN-FD & CAN-XL Specifications.
    • It also supports original Bosch Protocol & ISO 11898 specifications for TTCAN (Time Triggered Operation) as specified in ISO11898-4.
    • The design is fully optimized to support AUTOSAR and SAE J1939 specifications.
    Block Diagram -- CAN-XL Bus Controller IP
  • CAN FD LIGHT BUS CONTROLLER IP
    • The Controller Area Network – Flexible Data-Light (CAN-FD Light) Controller IP implements the CAN FD-Light (CIA 604-1) protocol.
    • It can be integrated into devices that require CAN-FD-Light connectivity commonly used in sensors and actuators for the automotive and industrial applications.
    Block Diagram -- CAN FD LIGHT BUS CONTROLLER IP
  • CAN FD Bus Controller IP
    • The Controller Area Network – Flexible Data (CAN-FD) Controller IP implements the CAN 2.0A, CAN 2.0B as well as the high-performance CAN-FD (Flexible Data Rate) protocols.
    • It is compliant to both Non-ISO CAN-FD from BOSCH as well as ISO11898-1:2015 DIS. It can be integrated into devices that require CAN connectivity commonly used in automotive and industrial applications.
    Block Diagram -- CAN FD Bus Controller IP
  • CAN 2.0 Bus Controller IP
    • The CAN IP Controller Core performs serial communication as per CAN IP 2.0 Specifications. It supports full CAN IP 2.0 (both CAN IP 2.0A and 2.0B).
    • The design implements the BOSCH CAN IP Message Transfer Protocols 2.0A (which is equivalent to CAN IP 1.2 and covers standard message formats with 11-bit identifiers); and 2.0B which covers both standard and extended message formats (both 11-bit and 29-bit identifiers).
    Block Diagram -- CAN 2.0 Bus Controller IP
  • SENT/SAE J2716 Transmitter
    • The CSENT-TX core implements a transmitter for the Single Edge Nibble Transmission (SENT) protocol.
    • It complies with the SAE J2716 standard and supports both synchronous and asynchronous transmission modes.
    Block Diagram -- SENT/SAE J2716 Transmitter
  • SENT/SAE J2716 Receiver
    • The CSENT-RX core implements a receiver for the Single Edge Nibble Transmission (SENT) protocol.
    • It complies with the SAE J2716 standard and supports both synchronous and asynchronous sensors.
    • It can be used for receiving data from one or multiple sensors using a single SENT line.
    Block Diagram -- SENT/SAE J2716 Receiver
×
Semiconductor IP