<?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>nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22558/nrf-connect-ubuntu-gnome-17-04-blank-window</link><description>Hello everyone, 
 I&amp;#39;m usually on the cutting edge with Ubuntu Linux. I upgrade my development box frequently, because I like the precompiled binaries in the Ubuntu repository. I prefer to use my time building nRF52 apps from source, rather than building</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 07 Jul 2017 01:44:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22558/nrf-connect-ubuntu-gnome-17-04-blank-window" /><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88769?ContentTypeID=1</link><pubDate>Fri, 07 Jul 2017 01:44:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a13c4f22-6fd0-4c24-9301-a47f9526ff6b</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;It took a few weeks, but I eventually solved this problem.  I am posting the solution in hopes that someone else will benefit.&lt;/p&gt;
&lt;p&gt;Upgrading JLink V6.16b to V6.16f corrected both the JLink and nRF Connect problems. Segger was slow to approve my posting privileges in their user support forums, but they appear to be very prompt with bug fixes.&lt;/p&gt;
&lt;p&gt;If you ever have a problem with JLink, or any software that depends on it, I recommend checking Segger&amp;#39;s web site for an update.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88759?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2017 02:28:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3adb20ac-ad03-4f56-a7ec-135fd7f0f56d</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;In both cases shown above, my log output is the same:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;--------------------------------------------------------------------------------
./nrfjprog --eraseall --snr 682202220 --log
nrfjprog verion 9.5.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
JLinkARM.dll OpenEx returned error &amp;#39;Cannot connect to J-Link via USB.&amp;#39;.
FUNCTION: close_dll.
FUNCTION: close_dll.
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88763?ContentTypeID=1</link><pubDate>Thu, 15 Jun 2017 02:26:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b6aec905-b4af-4e6e-9600-93a5839a9cc5</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;In the other thread it was suggested I post my questions on the SEGGER forum.  I am waiting for their admins to approve my forum registration.&lt;/p&gt;
&lt;p&gt;In the mean time, I will post my nrfjprog results.  I upgraded to 9.5.0.  Here is a session log from my attempt to run nrfjprog from within its own folder (I haven&amp;#39;t updated PATH yet):&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;j..@j...K:~/bin/nrfjprog$ ./nrfjprog -i
682202220
j..@j...K:~/bin/nrfjprog$ ./nrfjprog --eraseall --log
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
j..@j...K:~/bin/nrfjprog$ ./nrfjprog --eraseall --snr 682202220 --log
&amp;lt;same 3 error lines as above&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88760?ContentTypeID=1</link><pubDate>Wed, 14 Jun 2017 07:37:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:87aa03dc-a557-4a68-84e5-c4b73c5ffa8d</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;It sounds like the JLink issue is related.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I would suggest upgrading to the
latest &lt;a href="http://www.nordicsemi.com/eng/nordic/Products/nRF52832/nRF5x-Command-Line-Tools-Linux64/51388"&gt;command line
tools&lt;/a&gt;
(9.5.0).&lt;/li&gt;
&lt;li&gt;If the connectivity firmware is not discovered on the board, you will get asked to flash it when you connect the device in nRF Connect. Erasing the chip will bring this dialog up again and make sure you got the correct firmware.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88761?ContentTypeID=1</link><pubDate>Wed, 14 Jun 2017 01:49:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:446ba085-2cdd-4a21-bbb7-5172ba1090ea</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;I&amp;#39;m back again.  I appear to have a more fundamental problem.  I never tried JLink itself from Linux after the OS upgrade.  It is also not working!&lt;/p&gt;
&lt;p&gt;This problem could be connected to the problem that I am reporting here, but it&amp;#39;s different enough that I thought I should &lt;a href="https://devzone.nordicsemi.com/question/151080/jlink-works-on-win10-but-not-on-ubuntu-gnome-1704/"&gt;start a new thread&lt;/a&gt; to discuss it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88762?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 22:32:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c59d50a3-32ba-46f9-b7b2-eebff72b3a28</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;Hello again, Jørgen.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure what Google Chrome has to do with anything.  I am already using Chromium version 58.0.3029.110.&lt;/p&gt;
&lt;p&gt;I upgraded JLink from V6.16, compiled 2017-06-02, to V6.16b, compiled 2017-06-09.  V6.16b wasn&amp;#39;t even released as of your last message.&lt;/p&gt;
&lt;p&gt;I need to ask a few questions before erasing the board.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;I have nrfjprog 8.3.0, it&amp;#39;s about a year old.  I suspect that I should update it.  Where do I find it?&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The first time I ran nRF Connect on Ubuntu 16.04, I remember seeing a dialog box which reported a firmware upgrade.  The details were not important to me at that time.  But is it possible that I already have the current firmware?&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Thanks again for your continued assistance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88768?ContentTypeID=1</link><pubDate>Wed, 07 Jun 2017 12:09:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7ab4704-d732-4ee8-9cd7-973777fb8e87</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Could you try the following (if you have not allready):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Install Google Chrome and all dependecies.&lt;/li&gt;
&lt;li&gt;Install &lt;a href="https://www.segger.com/downloads/jlink"&gt;latest JLink driver&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Erase the board using nrfjprog &lt;code&gt;eraseall&lt;/code&gt; command.&lt;/li&gt;
&lt;li&gt;Upgrade &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/development/nrf52_dev_kit/int_mcu_firmw.html?cp=2_2_2_4_2"&gt;JLink Interface FW&lt;/a&gt; to latest version.&lt;/li&gt;
&lt;li&gt;Program the connectivity HEX file directly using nrfjprog. The file (for PCA10040) can be found in &lt;code&gt;nrf-connect-linux-x64/resources/app/node_modules/nrfconnect-appmodule-ble/node_modules/pc-ble-driver-js/pc-ble-driver/hex/sd_api_v3&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88767?ContentTypeID=1</link><pubDate>Tue, 06 Jun 2017 22:19:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e56bba19-c2de-4717-ba3f-3b539f8d3e47</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;One last thing.  My development box is a dual-boot, Windows 10 and Ubuntu system.  I just installed JLink and nRF Connect on Windows 10.  It works without errors.  The problem is software, not hardware.  I can boot into Windows when I need to do BLE work for now, but in the long run I would also like nRF Connect working on top of Ubuntu Gnome 17.04.  Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88766?ContentTypeID=1</link><pubDate>Tue, 06 Jun 2017 20:44:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:519ea97d-cd37-45ad-82e9-6fde9c517937</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;Item 3:&lt;/p&gt;
&lt;p&gt;/home/john/bin/nrf-connect-linux-x64/resources/app/node_modules/nrfconnect-appmodule-ble/node_modules/fbjs/lib/warning.js:36&lt;/p&gt;
&lt;p&gt;Warning: Using Maps as children is not yet fully supported. It is an experimental feature that might be removed. Convert it to a sequence / iterable of keyed ReactElements instead. Check the render method of &lt;code&gt;DiscoveredDevices&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Item 4:&lt;/p&gt;
&lt;p&gt;bundle.js:8483&lt;/p&gt;
&lt;p&gt;Database is not ready yet. Storing entries in queue for later storage in DB.&lt;/p&gt;
&lt;p&gt;Finally, when I try to connect to my PCA10040 board with the console log open, I see a popup window that was not visible with the console log closed.  It reads:&lt;/p&gt;
&lt;p&gt;DevTools was disconnected from the page.  Once page is reloaded, DevTools will automatically reconnect.&lt;/p&gt;
&lt;p&gt;Hope that helps.  Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88765?ContentTypeID=1</link><pubDate>Tue, 06 Jun 2017 20:40:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31481958-e5c5-4599-9cb1-f209951e59da</guid><dc:creator>Ladasky</dc:creator><description>&lt;p&gt;Thanks for your reply, Jørgen.  I didn&amp;#39;t know about the console log window.  It does not appear that I can post a screen shot, so I will have to type what I saw, and it may run longer than one post.&lt;/p&gt;
&lt;p&gt;Item 1 in the console log:&lt;/p&gt;
&lt;p&gt;/home/john/bin/nrf-connect-linux-x64/resources/app/node_modules/nrfconnect-appmodule-ble/node_modules/react/lib/ReactDOM.js:75&lt;/p&gt;
&lt;p&gt;Download the React DevTools and use an HTTP server (instead of a file: URL) for a better development experience: &lt;a href="https://fb.me/react-devtools"&gt;https://fb.me/react-devtools&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Item 2:&lt;/p&gt;
&lt;p&gt;bundle.js:8483&lt;/p&gt;
&lt;p&gt;Database is not ready yet. Storing entries in queue for later storage in DB.&lt;/p&gt;
&lt;p&gt;(to be continued)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect, Ubuntu Gnome 17.04, blank window</title><link>https://devzone.nordicsemi.com/thread/88764?ContentTypeID=1</link><pubDate>Tue, 06 Jun 2017 09:18:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:870c0720-dfbf-4382-8b94-f1ab780205ed</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Can you open the console log window by clicking &lt;code&gt;Shift + Ctrl + i&lt;/code&gt; in nRF Connect, and see if there are any errors reported?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>