Picking the right MPSoC-based video architecture: Part 4
By Santanu Dutta, Jens Rennert, Tiehan Lv, Jiang Xu, Shengqi Yang, and Wayne Wolf
Embedded.com (08/18/09, 11:21:00 PM EDT)
To provide some perspective on what we discussed in Part 1, Part 2, and Part 3, in this last part in this series, we will consider the important topic of characterization of applications and architectures.
To this end, trace-driven simulation is widely used to evaluate computer architectures and are useful in MPSoC design. Because we know more about the application code to be executed on an application-specific MPSoC design, we can use execution traces to refine the design, starting with capturing fairly general characteristics of the application and moving toward a more detailed study of the application running on a refined architectural model.
Because video applications are computationally intensive, we expect that more than one platform SoC will be necessary to build video systems for quite some time. For some relatively simple applications, it is possible to build a single platform that can support a wide variety of software.
To read the full article, click here
Related Semiconductor IP
- Root of Trust (RoT)
- Fixed Point Doppler Channel IP core
- Multi-protocol wireless plaform integrating Bluetooth Dual Mode, IEEE 802.15.4 (for Thread, Zigbee and Matter)
- Polyphase Video Scaler
- Compact, low-power, 8bit ADC on GF 22nm FDX
Related White Papers
- Picking the right MPSoC-based video architecture: Part 1
- Picking the right MPSoC-based video architecture: Part 2
- Picking the right MPSoC-based video architecture: Part 3
- Processor Architecture for High Performance Video Decode
Latest White Papers
- Reimagining AI Infrastructure: The Power of Converged Back-end Networks
- 40G UCIe IP Advantages for AI Applications
- Recent progress in spin-orbit torque magnetic random-access memory
- What is JESD204C? A quick glance at the standard
- Open-Source Design of Heterogeneous SoCs for AI Acceleration: the PULP Platform Experience