<?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: Debugger to show internal clock speed, baud, timer rates, ADC conversion times etc in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Debugger-to-show-internal-clock-speed-baud-timer-rates-ADC/m-p/210694#M8298</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Well the debugger has no awareness of the way the different devices are working.&lt;/P&gt;&lt;P&gt;So it does not know timing information derived from your current device initialization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Processor Expert or Device Initialization (if you are using CodeWarrior for MCU)&amp;nbsp;has the knowledge of the internal for all the devices and can calculate the various timing information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can submit a Change Request Service Request through our on-line support web site to report you&amp;nbsp; would be interested in such an extension in the debugger.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But keep in mind this is a brand new functionality and a big extension in the debugger. This cannot be implemented quickly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CrasyCat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Aug 2009 15:14:31 GMT</pubDate>
    <dc:creator>CrasyCat</dc:creator>
    <dc:date>2009-08-26T15:14:31Z</dc:date>
    <item>
      <title>Debugger to show internal clock speed, baud, timer rates, ADC conversion times etc</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Debugger-to-show-internal-clock-speed-baud-timer-rates-ADC/m-p/210693#M8297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be GREAT if the debugger could show the internal timing based on the settings of the processor. Every time we set up a new processor we are forever trying to calculate baud rates, timers rates, input capture compare rates, overflow times etc Why doesnt it just show all this in the debugger &lt;A href="http://freescale.i.lithium.com/i/smilies/16x16_smiley-happy.gif"&gt;&lt;IMG alt=":smileyhappy:" class="emoticon emoticon-smileyhappy" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-happy.gif" title="Smiley Happy" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Internal Clock =&lt;/P&gt;&lt;P&gt;Timer X singe clock time =&lt;/P&gt;&lt;P&gt;Baud rate =&amp;nbsp;&lt;/P&gt;&lt;P&gt;ADC Conversion time =&amp;nbsp;&lt;/P&gt;&lt;P&gt;Input/Output Capture singe clock time =&lt;/P&gt;&lt;P&gt;et&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All the things the debugger can easily tell you...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you could set an external xtal setting using some #pragma this would allow the debugger to tell you the same info when the external xtal is setup.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have been moving a heap of designs from 05 to S08 and there are so many variation and changes its always a 'task' that should really be done for you...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think beans look after this, but we just use straight c or assembly.&lt;/P&gt;&lt;DIV class="message-edit-history"&gt;&lt;SPAN class="edit-author"&gt;Message Edited by CarlFST60L on&lt;/SPAN&gt; &lt;SPAN class="local-date"&gt;2009-08-26&lt;/SPAN&gt; &lt;SPAN class="local-time"&gt;05:05 AM&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2009 11:02:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Debugger-to-show-internal-clock-speed-baud-timer-rates-ADC/m-p/210693#M8297</guid>
      <dc:creator>CarlFST60L</dc:creator>
      <dc:date>2009-08-26T11:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Debugger to show internal clock speed, baud, timer rates, ADC conversion times etc</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Debugger-to-show-internal-clock-speed-baud-timer-rates-ADC/m-p/210694#M8298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Well the debugger has no awareness of the way the different devices are working.&lt;/P&gt;&lt;P&gt;So it does not know timing information derived from your current device initialization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Processor Expert or Device Initialization (if you are using CodeWarrior for MCU)&amp;nbsp;has the knowledge of the internal for all the devices and can calculate the various timing information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can submit a Change Request Service Request through our on-line support web site to report you&amp;nbsp; would be interested in such an extension in the debugger.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But keep in mind this is a brand new functionality and a big extension in the debugger. This cannot be implemented quickly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CrasyCat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2009 15:14:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Debugger-to-show-internal-clock-speed-baud-timer-rates-ADC/m-p/210694#M8298</guid>
      <dc:creator>CrasyCat</dc:creator>
      <dc:date>2009-08-26T15:14:31Z</dc:date>
    </item>
  </channel>
</rss>

