nRF Connect for Desktop Bluetooth Low Energy - Keeps on saying "Device must be programmed"

[andreasd]

Hello,

I'm using the nRF Connect for Desktop Bluetooth Low Energy Standalone app version v4.0.4 with a PCA10056 (Rev. 3.0.0).

The DK has "one of those newer" NRF52840 chips on it which switch on APPPROTECT by default.

I guess this is the reason the application says "Device must be programmed" every time (1). However, if I click yes, the popup will simply disappear after a short while, nothing further will happen.

(1) To fix the problem properly, I have to enter "nrfjprog --recover" on the command line, and after the command is finished, I can select the DK in the nRF Connect for Desktop Bluetooth Low Energy app again, and when I confirm the programming, this time it will program the DK properly, and afterwards show the "nRF5x" box in the connection map.

But as soon as I power off or disconnect the DK, the problem begins anew. The Desktop will say again that "the device needs to be programmed".

The OS is Windows 11, 64bit (Build 22621).

[Edvin]

Hello,

I see what you mean. I have not tested any of the new DKs with nRF Connect for Desktop -> Bluetooth LE before. I am currently at a remote office, so I can't physically access the DKs. I will test when I get in the office on Monday, and let you know.

Thank you for reporting, and stay tuned!

Have a nice weekend!

Best regards,

Edvin

[Edvin]

I see the same as you see. I am able to use it using the --recover, but I need to do it after every power cycle, which is a bit unfortunate. I see that this is reported a couple of times by different users. I have asked our internal nRF Connect for Desktop team about this in an internal ticket. 

BR,

Edvin

[ShaolinZhang]

Hi Edvin

        Could you tell me how to use "--recover", I also can not use nRF52840 DK with Bluetooth Low Energy.

[ShaolinZhang]

Hi Edvin:

       I see,I should use nrf-command-line-tools,

[Mike Austin (LPI)]

Any improved resolution to this?  I've just come unstuck with this problem and the above approach does work, but its not ideal :-(

[Edvin]

Hello,

Unfortunately there has not been any progress on this yet. The reason is that the Bluetooth Low Energy module in nRF Connect for Desktop is in maintenance mode, becuase it is based on old FW (SoftDevice from nRF5 SDK). But seeing as this affects all new DKs and dongles, I imagine they will provide a patch for this. This is only speculations, though.

BR,

Edvin

[Mike Austin (LPI)]

Ok, thanks Ervin.

Even doing the recovery I was still having issues with 4.0.4 in that it wasn’t allowing my DK to start scanning.

j ended up uninstalling and installing 4.0.1 and that seems to work for what I want

Cheers,

Mike