<?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>CodeWarrior Development ToolsのトピックExternal J-link does not work with with K64F in CW 10.6, works with KDS and IAR?</title>
    <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456468#M3349</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After experimenting with the new KSDK and the KDS in various versions, as well as testing IAR with the KSDK, I've determined KDS and the KSDK is just a little too unstable to using going forward yet. Particularly the debugging in KDS seems buggy.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I've switched back to CodeWarrior 10.6 and the new MQX 4.2 (which includes the features of the KSDK I needed). However, I've run into something strange:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In CodeWarrior 10.4 and previous versions of MQX, as well as in the KDS 2.0 and KDS 3.0, and in IAR, I can choose to use either the internal emulated J-link in the K64F with the Segger firmware(which I find to be a bit buggy and inconsistent), or an external Segger J-Link box plugged into the JTAG 10-pin connector on the K64F. The external box works in the other IDEs, and works more consistently than the emulated J-link.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But with Codewarrior 10.6 and MQX 4.2, I can't get the external J-link to work. It's LED flashes red, and the LED near the reset button on the K64F flash red, and it eventually fails. I also can't figure out how to enable the output from the debugger to display in a console in CodeWarrior, where it was on by default in KDS.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sean &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 May 2015 14:57:46 GMT</pubDate>
    <dc:creator>ironsean</dc:creator>
    <dc:date>2015-05-22T14:57:46Z</dc:date>
    <item>
      <title>External J-link does not work with with K64F in CW 10.6, works with KDS and IAR?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456468#M3349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After experimenting with the new KSDK and the KDS in various versions, as well as testing IAR with the KSDK, I've determined KDS and the KSDK is just a little too unstable to using going forward yet. Particularly the debugging in KDS seems buggy.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I've switched back to CodeWarrior 10.6 and the new MQX 4.2 (which includes the features of the KSDK I needed). However, I've run into something strange:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In CodeWarrior 10.4 and previous versions of MQX, as well as in the KDS 2.0 and KDS 3.0, and in IAR, I can choose to use either the internal emulated J-link in the K64F with the Segger firmware(which I find to be a bit buggy and inconsistent), or an external Segger J-Link box plugged into the JTAG 10-pin connector on the K64F. The external box works in the other IDEs, and works more consistently than the emulated J-link.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But with Codewarrior 10.6 and MQX 4.2, I can't get the external J-link to work. It's LED flashes red, and the LED near the reset button on the K64F flash red, and it eventually fails. I also can't figure out how to enable the output from the debugger to display in a console in CodeWarrior, where it was on by default in KDS.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sean &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 May 2015 14:57:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456468#M3349</guid>
      <dc:creator>ironsean</dc:creator>
      <dc:date>2015-05-22T14:57:46Z</dc:date>
    </item>
    <item>
      <title>Re: External J-link does not work with with K64F in CW 10.6, works with KDS and IAR?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456469#M3350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Sean MacKay:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Open the Debug Configurations and go to Target Settings -&amp;gt; Edit. Make sure that the &lt;EM&gt;&lt;STRONG&gt;Debug port&lt;/STRONG&gt;&lt;/EM&gt;&lt;STRONG&gt; &lt;/STRONG&gt;&lt;STRONG&gt;interface&lt;/STRONG&gt; is set to &lt;STRONG&gt;SWD&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/35610i1EDA069D825AC3FF/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards!,&lt;BR /&gt;Jorge Gonzalez&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 May 2015 16:30:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456469#M3350</guid>
      <dc:creator>Jorge_Gonzalez</dc:creator>
      <dc:date>2015-05-23T16:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: External J-link does not work with with K64F in CW 10.6, works with KDS and IAR?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456470#M3351</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you! That did the trick!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 19:51:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456470#M3351</guid>
      <dc:creator>ironsean</dc:creator>
      <dc:date>2015-05-28T19:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: External J-link does not work with with K64F in CW 10.6, works with KDS and IAR?</title>
      <link>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456471#M3352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also strange, I've installed the v4.98e version of the segger tools, but CodeWarrior still runs J-Link V4.90e for some reason.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2015 20:27:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-Development-Tools/External-J-link-does-not-work-with-with-K64F-in-CW-10-6-works/m-p/456471#M3352</guid>
      <dc:creator>ironsean</dc:creator>
      <dc:date>2015-05-28T20:27:37Z</dc:date>
    </item>
  </channel>
</rss>

