<?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: KE04 / MCU-Link Target issue in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1567779#M64422</link>
    <description>&lt;P&gt;Hi Robin,&lt;/P&gt;&lt;P&gt;Sorry for the delay in responding.&lt;/P&gt;&lt;P&gt;Turns out our problem was that we did not have a pullup resistor on NMI.&lt;/P&gt;&lt;P&gt;We are now successfully debugging and programming our target board.&lt;/P&gt;&lt;P&gt;THANK YOU so much for all of your help!!!&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
    <pubDate>Sun, 11 Dec 2022 18:24:58 GMT</pubDate>
    <dc:creator>chicagomike</dc:creator>
    <dc:date>2022-12-11T18:24:58Z</dc:date>
    <item>
      <title>KE04 / MCU-Link Target issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1560193#M64365</link>
      <description>&lt;P&gt;This is a continuation of sorts from the thread "FRDM-KE04Z Quick Start problem". After receiving help from Robin, I brought up a simple test application on my KE04 Freedom board. My plan was to then migrate to our actual target hardware, which uses an MKE04Z8VFK4 processor.&lt;/P&gt;&lt;P&gt;I'm developing on a Windows 10 platform with MCUXpresso v11.6.1 and an MCU-Link debug probe running CMSIS-DAP V2.263 firmware. The debug probe has jumper J4 installed, J2 and J3 not installed.&lt;/P&gt;&lt;P&gt;My test application is just a simple main loop that toggles a GPIO pin, and it builds with no errors or warnings.&lt;/P&gt;&lt;P&gt;The problem is that I am unable to start a debug session, and I'm not sure how to address the problem. It seems that the SWD interface is talking, but something goes wrong with chip initialization. I also tried doing a simple blank-check using the GUI Flash Tool and had similar results.&lt;/P&gt;&lt;P&gt;I'm attaching a text file containing the MCUX console output.&lt;/P&gt;&lt;P&gt;Thanks in advance for your help,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 27 Nov 2022 20:41:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1560193#M64365</guid>
      <dc:creator>chicagomike</dc:creator>
      <dc:date>2022-11-27T20:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: KE04 / MCU-Link Target issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1562835#M64381</link>
      <description>&lt;P&gt;Hi Mike,&lt;/P&gt;
&lt;P&gt;Sorry for my delay! I'm training these days so I can't get back to you sooner.&lt;BR /&gt;I just update the&amp;nbsp;firmware of MCU-Link by refer:&amp;nbsp;&lt;A style="font-family: inherit; background-color: #ffffff;" href="https://www.nxp.com/document/guide/getting-started-with-the-mcu-link:GS-MCU-LINK" target="_self"&gt;Getting Started with the MCU-Link&lt;/A&gt;&lt;BR /&gt;There is no J2 on MCU-Link, would you please check again?&amp;nbsp; (I did not connect J3\4\5)&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MCULINKINSERT.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/202448i13AE8F11C46AB29F/image-size/large?v=v2&amp;amp;px=999" role="button" title="MCULINKINSERT.png" alt="MCULINKINSERT.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;After connect the J6 of MCU-Link to J7 of FRDM-KE04Z, I am able to debug the&amp;nbsp;PKE04Z8VFK4 on FRDM-KE04Z.&lt;BR /&gt;The following is a comparison of console output. It is not clear why Probe Firmware: MCU-LINK (&lt;STRONG&gt;r0BF&lt;/STRONG&gt;) (&lt;STRONG&gt;r0FF&lt;/STRONG&gt;) is slightly different.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MCU-LINK compare.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/202451i5EF098166D25F58F/image-size/large?v=v2&amp;amp;px=999" role="button" title="MCU-LINK compare.png" alt="MCU-LINK compare.png" /&gt;&lt;/span&gt;&lt;BR /&gt;Are you debug custom board or FRDM-KE04Z? If custom board, please check the hardware of KE04:&lt;BR /&gt;PTA0 SWD_CLK&amp;nbsp; external pullup&amp;nbsp;resistor&lt;BR /&gt;PTA4 SWD_DIO&amp;nbsp; external pulldown resistor&lt;BR /&gt;PTA5 RESET_b&amp;nbsp; &amp;nbsp;external pullup&amp;nbsp;resistor&lt;BR /&gt;PTB4 NMI_b external pullup&amp;nbsp;resistor&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Robin&lt;BR /&gt;-------------------------------------------------------------------------------&lt;BR /&gt;Note:&lt;BR /&gt;- If this post answers your question, please click the "Mark Correct" button. Thank you!&lt;/P&gt;
&lt;P&gt;- We are following threads for 7 weeks after the last post, later replies are ignored&lt;BR /&gt;Please open a new thread and refer to the closed one, if you have a related question at a later point in time.&lt;BR /&gt;-------------------------------------------------------------------------------&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2022 12:57:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1562835#M64381</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2022-12-01T12:57:43Z</dc:date>
    </item>
    <item>
      <title>Re: KE04 / MCU-Link Target issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1567779#M64422</link>
      <description>&lt;P&gt;Hi Robin,&lt;/P&gt;&lt;P&gt;Sorry for the delay in responding.&lt;/P&gt;&lt;P&gt;Turns out our problem was that we did not have a pullup resistor on NMI.&lt;/P&gt;&lt;P&gt;We are now successfully debugging and programming our target board.&lt;/P&gt;&lt;P&gt;THANK YOU so much for all of your help!!!&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Sun, 11 Dec 2022 18:24:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1567779#M64422</guid>
      <dc:creator>chicagomike</dc:creator>
      <dc:date>2022-12-11T18:24:58Z</dc:date>
    </item>
    <item>
      <title>Re: KE04 / MCU-Link Target issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1567797#M64424</link>
      <description>&lt;P&gt;You are welcome!&lt;BR /&gt;Thanks for sharing the cause of the problem.&lt;BR /&gt;I am glad to hear that it works now.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 00:51:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE04-MCU-Link-Target-issue/m-p/1567797#M64424</guid>
      <dc:creator>Robin_Shen</dc:creator>
      <dc:date>2022-12-12T00:51:18Z</dc:date>
    </item>
  </channel>
</rss>

