<?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: Using ST-Link V2 to flash KV31F Board in Kinetis Motor Suite</title>
    <link>https://community.nxp.com/t5/Kinetis-Motor-Suite/Using-ST-Link-V2-to-flash-KV31F-Board/m-p/1299205#M846</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181743"&gt;@SANGEERTH-P&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ST-Link V2 is not a product that I’m are too familiar with, considering its primarily developed for ST products. I don’t see why it wouldn’t be compatible if it supports JTAG/SWD communication. Unfortunately I don’t have a way of testing this for you, so I’ll leave you with some links that might prove useful for your inquiry:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips" target="_blank"&gt;https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042" target="_blank"&gt;https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I also noticed that the ST-Link V2 comes with the standard 20 pin connector. Perhaps a 20 pin to 10 pin JTAG adapter would be a better alternative than soldering the lines to make sure the connections are right.&lt;/P&gt;
&lt;P&gt;It goes without saying that we recommend using a different debug probe, like the MCU-Link, since this one is specifically developed for NXP devices. Here’s a link so you can check it out:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/" target="_blank"&gt;https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Edwin.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Jun 2021 16:30:37 GMT</pubDate>
    <dc:creator>EdwinHz</dc:creator>
    <dc:date>2021-06-28T16:30:37Z</dc:date>
    <item>
      <title>Using ST-Link V2 to flash KV31F Board</title>
      <link>https://community.nxp.com/t5/Kinetis-Motor-Suite/Using-ST-Link-V2-to-flash-KV31F-Board/m-p/1298982#M845</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I am currently using a KV31F512VLL12 Microcontroller. I tried to flash this board using ST-Link V2 Adapter. The jumper pins of ST Link was not matching the JTAG Jumper pins on the Evaluation Board. So I soldered few jumpers on the board. Then I connected KV31F Board JTAG pins to ST-Link Utility and then through the USB Port of ST-Link Utility I connected to my PC. I was able to see that my board was getting powered and it was executing the last dumped code. When i tried to debug the board with a new code, MCUXpresso-IDE was not showing any of the Debug port availability even when the ST-Link was connected to the PC. I changed the Debugger options too.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SANGEERTHP_0-1624869125843.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/148144i1BF3740970ADC626/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SANGEERTHP_0-1624869125843.png" alt="SANGEERTHP_0-1624869125843.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Even then I see this following error.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SANGEERTHP_1-1624869288442.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/148145i35D81C1052A7C56E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SANGEERTHP_1-1624869288442.png" alt="SANGEERTHP_1-1624869288442.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I am not sure of what is the cause for this error. I need your suggestions here.&lt;/P&gt;&lt;P&gt;Is the MCU KV31F incompatible with ST-LINK V2? If yes, what are the other ways to flash the code than this OPENSDA.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jun 2021 08:40:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Motor-Suite/Using-ST-Link-V2-to-flash-KV31F-Board/m-p/1298982#M845</guid>
      <dc:creator>SANGEERTH-P</dc:creator>
      <dc:date>2021-06-28T08:40:11Z</dc:date>
    </item>
    <item>
      <title>Re: Using ST-Link V2 to flash KV31F Board</title>
      <link>https://community.nxp.com/t5/Kinetis-Motor-Suite/Using-ST-Link-V2-to-flash-KV31F-Board/m-p/1299205#M846</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181743"&gt;@SANGEERTH-P&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The ST-Link V2 is not a product that I’m are too familiar with, considering its primarily developed for ST products. I don’t see why it wouldn’t be compatible if it supports JTAG/SWD communication. Unfortunately I don’t have a way of testing this for you, so I’ll leave you with some links that might prove useful for your inquiry:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips" target="_blank"&gt;https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042" target="_blank"&gt;https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I also noticed that the ST-Link V2 comes with the standard 20 pin connector. Perhaps a 20 pin to 10 pin JTAG adapter would be a better alternative than soldering the lines to make sure the connections are right.&lt;/P&gt;
&lt;P&gt;It goes without saying that we recommend using a different debug probe, like the MCU-Link, since this one is specifically developed for NXP devices. Here’s a link so you can check it out:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/" target="_blank"&gt;https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Edwin.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jun 2021 16:30:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Motor-Suite/Using-ST-Link-V2-to-flash-KV31F-Board/m-p/1299205#M846</guid>
      <dc:creator>EdwinHz</dc:creator>
      <dc:date>2021-06-28T16:30:37Z</dc:date>
    </item>
  </channel>
</rss>

