<?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: FPU Type options for MCUXpresso for double-precision floating point in i.MX RT Crossover MCUs</title>
    <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1870929#M30545</link>
    <description>&lt;P&gt;I know this is an older post but I found this looking for a similar problem, can a single precision FPU do any double precision math at a reduced rate? Or I need to get a double precision FPU to utilize FPU hardware for doubles&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/1431"&gt;@mjbcswitzerland&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 22 May 2024 16:12:47 GMT</pubDate>
    <dc:creator>223specialist</dc:creator>
    <dc:date>2024-05-22T16:12:47Z</dc:date>
    <item>
      <title>FPU Type options for MCUXpresso for double-precision floating point</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231085#M12673</link>
      <description>&lt;P&gt;How do I choose a double precision hardware FPU in the MCUXpresso project settings?&lt;/P&gt;&lt;P&gt;The FPU type selectors are confusing and does not seem to match with ARM documentation.&lt;/P&gt;&lt;P&gt;I need hardware double-precision floating point.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Hat_0-1613406140375.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/137193iFCD64D9711A8EBB4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Hat_0-1613406140375.png" alt="Hat_0-1613406140375.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;On Arm's documentation, the option for double precision is given as &lt;SPAN&gt;FPv5-DP-D16-M, and the MCUXpresso does not let me choose that.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Hat_1-1613406341316.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/137195iAF4219A832010D4A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Hat_1-1613406341316.png" alt="Hat_1-1613406341316.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 16:28:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231085#M12673</guid>
      <dc:creator>Hat</dc:creator>
      <dc:date>2021-02-15T16:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: FPU Type options for MCUXpresso for double-precision floating point</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231125#M12674</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mjbcswitzerland_0-1613411904999.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/137202i6D029CED02A6CE08/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mjbcswitzerland_0-1613411904999.png" alt="mjbcswitzerland_0-1613411904999.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;is correct for i.MX RT parts with double-precision FPU.&lt;/P&gt;&lt;P&gt;For those with only single-precision (i.MX RT 1011) the FPv5-SP16(Hard ABI) can be used instead.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mark&lt;BR /&gt;&lt;EM&gt;[uTasker project developer for Kinetis and i.MX RT]&lt;/EM&gt;&lt;BR /&gt;&lt;FONT color="#999999"&gt;Contact me by personal message or on the uTasker web site to discuss professional training, solutions to problems or rapid product development requirements&lt;BR /&gt;&lt;BR /&gt;For professionals searching for faster, problem-free Kinetis and i.MX RT 10xx developments the uTasker project holds the key: &lt;A href="https://www.utasker.com/iMX/RT1064.html" target="_blank"&gt;https://www.utasker.com/iMX/RT1064.html&lt;/A&gt;&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Feb 2021 18:00:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231125#M12674</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2021-02-15T18:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: FPU Type options for MCUXpresso for double-precision floating point</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231702#M12690</link>
      <description>&lt;P&gt;Perhaps also check the actual compiler command line being used, I think you need both&amp;nbsp;-mfpu=fpv5-d16 and -mfloat-abi=hard.&lt;/P&gt;&lt;P&gt;-Nick&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2021 19:45:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1231702#M12690</guid>
      <dc:creator>nickwallis</dc:creator>
      <dc:date>2021-02-16T19:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: FPU Type options for MCUXpresso for double-precision floating point</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1870929#M30545</link>
      <description>&lt;P&gt;I know this is an older post but I found this looking for a similar problem, can a single precision FPU do any double precision math at a reduced rate? Or I need to get a double precision FPU to utilize FPU hardware for doubles&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/1431"&gt;@mjbcswitzerland&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2024 16:12:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1870929#M30545</guid>
      <dc:creator>223specialist</dc:creator>
      <dc:date>2024-05-22T16:12:47Z</dc:date>
    </item>
    <item>
      <title>Re: FPU Type options for MCUXpresso for double-precision floating point</title>
      <link>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1871363#M30549</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;&lt;BR /&gt;It will depend on the compiler: possibly it will make use of single-precision FPU HW to help accelerate the calculations needed to achieve double precision accuracy but it may also be that this is not possible or the compiler developers didn't do it that way and used pure SW algorithms.&lt;BR /&gt;&lt;BR /&gt;There is a discussion here but I don't know whether it is all correct or not: &lt;A href="https://stackoverflow.com/questions/24701953/doing-double-precision-calculation-on-single-precision-cpu" target="_blank"&gt;https://stackoverflow.com/questions/24701953/doing-double-precision-calculation-on-single-precision-cpu&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To be sure it is best to test it with the compiler and its settings and compare it against a double-precision HW implementation to get an idea of the performance and compare it to what can be accepted in an application case.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Mark&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2024 22:20:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/FPU-Type-options-for-MCUXpresso-for-double-precision-floating/m-p/1871363#M30549</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2024-05-22T22:20:59Z</dc:date>
    </item>
  </channel>
</rss>

