<?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 Re: Full-duplex transfer using NXP Flex SPI in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1780308#M20631</link>
    <description>&lt;P&gt;I am discussing with the AE team, will provide more update later.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Dec 2023 06:33:50 GMT</pubDate>
    <dc:creator>yipingwang</dc:creator>
    <dc:date>2023-12-27T06:33:50Z</dc:date>
    <item>
      <title>Full-duplex transfer using NXP Flex SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1774043#M20472</link>
      <description>&lt;P class=""&gt;Hi, I've got two boards, LS1028 ardb and Hilsher netX 90.&lt;/P&gt;&lt;P class=""&gt;Both of them are connected through SPI using following lines:&lt;/P&gt;&lt;P class=""&gt;- SCK&lt;/P&gt;&lt;P class=""&gt;- CS&lt;/P&gt;&lt;P class=""&gt;- GND&lt;/P&gt;&lt;P class=""&gt;- MOSI&lt;/P&gt;&lt;P class=""&gt;- MISO&lt;/P&gt;&lt;P class=""&gt;I also have a logic analyzer connected to see what's going on on the bus.&lt;/P&gt;&lt;P class=""&gt;The SPI controller I use on the LS side is FlexSPI (spi-nxp-fspi) provides only implementation for SPI_MEM framework operations.&lt;/P&gt;&lt;P class=""&gt;I tried to perform some tests to check how it works:&lt;/P&gt;&lt;P class=""&gt;Here is the code of my driver&lt;/P&gt;&lt;P class=""&gt;&lt;A href="https://tutuappx.com/" target="_blank"&gt;https://tutuappx.com/&lt;/A&gt;&amp;nbsp;&lt;A href="https://vidmate.onl/" target="_self"&gt;Vidmate&lt;/A&gt;&lt;/P&gt;&lt;P class=""&gt;uint8_t buf[4];&lt;/P&gt;&lt;P class=""&gt;struct spi_mem_op op = SPI_MEM_OP(SPI_MEM_OP_CMD(0x80, 1),SPI_MEM_OP_ADDR(3, 0x000004, 1),SPI_MEM_OP_NO_DUMMY,SPI_MEM_OP_DATA_IN(4, buf, 1));&lt;/P&gt;&lt;P class=""&gt;ret = spi_mem_exec_op(spimem, &amp;amp;op);if (ret) {pr_info("Cannot execute op\n");}&lt;/P&gt;&lt;P class=""&gt;This is what I see on the logic analyzer:&lt;/P&gt;&lt;P class=""&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="r37x22fd526c1.jpg" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/254233i2D73E3D78CD509CD/image-size/large?v=v2&amp;amp;px=999" role="button" title="r37x22fd526c1.jpg" alt="r37x22fd526c1.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P class=""&gt;As you can see on the MOSI line I have what I expect in the format: opcode | addr&lt;/P&gt;&lt;P class=""&gt;The problem is that, once the Hilsher SPI is clocked it immediately sends 4 bytes on the MISO line where the first one is 0x11 (it is used to distinguish the device type).&lt;/P&gt;&lt;P class=""&gt;And due to that fact - once the transfer is finished, my buf consists of the following bytes:&lt;/P&gt;&lt;P class=""&gt;0x6e 0x65 0x74 0x58&lt;/P&gt;&lt;P class=""&gt;so the first 4 bytes were skipped &lt;LI-EMOJI id="lia_disappointed-face" title=":disappointed_face:"&gt;&lt;/LI-EMOJI&gt; But I need them especially this first byte (0x11).&lt;/P&gt;&lt;P class=""&gt;Any ideas about what goes wrong?&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 14:52:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1774043#M20472</guid>
      <dc:creator>pibew84514</dc:creator>
      <dc:date>2023-12-15T14:52:37Z</dc:date>
    </item>
    <item>
      <title>Re: Full-duplex transfer using NXP Flex SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1780308#M20631</link>
      <description>&lt;P&gt;I am discussing with the AE team, will provide more update later.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Dec 2023 06:33:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1780308#M20631</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2023-12-27T06:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: Full-duplex transfer using NXP Flex SPI</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1784865#M20738</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We have following questions:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Is this customer using LSDK or have their own software?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If they are using LSDK then please ask them to run following commands on U-Boot console: 'sf probe' and 'sf read &amp;lt;offset&amp;gt; &amp;lt;address&amp;gt; &amp;lt;count&amp;gt;' &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Please share the register dump of XSPI controller&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Provide the schematic with wiring diagram of xspi controller and SPI?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;What is the platform clock used?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Can you also share the logic analyser screen shot with data skip showing?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2024 05:04:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Full-duplex-transfer-using-NXP-Flex-SPI/m-p/1784865#M20738</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2024-01-09T05:04:40Z</dc:date>
    </item>
  </channel>
</rss>

