<?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: Licence problem after linux update in LPCXpresso IDE</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545256#M9130</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by DiligentMinds.com on Sat Oct 29 14:22:49 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;That is one of the silliest license schemes I have ever heard of-- everyone else ties the license to the Ethernet MAC address, which is a hard-coded serial number.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I also run Ubuntu (since 2005), and I can tell you that the kernel is updated very often-- every time that a serious security issue is found and corrected, there will be a new update of the kernel.&amp;nbsp; I have seen this happen as often as once per week.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Code Red people should get it together, and change their goofy licensing policy to something that makes better sense.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 23:21:15 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T23:21:15Z</dc:date>
    <item>
      <title>Licence problem after linux update</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545252#M9126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ngoncalves on Tue Oct 25 06:45:49 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; I have the LPCXpresso IDE limited to 128K download, running on Ubuntu. Today I did some updates, including the kernel. Now the IDE no longer allows for a debug session when it did before the update.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; This is the final result of the compilation:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; text&amp;nbsp;&amp;nbsp; data&amp;nbsp;&amp;nbsp;&amp;nbsp; bss&amp;nbsp;&amp;nbsp;&amp;nbsp; dec&amp;nbsp;&amp;nbsp;&amp;nbsp; hexfilename&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; 14548&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 8&amp;nbsp;&amp;nbsp;&amp;nbsp; 540&amp;nbsp; 15096&amp;nbsp;&amp;nbsp; 3af8PLC_Remote_Device.axf&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; If I am reading correctly, the flash size is about 14K. Or are the values in KB ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; When I run "uname" this is what I get:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Linux duke 2.6.38-12-generic #51-Ubuntu SMP Wed Sep 28 14:25:20 UTC 2011 i686 i686 i386 GNU/Linux&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; Also, I checked and the file "PLC_Remote_Device.axf" is about 308 KB on the disk. Is this normal ?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:21:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545252#M9126</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: Licence problem after linux update</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545253#M9127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ngoncalves on Tue Oct 25 06:59:20 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Following the instructions at:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A _jive_internal="true" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2F" rel="nofollow" target="_blank"&gt;http://support.code-red-tech.com/CodeRedWiki/LPCXLicenseDiag&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;this is the output of running "crt_emu_cm3_nxp -info-license":&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Ni: LPCXpresso Debug Driver v4.0 (Jul 22 2011 09:57:25)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The contents of the directory " /usr/share/LPCXpresso" are in the attached file&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:21:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545253#M9127</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: Licence problem after linux update</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545254#M9128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by CodeRedSupport on Tue Oct 25 07:20:30 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;try getting a new serial number and reactivate - the license scheme does rely on the kernel version.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:21:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545254#M9128</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Licence problem after linux update</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545255#M9129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by ngoncalves on Tue Oct 25 07:42:41 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks, that solved the problem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I must say that, from the perspective of the user, tying the serial number to the kernel version is not correct. I spent two hours chasing a problem that it turns out, was not mine.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can't you provide a binary distribution of the IDE that is limited to the 128K, instead of the hassles of using a licence ?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:21:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545255#M9129</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Licence problem after linux update</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545256#M9130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by DiligentMinds.com on Sat Oct 29 14:22:49 MST 2011&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;That is one of the silliest license schemes I have ever heard of-- everyone else ties the license to the Ethernet MAC address, which is a hard-coded serial number.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I also run Ubuntu (since 2005), and I can tell you that the kernel is updated very often-- every time that a serious security issue is found and corrected, there will be a new update of the kernel.&amp;nbsp; I have seen this happen as often as once per week.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Code Red people should get it together, and change their goofy licensing policy to something that makes better sense.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 23:21:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE/Licence-problem-after-linux-update/m-p/545256#M9130</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T23:21:15Z</dc:date>
    </item>
  </channel>
</rss>

