<?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: LPC 1857 SSP0 issue when using P1_1 as MISO in LPC Microcontrollers</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534063#M10750</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcmunich on Thu May 19 07:29:27 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi Manikandan,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When you are using P1_1 as SSP0_MISO, you should not tie it to HIGH or LOW.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;So just remove the on-board boot status jumper completely and test it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;One more thing, on Keil MCB1857 board P1_1 is also connected to the external memories.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And this might affect SSP/SPI functionality, so you should try isolating these connections if you are not using these external memories.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But considering the effort/complexity, I would suggest you to use PF_2 or any other pin for SSP0_MISO function.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jun 2016 18:21:39 GMT</pubDate>
    <dc:creator>lpcware</dc:creator>
    <dc:date>2016-06-15T18:21:39Z</dc:date>
    <item>
      <title>LPC 1857 SSP0 issue when using P1_1 as MISO</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534062#M10749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by Manikandan_108 on Thu May 05 01:59:06 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi NXP support team,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using Keil MCB1857 Evaluation Board and i have configured SSP0 as below:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;P3_0 =&amp;gt; clock&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;P1_0 =&amp;gt; CS&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;P1_1 =&amp;gt; MISO&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;P1_2 =&amp;gt; MOSI&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;configured as SSP_MODE_MASTER,SSP_BITS_8, SSP_FRAMEFORMAT_SPI, SSP_CLOCK_CPHA1_CPOL0, speed 3 MHZ.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Issue:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As a master SSP0 writes data in the bus which is correctly received at the slave end hence, no issue on the MOSI but, when reads data from the slave, data is always 0xFF. Upon probing the MISO line on a CRO, data comes properly on the CRO but, data register always reads 0xFF. When i used a different pin[PF_2] for MISO then, the data register is reading the correct values.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Chip_SCU_PinMuxSet(0xf, 2, (SCU_MODE_INACT | SCU_MODE_INBUFF_EN | SCU_MODE_ZIF_DIS | SCU_MODE_FUNC2)); =&amp;gt; Working case&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Chip_SCU_PinMuxSet(0x1, 1, (SCU_MODE_INACT | SCU_MODE_INBUFF_EN | SCU_MODE_ZIF_DIS | SCU_MODE_FUNC5 )); =&amp;gt; Not working case&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Since P1_1 is also a boot status pin, I tried both high and low of the P1_1 on board jumper but didn't help, Any special configuration is required to use P1_1 as MISO for SSP0 ? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Manikandan.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:21:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534062#M10749</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: LPC 1857 SSP0 issue when using P1_1 as MISO</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534063#M10750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;STRONG&gt;Content originally posted in LPCWare by lpcmunich on Thu May 19 07:29:27 MST 2016&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;Hi Manikandan,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When you are using P1_1 as SSP0_MISO, you should not tie it to HIGH or LOW.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;So just remove the on-board boot status jumper completely and test it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;One more thing, on Keil MCB1857 board P1_1 is also connected to the external memories.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And this might affect SSP/SPI functionality, so you should try isolating these connections if you are not using these external memories.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But considering the effort/complexity, I would suggest you to use PF_2 or any other pin for SSP0_MISO function.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 18:21:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534063#M10750</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-15T18:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: LPC 1857 SSP0 issue when using P1_1 as MISO</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534064#M10751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;bump&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 19 Jun 2016 01:10:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-1857-SSP0-issue-when-using-P1-1-as-MISO/m-p/534064#M10751</guid>
      <dc:creator>lpcware</dc:creator>
      <dc:date>2016-06-19T01:10:04Z</dc:date>
    </item>
  </channel>
</rss>

