<?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: Pin assignment (or mapping) procedure</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251745#M7142</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question - no real/easyanswer.&lt;/P&gt;&lt;P&gt;what I (would) do is to go ahead and just happily assign pins waiting with GPIO till the end. If when assigning pins to one of the sat devices all possible pinnings give a conflict, go back and change the pinning of some of the earlier defined device..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Apr 2013 14:59:54 GMT</pubDate>
    <dc:creator>erikmalund</dc:creator>
    <dc:date>2013-04-04T14:59:54Z</dc:date>
    <item>
      <title>Pin assignment (or mapping) procedure</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251744#M7141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the proper technique or design procedure for mapping I/O pins on a Kinetis part?&amp;nbsp; I am new to Kinetis family.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I went through (briefly) the Processor Expert (within Code Warrior) and I see how to assign pins, but it is not clear to me which embedded components you should lay down first, second and so on in order to get maximum/optimal pinout arrangement.&amp;nbsp; I can see in the Processor window, that if you put your mouse say over the "ADC0" component it highlights all the pins that can be assigned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for a big picture approach to specifying pin assignments.&amp;nbsp; I know what pins I need from a PCB schematic level and was hoping to quickly define them so we can get on with schematic capture.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a prioritization scheme for specifying pin assignments so that you can get the optimal functionality you are looking for in a design?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if I specify an ADC pin for a MKL14Z64 within the Processor Expert there seems to be a lot of pins to chose from, but it is not clear which pins will become conflicts later as you add to the design.&amp;nbsp; How to resolve or methodically deal with these conflicts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 14:49:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251744#M7141</guid>
      <dc:creator>aes_mike</dc:creator>
      <dc:date>2013-04-04T14:49:52Z</dc:date>
    </item>
    <item>
      <title>Re: Pin assignment (or mapping) procedure</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251745#M7142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question - no real/easyanswer.&lt;/P&gt;&lt;P&gt;what I (would) do is to go ahead and just happily assign pins waiting with GPIO till the end. If when assigning pins to one of the sat devices all possible pinnings give a conflict, go back and change the pinning of some of the earlier defined device..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 14:59:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251745#M7142</guid>
      <dc:creator>erikmalund</dc:creator>
      <dc:date>2013-04-04T14:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: Pin assignment (or mapping) procedure</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251746#M7143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The data sheet shows the pin outs.&lt;/P&gt;&lt;P&gt;I wold not use Processor Expert for this purpose. The data sheet has a chart (8.1 KL14 Signal Multiplexing and Pin Assignments) that clearly shows all the multiplexing for the pins. Also, I am not sure how there could be guidelines, as it depends on&amp;nbsp; what your requirements are.&lt;/P&gt;&lt;P&gt;&lt;A href="http://cache.freescale.com/files/32bit/doc/data_sheet/KL14P80M48SF0.pdf?fpsp=1" title="KL14P80M48SF0.pdf"&gt;KL14P80M48SF0.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 17:30:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251746#M7143</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2013-04-04T17:30:01Z</dc:date>
    </item>
    <item>
      <title>Re: Pin assignment (or mapping) procedure</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251747#M7144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&amp;nbsp; Yes, I have looked at those charts, several in fact.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe a better term for what I am looking for is a pin allocation algorithm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are other manufactures that have a suggested pin out allocation scheme that goes something like the algorithm below.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;0. Make a list of the pins require (i.e. ADC inputs, digital I/Os, etc.).&amp;nbsp; I usually end up with two lists, an absolute must have and a wish list.&lt;/P&gt;&lt;P&gt;1. Allocate those pins that only have one available location&lt;/P&gt;&lt;P&gt;2. then assign the ones that have two, then three and so on.&lt;/P&gt;&lt;P&gt;3. You may have to iterate once or twice depending on fulfillment of your needs/wish lists (i.e. always tradeoffs, especially pin multiplexing since it is a highly constrained resource).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To do this you need a combination of the datasheet table (as Jim mentioned) and a list of signals&amp;nbsp; (i.e.&amp;nbsp; UART1_TX ) and their frequency of occurrence within the pin list to assist in the algorithm above.&amp;nbsp;&amp;nbsp; Some pins are exchangeable in the process so some consideration must be done with respect to that too. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does Freescale have a pin list signal frequency list for their parts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am wondering if perhaps Freescale has automated this somehow within their tools?&amp;nbsp;&amp;nbsp; If not, they ought too because then one can further assess a part for feasibility within a design that much faster and get it into PCB layout that much faster; the Processor Expert probably already has all the internal logic to do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 18:05:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Pin-assignment-or-mapping-procedure/m-p/251747#M7144</guid>
      <dc:creator>aes_mike</dc:creator>
      <dc:date>2013-04-04T18:05:15Z</dc:date>
    </item>
  </channel>
</rss>

