No signal when connecting the DK after starting RSSI Viewer

[SebastianBoe]

Hi,

I'm not getting a signal.

Not sure what I could be doing wrong ...

You don't need to have a device advertising to guarantee that some noise will be registered, or?
And there is no GO button that I'm not seeing, or?

sebo@mach:~/Downloads/nrfconnect-2.2.1$ ./nrfconnect
Gtk-Message: Failed to load module "overlay-scrollbar"
[14:23:50:0059] [warn] Not checking for nRF Connect updates. Auto update is not yet supported for this platform.
Created new window in existing browser session.
[11309:11346:0112/142431.909435:ERROR:browser_gpu_channel_host_factory.cc(107)] Failed to launch GPU process.

14:26:10.8900 Application data folder: /home/sebo/.config/nrfconnect
14:28:04.8600 /dev/ttyACM0 is open

[IvanSanchez]

@SebastianBoe What kind of devkit are you using? An you're on Linux, right?

[SebastianBoe]

Hah, rebooted nrfconnect and it worked.

Perhaps it doesn't work if the DK does not already have the FW flashed.

PC10040

Ubuntu 16.04.

[SebastianBoe]

Logs from first and second boot.

sebo@mach:~/Downloads/nrfconnect-2.2.1$ ./nrfconnect 
Gtk-Message: Failed to load module "overlay-scrollbar"
[14:23:50:0059] [warn] Not checking for nRF Connect updates. Auto update is not yet supported for this platform.
Created new window in existing browser session.
[11309:11346:0112/142431.909435:ERROR:browser_gpu_channel_host_factory.cc(107)] Failed to launch GPU process.
sebo@mach:~/Downloads/nrfconnect-2.2.1$ ./nrfconnect 
Gtk-Message: Failed to load module "overlay-scrollbar"
[14:37:37:0888] [warn] Not checking for nRF Connect updates. Auto update is not yet supported for this platform.

[SebastianBoe]

Only difference is the gpu error. Don't know if it's related though.

[SebastianBoe]

In addition to the signal not showing, the LED button wasn't working on the first boot. Now it is.

[IvanSanchez]

nrfconnect is supposed to check that the right firmware is already in the devkit, and offer a GUI dialog (puts nothing in the log, though).

You might encounter scenarios where the serial port (/dev/ttyACM0) cannot be opened, or is claimed by ModemManager, or is lacking permissions.

Is this reproducible? I mean: Does the problem keep happening after unplugging the devkit, closing nrfconnect and starting everything again?

[SebastianBoe]

nrfconnect is supposed to check that the right firmware is already in the devkit, and offer a GUI dialog (puts nothing in the log, though).

It did.

Is this reproducible? I mean: Does the problem keep happening after unplugging the devkit, closing nrfconnect and starting everything again?

Let me try to reproduce ...

[SebastianBoe]

Yep, was able to reproduce.

When I connect the devkit AFTER booting RSSI Viewer I don't get a signal.
When I connect the devkit BEFORE booting RSSI Viewer I get a signal.

[SebastianBoe]

@IvanSanchez : This is what I was talking about when discussing udev. Don't know if it is related to any of this though.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jlink-software-and-documentation#n52

[IvanSanchez]

I can reproduce, kinda.

It seems that there is a noticeable (~2sec) delay between the serial port being opened, and data starting to come. And this delay only shows up whenever first launching nrfconnect then powering up the devkit. I'm gonna guess you're experiencing a similar problem, or that there is a race condition that's affecting your hardware in a slightly different way.

[bencefr]

Closing due to inactivity.