nRF Connect for PC v1.0, updating connectivity firmware

[mrono]

Hi. I'm using NRF Connect v1.0 on a Windows 10 PC, together with an nRF52-DK (PCA10040). It works nicely with the connectivity firmware 1.0.0 that the PC app offers to flash to the DK.

If I update the firmware of the DK with either of the v1.1.0 precompiled hex files from the pc_ble_driver -project, NRF Connect no longer communicates with the DK.

Using the sd_api_v3 hex file, I get a flood of internal errors as soon as I select the COM port from the NRF Connect app:

Enabling BLE failed. (NRF_ERROR_INTERNAL)

Error occured when enabling SoftDevice. Errorcode: NRF_ERROR_INTERNAL (0x3)

With the sd_api_v2 hex file, I get an NRF_ERROR_TIMEOUT instead.

Is this even supposed to work? Or am I doing something wrong?

[Hung Bui]

Hi Mrono,

Could you tell why you want to update the hex ?

The current version of nRFConnect is not compatible with v3 hex file. On v2, we removed support for S132. You may want to wait for the next nRFConnect release.

[mrono]

My goal here is to profile the power consumption of a peripheral that sends larger data packets, using MTU size extension available with SDv3. A PC app would have been the easiest central to test this with. I thought that I could get the central to support longer MTUs and DLE simply by updating the connectivity firmware.

Since I posted this question I have realized that this probably wouldn't have worked anyway, as the features require more RAM to be allocated for the softdevice. I assume the precompiled hex files don't have this even if the PC app supported the v3 softdevice.

Anyway, I saw a few posts on this forum where updating the firmware to 1.0.1(?) was recommended, so I thought 1.1.0 should work also. That's why I asked if what I'm trying to do should work.