<?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: [LPC43xx] Multicore linking problem in LPCXpresso IDE</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581028#M24796</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Wed Oct 30 01:48:05 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;You shouldn't link them together, you need a separate binary for each core.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 22:40:46 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T22:40:46Z</dc:date>
    <item>
      <title>[LPC43xx] Multicore linking problem</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581026#M24794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by MaSt on Tue Oct 29 23:35:36 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;when linking the two projects CortexM4 with FPv4-SP(Hard ABI) enabled for C-Compiler and Linker and the Cortex-M0 to one binary, the linker complains following:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;error: Multicore-M4.axf uses VFP register arguments, Multicore-M0.axf.o does not&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;failed to merge target specific data of file Multicore-M0.axf.o&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have floating-point calculations on the M4-core, so HW-Floating point is highly appreciated. How can i use the M4-HW-Floating point and dualcore in LPCXpresso (V6.1.0)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:40:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581026#M24794</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:40:44Z</dc:date>
    </item>
    <item>
      <title>Re: [LPC43xx] Multicore linking problem</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581027#M24795</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcxpresso-support on Wed Oct 30 01:37:42 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Switching back to the default floating point option of using FPv4-SP (Soft ABI) is the simplest way to avoid this issue. This will still use floating point instructions but passes FP parameters between functions using the integer registers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However it ought be possible to use Hard ABI, and as you have found this currently causes issues when doing multicore projects.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We will investigate this. But in the meantime you could temporarily add the "--no-warn-mismatch" option to the &lt;/SPAN&gt;&lt;STRONG&gt;MCU Linker - Miscellaneous - Other options&lt;/STRONG&gt;&lt;SPAN&gt; settings in Project Properties to avoid the issue.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPCXpresso Support&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:40:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581027#M24795</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: [LPC43xx] Multicore linking problem</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581028#M24796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by starblue on Wed Oct 30 01:48:05 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;You shouldn't link them together, you need a separate binary for each core.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:40:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581028#M24796</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: [LPC43xx] Multicore linking problem</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581029#M24797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcxpresso-support on Wed Oct 30 03:22:55 MST 2013&lt;/STRONG&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;SPAN style="color: #0000ff;"&gt;&lt;STRONG&gt;Quote: starblue&lt;/STRONG&gt;&lt;BR /&gt;You shouldn't link them together, you need a separate binary for each core.&lt;/SPAN&gt;&lt;HR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Suggest you read:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.lpcware.com%2Fcontent%2Ffaq%2Flpcxpresso%2Flpc43xx-multicore-apps" rel="nofollow" target="_blank"&gt;http://www.lpcware.com/content/faq/lpcxpresso/lpc43xx-multicore-apps&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;LPCXpresso Support&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 22:40:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/LPC43xx-Multicore-linking-problem/m-p/581029#M24797</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T22:40:46Z</dc:date>
    </item>
  </channel>
</rss>

