<?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 I3C using FRDM-MCXW71 board in Wireless MCU</title>
    <link>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2324723#M20297</link>
    <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;I'm wondering if it's possible to evaluate I3C using the FRDM-MCXW71 board.&amp;nbsp; Documentation for the board suggests that only I2C support is enabled, specifically for LPI2C1 peripheral.&amp;nbsp; Technically the MCU could be reconfigured to be I3C for those pins, (or alternatively the SPI could be reconfigured), but the traces on the board connect to the accelerometer and the MCU-Link, as well as the various IO Headers (Arduino etc).&lt;/P&gt;&lt;P&gt;What limitations would be encountered if I3C was configured on either of those ports? Would there be a preferred approach?&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Ross&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 28 Feb 2026 18:26:56 GMT</pubDate>
    <dc:creator>compcorp</dc:creator>
    <dc:date>2026-02-28T18:26:56Z</dc:date>
    <item>
      <title>I3C using FRDM-MCXW71 board</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2324723#M20297</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;I'm wondering if it's possible to evaluate I3C using the FRDM-MCXW71 board.&amp;nbsp; Documentation for the board suggests that only I2C support is enabled, specifically for LPI2C1 peripheral.&amp;nbsp; Technically the MCU could be reconfigured to be I3C for those pins, (or alternatively the SPI could be reconfigured), but the traces on the board connect to the accelerometer and the MCU-Link, as well as the various IO Headers (Arduino etc).&lt;/P&gt;&lt;P&gt;What limitations would be encountered if I3C was configured on either of those ports? Would there be a preferred approach?&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Ross&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Feb 2026 18:26:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2324723#M20297</guid>
      <dc:creator>compcorp</dc:creator>
      <dc:date>2026-02-28T18:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: I3C using FRDM-MCXW71 board</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2325748#M20299</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/260298"&gt;@compcorp&lt;/a&gt;, hope you are doing well.&lt;/P&gt;
&lt;P&gt;It is possible to use I3C with the FRDM-MCXW71, specifically on the J2 header in which pins 1 and 2 are routed to MCU pins which can be configured for I2C or I3C. For a reference example please refer to the SDK (v25.12.00 preferably) which includes board to board examples that may act as reference on how to configure the I3C module properly.&lt;/P&gt;
&lt;P&gt;Please let me know if these work for you.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2026 20:52:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2325748#M20299</guid>
      <dc:creator>RomanVR</dc:creator>
      <dc:date>2026-03-03T20:52:50Z</dc:date>
    </item>
    <item>
      <title>Re: I3C using FRDM-MCXW71 board</title>
      <link>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2329224#M20311</link>
      <description>&lt;P&gt;Thanks! I'll look into it.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2026 19:11:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Wireless-MCU/I3C-using-FRDM-MCXW71-board/m-p/2329224#M20311</guid>
      <dc:creator>compcorp</dc:creator>
      <dc:date>2026-03-09T19:11:47Z</dc:date>
    </item>
  </channel>
</rss>

