<?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>Other NXP ProductsのトピックSPI's CPHA description in NXP's Block Guide</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/SPI-s-CPHA-description-in-NXP-s-Block-Guide/m-p/1658703#M17907</link>
    <description>&lt;P&gt;I'm a little confused about the CPHA description on the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;SPI Block Guide V04.01&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;from Motorola/NXP. The description is the following:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;"If the CPHA bit in SPI Control Register 1 is clear, odd numbered edges on the SCK input cause the data at the serial data input pin to be latched. Even numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register&amp;nbsp;&lt;A href="https://www.mythdhr.biz/" target="_self"&gt;&lt;SPAN&gt;&lt;FONT color="#333333"&gt;mythdhr&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/A&gt;, depending on the LSBFE bit. If the CPHA bit is set, even numbered edges on the SCK input cause the data at the serial data input pin to be latched. Odd numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register, depending on the LSBFE bit."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;My confusion is about&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;why using different clock edges (I mean rising vs. falling or vice-versa) to latch the serial data input and shift it into the shift register. What does motivate this behavior?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Doesn't it make a configurable master device much more complicated? Doesn't it make STA more complicated as well? I did some sketches here and it seems to be possible to use the same clock edge to latch the serial input data and to shift it into the shift register without any penalty...&lt;/P&gt;</description>
    <pubDate>Sat, 27 May 2023 09:45:10 GMT</pubDate>
    <dc:creator>Sophie5387</dc:creator>
    <dc:date>2023-05-27T09:45:10Z</dc:date>
    <item>
      <title>SPI's CPHA description in NXP's Block Guide</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SPI-s-CPHA-description-in-NXP-s-Block-Guide/m-p/1658703#M17907</link>
      <description>&lt;P&gt;I'm a little confused about the CPHA description on the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;SPI Block Guide V04.01&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;from Motorola/NXP. The description is the following:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;"If the CPHA bit in SPI Control Register 1 is clear, odd numbered edges on the SCK input cause the data at the serial data input pin to be latched. Even numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register&amp;nbsp;&lt;A href="https://www.mythdhr.biz/" target="_self"&gt;&lt;SPAN&gt;&lt;FONT color="#333333"&gt;mythdhr&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/A&gt;, depending on the LSBFE bit. If the CPHA bit is set, even numbered edges on the SCK input cause the data at the serial data input pin to be latched. Odd numbered edges cause the value previously latched from the serial data input pin to shift into the LSB or MSB of the SPI shift register, depending on the LSBFE bit."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;My confusion is about&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;why using different clock edges (I mean rising vs. falling or vice-versa) to latch the serial data input and shift it into the shift register. What does motivate this behavior?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Doesn't it make a configurable master device much more complicated? Doesn't it make STA more complicated as well? I did some sketches here and it seems to be possible to use the same clock edge to latch the serial input data and to shift it into the shift register without any penalty...&lt;/P&gt;</description>
      <pubDate>Sat, 27 May 2023 09:45:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SPI-s-CPHA-description-in-NXP-s-Block-Guide/m-p/1658703#M17907</guid>
      <dc:creator>Sophie5387</dc:creator>
      <dc:date>2023-05-27T09:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: SPI's CPHA description in NXP's Block Guide</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/SPI-s-CPHA-description-in-NXP-s-Block-Guide/m-p/1663693#M18010</link>
      <description>&lt;P class="lia-align-justify"&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/217957"&gt;@Sophie5387&lt;/a&gt;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;First of all, could you please tell us which microcontroller are you using or referring to?&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;We recommend you use the SPI as mentions in the&amp;nbsp;&lt;A href="https://www.nxp.com/files-static/microcontrollers/doc/ref_manual/S12SPIV4.pdf" target="_self"&gt;SPI Block Guide V4&lt;/A&gt;. The usage of latching and then shifting the data in different clock edges could be to prevent delay skews, and other possible errors in the data transmission.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Best regards, Raul.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 21:00:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/SPI-s-CPHA-description-in-NXP-s-Block-Guide/m-p/1663693#M18010</guid>
      <dc:creator>RaRo</dc:creator>
      <dc:date>2023-06-05T21:00:42Z</dc:date>
    </item>
  </channel>
</rss>

