<?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>MCUXpresso SDKのトピックDetermining the appropriate peripheral driver for a device</title>
    <link>https://community.nxp.com/t5/MCUXpresso-SDK/Determining-the-appropriate-peripheral-driver-for-a-device/m-p/1503512#M3855</link>
    <description>&lt;P&gt;In the MCUX SDK (&lt;A href="https://github.com/NXPmicro/mcux-sdk)" target="_blank"&gt;https://github.com/NXPmicro/mcux-sdk)&lt;/A&gt;&amp;nbsp;there are many variants of a driver for a particular peripheral. For example, consider a SPI peripheral for which there are many drivers:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/spi/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/flexcomm/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/lpc_minispi/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/ecspi/fsl_ecspi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/lpspi/fsl_lpspi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;etc. In addition, in many cases there are derivatives of these drivers for DMA use.&lt;/P&gt;&lt;P&gt;I understand the implementations are for different silicon implementations of the peripherals. For example, a SPI peripheral in i.MX RT1176 can be a different architecture/silicon design from the SPI peripheral in an LPC55S69, and therefore require a different driver implementation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the correct way to identify the "right" driver for a given device?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The best I have found so far is to reference the appropriate&amp;nbsp;&lt;FONT face="courier new,courier"&gt;mcux-sdk/devices/&amp;lt;device&amp;gt;/all_lib_device_&amp;lt;device&amp;gt;.cmake&lt;/FONT&gt; and look at the included &lt;FONT face="courier new,courier"&gt;drivers/*&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is this the recommended and most official way, or is there something else?&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 09 Aug 2022 20:24:39 GMT</pubDate>
    <dc:creator>socalsparky</dc:creator>
    <dc:date>2022-08-09T20:24:39Z</dc:date>
    <item>
      <title>Determining the appropriate peripheral driver for a device</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/Determining-the-appropriate-peripheral-driver-for-a-device/m-p/1503512#M3855</link>
      <description>&lt;P&gt;In the MCUX SDK (&lt;A href="https://github.com/NXPmicro/mcux-sdk)" target="_blank"&gt;https://github.com/NXPmicro/mcux-sdk)&lt;/A&gt;&amp;nbsp;there are many variants of a driver for a particular peripheral. For example, consider a SPI peripheral for which there are many drivers:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/spi/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/flexcomm/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/lpc_minispi/fsl_spi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/ecspi/fsl_ecspi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;mcux-sdk/drivers/lpspi/fsl_lpspi.c&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;etc. In addition, in many cases there are derivatives of these drivers for DMA use.&lt;/P&gt;&lt;P&gt;I understand the implementations are for different silicon implementations of the peripherals. For example, a SPI peripheral in i.MX RT1176 can be a different architecture/silicon design from the SPI peripheral in an LPC55S69, and therefore require a different driver implementation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the correct way to identify the "right" driver for a given device?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The best I have found so far is to reference the appropriate&amp;nbsp;&lt;FONT face="courier new,courier"&gt;mcux-sdk/devices/&amp;lt;device&amp;gt;/all_lib_device_&amp;lt;device&amp;gt;.cmake&lt;/FONT&gt; and look at the included &lt;FONT face="courier new,courier"&gt;drivers/*&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Is this the recommended and most official way, or is there something else?&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2022 20:24:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/Determining-the-appropriate-peripheral-driver-for-a-device/m-p/1503512#M3855</guid>
      <dc:creator>socalsparky</dc:creator>
      <dc:date>2022-08-09T20:24:39Z</dc:date>
    </item>
    <item>
      <title>Re: Determining the appropriate peripheral driver for a device</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/Determining-the-appropriate-peripheral-driver-for-a-device/m-p/1504099#M3859</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/104304"&gt;@socalsparky&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;We currently have the "MCUXpresso SDK Builder", where you can select any development board available, and build an SDK with all the middleware needed for you application:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://mcuxpresso.nxp.com/en/select" target="_blank"&gt;Select Board | MCUXpresso SDK Builder (nxp.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I hope you find this helpful!&lt;/P&gt;
&lt;P&gt;Best regards, Julian&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2022 15:15:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/Determining-the-appropriate-peripheral-driver-for-a-device/m-p/1504099#M3859</guid>
      <dc:creator>Julián_AragónM</dc:creator>
      <dc:date>2022-08-10T15:15:04Z</dc:date>
    </item>
  </channel>
</rss>

