<?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: issue with mux'd pins in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314924#M13761</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vinod&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default pin function is SWD CLK out of reset. If you ensure that the analoge signal can be removed when debugging (so that the clock from the debugger is not disturbed) you will be able to program and debug on the port.&lt;/P&gt;&lt;P&gt;It will however not be possible to test the cmparator input operation when the debugger is attached.&lt;/P&gt;&lt;P&gt;The application needs to change the pin function for it to become a comparator input so it may be advisable to make the code detect when you are debugging (eg. set the state of a spare input to signal that you want to retain debugging functionality) and not reprogram the pin so that the debugger can continue to operate when debugging other parts of the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Jul 2014 19:50:59 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2014-07-02T19:50:59Z</dc:date>
    <item>
      <title>issue with mux'd pins</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314923#M13760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using the KL04 chip (24 pins package).&lt;/P&gt;&lt;P&gt;I want to use the comparator module in this chip(pins 13,19,20 and 22).&lt;/P&gt;&lt;P&gt;Assuming I give the reference ('-') input to the pin 22 (so its a step down of a supply of 11V to a&lt;/P&gt;&lt;P&gt;KL04 compatible 3.3V.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But, this is muxed to SWD_CLK programming pin. This would mean that there might be an issue&lt;/P&gt;&lt;P&gt;with programming and/or debugging. How can this be solved. I am using the Multilink Universal from PE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vinod.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2014 08:55:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314923#M13760</guid>
      <dc:creator>vinkar</dc:creator>
      <dc:date>2014-07-02T08:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: issue with mux'd pins</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314924#M13761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Vinod&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The default pin function is SWD CLK out of reset. If you ensure that the analoge signal can be removed when debugging (so that the clock from the debugger is not disturbed) you will be able to program and debug on the port.&lt;/P&gt;&lt;P&gt;It will however not be possible to test the cmparator input operation when the debugger is attached.&lt;/P&gt;&lt;P&gt;The application needs to change the pin function for it to become a comparator input so it may be advisable to make the code detect when you are debugging (eg. set the state of a spare input to signal that you want to retain debugging functionality) and not reprogram the pin so that the debugger can continue to operate when debugging other parts of the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Jul 2014 19:50:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314924#M13761</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2014-07-02T19:50:59Z</dc:date>
    </item>
    <item>
      <title>Re: issue with mux'd pins</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314925#M13762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See if you can connect the - signal to another pin.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;If you disable the SWD_CLK then you won't be able to do any debugging. Further more, it will be tricky to program the chip.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Jul 2014 18:47:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/issue-with-mux-d-pins/m-p/314925#M13762</guid>
      <dc:creator>galadragos</dc:creator>
      <dc:date>2014-07-03T18:47:03Z</dc:date>
    </item>
  </channel>
</rss>

