<?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: How to program KL-MCUs by P&amp;E usb multilink universal? in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150101#M183</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;P&amp;amp;E Universal Multilink does an update automatically as needed at the time of connect. Reasons for an update are&lt;/P&gt;&lt;P&gt;- updated (newer version) of the firmware available (e.g. you have V1 on the Multilink, but your debugger has &amp;gt;V1 available)&lt;/P&gt;&lt;P&gt;- switching Processor (e.g. from a ColdFire to a Kinetis): in that case a different firmware is needed on the Multilink, and it is downloaded to the Multilink automatically&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally P&amp;amp;E has a utility on their website to inspect the firmware version and to upgrade/downgrade the firmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this clarifies it,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Oct 2012 05:14:41 GMT</pubDate>
    <dc:creator>BlackNight</dc:creator>
    <dc:date>2012-10-24T05:14:41Z</dc:date>
    <item>
      <title>How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150097#M179</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;&lt;/P&gt;&lt;P&gt;I have one Usb Multilink Universal programmer which version is V1. There is no SWD support information on user's guide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I found that P&amp;amp;E have announced Usb Multilink Universal supporting for &lt;A href="http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=KINETIS_L_SERIES"&gt;Kinetis L series MCUs&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I use my own Usb Multilink Universal to program &lt;A href="http://www.freescale.com/webapp/sps/site/taxonomy.jsp?code=KINETIS_L_SERIES"&gt;KL-MCUs&lt;/A&gt;? Need to update the firmware of programmer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls see the attached files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THX!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="old.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/38365i936168229873AB4F/image-size/large?v=v2&amp;amp;px=999" role="button" title="old.png" alt="old.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;---------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="new.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/38376i4ED022AEBF31093B/image-size/large?v=v2&amp;amp;px=999" role="button" title="new.png" alt="new.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2012 02:41:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150097#M179</guid>
      <dc:creator>w_x</dc:creator>
      <dc:date>2012-10-24T02:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150098#M180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It does support SWD, I am using to program and debug the Freedom board, but I did have to solder in a .05" header.&lt;/P&gt;&lt;P&gt;Refer to a schematic of&amp;nbsp; similar Freescale reference board to see&amp;nbsp; to how to connect it on your prototype board.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2012 03:04:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150098#M180</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2012-10-24T03:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150099#M181</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Jim.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mostly what I care about is if there is need to update the firmware of Usb Multilink Universal?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will be good news if we can use it without any change.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2012 03:52:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150099#M181</guid>
      <dc:creator>w_x</dc:creator>
      <dc:date>2012-10-24T03:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150100#M182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, if the firmware need to be updated, CW will do that the first time you connect. You will get a dialog say it is updating the firmware.&lt;/P&gt;&lt;P&gt;I think it did.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2012 04:01:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150100#M182</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2012-10-24T04:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150101#M183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;P&amp;amp;E Universal Multilink does an update automatically as needed at the time of connect. Reasons for an update are&lt;/P&gt;&lt;P&gt;- updated (newer version) of the firmware available (e.g. you have V1 on the Multilink, but your debugger has &amp;gt;V1 available)&lt;/P&gt;&lt;P&gt;- switching Processor (e.g. from a ColdFire to a Kinetis): in that case a different firmware is needed on the Multilink, and it is downloaded to the Multilink automatically&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally P&amp;amp;E has a utility on their website to inspect the firmware version and to upgrade/downgrade the firmware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this clarifies it,&lt;/P&gt;&lt;P&gt;Erich&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2012 05:14:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150101#M183</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2012-10-24T05:14:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to program KL-MCUs by P&amp;E usb multilink universal?</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150102#M184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The most common mistake is wrong wiring to match pins between Multilink and PCB board. Therefore Reset pin is always low!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Feb 2017 04:20:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/How-to-program-KL-MCUs-by-P-E-usb-multilink-universal/m-p/150102#M184</guid>
      <dc:creator>marceli1</dc:creator>
      <dc:date>2017-02-27T04:20:54Z</dc:date>
    </item>
  </channel>
</rss>

