<?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>MPC5xxx中的主题 could MPC5746C slave DSPI2 correct clock/bit skew error on next comming CS period</title>
    <link>https://community.nxp.com/t5/MPC5xxx/could-MPC5746C-slave-DSPI2-correct-clock-bit-skew-error-on-next/m-p/834035#M12257</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, NXP guys&lt;/P&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/khumphri"&gt;khumphri&lt;/A&gt;‌&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Mandar"&gt;Mandar&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/dhaval"&gt;dhaval&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RHinnen"&gt;RHinnen&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/jimtrudeau"&gt;jimtrudeau&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Martin"&gt;Martin&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/vladcentea"&gt;vladcentea&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/marc.paquette"&gt;marc.paquette&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RChapman"&gt;RChapman&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Alban"&gt;Alban&lt;/A&gt;&lt;/P&gt;&lt;P&gt;on our board design, the MPC5746C play as a SPI slave (DSPI2), and the SPI master is IMX6.d.&lt;/P&gt;&lt;P&gt;I am wondering if a clock/bit skew error occured in one CS period on the SPI bus (which may caused by electronic jamming&amp;nbsp;or Master start sending data before Slave ready ), will this error still exist in the next CS period ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand the Rx / Tx datas on the MPC5746C(slave) side will goes wrong&amp;nbsp;if clock/bit skew&lt;SPAN&gt;&amp;nbsp;occured in current CS period,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;but can the MPC5746C Rx / Tx correct datas on the next comming CS (CS deasserted and then asserted) without&amp;nbsp; Application software doing anything ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if yes, could you please explain how it works ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if not, could you please teach me how to fix this issue ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thanks and best regards.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/76484i04D50AC66CB82649/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Oct 2018 09:29:06 GMT</pubDate>
    <dc:creator>wesleyxie</dc:creator>
    <dc:date>2018-10-25T09:29:06Z</dc:date>
    <item>
      <title>could MPC5746C slave DSPI2 correct clock/bit skew error on next comming CS period</title>
      <link>https://community.nxp.com/t5/MPC5xxx/could-MPC5746C-slave-DSPI2-correct-clock-bit-skew-error-on-next/m-p/834035#M12257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, NXP guys&lt;/P&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/khumphri"&gt;khumphri&lt;/A&gt;‌&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Mandar"&gt;Mandar&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/dhaval"&gt;dhaval&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RHinnen"&gt;RHinnen&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/jimtrudeau"&gt;jimtrudeau&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Martin"&gt;Martin&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/vladcentea"&gt;vladcentea&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/marc.paquette"&gt;marc.paquette&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/RChapman"&gt;RChapman&lt;/A&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/Alban"&gt;Alban&lt;/A&gt;&lt;/P&gt;&lt;P&gt;on our board design, the MPC5746C play as a SPI slave (DSPI2), and the SPI master is IMX6.d.&lt;/P&gt;&lt;P&gt;I am wondering if a clock/bit skew error occured in one CS period on the SPI bus (which may caused by electronic jamming&amp;nbsp;or Master start sending data before Slave ready ), will this error still exist in the next CS period ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand the Rx / Tx datas on the MPC5746C(slave) side will goes wrong&amp;nbsp;if clock/bit skew&lt;SPAN&gt;&amp;nbsp;occured in current CS period,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;but can the MPC5746C Rx / Tx correct datas on the next comming CS (CS deasserted and then asserted) without&amp;nbsp; Application software doing anything ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if yes, could you please explain how it works ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;if not, could you please teach me how to fix this issue ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;thanks and best regards.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/76484i04D50AC66CB82649/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Oct 2018 09:29:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/could-MPC5746C-slave-DSPI2-correct-clock-bit-skew-error-on-next/m-p/834035#M12257</guid>
      <dc:creator>wesleyxie</dc:creator>
      <dc:date>2018-10-25T09:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: could MPC5746C slave DSPI2 correct clock/bit skew error on next comming CS period</title>
      <link>https://community.nxp.com/t5/MPC5xxx/could-MPC5746C-slave-DSPI2-correct-clock-bit-skew-error-on-next/m-p/834036#M12258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, any comments ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2018 16:22:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/could-MPC5746C-slave-DSPI2-correct-clock-bit-skew-error-on-next/m-p/834036#M12258</guid>
      <dc:creator>wesleyxie</dc:creator>
      <dc:date>2018-11-02T16:22:01Z</dc:date>
    </item>
  </channel>
</rss>

