The DS90UB953/954 System Design & Operation video series offers training for FPD-Link III devices for ADAS. FPD-Link III devices such as the DS90UB953-Q1/ DS90UB954-Q1 support sensor use over serial link for Advanced Driver Assist Systems (ADAS) in the automotive industry. In this training series, we will guide you through step-by-step procedures to initialize and bring-up the “Sensor-Serializer-Deserializer-ISP” link to an optimal performance level.
This module discusses discrete implementation typically seen inside automotive body control module to monitor external switches. Common implementation methodology is reviewed in this section, and some of the challenges using discrete implementation is discussed in detail.
In this section, the MSDI concept is introduced and how the MSDI helps solve system challenges is discussed in details
This module discusses some of the advanced features offered by the MSDI, and how a system designer can take advantage of these features to improve their system performance.
This module discusses how the MSDI device can be used in an industrial data acquisition system in details.
This module concluds this traning session with highlights of the MSDI value propositions, as well as collaterals available to obtain more information about this MSDI device from Texas Instruments.
This introduction video will give the background on FPD-Link III devices, such as the DS90UB953-Q1/ DS90UB954-Q1; the device's role within Advanced Driver Assist Systems (ADAS) in the automotive industry; and explain their broad appeal to engineers of all experience levels. This is fundamental to diving deeper into a 953/954 system, as well as, the links within the system.
This section frames the design and operation video series by showing why it is important to contextualize customer problems in terms of the links between the devices.
Specifically, this section will discuss: issues with initializing the camera and issues with reading the incorrect serializer ID from the deserializer.
Understanding what hardware and software settings are important is critical to establishing a foundation for the 953/954 system. These settings can occur during or after power up and may need to be changed via software. As a result, these settings are routinely checked and verified before checking any of the other links in the system.
Specifically, this sections discusses: Diagnostics post power up, Mode and IDX Pins, Clocking Modes between the 953/954, Aliasing, I2C Pass Through, Port selection on 954, Analog Launch Pad (ALP), and Successful I2C Communication
This section analyzes the link between the 953 and 954 and establishes how to identify the health and operation of the link. Since the link between the 953-954 is the most fundamental link used to communicate between devices, it is often checked first.
Specifically, this section discusses: Back Channel configuration, Built in Self Test (BIST), Adaptive Equalization (AEQ), and Channel Monitor Loop (CMLOUT)
This section discusses what frame synchronization (FrameSync) is and how to configure in on the 953 and 954 and how CSI2 data is transferred across the link from the 954 to the ISP/SoC
Specifically, this section discusses: Frame Synchronization (FrameSync), Controlling 953 GPIOs locally and remotely via I2C, Unsynchronized and synchronized sensors, Internal and External Frame Sync, Port Forwarding, Accessing Indirect Registers, and Pattern Generation on 953 & 954
This section discusses how design a 953/954 using Power over Coax (PoC), and various hardware checks and concepts that need to be considered when analyzing a 953/954 system.
Specifically, this section discusses: Power Over Coax (PoC), AC Coupling Capacitors, PoC Inductors, Typical PoC Schematic, Critical Signal Routing, I2C Pullups, Loop Filter Capacitors on 953, Insertion Loss, Return Loss, and Time Domain Reflection (TDR) measurements.