<?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>JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14428/jlink-disconnecting-or-just-a-bug</link><description>I&amp;#39;ve either got a bug in my code or the JLINK connection is dying. Either way it&amp;#39;s a real headache to pinpoint and discover how to resolve. Knowing more about extracting info from the JLINK Log would probably be helpful in these cases. 
 Within Crossworks</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Jun 2016 13:58:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14428/jlink-disconnecting-or-just-a-bug" /><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55130?ContentTypeID=1</link><pubDate>Tue, 14 Jun 2016 13:58:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a56b7978-e32e-48fc-913a-793028edbb59</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;I reported it in the thread. Although I&amp;#39;m a little in doubt if it belongs there as technically it is not an SDK bug, but rather a hardware bug in the nRF52. The SDK team chose (inconveniently) to remove the feature from the nRF51 part of the driver as well for consistency. However, they are aware of it and they miss the feature too. So maybe one day it will be back.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55129?ContentTypeID=1</link><pubDate>Mon, 13 Jun 2016 16:14:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:19f13ba5-142f-4b3a-835b-af6b1e51952f</guid><dc:creator>kevray</dc:creator><description>&lt;p&gt;Thanks. Can we update the SDK11 known issues list with this until it&amp;#39;s fixed?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55128?ContentTypeID=1</link><pubDate>Mon, 13 Jun 2016 06:50:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de45cacc-708a-4c20-bf9b-5a2aa81deab8</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Unfortunately we don&amp;#39;t have any migration guides, but I guess you can look in the SDK 10 examples or maybe this &lt;a href="https://github.com/Martinsbl/twi-find-devices-on-bus"&gt;simple example&lt;/a&gt;. I believe the look and feel of the drivers are quite similar, but some of the functions take some different parameters and the event handler &amp;quot;redesigned&amp;quot; when moving from SDK 10 to 11. However, in my experience it isn&amp;#39;t that hard to port.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55127?ContentTypeID=1</link><pubDate>Sun, 12 Jun 2016 19:59:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7fb021e-eab9-4cae-b010-d5a4607e3973</guid><dc:creator>kevray</dc:creator><description>&lt;p&gt;Thanks Martin. Can you point me to a post about swapping the driver from SDK10? Or is it just a drop in of nrf_drv_twi.* from that SDK?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55126?ContentTypeID=1</link><pubDate>Sun, 12 Jun 2016 15:33:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f40a77a-1f8e-4572-ab51-c4c5b3812314</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;I&amp;#39;m glad you solved your problem. The TWI issue is briefly discussed &lt;a href="https://devzone.nordicsemi.com/question/82256/multiple-nrf_drv_twi_tx-fails-in-nrf52/"&gt;here&lt;/a&gt; and &lt;a href="https://devzone.nordicsemi.com/question/68741/twi-issue-migrating-sdk8-sdk11/"&gt;here&lt;/a&gt; if someone is interested. It is related to the nRF52 hardware, but since you are using nRF51 you can work around it by using the drivers from SDK 10.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Disconnecting? Or just a bug?</title><link>https://devzone.nordicsemi.com/thread/55125?ContentTypeID=1</link><pubDate>Sat, 11 Jun 2016 21:46:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32e6ee96-72b4-44b8-8789-7fcc1ad1e712</guid><dc:creator>kevray</dc:creator><description>&lt;p&gt;Updated JLINK to v512f -- (v512g crashes). Updated Crossworks. Reflashed the nrf51-DK. Problem went away.&lt;/p&gt;
&lt;p&gt;Updated SDK9-&amp;gt;SDK11 and found out TWI is broken again. :(&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&amp;quot;The new SDK 11 TWI driver is not able
to do two transmits without repeating
the ADDRESS + Write bit byte. Hence we
need to merge the MPU register address
with the buffer and then transmit all
as one transmission.&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>