<?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: FLEXBUS_Init trouble? in MCUXpresso SDK</title>
    <link>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730095#M457</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jing,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have the Flexbus driver been updated?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Biafra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Jul 2018 08:54:46 GMT</pubDate>
    <dc:creator>biafra</dc:creator>
    <dc:date>2018-07-30T08:54:46Z</dc:date>
    <item>
      <title>FLEXBUS_Init trouble?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730093#M455</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using a custom board based on K66FN2M0VMD18 chip with MCUXpresso 10.0.2 (build 411) and an SDK created with online tools.&lt;/P&gt;&lt;P&gt;It seems that there an issue on using two different chip select pins on external flexbus.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on the example provided with the SDK, i think that the initialization procedure should be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;//chip select 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;FLEXBUS_GetDefaultConfig(&amp;amp;flexbusUserConfig);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;//do some modification on the dafault config for CS1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;/* Initialize and configure FLEXBUS module */&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt; FLEXBUS_Init(FB, &amp;amp;flexbusUserConfig); //initialize CS1&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding: 0px;"&gt;&lt;/P&gt;&lt;P style="padding: 0px;"&gt;&lt;SPAN&gt;And then:&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding: 0px;"&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;//chip select&amp;nbsp;2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;FLEXBUS_GetDefaultConfig(&amp;amp;flexbusUserConfig);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;//do some modification on the dafault config for CS2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;/* Initialize and configure FLEXBUS module */&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;FLEXBUS_Init(FB, &amp;amp;flexbusUserConfig); //initialize CS2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At this point the configuration of CS1 is wiped out because of&amp;nbsp;&lt;SPAN&gt;FLEXBUS_Init() function.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier, monospace;"&gt;for (chip = 0; chip &amp;lt; FB_CSAR_COUNT; chip++)&lt;BR /&gt; {&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;/* Reset CSMR register, all chips not valid (disabled) */&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;base-&amp;gt;CS[chip].CSMR = 0x0000U;&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;/* Set default base address */&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;base-&amp;gt;CS[chip].CSAR &amp;amp;= (~FB_CSAR_BA_MASK);&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;/* Reset FB_CSCRx register */&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;base-&amp;gt;CS[chip].CSCR = 0x0000U;&lt;BR /&gt; }&lt;BR /&gt;...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When the&amp;nbsp;FLEXBUS_Init() function is called for the second time, it deletes the settings of CS1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Which is the correct way to initialize two different chip select pins?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Biafra&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Oct 2017 10:55:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730093#M455</guid>
      <dc:creator>biafra</dc:creator>
      <dc:date>2017-10-30T10:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: FLEXBUS_Init trouble?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730094#M456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Francesco,&lt;/P&gt;&lt;P&gt;Yes, you are right. FLEXBUS_Init() can only be used one time. Otherwise it will clear the work before.In fact, the MCUXpresso SDK V2.2.0 software Flexbus driver doesn't provide full features of the Flexbus module.&lt;BR /&gt;Customer can add related secondary wait states setting function in application code.&lt;BR /&gt;Sorry for that may bring any inconvenience to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jing&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 09:11:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730094#M456</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2017-10-31T09:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: FLEXBUS_Init trouble?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730095#M457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jing,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have the Flexbus driver been updated?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Biafra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2018 08:54:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730095#M457</guid>
      <dc:creator>biafra</dc:creator>
      <dc:date>2018-07-30T08:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: FLEXBUS_Init trouble?</title>
      <link>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730096#M458</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Biafra,&lt;/P&gt;&lt;P&gt;No, it hasn't. You can see the driver version at the top of each .h file. It looks like&lt;/P&gt;&lt;P&gt;#define FSL_FLEXBUS_DRIVER_VERSION (MAKE_VERSION(2, 0, 1)) /*!&amp;lt; Version 2.0.1. */&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jing&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Aug 2018 07:00:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-SDK/FLEXBUS-Init-trouble/m-p/730096#M458</guid>
      <dc:creator>jingpan</dc:creator>
      <dc:date>2018-08-02T07:00:14Z</dc:date>
    </item>
  </channel>
</rss>

