<?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>Kinetis Software Development KitのトピックRe: Shift in SPI Rx Buffer MKL17Z256</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564197#M5757</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Samuel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not check the data sheet of the S25FL116K0XNF1011 FLASH memory. But from first look, as you know,&amp;nbsp; the SPI uses synchronized transfer for transmitter and receiver, in other words, after the SPI transmits the command 0x09, it receives the 0x00 at the same time(the received 0x00 is a dummy data), after the command 0x09 is received by flash, the SPI will receive the response sequence as 0x01, 0x40...from flash.&lt;/P&gt;&lt;P&gt;Hope it can help you.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;XiangJun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Jun 2016 00:21:58 GMT</pubDate>
    <dc:creator>xiangjun_rong</dc:creator>
    <dc:date>2016-06-24T00:21:58Z</dc:date>
    <item>
      <title>Shift in SPI Rx Buffer MKL17Z256</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564196#M5756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I use the SPI of the MKL17Z256VFT4 and I have a question about the received char, in fact I have a 1 byte shift in my received buffer.&lt;/P&gt;&lt;P&gt;The MCU communicate with a S25FL116K0XNF1011 FLASH memory. I simply send the JEDECID 0x9F command to read the manufacturer ID (0x01), the device type (0x40) and the capacity (0x15) according to the datasheet.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here the code who read these values :&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FLA_TxBuffer_U8A[0] = cFLA_JEDECID_U8;&lt;/P&gt;&lt;P&gt;GPIO_DRV_WritePinOutput(CS_SPI , 0);&lt;/P&gt;&lt;P&gt;SPI_DRV_MasterTransferBlocking(spiCom1_IDX, &amp;amp;spiCom1_MasterConfig0, FLA_TxBuffer_U8A, FLA_RxBuffer_U8A, 4, 100);&lt;/P&gt;&lt;P&gt; GPIO_DRV_WritePinOutput(CS_SPI , 1);&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see I have a Rx Buffer named FLA_RxBuffer_U8A which is an array of 6 bytes.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After these lines was executed, in the buffer I have this :&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="154194_154194.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/121853iE4605BBDB2B63C70/image-size/large?v=v2&amp;amp;px=999" role="button" title="154194_154194.png" alt="154194_154194.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/60014i510982C305740A2C/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the 3 correct values, but why these values don't begin at the value FLA_RxBuffer_U8A[0]&amp;nbsp; but at ....[1] ?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried with 3 instead of 4 for the 5th argument of the read function (transfertByteCount) but I d'ont received the 0x15 in this case.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2016 10:15:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564196#M5756</guid>
      <dc:creator>samc</dc:creator>
      <dc:date>2016-06-23T10:15:57Z</dc:date>
    </item>
    <item>
      <title>Re: Shift in SPI Rx Buffer MKL17Z256</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564197#M5757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Samuel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not check the data sheet of the S25FL116K0XNF1011 FLASH memory. But from first look, as you know,&amp;nbsp; the SPI uses synchronized transfer for transmitter and receiver, in other words, after the SPI transmits the command 0x09, it receives the 0x00 at the same time(the received 0x00 is a dummy data), after the command 0x09 is received by flash, the SPI will receive the response sequence as 0x01, 0x40...from flash.&lt;/P&gt;&lt;P&gt;Hope it can help you.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;XiangJun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2016 00:21:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564197#M5757</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2016-06-24T00:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Shift in SPI Rx Buffer MKL17Z256</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564198#M5758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK in fact that's a dummy byte read by the MCU when he send the commande byte 0x9F ? as there is a clock pulse during this command sending, the MISO read at the same time , it's right ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2016 06:48:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564198#M5758</guid>
      <dc:creator>samc</dc:creator>
      <dc:date>2016-06-24T06:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: Shift in SPI Rx Buffer MKL17Z256</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564199#M5759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;Yes, it is dumy byte, SPI uses the same clock to read and write.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;XiangJun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Jun 2016 14:18:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Shift-in-SPI-Rx-Buffer-MKL17Z256/m-p/564199#M5759</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2016-06-24T14:18:48Z</dc:date>
    </item>
  </channel>
</rss>

