<?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: Driving the CLRC663 using K60-based MCU in NFC</title>
    <link>https://community.nxp.com/t5/NFC/Driving-the-CLRC663-using-K60-based-MCU/m-p/1895421#M11864</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/7386"&gt;@MWMinor&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;We will continue the communication in your internal ticket.&lt;/P&gt;
&lt;P&gt;Have a nice day!&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2024 21:21:57 GMT</pubDate>
    <dc:creator>EduardoZamora</dc:creator>
    <dc:date>2024-06-27T21:21:57Z</dc:date>
    <item>
      <title>Driving the CLRC663 using K60-based MCU</title>
      <link>https://community.nxp.com/t5/NFC/Driving-the-CLRC663-using-K60-based-MCU/m-p/1894435#M11855</link>
      <description>&lt;P&gt;I want to drive the CLRC663 with our custom K60-based board. The custom board is similar in architecture to the TWR-K60 board.&lt;/P&gt;&lt;P&gt;Using the application note NFC Reader Library Porting FRDM_K64F, I have successfully built a version of the basic discovery loop project, which compiles and downloads to the target.&lt;/P&gt;&lt;P&gt;When the program runs, I can see the SPI bus is communicating with the CLRC663, and the message "BasicDiscoveryLoop Example: " prints on the console. But the board doesn't respond to the EV3 card.&lt;/P&gt;&lt;P&gt;The program appears to be stuck in a loop within phOsal_NullOs.c...&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MWMinor_1-1719406945951.png" style="width: 556px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/285871i76388470C7504F25/image-dimensions/556x246?v=v2" width="556" height="246" role="button" title="MWMinor_1-1719406945951.png" alt="MWMinor_1-1719406945951.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;It seems the condition is never met to set Status = PH_OSAL_SUCCESS;&lt;/P&gt;&lt;P&gt;The main differences between the FRDM64F set-up and the custom boards is the use of SPI1 for the communication through PORTB. I have attached the header file I created to this post to hopefully assist.&lt;/P&gt;&lt;P&gt;Hope someone can help here....&lt;/P&gt;&lt;P&gt;MWM&lt;/P&gt;&lt;H1&gt;&amp;nbsp;&lt;/H1&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 13:08:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Driving-the-CLRC663-using-K60-based-MCU/m-p/1894435#M11855</guid>
      <dc:creator>MWMinor</dc:creator>
      <dc:date>2024-06-26T13:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: Driving the CLRC663 using K60-based MCU</title>
      <link>https://community.nxp.com/t5/NFC/Driving-the-CLRC663-using-K60-based-MCU/m-p/1895421#M11864</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/7386"&gt;@MWMinor&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;We will continue the communication in your internal ticket.&lt;/P&gt;
&lt;P&gt;Have a nice day!&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Eduardo.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 21:21:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/NFC/Driving-the-CLRC663-using-K60-based-MCU/m-p/1895421#M11864</guid>
      <dc:creator>EduardoZamora</dc:creator>
      <dc:date>2024-06-27T21:21:57Z</dc:date>
    </item>
  </channel>
</rss>

