<?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 Feedback: SPI example for FRDM-MKL27z has MOSI/MISO reversed in readme file in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Feedback-SPI-example-for-FRDM-MKL27z-has-MOSI-MISO-reversed-in/m-p/476754#M3982</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure if this applies to the other board's examples as well. The SPI Examples have a readme file which tells you how to connect up the example. Unfortunately, the readme file is incorrect compared to the "pinmux.c" source files for SPI-0:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Readme file (incorrect) - says MISO is J2 pin 8, MOSI is J2 pin 10, for SPI0&lt;/P&gt;&lt;PRE class="c++" name="code"&gt;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ INSTANCE0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CONNECTS TO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INSTANCE1 Pin Name&amp;nbsp;&amp;nbsp; Board Location&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Pin Name&amp;nbsp; Board Location MISO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 8&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MISO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 20 MOSI&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MOSI&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 18 SCK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 12&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SCK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J1 pin 11 PCS0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PCS0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J1 pin 9 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;/PRE&gt;&lt;DIV style="display:none;"&gt; &lt;/DIV&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pinmux file (correct) - says MISO is J2 pin 10, MOSI is J2 pin 8, for SPI0&lt;/P&gt;&lt;PRE class="c++" name="code"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* SPI0 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 4U, kPORT_MuxAlt2); /* PCS0 J2-6&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 5U, kPORT_MuxAlt2); /* SCK&amp;nbsp; J2-12 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 6U, kPORT_MuxAlt2); /* MOSI J2-8&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 7U, kPORT_MuxAlt2); /* MISO J2-10 */&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; /* SPI1 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 4U, kPORT_MuxAlt2); /* PCS0 J1-9&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 5U, kPORT_MuxAlt2); /* SCK&amp;nbsp; J1-11 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 6U, kPORT_MuxAlt2); /* MOSI J2_18 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 7U, kPORT_MuxAlt2); /* MISO J2-20 */&lt;/PRE&gt;&lt;DIV style="display:none;"&gt; &lt;/DIV&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Connecting incorrectly doesn't appear to damage the board, but the SPI demo will fail.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I obtained the SDK using the custom builder to get a custom sdk for the mkl27z: "&lt;SPAN style="color: #0490c5; font-size: 18px; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;SDK_2.0_FRDM-KL27Z"&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wouldn't normally post this on the forum, but I can't find anywhere to give feedback on the SDK besides here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 03 Apr 2016 03:56:36 GMT</pubDate>
    <dc:creator>drojf</dc:creator>
    <dc:date>2016-04-03T03:56:36Z</dc:date>
    <item>
      <title>Feedback: SPI example for FRDM-MKL27z has MOSI/MISO reversed in readme file</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Feedback-SPI-example-for-FRDM-MKL27z-has-MOSI-MISO-reversed-in/m-p/476754#M3982</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure if this applies to the other board's examples as well. The SPI Examples have a readme file which tells you how to connect up the example. Unfortunately, the readme file is incorrect compared to the "pinmux.c" source files for SPI-0:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Readme file (incorrect) - says MISO is J2 pin 8, MOSI is J2 pin 10, for SPI0&lt;/P&gt;&lt;PRE class="c++" name="code"&gt;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ INSTANCE0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CONNECTS TO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; INSTANCE1 Pin Name&amp;nbsp;&amp;nbsp; Board Location&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Pin Name&amp;nbsp; Board Location MISO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 8&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MISO&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 20 MOSI&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MOSI&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 18 SCK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 12&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; SCK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J1 pin 11 PCS0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J2 pin 6&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PCS0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; J1 pin 9 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~&lt;/PRE&gt;&lt;DIV style="display:none;"&gt; &lt;/DIV&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pinmux file (correct) - says MISO is J2 pin 10, MOSI is J2 pin 8, for SPI0&lt;/P&gt;&lt;PRE class="c++" name="code"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* SPI0 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 4U, kPORT_MuxAlt2); /* PCS0 J2-6&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 5U, kPORT_MuxAlt2); /* SCK&amp;nbsp; J2-12 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 6U, kPORT_MuxAlt2); /* MOSI J2-8&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTC, 7U, kPORT_MuxAlt2); /* MISO J2-10 */&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; /* SPI1 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 4U, kPORT_MuxAlt2); /* PCS0 J1-9&amp;nbsp; */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 5U, kPORT_MuxAlt2); /* SCK&amp;nbsp; J1-11 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 6U, kPORT_MuxAlt2); /* MOSI J2_18 */ &amp;nbsp;&amp;nbsp;&amp;nbsp; PORT_SetPinMux(PORTD, 7U, kPORT_MuxAlt2); /* MISO J2-20 */&lt;/PRE&gt;&lt;DIV style="display:none;"&gt; &lt;/DIV&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Connecting incorrectly doesn't appear to damage the board, but the SPI demo will fail.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I obtained the SDK using the custom builder to get a custom sdk for the mkl27z: "&lt;SPAN style="color: #0490c5; font-size: 18px; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;"&gt;&lt;STRONG&gt;SDK_2.0_FRDM-KL27Z"&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wouldn't normally post this on the forum, but I can't find anywhere to give feedback on the SDK besides here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Apr 2016 03:56:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Feedback-SPI-example-for-FRDM-MKL27z-has-MOSI-MISO-reversed-in/m-p/476754#M3982</guid>
      <dc:creator>drojf</dc:creator>
      <dc:date>2016-04-03T03:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Feedback: SPI example for FRDM-MKL27z has MOSI/MISO reversed in readme file</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Feedback-SPI-example-for-FRDM-MKL27z-has-MOSI-MISO-reversed-in/m-p/476755#M3983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reporting this! I will forward this to our KSDK team.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Kan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2016 07:15:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Feedback-SPI-example-for-FRDM-MKL27z-has-MOSI-MISO-reversed-in/m-p/476755#M3983</guid>
      <dc:creator>Kan_Li</dc:creator>
      <dc:date>2016-04-06T07:15:19Z</dc:date>
    </item>
  </channel>
</rss>

