Downloaded 14 times
Uploaded byCAST, Inc.
Automotive Interconnect Challenges
The document discusses the challenges and complexities in automotive interface controller cores, driven by advancements such as ADAS and connected vehicles. It highlights the increasing need for robust communication infrastructures, noting the transition to automotive Ethernet due to its higher bandwidth and flexibility, as well as the necessity for functional safety and interoperability among components. Additionally, it outlines various components, protocols, and security measures pertinent to automotive applications.
More Related Content
Similar to Automotive Interconnect Challenges
Automotive Interconnect Challenges
- 1. Automotive Interface ControllerCores 1 REUSE 2017 Meredith Lucky VP of Sales CAST, Inc. Automotive Interconnect Challenges
- 2. Automotive Interface ControllerCores 2 Factors Driving Auto Complexity Advanced Driver Assistance Systems (ADAS) Autonomous Automobiles In-Vehicle Info- tainment (IVI) and the “Connected Car” Electric Cars and energy efficiency How to address these needs and balance safety, performance, power, area and cost?
- 3. Automotive Interface ControllerCores 3 Communications in Vehicle Networks Today CAN 1Mbps • Engine • Audio • Radar • Navigation • Instruments • Climate FlexRay 10Mbps deterministic • Brakes • Advanced Driver Assistance Systems (ADAS) LIDAR • Distance MOST 150 Mbps • Speakers • Radio • Navigation • GPS LIN 19.2 kBaud • Wipers • Sensors • Mirror • Doors • Seats • Lights • Turn Signals • Window • Locks CAN used for Safety • Seatbelts • Airbags Ethernet 100 Mbps • Diagnostics • Backup Cameras
- 4. Automotive Interface ControllerCores 4 Communications in Vehicle Networks Today
- 5. Automotive Interface ControllerCores 5 Increasing Needs / New Challenges Supporting the new features is stressing the current connectivity infrastructure Outlook for 2019 exceeding 100K sensors and 500 processors Live video streaming from >= 10 cameras More mission critical communications: ISO 26262 and J3016 Cyber Attack Defenses Error Detection
- 6. Automotive Interface ControllerCores 6 Increasing Connectivity needs Soon hundreds of sensors and cameras in every car
- 7. Automotive Interface ControllerCores 7 Addressing additional requirements Hard to add functional safety to a design and almost impossible later on Good data that is delayed in an ASIL C/D level is as catastrophic as a data error Functional safety affects performance, power, area, and cost Interoperability from different vendors – every component needs to comply to the standard and be validated
- 8. Automotive Interface ControllerCores 8 The Single-Nibble Transmission Protocol: SENT Unidirectional, low-cost, interface for high- precision automotive sensors Low-cost: Uses only one wire for data transmission (and VDD and GND) and does not require special PHY on receiver or transmitter For high-precision sensors: Up to 24-data bits per message Standardized by SAE (SAE J2716) and used by several automotive sensor providers Lower cost & higher bit-rate alternative to LIN
- 9. Automotive Interface ControllerCores 9 The New Backbone: Automotive Ethernet Increased bandwidth: 100-1000x faster than CAN Low-cost, but higher cost per node than CAN Low-weight Flexible installation Simplifies design: a harness system is 50% of a car’s labor cost Flexibility for future expansion
- 10. Automotive Interface ControllerCores 10 Automotive Ethernet: IEEE802_1AS IP core TSN Time Sensitive Network – enables a predictable, deterministic, delivery time Goal is to provide a common time reference to all devices participating in the real-time network 802.1C*/Qc* - Reserve and use fault-tolerant paths for specific types of traffic. Enables time-aware application development
- 11. Automotive Interface ControllerCores 11 Automotive Ethernet as the New Backbone
- 12. Automotive Interface ControllerCores 12 Actual adaption of Automotive Ethernet: Hybrid System
- 13. Automotive Interface ControllerCores 13 Example of a Robust Low-Risk IP Core: CAST CAN2.0/CAN-FD CPU CAN-CTRL UART Other Peripherals (Timers, GPIO, SPI, etc) TALOS Dev. Board Debug Pod UART2USB CAN-FD PHY Daughter-Card NCV7340-4 CAN-FD PHY DB9DB9 CAN Bus CAN Bus Host PC Low-Level CAN Driver Sample Applica on IDE Terminal App. Survived three CIA Plug Fests In production use Avery VIP available Reference design board for easy eval.
- 14. Automotive Interface ControllerCores 14 IP Products 14 SECURITY & ENCRYPTION AES, Programmable, GCM, CCM, XTS; Key Expander DES Single, Triple Hash Functions SHA-3 (Keccak), SHA-256, SHA-1, MD5 COMPRESSION Lossless Data Compression GZIP/ZLIB/Deflate; Ref. Design GUNZIP/ZLIB/Inflate H.264/AVC Encoders: Low-Power through Ultra-Fast; Intra-Only H.264/AVC Decoders: Low-Latency, Low-Power JPEG & Motion JPEG: Encoders & Decoders: Baseline, Extended 16-bit, Ultra-Fast Video Over IP Subsystems & Ref. Designs H.265/HEVC Decoder Companion Cores Image Processing WDR/HDR CAMFE Camera Processor Network Stacks 40G & 1G/10G UDPIP Stacks RTP Stacsk for H.264 & JPEG MPEG Transport Stream Encapsulator PERIPHERALS AMBA Infrastructure Cores AHB matrix, multi-layer AXI, AHB/APB/AXI Bus-Bridges, DMAs, Peripherals & AHB Cache Controller Device Controllers: Smart Card Reader, TFT-LCD Display Parallel NOR Flash & Serial NOR Flash (QSPI-XIP) Legacy Peripherals: DMA Controllers, UARTs, Timer/Counter CONTROLLERS & PROCESSORS 32-bit BA2x Family Application Processors Full & Basic Embedded Processors Cache-Enabled Deeply Embedded PipelineZero Low-Power Dev & Debug Packages 8051 Compatibles: Super-Fast Advanced Fast & Mature; Tiny Legacy-Configurable 16-bit 80251s: Fast, Tiny INTERCONNECTS Automotive CAN2.0/CAN FD, VIP LIN, SENT, IEEE 802.1AS Avionics DO-254 MIL-STD 1553, ARINC 429, 825 SPI Octal, Quad; AHB, AXI; Master/Slave; Bridge I2C/SMBUS; PCI; Ethernet MAC UARTS; SDLC & HDLC Automotive Applications • Currently Used • Used in Future
- 15. Automotive Interface ControllerCores 15 Thank You. Learn more: www.cast-inc.com info@cast-inc.com +1 201.391.8300
Editor's Notes
- #3 Connected car – Audio, Visual, in-vehicle M2M, external communications Internal M2M uses cellular and wireless communications like wifi and bluetooth – leveraging on IoT
- #4 CAN <1Mbps so not good for sending messages >100 times/sec updates, good for mechanical sensor info where the amount of data is limited and low bandwidth LiDAR – Light Detection and Ranging (determine distance) MOST – Media Oriented Systems Transport – fiber, daisy-chained or dedicated ECU – Electronic Control Units for sensors and nodes
- #5 CAN <1Mbps so not good for sending messages >100 times/sec updates, good for mechanical sensor info where the amount of data is limited and low bandwidth LiDAR – Light Detection and Ranging (determine distance) MOST – Media Oriented Systems Transport – fiber, daisy-chained or dedicated ECU – Electronic Control Units for sensors and nodes
- #6 Summary of the presentation: With all the new connectivity and challenges in the Automotive industry with infotainment, ADAS, etc. - surprise: old standards like CAN, LIN and Ethernet are still the high-tech backbone. ADAS - Advanced Driver Assistance Systems ASIL Automotive Safety Integrity Levels) risk classes: ASIL A for assist (lowest) ASIL D for automation (highest) SAE International created the J3016 standard: level 0-lowest to fully self-driving level 5-highest Error Detection – hardware redundancy and ECC
- #7 More video channels – send over different networks fo infotainment, adas, engine control Video used in critical applications – low latency guarantee
- #8 Implementing the connectivity to address the increasing needs
- #10 Speed of Ethernet – 802.3bp – 1GB 100MB/s good for speed around vehicle for most info
- #11 TCP’s handshaking make delivery time long and unpredictable AVB Audio/Video Bridging IEEE 802.1 – standard replaced by TCN Enables time-aware application development Provides Alarm: Dedicated host-interrupt line is asserted at a specific absolute time. Can be used by when system needs to execute a task at a specific time
- #12 DCU – Data Communications Unit
- #13 Ethernet used as the new Backplane, but using existing proven subsystems as new standardization evolves in TSN, QoS, safety requirements Adoption includes test, validation, component interoperability testing , security (potential vulnerabilities identified)
- #14 Plug Fests- Real-world testing: diverse topologies, timing challenges, many vendors Proven with all popular transceivers Refrence design – Software Sample low-level drivers Sample embedded application Hardware Complete MCU with CAN Controller Interface Debug Pod for MCU Software Development PHY Daughter-Card using OnSemi’s NCV7340-4 or NCV7351