<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>regarding SPI communication</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/41001/regarding-spi-communication</link><description> 
while interfacing SPI with EEPROM we generally send some commands
before writing or reading 
how does slave differentiates that incoming data is DATA or Address
or COMMAND? 
 </description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: regarding SPI communication</title><link>https://community.arm.com/thread/108279?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 17:18:09 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f906cb42-8850-41f9-8c55-a26acf566e21</guid><dc:creator>Gary Olson</dc:creator><description>&lt;p&gt;&lt;p&gt;
Keil has a SPI program for the LPC2148, the part it is to
interface with is a&lt;br /&gt;
Atmel AT25160 SPI EEPROM. Here is the datasheet for that part.&lt;/p&gt;

&lt;p&gt;
&lt;a href="http://www.atmel.com/Images/doc0675.pdf"&gt;www.atmel.com/.../doc0675.pdf&lt;/a&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: regarding SPI communication</title><link>https://community.arm.com/thread/93449?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 11:11:43 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:df67457f-6dbe-4748-bd6a-f88e88d28e16</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Note that the slave-select signal is normally extremely important
for the SPI listener to synchronize the internal state machine. A
single spurious clock pulse would totally confuse a SPI slave about
what the next bit received would mean. And it&amp;#39;s critical for SPI to
have a way to reset the slave state machine since SPI is a
synchronous protocol where the slave counts bits to keep track of the
state.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: regarding SPI communication</title><link>https://community.arm.com/thread/63830?ContentTypeID=1</link><pubDate>Tue, 16 Jun 2015 10:34:49 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:953feec5-4d75-46d4-8ccb-d0a5afd98730</guid><dc:creator>&amp;#178;erik malund</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;how does slave differentiates that incoming data is DATA or
Address or COMMAND&lt;/i&gt;&lt;br /&gt;
exactly as described in the EEPROM datasheet.&lt;/p&gt;

&lt;p&gt;
If you want someone to read the datasheet for you, you need to
specify the part number of your EEPROM (they do not all do it the
same way)&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>