<?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>LPC MicrocontrollersのトピックRe: LPC SPI</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833057#M33241</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" class="" data-content-finding="Community" data-userid="327842" data-username="sveer9211@gmail.com" href="https://community.nxp.com/people/sveer9211@gmail.com"&gt;Lakhbir Singh&lt;/A&gt;,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;I'd highly recommend you to visualize the SPI wave via the oscilloscope or logic analyzer when writing or reading SPI flash, then comparing with the standard process which is illustrated in SPI flash's datasheet, it will help you to figure the root cause out.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&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>Tue, 09 Oct 2018 03:11:48 GMT</pubDate>
    <dc:creator>jeremyzhou</dc:creator>
    <dc:date>2018-10-09T03:11:48Z</dc:date>
    <item>
      <title>LPC SPI</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833056#M33240</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Sir,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;I am currently working on the&amp;nbsp; LPC1549 SPI protocol . i want to interface&amp;nbsp; a SPI flash to the&amp;nbsp; LPC1549&amp;nbsp;&lt;/P&gt;&lt;P&gt;i am able to read the Manufacture ID and&amp;nbsp; JEDEC ID but reading and writing of bytes or pages in not possible .&lt;/P&gt;&lt;P&gt;kindly give me some direction to proceed&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Oct 2018 04:07:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833056#M33240</guid>
      <dc:creator>sveer9211</dc:creator>
      <dc:date>2018-10-08T04:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: LPC SPI</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833057#M33241</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A _jive_internal="true" class="" data-content-finding="Community" data-userid="327842" data-username="sveer9211@gmail.com" href="https://community.nxp.com/people/sveer9211@gmail.com"&gt;Lakhbir Singh&lt;/A&gt;,&lt;BR /&gt;Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.&lt;BR /&gt;I'd highly recommend you to visualize the SPI wave via the oscilloscope or logic analyzer when writing or reading SPI flash, then comparing with the standard process which is illustrated in SPI flash's datasheet, it will help you to figure the root cause out.&lt;BR /&gt;Have a great day,&lt;BR /&gt;TIC&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>Tue, 09 Oct 2018 03:11:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833057#M33241</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2018-10-09T03:11:48Z</dc:date>
    </item>
    <item>
      <title>Re: LPC SPI</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833058#M33242</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The usual trap for the unwary is the "write enable" command. This has to be sent before EVERY write instruction.&lt;/P&gt;&lt;P&gt;CS low - send 0x06 - CS high.&lt;/P&gt;&lt;P&gt;Then send the write command:&lt;/P&gt;&lt;P&gt;CS low&amp;nbsp; - send 0x02, send the address, send the data - CS high.&lt;/P&gt;&lt;P&gt;Also, there is generally a limit on how much data you can send it one go.&lt;/P&gt;&lt;P&gt;And on SOME devices, pin 3 (Write protect) has a pull up, so you can leave it floating, and on OTHER devices it doesn't, so it won't write unless it is connected to V+.&lt;/P&gt;&lt;P&gt;Read isn't usually a problem, it will read 0xFF if it is new.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Oct 2018 10:07:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833058#M33242</guid>
      <dc:creator>ianbenton</dc:creator>
      <dc:date>2018-10-10T10:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: LPC SPI</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833059#M33243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks all for the reply i got SPI in working condition&amp;nbsp; again thanks to all who responce in mean time .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Nov 2018 04:30:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC-SPI/m-p/833059#M33243</guid>
      <dc:creator>sveer9211</dc:creator>
      <dc:date>2018-11-10T04:30:36Z</dc:date>
    </item>
  </channel>
</rss>

