<?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>S32 SDK中的主题 Re: Lpspi AsyncTransmit call takes long time</title>
    <link>https://community.nxp.com/t5/S32-SDK/Lpspi-AsyncTransmit-call-takes-long-time/m-p/1903793#M3889</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/233204"&gt;@sstelmak&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;There is a Quality package for the RTD driver that specify the execution time of the APIs in the profile report.&lt;/P&gt;
&lt;P&gt;Such overhead should be expected though. If the code is in cacheable memory, this can reduce the overhead slightly.&lt;/P&gt;
&lt;P&gt;Compiler optimization should be set exactly as per the RTD release note.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
    <pubDate>Tue, 09 Jul 2024 08:01:09 GMT</pubDate>
    <dc:creator>danielmartynek</dc:creator>
    <dc:date>2024-07-09T08:01:09Z</dc:date>
    <item>
      <title>Lpspi AsyncTransmit call takes long time</title>
      <link>https://community.nxp.com/t5/S32-SDK/Lpspi-AsyncTransmit-call-takes-long-time/m-p/1898664#M3887</link>
      <description>&lt;P&gt;I configured RTD 4.0.0 Lpspi to send stream of bytes and several CS by a single call Lpspi_Ip_AsyncTransmit, using DMA.&amp;nbsp; All SPI activities get performed by hw, however I noticed that Lpspi_Ip_AsyncTransmit call itself takes 36/41uS depending on DEV ERROR detection off or on.&lt;/P&gt;&lt;P&gt;I need to schedule SPI every 300uS. It means that this single call takes 12% of the entire throughput of the micro running at 160MHz. This looks very inefficient.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a possibility to optimize Lpspi performance?&lt;/P&gt;&lt;P&gt;Here is scope screenshot. Channel 3 shows a signal from DIO_SetPins/ClearPins that surround Lpspi_Ip_AsyncTransmit call.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sstelmak_2-1720032188660.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/286951i80DAFA45F39427E7/image-size/medium?v=v2&amp;amp;px=400" role="button" title="sstelmak_2-1720032188660.jpeg" alt="sstelmak_2-1720032188660.jpeg" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;sstelmak_2-1720032188660.jpeg&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2024 18:45:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/Lpspi-AsyncTransmit-call-takes-long-time/m-p/1898664#M3887</guid>
      <dc:creator>sstelmak</dc:creator>
      <dc:date>2024-07-03T18:45:29Z</dc:date>
    </item>
    <item>
      <title>Re: Lpspi AsyncTransmit call takes long time</title>
      <link>https://community.nxp.com/t5/S32-SDK/Lpspi-AsyncTransmit-call-takes-long-time/m-p/1903793#M3889</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/233204"&gt;@sstelmak&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;There is a Quality package for the RTD driver that specify the execution time of the APIs in the profile report.&lt;/P&gt;
&lt;P&gt;Such overhead should be expected though. If the code is in cacheable memory, this can reduce the overhead slightly.&lt;/P&gt;
&lt;P&gt;Compiler optimization should be set exactly as per the RTD release note.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jul 2024 08:01:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/Lpspi-AsyncTransmit-call-takes-long-time/m-p/1903793#M3889</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2024-07-09T08:01:09Z</dc:date>
    </item>
  </channel>
</rss>

