<?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 S32K1 RTD function Lpspi_Ip_SyncTransmitHalfDuplex() clocks too many bytes in S32 SDK</title>
    <link>https://community.nxp.com/t5/S32-SDK/S32K1-RTD-function-Lpspi-Ip-SyncTransmitHalfDuplex-clocks-too/m-p/1450117#M2515</link>
    <description>&lt;P&gt;When using the SPI in half duplex mode, the following call sends two bytes, which is expected:&lt;/P&gt;&lt;P&gt;Lpspi_Ip_SyncTransmitHalfDuplex(&amp;amp;Lpspi_Ip_DeviceAttributes_SpiExternalDevice_0_BOARD_InitPeripherals, txBuffer, 2, LPSPI_IP_HALF_DUPLEX_TRANSMIT, timeOut);&lt;/P&gt;&lt;P&gt;When receiving, though, the function clocks multiple bytes. I tried specifying from 1 to 4 bytes and see the peripheral send enough clocks for 6 or 7 bytes:&lt;/P&gt;&lt;P&gt;Lpspi_Ip_SyncTransmitHalfDuplex(&amp;amp;Lpspi_Ip_DeviceAttributes_SpiExternalDevice_0_BOARD_InitPeripherals, rxBuffer, 1, LPSPI_IP_HALF_DUPLEX_RECEIVE, timeOut);&lt;/P&gt;&lt;P&gt;I see the same behavior whether I use interrupt driven SPI or polling.&lt;/P&gt;&lt;P&gt;How can I use the RTD calls to get the peripheral to receive a single byte with no extra clock pulses?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Apr 2022 20:11:35 GMT</pubDate>
    <dc:creator>hns80</dc:creator>
    <dc:date>2022-04-27T20:11:35Z</dc:date>
    <item>
      <title>S32K1 RTD function Lpspi_Ip_SyncTransmitHalfDuplex() clocks too many bytes</title>
      <link>https://community.nxp.com/t5/S32-SDK/S32K1-RTD-function-Lpspi-Ip-SyncTransmitHalfDuplex-clocks-too/m-p/1450117#M2515</link>
      <description>&lt;P&gt;When using the SPI in half duplex mode, the following call sends two bytes, which is expected:&lt;/P&gt;&lt;P&gt;Lpspi_Ip_SyncTransmitHalfDuplex(&amp;amp;Lpspi_Ip_DeviceAttributes_SpiExternalDevice_0_BOARD_InitPeripherals, txBuffer, 2, LPSPI_IP_HALF_DUPLEX_TRANSMIT, timeOut);&lt;/P&gt;&lt;P&gt;When receiving, though, the function clocks multiple bytes. I tried specifying from 1 to 4 bytes and see the peripheral send enough clocks for 6 or 7 bytes:&lt;/P&gt;&lt;P&gt;Lpspi_Ip_SyncTransmitHalfDuplex(&amp;amp;Lpspi_Ip_DeviceAttributes_SpiExternalDevice_0_BOARD_InitPeripherals, rxBuffer, 1, LPSPI_IP_HALF_DUPLEX_RECEIVE, timeOut);&lt;/P&gt;&lt;P&gt;I see the same behavior whether I use interrupt driven SPI or polling.&lt;/P&gt;&lt;P&gt;How can I use the RTD calls to get the peripheral to receive a single byte with no extra clock pulses?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Apr 2022 20:11:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/S32K1-RTD-function-Lpspi-Ip-SyncTransmitHalfDuplex-clocks-too/m-p/1450117#M2515</guid>
      <dc:creator>hns80</dc:creator>
      <dc:date>2022-04-27T20:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: S32K1 RTD function Lpspi_Ip_SyncTransmitHalfDuplex() clocks too many bytes</title>
      <link>https://community.nxp.com/t5/S32-SDK/S32K1-RTD-function-Lpspi-Ip-SyncTransmitHalfDuplex-clocks-too/m-p/1450318#M2516</link>
      <description>&lt;P&gt;Changing SpiCsContinuous to FALSE fixed the problem&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 02:18:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-SDK/S32K1-RTD-function-Lpspi-Ip-SyncTransmitHalfDuplex-clocks-too/m-p/1450318#M2516</guid>
      <dc:creator>hns80</dc:creator>
      <dc:date>2022-04-28T02:18:24Z</dc:date>
    </item>
  </channel>
</rss>

