<?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: LPSPI Peripheral Chip Select in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-Peripheral-Chip-Select/m-p/1695524#M26114</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/219346"&gt;@Angel487&lt;/a&gt;&amp;nbsp;，&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; I checked the LPSPI IP module, from the register, just can select one PCS pin:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kerryzhou_0-1690782247227.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/234282i05D1815AAFE841CB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kerryzhou_0-1690782247227.png" alt="kerryzhou_0-1690782247227.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;TCR register:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kerryzhou_1-1690782256522.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/234283i47C25FBC713AFD9E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kerryzhou_1-1690782256522.png" alt="kerryzhou_1-1690782256522.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;If you want more than one pin as the SPI_CS function.&lt;/P&gt;
&lt;P&gt;Just the LPSPI IP hardware, no register to select it.&lt;/P&gt;
&lt;P&gt;So, maybe still need to use the GPIO method.&lt;/P&gt;
&lt;P&gt;You mentioned:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;I also tried to drive the pins as normal GPIOs, but this results in an out of timing behavior of CS.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;What's the detail situation? Which timing behavior is out?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Can you share some wave about it?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you think the normal GPIO speed is slow, you can use the fast GPIO:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cnblogs.com/henjay724/p/15518705.html" target="_blank"&gt;https://www.cnblogs.com/henjay724/p/15518705.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If just the CS area is not correct, it is related to your GPIO CS code insert area, you need to go to the fsl_lpspi to add it.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With it helps you!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Kerry&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 05:49:26 GMT</pubDate>
    <dc:creator>kerryzhou</dc:creator>
    <dc:date>2023-07-31T05:49:26Z</dc:date>
    <item>
      <title>LPSPI Peripheral Chip Select</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-Peripheral-Chip-Select/m-p/1695037#M26098</link>
      <description>&lt;P&gt;Hello NXP Community&lt;/P&gt;&lt;P&gt;On my project I need to drive a decoder/demultiplexer with SPI "chip select" pins (Pcs0, Pcs1, Pcs2).&lt;/P&gt;&lt;P&gt;This pins must be all active high (done) and I also need to drive more than one pin high or low.&lt;/P&gt;&lt;P&gt;This last requirement doesn't seem to be provided by the "fsl_lpspi" NXP driver.&lt;/P&gt;&lt;P&gt;I also tried to drive the pins as normal GPIOs, but this results in an out of timing behavior of CS.&lt;/P&gt;&lt;P&gt;Can you please help me?!&lt;/P&gt;&lt;P&gt;Thanks in Advance!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Angelo&lt;/P&gt;&lt;P&gt;P.S. we are using this logic with de decoder since we have more than 4 chips on the SPI bus (see the attached schematics)&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2023 12:56:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-Peripheral-Chip-Select/m-p/1695037#M26098</guid>
      <dc:creator>Angel487</dc:creator>
      <dc:date>2023-07-28T12:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: LPSPI Peripheral Chip Select</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-Peripheral-Chip-Select/m-p/1695524#M26114</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/219346"&gt;@Angel487&lt;/a&gt;&amp;nbsp;，&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; I checked the LPSPI IP module, from the register, just can select one PCS pin:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kerryzhou_0-1690782247227.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/234282i05D1815AAFE841CB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kerryzhou_0-1690782247227.png" alt="kerryzhou_0-1690782247227.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;TCR register:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="kerryzhou_1-1690782256522.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/234283i47C25FBC713AFD9E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="kerryzhou_1-1690782256522.png" alt="kerryzhou_1-1690782256522.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;If you want more than one pin as the SPI_CS function.&lt;/P&gt;
&lt;P&gt;Just the LPSPI IP hardware, no register to select it.&lt;/P&gt;
&lt;P&gt;So, maybe still need to use the GPIO method.&lt;/P&gt;
&lt;P&gt;You mentioned:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;I also tried to drive the pins as normal GPIOs, but this results in an out of timing behavior of CS.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;What's the detail situation? Which timing behavior is out?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Can you share some wave about it?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you think the normal GPIO speed is slow, you can use the fast GPIO:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cnblogs.com/henjay724/p/15518705.html" target="_blank"&gt;https://www.cnblogs.com/henjay724/p/15518705.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If just the CS area is not correct, it is related to your GPIO CS code insert area, you need to go to the fsl_lpspi to add it.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With it helps you!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Kerry&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 05:49:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/LPSPI-Peripheral-Chip-Select/m-p/1695524#M26114</guid>
      <dc:creator>kerryzhou</dc:creator>
      <dc:date>2023-07-31T05:49:26Z</dc:date>
    </item>
  </channel>
</rss>

