<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/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/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23355/nrf8001-interpreting-logic-data</link><description>I&amp;#39;m running the ble_my_project_template example from ble-sdk-arduino , and listening to the ACI lines with a logic analyzer. Here is what I found in the first transmission, in which RDY is pulled low before REQ. One row for each byte transferred. 
 </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 Aug 2017 07:29:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23355/nrf8001-interpreting-logic-data" /><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91823?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2017 07:29:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f5e1ff1-d327-4ccc-b017-5efe479650d3</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;No. on the MOSI line there is no debug byte. So the first packet is the length = 0. The second is what is left in the spi buffer on your controller.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91822?ContentTypeID=1</link><pubDate>Tue, 22 Aug 2017 19:33:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b57ca613-5384-4d85-840f-69e513cd7a6c</guid><dc:creator>Erlend</dc:creator><description>&lt;p&gt;Thanks for the answer. But what does the second value of MOSI mean then (15, in the original post)? Is Master really sending a packet of 15 bytes?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91818?ContentTypeID=1</link><pubDate>Fri, 11 Aug 2017 14:40:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dab77f5b-cead-47ba-95d2-216681931232</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;The nRF8001 will always send a device started event after power on reset. Usually with a started in setup mode event, but this could also be a standby event, if the configuration was previously writen to OTP. MOSI will use a lenght of 0 as it doesn&amp;#39;t have anything to send to the slave in this case. it should use the length field of the received packet to see how many bytes it needs to clock out. What follow after the 0 depends on what is in the MOSI buffer, as long as the length is zero the nRF8001 doesn&amp;#39;t care about this. Of course you could clear the whole buffer as well, but it&amp;#39;s not needed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91821?ContentTypeID=1</link><pubDate>Sun, 09 Jul 2017 13:13:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1edd549e-baaf-4ee1-873a-8b05fc047024</guid><dc:creator>Erlend</dc:creator><description>&lt;p&gt;Doing the logic capture after Uploading the code, the decoded data makes more sense: This time MISO starts with (after the first byte (1)) &lt;code&gt;4, 129, 2, 0, 2&lt;/code&gt; which is as expected. But MOSI still starts with &lt;code&gt;0, 15, 180 ...&lt;/code&gt; which makes no sense to me.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91820?ContentTypeID=1</link><pubDate>Sun, 09 Jul 2017 13:06:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a977672-dfab-49ee-89d4-070f89e0d342</guid><dc:creator>Erlend</dc:creator><description>&lt;p&gt;Now I see that when I press Reset to start everything again (as I do when I start Logic capture), I get errors in serial output:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Evt Device Started: Standby
Advertising started
Evt Device Started: Standby
HW error: 572
ll_ctrl.s0.c�⸮⸮⸮u1 ���
Advertising started
Evt Device Started: Standby
HW error: 572
ll_ctrl.s0.c�⸮⸮⸮u1 ���
Advertising started
Evt Device Started: Standby
HW error: 572
ll_ctrl.s0.c�⸮⸮⸮u1 ���
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;ETC&lt;/p&gt;
&lt;p&gt;But when I restart the arduino by uploading the program it works like in the original post.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF8001: interpreting logic data</title><link>https://devzone.nordicsemi.com/thread/91819?ContentTypeID=1</link><pubDate>Sun, 09 Jul 2017 13:01:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54c2f7ef-fb6a-485e-ae99-e18fb5e77fe8</guid><dc:creator>Erlend</dc:creator><description>&lt;p&gt;I would expect the first byte of MOSI to be 5, which is the length of Connect command (15).&lt;/p&gt;
&lt;p&gt;This is the serial output:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;Arduino setup
Evt Device Started: Setup
Evt Device Started: Standby
Advertising started
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I&amp;#39;m also puzzled that Evt Device Started happens with &lt;code&gt;mode = Setup&lt;/code&gt;. In the decoding done by Logic (with LSBit first, 8 bits per transfer, CPOL = CPHA = 0, Enable line is active low, and using RDY as enable line) there are no &lt;code&gt;129&lt;/code&gt; followed by &lt;code&gt;2&lt;/code&gt; that makes this possible. Decoded logic data: &lt;a href="https://bpaste.net/show/252237975ab0"&gt;bpaste.net/.../252237975ab0&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>