nRF Connect, Ubuntu Gnome 17.04, blank window

[Ladasky]

Hello everyone,

I'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 Linux apps from source.

I just upgraded to Ubuntu Gnome 17.04. I also have nRF Connect v 1.1.1. I have a PCA10040 board connected to a USB port, to use as a BLE receiver.

I had everything working in 16.04, save for a mysterious, but apparently harmless, JavaScript error message which occurred when I closed nRF Connect (click here if you're interested).

On 17.04, nRF Connect starts up correctly. The Select serial port pull down menu shows my PCA10040 board attached to /dev/tty/ACM0. However, when I select that board, the whole nRF Connect window goes... blank.

Please advise, thanks.

[Ladasky]

Hello again, Jørgen.

I'm not sure what Google Chrome has to do with anything. I am already using Chromium version 58.0.3029.110.

I upgraded JLink from V6.16, compiled 2017-06-02, to V6.16b, compiled 2017-06-09. V6.16b wasn't even released as of your last message.

I need to ask a few questions before erasing the board.

1. I have nrfjprog 8.3.0, it's about a year old. I suspect that I should update it. Where do I find it?

2. 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?

Thanks again for your continued assistance.

[Ladasky]

I'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!

This problem could be connected to the problem that I am reporting here, but it's different enough that I thought I should start a new thread to discuss it.

[Jørgen Holmefjord]

It sounds like the JLink issue is related.

1. I would suggest upgrading to the latest command line tools (9.5.0).
2. 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.

[Ladasky]

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.

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't updated PATH yet):

[email protected]:~/bin/nrfjprog$ ./nrfjprog -i
682202220
[email protected]:~/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.
[email protected]:~/bin/nrfjprog$ ./nrfjprog --eraseall --snr 682202220 --log
<same 3 error lines as above>

[Ladasky]

In both cases shown above, my log output is the same:

--------------------------------------------------------------------------------
./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 'Cannot connect to J-Link via USB.'.
FUNCTION: close_dll.
FUNCTION: close_dll.