nRF Connect for Desktop v3.3.0 confusing messages

[Don]

Windows 8.1, 64bit PC

I have a nrf52840 app that works from "SEGGER Release 4.30  Build 2019101800.40379
Windows x64" on the DK 16.0.0, and from "nRF Connect for Desktop "on the  nrf52840 Dongle,

A) when programming the Dongle  nRF Connect for Desktop logs a confusing message:

1.  Does not need to be reloaded <SoftDevice.hex file>

2.  Does not need to be reloaded <My app.hex file>  (but displays a graphic that may be intended to indicate loading progress)

I expect Message 1

I am confused by Message 2. since immediate prior the app loaded and run was a totally different Nordic example (hrs)
I assume  Message 2  is just wrong, since the Dongle then runs my app, not the hrs app.

B) If I omit <SoftDevice.hex file> from the files to be flashed, I get prompted with a list of SoftDevice versions that does not include the one I am using (7.1.1 as I recall)

Don

[Hakon]

I assume  Message 2  is just wrong, since the Dongle then runs my app, not the hrs app.

 Does the application get flashed properly though?

 

If I omit <SoftDevice.hex file> from the files to be flashed, I get prompted with a list of SoftDevice versions that does not include the one I am using (7.1.1 as I recall)

 Have you updated nRF Connect for desktop recently? 7.1.1 is fairly new, so that could have something to do with it.

[Don]

Correction: I am using  SoftDevice  7.0.1 , and nRF Connect v3.3.0, which seems to be the latest, thanks.

[Hakon]

Okay, but from what you are saying it sounds like the application gets flashed just fine. Do you have any problems besides the nRF Connect showing an incorrect error message?

[Don]

The app works reliably, responding to commands from a web-app running in a Chrome browser on a variety of Android phones as intended,

The problem that  i have "Any special requirements for discovery by ios 13.2.2, iphone 8?" may possibly be due to the state of that particular phone, bluetooth discovery problems having been reported tor ios 13.2.2. I will eventually try another iphone. If you have suggestions about this problem, I would be grateful.

Thanks

[Einar Thorsrud]

Hi,

I don't understand the connection between this last comment and the earlier discussion. Can you elaborate?