<?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>Kinetis MicrocontrollersのトピックRe: OpenSDA V2 Release 11.2017 - ISSUE with MKw41Z</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OpenSDA-V2-Release-11-2017-ISSUE-with-MKw41Z/m-p/756150#M46097</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Matteo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was also able to program the KW41 MCU from a FRDM-KW41Z with the OpenSDA JLink debugger interface from another freedom board. This must mean that there is something in your custom hardware that is affecting the OpenSDA JLink interface and the CMSIS-DAP interface is robust enough to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you checked with an oscilloscope that the SWD_DIO, SWD_CLK and Reset signals are clean and noise free?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My suggestion would be to try with a dedicated external JLink debug probe to see if it has the same behavior as the OpenSDA JLink interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About your questions, I believe you are not missing any step. Debugging your custom board should be the same as with the freedom board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know your findings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Mar 2018 03:10:08 GMT</pubDate>
    <dc:creator>gerardo_rodriguez</dc:creator>
    <dc:date>2018-03-06T03:10:08Z</dc:date>
    <item>
      <title>OpenSDA V2 Release 11.2017 - ISSUE with MKw41Z</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OpenSDA-V2-Release-11-2017-ISSUE-with-MKw41Z/m-p/756149#M46096</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;we have a custom design based on the MKW41z, which gives us troubles when trying to programming it.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;We use a board FRDM-KW41Z as an external programmer, after having appropriately modified the board to program an external MCU. In particular, we have cut the jumpers J14, J13 and J25 of the FRDM-KW41Z and connected them respectively to SWCLK, SWDIO, and Reset of R41Z.&lt;/DIV&gt;What we notice is that:&lt;/DIV&gt;- The target MCU supplied with 3V draws 6mA before being programmed. To us, this value looks a bit too high.&lt;/DIV&gt;- Apparently the target MKW41Z keeps resetting while programming. &lt;/DIV&gt;- We notice that this issue only occurs when the &lt;SPAN class=""&gt;FRDM-KW41Z is programmed with &lt;/SPAN&gt; OpenSDA v2.2 and JLink is used; instead, with &lt;SPAN class=""&gt;DAPLink rev0241 this issue does not occur and the target MCU can be programmed.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN class=""&gt;In&lt;/SPAN&gt; attachment the error generated when trying to program the node via JLink command line interface.&lt;P&gt;The same&amp;nbsp; approach works fine when programming the MKw41Z embedded on the same FRDM-KW41Z or the MKw41Z embedded on another MKw41Z.&lt;/P&gt;&lt;P&gt;Our custom board is designed according to the recommendation of NXP, namely we followed the same schematic as indicated for the FRDM-KW41Z.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;1. Is there any step that we are overlooking for correctly programming the node?&lt;/DIV&gt;&lt;DIV&gt;2. Is it necessary to configure any flag of the MKW41Z before programming it?&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;Best regards,&lt;/DIV&gt;&lt;DIV&gt;Matteo Lasagni&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Feb 2018 10:42:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OpenSDA-V2-Release-11-2017-ISSUE-with-MKw41Z/m-p/756149#M46096</guid>
      <dc:creator>matteolasagni</dc:creator>
      <dc:date>2018-02-19T10:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: OpenSDA V2 Release 11.2017 - ISSUE with MKw41Z</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OpenSDA-V2-Release-11-2017-ISSUE-with-MKw41Z/m-p/756150#M46097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Matteo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was also able to program the KW41 MCU from a FRDM-KW41Z with the OpenSDA JLink debugger interface from another freedom board. This must mean that there is something in your custom hardware that is affecting the OpenSDA JLink interface and the CMSIS-DAP interface is robust enough to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you checked with an oscilloscope that the SWD_DIO, SWD_CLK and Reset signals are clean and noise free?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My suggestion would be to try with a dedicated external JLink debug probe to see if it has the same behavior as the OpenSDA JLink interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About your questions, I believe you are not missing any step. Debugging your custom board should be the same as with the freedom board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know your findings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Gerardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2018 03:10:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OpenSDA-V2-Release-11-2017-ISSUE-with-MKw41Z/m-p/756150#M46097</guid>
      <dc:creator>gerardo_rodriguez</dc:creator>
      <dc:date>2018-03-06T03:10:08Z</dc:date>
    </item>
  </channel>
</rss>

