<?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: Starting code with IAR in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290036#M11490</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are certainly several options to look into.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, the debugger-interface does not 'bother' to read the actual reset-vector from Flash, since it 'already knows' where to start from.&amp;nbsp; So the first thing to check is to see if absolute 0 contains a valid stack-pointer preset, and is followed by your proper code entry point (0x411?).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If that looks OK, then the next steps to consider are 'startup time'.&amp;nbsp; When you run the debugger, the time from 'power up' to 'code start' is 'very long', while using the internal chip power-on-reset the CPU will start running code just over 1.7V.&amp;nbsp; If you use an external oscillator clock source, for instance, you can be sure that it has to wait 'many milliseconds' after a full 3.3V to get to full oscillation.&amp;nbsp; Look for issues like this where the CPU may be starting long before something external is really 'ready to go'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Jan 2014 16:41:24 GMT</pubDate>
    <dc:creator>egoodii</dc:creator>
    <dc:date>2014-01-07T16:41:24Z</dc:date>
    <item>
      <title>Starting code with IAR</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290035#M11489</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello World !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a code starting with j-trace IAR debug and running correctly&lt;/P&gt;&lt;P&gt;Reset hardware restart correctly program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i disconnect debugger (red cross in IDE) it is no more possible to run software.&lt;/P&gt;&lt;P&gt;Same when i disconnect j-trace, reset (hardware) do no start my code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An idea ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 16:15:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290035#M11489</guid>
      <dc:creator>lucky06200</dc:creator>
      <dc:date>2014-01-07T16:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: Starting code with IAR</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290036#M11490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are certainly several options to look into.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all, the debugger-interface does not 'bother' to read the actual reset-vector from Flash, since it 'already knows' where to start from.&amp;nbsp; So the first thing to check is to see if absolute 0 contains a valid stack-pointer preset, and is followed by your proper code entry point (0x411?).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If that looks OK, then the next steps to consider are 'startup time'.&amp;nbsp; When you run the debugger, the time from 'power up' to 'code start' is 'very long', while using the internal chip power-on-reset the CPU will start running code just over 1.7V.&amp;nbsp; If you use an external oscillator clock source, for instance, you can be sure that it has to wait 'many milliseconds' after a full 3.3V to get to full oscillation.&amp;nbsp; Look for issues like this where the CPU may be starting long before something external is really 'ready to go'.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Jan 2014 16:41:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290036#M11490</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2014-01-07T16:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Starting code with IAR</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290037#M11491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In fact, my application is a little more complicated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 MQX application running on the same kinetis, but not together.&lt;/P&gt;&lt;P&gt;One is flashed @0x00000000 and second @0x00041000 (first and second half of internal flash memory).&lt;/P&gt;&lt;P&gt;First application is a boot-loader running from start of ROM and use as loader/application updater/maintenance code.&lt;/P&gt;&lt;P&gt;Second is my real application (analog data measurement).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When request in first code (automatically, command line or cgi script) we invalidate interrupt, get SP and PC from second application, and call it. This work very well with j-trace connected (in all mode of use).&lt;/P&gt;&lt;P&gt;As soon as i disconnect debugger ("Stop debugging" red cross button in IAR IDE) going from loader to second application do not work anymore. And i have no more debugger to understand what appends!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: second application, linked at adresse 0x00000000 work without any problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea/suggestion? Where can i look? What can i do?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Feb 2014 10:20:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290037#M11491</guid>
      <dc:creator>lucky06200</dc:creator>
      <dc:date>2014-02-13T10:20:09Z</dc:date>
    </item>
    <item>
      <title>Re: Starting code with IAR</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290038#M11492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a 'change' in clocking strategy between the two 'applications'?&amp;nbsp; I assume the Interrupt Vector Table (and pointer thereto) handoff is expected to be OK, and not 're-enabled' until that (and all the NVIC registers that individually enable them) are all valid again.&amp;nbsp; I'm trying to think of things where 'time since power-up (or last interrupt)' would directly affect the 'run-ability' of the second app.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Feb 2014 20:46:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290038#M11492</guid>
      <dc:creator>egoodii</dc:creator>
      <dc:date>2014-02-13T20:46:04Z</dc:date>
    </item>
    <item>
      <title>Re: Starting code with IAR</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290039#M11493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have found the reason.&lt;/P&gt;&lt;P&gt;In my code, after invalidate interrupt, there were a printf to display function call.&lt;/P&gt;&lt;P&gt;But printf do no work if interrupt not functioning, and wait for them ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, my code without printf work correctly..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Feb 2014 08:34:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Starting-code-with-IAR/m-p/290039#M11493</guid>
      <dc:creator>lucky06200</dc:creator>
      <dc:date>2014-02-27T08:34:41Z</dc:date>
    </item>
  </channel>
</rss>

