<?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>S32Z/E中的主题 S32E2 IPCF latency timings between M33 and R52</title>
    <link>https://community.nxp.com/t5/S32Z-E/S32E2-IPCF-latency-timings-between-M33-and-R52/m-p/2413097#M410</link>
    <description>&lt;P&gt;I am working with S32E2 and configuring the IPCF framework and here is my setup&lt;/P&gt;&lt;DIV&gt;&lt;UL&gt;&lt;LI&gt;Device: S32E288&lt;/LI&gt;&lt;LI&gt;IPCF transport: Shared Memory + MRU notification&lt;/LI&gt;&lt;LI&gt;Communication: M33 ↔ R52&lt;/LI&gt;&lt;LI&gt;IPCF channel type: Managed channel&lt;/LI&gt;&lt;LI&gt;1 IPCF channel configured&lt;/LI&gt;&lt;LI&gt;Interrupt mode (not polling)&lt;/LI&gt;&lt;LI&gt;Ping/Pong RTT test implemented&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Communication is functioning correctly in both directions.&lt;/P&gt;&lt;P&gt;I use STM to measure the timing ticks between the 2 cores.&lt;/P&gt;&lt;P&gt;Measurement flow:&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;R52:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;timestamp&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;send PING&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;M33:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;receive PING&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;immediately send PONG from RX callback&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;R52:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;receive PONG&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;compute RTT&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The values computed for a STM running on 24Mhz are close to 200us RTT(Round trip time). My transport overhead is about 30us but the transfer itself takes up bulk of the time. I have tried various things like increasing MRU IRQ notification but has not improved the timings. Having optimisation in code from -o0 to -o1 helped but -o2 didnt make any difference. The payload itself is 16 bytes.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;1. what is expected IPCF latency for managed /unmanaged channels.&lt;/P&gt;&lt;P&gt;2. can we acheive a low double digit latency?&lt;/P&gt;&lt;P&gt;If you need any more details, please reply back.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 11 Sep 2026 14:01:04 GMT</pubDate>
    <dc:creator>PrabhanjanKopp</dc:creator>
    <dc:date>2026-09-11T14:01:04Z</dc:date>
    <item>
      <title>S32E2 IPCF latency timings between M33 and R52</title>
      <link>https://community.nxp.com/t5/S32Z-E/S32E2-IPCF-latency-timings-between-M33-and-R52/m-p/2413097#M410</link>
      <description>&lt;P&gt;I am working with S32E2 and configuring the IPCF framework and here is my setup&lt;/P&gt;&lt;DIV&gt;&lt;UL&gt;&lt;LI&gt;Device: S32E288&lt;/LI&gt;&lt;LI&gt;IPCF transport: Shared Memory + MRU notification&lt;/LI&gt;&lt;LI&gt;Communication: M33 ↔ R52&lt;/LI&gt;&lt;LI&gt;IPCF channel type: Managed channel&lt;/LI&gt;&lt;LI&gt;1 IPCF channel configured&lt;/LI&gt;&lt;LI&gt;Interrupt mode (not polling)&lt;/LI&gt;&lt;LI&gt;Ping/Pong RTT test implemented&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Communication is functioning correctly in both directions.&lt;/P&gt;&lt;P&gt;I use STM to measure the timing ticks between the 2 cores.&lt;/P&gt;&lt;P&gt;Measurement flow:&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;R52:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;timestamp&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;send PING&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;M33:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;receive PING&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;immediately send PONG from RX callback&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;R52:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;receive PONG&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;compute RTT&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The values computed for a STM running on 24Mhz are close to 200us RTT(Round trip time). My transport overhead is about 30us but the transfer itself takes up bulk of the time. I have tried various things like increasing MRU IRQ notification but has not improved the timings. Having optimisation in code from -o0 to -o1 helped but -o2 didnt make any difference. The payload itself is 16 bytes.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Questions:&lt;BR /&gt;1. what is expected IPCF latency for managed /unmanaged channels.&lt;/P&gt;&lt;P&gt;2. can we acheive a low double digit latency?&lt;/P&gt;&lt;P&gt;If you need any more details, please reply back.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 11 Sep 2026 14:01:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32Z-E/S32E2-IPCF-latency-timings-between-M33-and-R52/m-p/2413097#M410</guid>
      <dc:creator>PrabhanjanKopp</dc:creator>
      <dc:date>2026-09-11T14:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: S32E2 IPCF latency timings between M33 and R52</title>
      <link>https://community.nxp.com/t5/S32Z-E/S32E2-IPCF-latency-timings-between-M33-and-R52/m-p/2413280#M411</link>
      <description>&lt;P&gt;Hi,PrabhanjanKopp&lt;/P&gt;
&lt;P&gt;Thank you for contacting us.&lt;/P&gt;
&lt;P&gt;For your testing scenario, you can try to refer to GreenVIP. The Loop Time is about 20-30us.(S32ZE_GreenVIP_1.x.1/doc/UG_S32ZE_GreenVIP.pdf)&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Joey_z_0-1789354232929.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/396305iB585F26D7253BDB4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Joey_z_0-1789354232929.png" alt="Joey_z_0-1789354232929.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Joey_z_0-1789354232929.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Joey_z_1-1789354243644.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/396306iC75EA3F5EB2727A3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Joey_z_1-1789354243644.png" alt="Joey_z_1-1789354243644.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Joey_z_1-1789354243644.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;If you have other issue, you can contact us at any time.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Joey&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2026 02:57:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32Z-E/S32E2-IPCF-latency-timings-between-M33-and-R52/m-p/2413280#M411</guid>
      <dc:creator>Joey_z</dc:creator>
      <dc:date>2026-09-14T02:57:37Z</dc:date>
    </item>
  </channel>
</rss>

