<?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 Cannot be Connected</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38580/jlink-cannot-be-connected</link><description>Hello, 
 I am trying to use nrf5280dk with RIOT OS and Contiki OS. I am following these steps to enable access to the device from os. https://devzone.nordicsemi.com/b/blog/posts/setting-up-ipv6-over-ble-using-nrf52-series-and-ri 
 and 
 https://devzone</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 Sep 2018 04:16:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38580/jlink-cannot-be-connected" /><item><title>RE: JLINK Cannot be Connected</title><link>https://devzone.nordicsemi.com/thread/149332?ContentTypeID=1</link><pubDate>Wed, 19 Sep 2018 04:16:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbdfe413-2a83-44a1-a1eb-c0cff776d6ed</guid><dc:creator>Navneet</dc:creator><description>&lt;p&gt;Hey Paul, thanks for the insight. Actually, the issue was that the toolchain was not upgraded&amp;nbsp;to v7. Even a fresh install via Linux cmd was resulting in v6.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Cannot be Connected</title><link>https://devzone.nordicsemi.com/thread/149133?ContentTypeID=1</link><pubDate>Tue, 18 Sep 2018 02:47:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a52bda61-385d-4a3b-b35b-6a8b280f4a06</guid><dc:creator>paul</dc:creator><description>&lt;p&gt;Hi Navneet,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;I think that the soft/hard thing refers to how the floating point is handled. Some arm processors&amp;nbsp;can do floating point in hardware otherwise gcc adds software support.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you hang around here long enough you will find out that relatively recently Nordic moved from pushing an IDE called IAC and another called Keil to pushing a new one called Segger Embedded studio (often abreviated to SES). When I say pushing, you can use whatever you like and people, including Nordic, will try and help you, but that is now the default. It was also built in consultation with this forum and Nordic so possibly supports the nordic chips the best.&lt;/p&gt;
&lt;p&gt;Because you are using a nordic chipset, you can get a free license for SES and download it. Things that I hate about it are that it uses all its own libraries etc - one mistake I made was to try and mix in some standard Linux libs. Secondly it tends to put every file in the root directory. Thirdly you have to essentially list every file you use which makes starting hard especially if you are building off a Nordic example and want to move the code.&lt;/p&gt;
&lt;p&gt;I am very much a newbie with only about 6 weeks in this environment.&lt;/p&gt;
&lt;p&gt;Cheers Paul&lt;/p&gt;
&lt;p&gt;BTW generally best to start a new thread when you have a new question - makes it easier for the searchers who follow.&lt;/p&gt;
&lt;p&gt;BTW2 Nordic tends to chime in on unanswered posts after a couple of days - all cudos to them.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Cannot be Connected</title><link>https://devzone.nordicsemi.com/thread/149126?ContentTypeID=1</link><pubDate>Tue, 18 Sep 2018 00:29:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca1387cd-d68e-4630-a960-f13d256c7f66</guid><dc:creator>Navneet</dc:creator><description>&lt;p&gt;Hey Paul, actually virtual is having some issue. So, switched to VMWare and it worked. I have another question though.&lt;/p&gt;
&lt;p&gt;There seems to a conflict between toolchain/device and RIOT OS (hard compilation vs soft compilation).&amp;nbsp;Does anything&amp;nbsp;come to&amp;nbsp;your&amp;nbsp;mind? I am using GCC ARM toolchain.&lt;/p&gt;
&lt;p&gt;Is there a particular toolchain&amp;nbsp;I should install to make it work? Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: JLINK Cannot be Connected</title><link>https://devzone.nordicsemi.com/thread/148891?ContentTypeID=1</link><pubDate>Mon, 17 Sep 2018 02:20:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c15eb5b-eeb9-4780-8ad4-90dc924f09f3</guid><dc:creator>paul</dc:creator><description>&lt;p&gt;Hi Navneet. Two things spring to mind. Firstly are other USB devices able to be seen from these two OS&amp;#39;s. I know I have been bitten by problems with USB support into a VM in the past. Secondly I have found the physical USB connection on the DK board to be a bit sub par. Make sure you plug into a USB 3 socket - more current. Secondly ensure there is no strain on the plugs either end - cable is loose and not bent. Finally try another cable.&lt;/p&gt;
&lt;p&gt;hope this helps&lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>