<?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>8-bit Microcontrollers中的主题 Re: Question about MC9S08EL32 ICS Trim</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214745#M18600</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="lia-spoiler-container"&gt;&lt;A class="lia-spoiler-link" href="http://forums.freescale.com/#" rel="nofollow"&gt;Spoiler&lt;/A&gt;&lt;NOSCRIPT&gt;(Highlight to read)&lt;/NOSCRIPT&gt;&lt;DIV class="lia-spoiler-border"&gt;&lt;DIV class="lia-spoiler-content"&gt;If you are using Code Warrior in conjunction with USB Multilink interface, this is usually done automatically&lt;/DIV&gt;&lt;NOSCRIPT&gt;&lt;DIV class="lia-spoiler-noscript-container"&gt;&lt;DIV class="lia-spoiler-noscript-content"&gt;If you are using Code Warrior in conjunction with USB Multilink interface, this is usually done automatically&lt;/DIV&gt;&lt;/DIV&gt;&lt;/NOSCRIPT&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Where can I found information about what does automaticilly the USB multilink interface ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 May 2012 15:55:09 GMT</pubDate>
    <dc:creator>Brax02</dc:creator>
    <dc:date>2012-05-31T15:55:09Z</dc:date>
    <item>
      <title>Question about MC9S08EL32 ICS Trim</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214742#M18597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, all:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; In the datasheet of MC9S08EL32, charpter 8.4.5 said: " All MCU devices are factory programmed with a trim value in a reserved memory location. This value can be copied to the ICSTRM register during reset initialization. The factory trim value does not include the FTRIM bit. For finer precision, the user can trim the internal oscillator in the application and set the FTRIM bit accordingly".&lt;/P&gt;&lt;P&gt;&amp;nbsp; My question: I read the reserved memory location 0xFFAF and 0xFFAE, the ruturn value is 0xFF, is this the trim value?&lt;/P&gt;&lt;P&gt;&amp;nbsp; I tested the busclk using&amp;nbsp; code： for(&lt;A href="http://freescale.i.lithium.com/i/smilies/16x16_smiley-wink.gif"&gt;&lt;IMG alt=":smileywink:" class="emoticon emoticon-smileywink" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-wink.gif" title="Smiley Wink" /&gt;&lt;/A&gt;{PTBD6=0;PTBD6=1;}, what I get is 17.784Mhz!!! But my system's busclk setting&amp;nbsp;is 16MHz, seems this chip is not trimed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 08:07:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214742#M18597</guid>
      <dc:creator>JalenZ</dc:creator>
      <dc:date>2011-06-14T08:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: Question about MC9S08EL32 ICS Trim</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214743#M18598</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;A value of 0xFF within flash corresponds to an unprogrammed value.&amp;nbsp; The original contents of locations 0xFFAE and 0xFFAF have likely been erased by a mass erase operation prior to programming.&amp;nbsp; The internal reference clock will need to be re-calibrated during programming&amp;nbsp; If you are using Code Warrior in conjunction with USB Multilink interface, this is usually done automatically.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does your code write the value at address 0xFFAE into ICSTRM register?&amp;nbsp; This needs to be done once you have the proper calibration values stored in flash.&amp;nbsp; If you had written 0xFF into ICSTRM, I would have expected a bus frequency that was too low.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The POR value in ICSTRM is 0x80, and maybe this is the current setting.&amp;nbsp; An uncalibrated&amp;nbsp;bus frequency that is about 11 percent too high would be within the unit-to-unit production tolerance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mac&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 12:52:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214743#M18598</guid>
      <dc:creator>bigmac</dc:creator>
      <dc:date>2011-06-14T12:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Question about MC9S08EL32 ICS Trim</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214744#M18599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, bigMac!&lt;/P&gt;&lt;P&gt;I use CW conjunction with open source BDM. The factory trim value was erased&amp;nbsp;by the&amp;nbsp;BDM&amp;nbsp;before download the&amp;nbsp;object&amp;nbsp;code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now I read the factory&amp;nbsp;trim value before doing a mass erase, and then write the value back. My initial code&amp;nbsp; write the value at address 0xFFAE into ICSTRM register, but when I using the SCI module, the communication is not work well, seems the bus frequency is not&amp;nbsp;pricise enough. Is that means I need calibrate&amp;nbsp;again?&lt;/P&gt;&lt;P&gt;Thanks!&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2011 17:00:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214744#M18599</guid>
      <dc:creator>JalenZ</dc:creator>
      <dc:date>2011-06-14T17:00:41Z</dc:date>
    </item>
    <item>
      <title>Re: Question about MC9S08EL32 ICS Trim</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214745#M18600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="lia-spoiler-container"&gt;&lt;A class="lia-spoiler-link" href="http://forums.freescale.com/#" rel="nofollow"&gt;Spoiler&lt;/A&gt;&lt;NOSCRIPT&gt;(Highlight to read)&lt;/NOSCRIPT&gt;&lt;DIV class="lia-spoiler-border"&gt;&lt;DIV class="lia-spoiler-content"&gt;If you are using Code Warrior in conjunction with USB Multilink interface, this is usually done automatically&lt;/DIV&gt;&lt;NOSCRIPT&gt;&lt;DIV class="lia-spoiler-noscript-container"&gt;&lt;DIV class="lia-spoiler-noscript-content"&gt;If you are using Code Warrior in conjunction with USB Multilink interface, this is usually done automatically&lt;/DIV&gt;&lt;/DIV&gt;&lt;/NOSCRIPT&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Where can I found information about what does automaticilly the USB multilink interface ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2012 15:55:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Question-about-MC9S08EL32-ICS-Trim/m-p/214745#M18600</guid>
      <dc:creator>Brax02</dc:creator>
      <dc:date>2012-05-31T15:55:09Z</dc:date>
    </item>
  </channel>
</rss>

