<?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>LPC MicrocontrollersのトピックGlitch in PLL1 source code</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/Glitch-in-PLL1-source-code/m-p/590771#M22116</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by mch0 on Sat May 31 03:57:51 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;OK, back again after I realized my first solution did not work.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem is this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The code supplied with LPCOpen (V2.12) to set up the core frequency has a fair chance to crash when executed from local SRAM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For my project I need to execute from SRAM, since I have to modify the SPIFI flash content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To do this I decided to relocate all code as early as possible from SPIFI to SRAM and then solely execute from there. I specically wanted to move everything, because then I don't have to care about later additions or whatever to the project and keep track of what resides where.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I moved also the SysInit-Code and executed it from SRAM. Result: crash.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It turned out the original code (as supplied) would change the CPU frequency to 204MHz when executing from SPIFI, but not when executing from SRAM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I feel that someone from NXP should look into this and check whether this is really a bug. In that case I'd suggest a correction of the code in V2.13.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll be glad to help if questions arise.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The attached report describes the battle and also contains a preliminary fix.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Somehow I feel I could do with a full license instead of the free license I use now :) (hint, hint).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 19:19:38 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T19:19:38Z</dc:date>
    <item>
      <title>Glitch in PLL1 source code</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/Glitch-in-PLL1-source-code/m-p/590771#M22116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by mch0 on Sat May 31 03:57:51 MST 2014&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;OK, back again after I realized my first solution did not work.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem is this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The code supplied with LPCOpen (V2.12) to set up the core frequency has a fair chance to crash when executed from local SRAM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;For my project I need to execute from SRAM, since I have to modify the SPIFI flash content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To do this I decided to relocate all code as early as possible from SPIFI to SRAM and then solely execute from there. I specically wanted to move everything, because then I don't have to care about later additions or whatever to the project and keep track of what resides where.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So I moved also the SysInit-Code and executed it from SRAM. Result: crash.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It turned out the original code (as supplied) would change the CPU frequency to 204MHz when executing from SPIFI, but not when executing from SRAM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I feel that someone from NXP should look into this and check whether this is really a bug. In that case I'd suggest a correction of the code in V2.13.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll be glad to help if questions arise.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The attached report describes the battle and also contains a preliminary fix.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Somehow I feel I could do with a full license instead of the free license I use now :) (hint, hint).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 19:19:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/Glitch-in-PLL1-source-code/m-p/590771#M22116</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T19:19:38Z</dc:date>
    </item>
  </channel>
</rss>

