Leverage video for auto electronics design
By John A. Swanson Senior Manager Synopsys, MBD Group
EETimes (10/29/2012 3:20 PM EDT)
“Where is the V in AVB?” asked a thread in the Audio/Video Bridging (AVB) LinkedIn group. This caught my eye. While it is a popular and growing product in Synopsys' Ethernet portfolio, it’s critical to understand how customers choose to use it. AVB products using Ethernet are popping up in a range of applications, and the automotive market is one area of development.
Yes, the “V” is in there, too.
It is worth taking a step back to understand some of the market dynamics of networking AVB.
- First, what is the AVB “standard"?
- Is the lack of a defined standard something that consumers should care about?
- What are the financial impacts to AVB for providers of products using an IEEE 802.1 compliant network to distribute audio and video?
This article will expand on these points, and explain why AVB is gaining traction in many markets, and first may be your automobile.
To read the full article, click here
Related Semiconductor IP
- 1G BASE-T Ethernet Verification IP
- Simulation VIP for Ethernet UEC
- Verification IP for Ultra Ethernet (UEC)
- Ultra Ethernet Verification IP
- Ethernet Switch VLAN 5x100M
Related Articles
- QiMeng: Fully Automated Hardware and Software Design for Processor Chip
- FD-SOI: A Cyber-Resilient Substrate Against Laser Fault Injection—The Future Platform for Secure Automotive Electronics
- Revisiting the analogue video decoder: Brushing up on your comb filters
- How FPGAs are breathing new life into the analog video format
Latest Articles
- A 14ns-Latency 9Gb/s 0.44mm² 62pJ/b Short-Blocklength LDPC Decoder ASIC in 22FDX
- Pipeline Stage Resolved Timing Characterization of FPGA and ASIC Implementations of a RISC V Processor
- Lyra: A Hardware-Accelerated RISC-V Verification Framework with Generative Model-Based Processor Fuzzing
- Leveraging FPGAs for Homomorphic Matrix-Vector Multiplication in Oblivious Message Retrieval
- Extending and Accelerating Inner Product Masking with Fault Detection via Instruction Set Extension