<?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: FRDM-KL27Z  Using J11 with a Segger in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/1859210#M66347</link>
    <description>&lt;P&gt;The user guide section 5.3 is wrong.&lt;/P&gt;&lt;P&gt;To use a segger J-Link&amp;nbsp; or somesuch instead of the on-board SDA&lt;/P&gt;&lt;P&gt;Remove K5 RST, Remove J6 SWD-DIO, Remove J7 SWD-CLK.&amp;nbsp; KEEP J18 shorted&lt;/P&gt;&lt;P&gt;You can then go in on the 10 pin J11&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 04 May 2024 13:03:20 GMT</pubDate>
    <dc:creator>tonytonick</dc:creator>
    <dc:date>2024-05-04T13:03:20Z</dc:date>
    <item>
      <title>FRDM-KL27Z Schematics and Bootloader Questions</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350794#M17313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm doing a fairly simple design using the MKL17Z256VFM4.&lt;/P&gt;&lt;P&gt;There's a couple of things I'd like to ask you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: black; background: white;"&gt;I ordered the &lt;/SPAN&gt;&lt;SPAN style="font-size: 9.0pt; color: black; background: white;"&gt;FRDM-KL27Z as a dev platform.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black; background: white;"&gt; Is this the best dev platform for the KL17?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black; background: white;"&gt; Are the schematics available? I didn't find them.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black; background: white;"&gt;About the ROM Bootloader:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black; background: white;"&gt; Apparently you can force the CPU to enter the bootloader by asserting the &lt;/SPAN&gt;&lt;SPAN style="font-size: 9.0pt; color: black;"&gt; BOOTCFG0 pin which is apparently the NMI_b pin; what does assert mean in this case? Is it high or low?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black;"&gt;&amp;nbsp; The Bootloader looks at LPUART among others as a boot device. Which one does it use? LPUART0 or LPUART1 or both?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 9.0pt; color: black;"&gt;Thanks for your help,&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Mar 2015 18:43:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350794#M17313</guid>
      <dc:creator>adamgarrison</dc:creator>
      <dc:date>2015-03-25T18:43:43Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-KL27Z Schematics and Bootloader Questions</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350795#M17314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, FRDM-KL27 is the best dev platform for KL17 at present.&lt;/P&gt;&lt;P&gt;Compare, FRDM-KL27 only has one USB module than KL17.&lt;/P&gt;&lt;P&gt;The schematic is attached here. It is still not available at Freescale website.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding Bootloader:&lt;/P&gt;&lt;P&gt;BOOTCFG0 pin need in low level to enter bootloader when power on.&lt;/P&gt;&lt;P&gt;It use LPUART0 as the boot device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope it helps!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2015 08:12:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350795#M17314</guid>
      <dc:creator>Rick_Li</dc:creator>
      <dc:date>2015-03-26T08:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-KL27Z Schematics and Bootloader Questions</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350796#M17315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Yong Li,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for the input and the schematics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my research I was unable to find where only LPUART0 is the boot device.&amp;nbsp; Section 13.4.3 of the K27 TRM does not mention that the Boot device is restricted to LPUART0.&amp;nbsp; Can you please direct me to where this assignment to only LPUART0 is mentioned in the TRM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, i&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;n the case of the MKL17Z256VFM4 (32 QFN) the LPUART0 two locations in the pinmap.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For example LPUART0_RX can be on pin 11 or 31, likewise LPUART0_TX can be on pin 12 or 32.&lt;/P&gt;&lt;P&gt;Am I obliged to use a particular RX/TX pair or does the ROM bootloader check both?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Mar 2015 16:58:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350796#M17315</guid>
      <dc:creator>adamgarrison</dc:creator>
      <dc:date>2015-03-26T16:58:05Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-KL27Z Schematics and Bootloader Questions</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350797#M17316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Adam Garrison wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;In my research I was unable to find where only LPUART0 is the boot device.&amp;nbsp; Section 13.4.3 of the K27 TRM does not mention that the Boot device is restricted to LPUART0.&amp;nbsp; Can you please direct me to where this assignment to only LPUART0 is mentioned in the TRM?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Also, i&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;n the case of the MKL17Z256VFM4 (32 QFN) the LPUART0 two locations in the pinmap.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;For example LPUART0_RX can be on pin 11 or 31, likewise LPUART0_TX can be on pin 12 or 32.&lt;/P&gt;
&lt;P&gt;Am I obliged to use a particular RX/TX pair or does the ROM bootloader check both?&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;I second this query.&amp;nbsp; I'm looking at the reference manual for the KL17 (KL17P64M48SF6RM.pdf), and one would be hard-pressed to say definitively which SPI, I2C, and LPUART pins are active within the bootloader.&amp;nbsp; In fact, there would seem to be conflicting information.&amp;nbsp; From page 185, section 13.2.9, Bootloader Exit State, detailing which registers and peripherals are not returned to their default state after a bootloader operation:&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Affected pin mux:&lt;/P&gt;
&lt;P&gt;• UART1(PTE0, PTE1)&lt;/P&gt;
&lt;P&gt;• I2C1(PTC10, PTC11)&lt;/P&gt;
&lt;P&gt;• SPI1(PTD4, PTD5, PTD6, PTD7)&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;But this is from page 190, section 13.3.3, LPUART Peripheral:&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Autobaud feature: If LPUARTn is used to connect to the bootloader, then the LPUARTn_RX (PTA1) pin must be kept high and not left floating during the detection phase in order to comply with the autobaud detection algorithm.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;So, Freescale, which is it?&amp;nbsp; I'm pretty sure from other forum posts I've read that it's LPUART0 on PTA1/2 that's used for the bootloader.&amp;nbsp; And if someone wanted to use I2C to bootload the device, can we be sure it's PTC10/11?&amp;nbsp; Those pins aren't even available on the 32-pin and 48-pin parts, only the 64-pin package.&amp;nbsp; It would be extremely useful if you would update your documentation and make it clear which communication pins are active for a given Kinetis device in the bootloader.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2015 20:35:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350797#M17316</guid>
      <dc:creator>dmarks_ls</dc:creator>
      <dc:date>2015-04-17T20:35:19Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-KL27Z Schematics and Bootloader Questions</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350798#M17317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello David Rodgers:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for the confusion caused. The technical documentation team is working on updating the manuals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The correct pinout should be this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD class="xl73" colspan="4" height="26" style="border: 0px solid black;" width="519"&gt;Pinmux&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl72" height="22" style="border: 0px solid black; border-top: none;" width="261"&gt;Port&lt;/TD&gt;&lt;TD class="xl72" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;Signal&lt;/TD&gt;&lt;TD class="xl72" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp;&amp;nbsp; Alt&lt;/TD&gt;&lt;TD class="xl72" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl69" height="21" style="border: 0px solid black;" width="261"&gt;PTA1&lt;/TD&gt;&lt;TD class="xl70" style="border: 0px solid black; border-left: none;" width="87"&gt;LPUART0_RX&lt;/TD&gt;&lt;TD class="xl70" style="border: 0px solid black; border-left: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl71" style="border: 0px solid black; border-left: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTA2&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;LPUART0_TX&amp;nbsp; &lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTB0&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;I2C0_SCL&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTB1&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;I2C0_SDA&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTC4&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;SPI0_PCS0&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTC5&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;SPI0_SCK&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl63" height="20" style="border: 0px solid black; border-top: none;" width="261"&gt;PTC6&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;SPI0_MOSI&lt;/TD&gt;&lt;TD class="xl64" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;TD class="xl65" style="border: 0px solid black; border-left: none; border-top: none;" width="122"&gt; &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl66" height="21" style="border: 0px solid black; border-top: none;" width="261"&gt;PTC7&lt;/TD&gt;&lt;TD class="xl67" style="border: 0px solid black; border-left: none; border-top: none;" width="87"&gt;SPI0_MISO&lt;/TD&gt;&lt;TD class="xl67" style="border: 0px solid black; border-left: none; border-top: none;" width="49"&gt;&amp;nbsp; ALT2&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;&lt;P&gt;Jorge Gonzalez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Apr 2015 00:15:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/350798#M17317</guid>
      <dc:creator>Jorge_Gonzalez</dc:creator>
      <dc:date>2015-04-18T00:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: FRDM-KL27Z  Using J11 with a Segger</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/1859210#M66347</link>
      <description>&lt;P&gt;The user guide section 5.3 is wrong.&lt;/P&gt;&lt;P&gt;To use a segger J-Link&amp;nbsp; or somesuch instead of the on-board SDA&lt;/P&gt;&lt;P&gt;Remove K5 RST, Remove J6 SWD-DIO, Remove J7 SWD-CLK.&amp;nbsp; KEEP J18 shorted&lt;/P&gt;&lt;P&gt;You can then go in on the 10 pin J11&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2024 13:03:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FRDM-KL27Z-Schematics-and-Bootloader-Questions/m-p/1859210#M66347</guid>
      <dc:creator>tonytonick</dc:creator>
      <dc:date>2024-05-04T13:03:20Z</dc:date>
    </item>
  </channel>
</rss>

