<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Simultaneous Ethernet Camera Streaming Solution in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2381988#M32582</link>
    <description>&lt;P&gt;We are developing a custom i.MX8MP-based board for an automotive camera system. We have a working single-camera H.264 RTP streaming pipeline using the VPU hardware decoder on our 5.15.71 NXP Yocto BSP. We are now planning to scale to 4 simultaneous camera streams via an Ethernet switch.&amp;nbsp; The switch will aggregate 4x 100BASE-T1 camera ports and connect to the i.MX8MP EQOS MAC via a gigabit RGMII uplink, with each camera isolated on its own VLAN.&lt;/P&gt;&lt;P&gt;Our display is 1280x800. For 4-stream simultaneous view each stream only needs to fill a quarter of the display (~640x400 or lower @30 fps), so we can scale camera resolution down as needed.&lt;BR /&gt;&lt;BR /&gt;1. Is there an NXP i.MX8MP reference design or application note covering multi-channel video decode that we can use as a starting point?&lt;BR /&gt;&lt;BR /&gt;2. Can the H.264 VPU decoder handle multiple independent instances from separate sources, or is a pre-decode composition step required to reduce the number of processes and context switches? If composition is required, what is the recommended approach on i.MX8MP?&lt;/P&gt;&lt;P&gt;3. What is the overall recommended software architecture for this use case from NXP's perspective?&lt;BR /&gt;&lt;BR /&gt;Our future application is surround view, so scalability and low latency are key requirements.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jun 2026 13:15:10 GMT</pubDate>
    <dc:creator>Wobaffet</dc:creator>
    <dc:date>2026-06-16T13:15:10Z</dc:date>
    <item>
      <title>Simultaneous Ethernet Camera Streaming Solution</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2381988#M32582</link>
      <description>&lt;P&gt;We are developing a custom i.MX8MP-based board for an automotive camera system. We have a working single-camera H.264 RTP streaming pipeline using the VPU hardware decoder on our 5.15.71 NXP Yocto BSP. We are now planning to scale to 4 simultaneous camera streams via an Ethernet switch.&amp;nbsp; The switch will aggregate 4x 100BASE-T1 camera ports and connect to the i.MX8MP EQOS MAC via a gigabit RGMII uplink, with each camera isolated on its own VLAN.&lt;/P&gt;&lt;P&gt;Our display is 1280x800. For 4-stream simultaneous view each stream only needs to fill a quarter of the display (~640x400 or lower @30 fps), so we can scale camera resolution down as needed.&lt;BR /&gt;&lt;BR /&gt;1. Is there an NXP i.MX8MP reference design or application note covering multi-channel video decode that we can use as a starting point?&lt;BR /&gt;&lt;BR /&gt;2. Can the H.264 VPU decoder handle multiple independent instances from separate sources, or is a pre-decode composition step required to reduce the number of processes and context switches? If composition is required, what is the recommended approach on i.MX8MP?&lt;/P&gt;&lt;P&gt;3. What is the overall recommended software architecture for this use case from NXP's perspective?&lt;BR /&gt;&lt;BR /&gt;Our future application is surround view, so scalability and low latency are key requirements.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jun 2026 13:15:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2381988#M32582</guid>
      <dc:creator>Wobaffet</dc:creator>
      <dc:date>2026-06-16T13:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Simultaneous Ethernet Camera Streaming Solution</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2384119#M32632</link>
      <description>&lt;P&gt;reminder&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 11:06:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2384119#M32632</guid>
      <dc:creator>Wobaffet</dc:creator>
      <dc:date>2026-06-22T11:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: Simultaneous Ethernet Camera Streaming Solution</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2384590#M32650</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/206842"&gt;@Wobaffet&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The i.MX8MP can serve as a candidate platform for this 4-channel Ethernet H.264 camera quad-view application; however, only the i.MX8QM and i.MX95 have reference designs for surround view.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The recommended architecture is for the four RTP/H.264 streams to enter separate GStreamer pipelines, be decoded individually by VPU hardware decoders, and then undergo hardware-assisted scaling and composition after decoding, with the output displayed on a 1280×800 display. It is not recommended to attempt composition before H.264 decoding, as separate H.264 streams cannot be directly composited into a single display frame in the compressed domain unless decoding and re-encoding have already been completed at the upstream switch or camera.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For a display requirement of 4 streams at approximately 640×400@30fps, a rough estimate based on pixel rate indicates that the load is significantly lower than that of 1080p60 decoding, so this approach is reasonable. However, whether this ultimately meets the low-latency and stability requirements for surround view will require system-level verification, taking into account actual camera bitrate, profile, GOP, RTP jitter, DDR bandwidth, the GStreamer zero-copy path, and the composition method.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Zhiming&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2026 01:46:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Simultaneous-Ethernet-Camera-Streaming-Solution/m-p/2384590#M32650</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2026-06-23T01:46:39Z</dc:date>
    </item>
  </channel>
</rss>

