nRF52840 Dongle firmware programming for nRF Connect v2.6.2

[Gregor]

We bought a handful of nRF52840 Dongles and want to develop firmware based on the nRF Connect BLE app + nRF connectivity firmware reference design.

I am using v2.6.2 of the app and SDK version 15.3.0_59ac345.

When I open the nRF Connect BLE app and connect the dongle, the app asks to perform a firmware update, which is successful. Everything behaves as expected and I'm able to scan for devices.

I wish to be able to also:

1) Load the pre-compiled connectivity hex from the SDK (\nrf52840\nRF5_SDK_15.3.0_59ac345\examples\connectivity\ble_connectivity\hex\ble_connectivity_s140_usb_hci_pca10059.hex).

2) Compile the example connectivity app for the dongle (\nrf52840\nRF5_SDK_15.3.0_59ac345\examples\connectivity\ble_connectivity\pca10059\ser_s140_usb_hci\armgcc)

I can't get either #1 or #2 to work properly with the BLE app. When I load the pre-compiled hex via the Programmer (v2.6.2), I can see the memory footprint is different from what the image that the BLE app tries to load. Also the dongle appears differently in my device manager (image below). When I try to run the BLE app, it doesn't work.

For #2, I was able to successfully compile the firmware. I didn't change any of the compiler switches since it appeared to be configured for the pca10059 in DFU mode by default. When loading the hex file, the Programmer app asks for the SoftDevice, which I select S140 for, but then it errors out (see below).

What am I doing wrong here, is there a compatibility issue between the SDK and the latest Connect app??

Thanks,

Gregor

[Amanda Hsieh]

Hi, 

For #1:

Could you please put the dongle in bootloader mode by attaching the dongle to the computer & pressing the reset button on the dongle (not the big white one, but the smaller one that is angled perpendicular to SW1)? Then, open the nRF Connect BLE app again & redownload the connectivity FW.

Please take a loot on nrf52840 Dongle Programming Tutorial. 

For #2:

From the figure, it seems you can download the file with nRC Connect BLE app without problem. When upgrade completes the device will reset and the dongle will no longer show up in nRF Connect unless the application used DFU Trigger Library is used, as it is no longer in DFU mode. That's why you see the error.

Best regards,

Amanda

[Gregor]

Thanks Amanda. I did those steps already for #1, I have no problem loading the firmware. Even when removing the dongle and reconnecting, the device does not seem compatible with nRf Connect ble app. Note the device manager has some connectivity device, what is that about?

[Amanda Hsieh]

You should press the RESET button in order to get the Dongle in bootloader mode. then it will be recognized in your Device Manager.

-Amanda

[Gregor]

So after loading the firmware, I need to push the reset Button again? I have no issues putting the device into bootloader mode.

[Amanda Hsieh]

Yes.

Please kindly verify the answer if that one help this case. Thanks. 

-Amanda

[Gregor]

It does not help. When I hit the reset button it puts me into DFU mode, not into the connectivity firmware I just loaded. This is shown by device manager below.

When I load the firmware through the nRF Connect BLE app, it loads the correct firmware. Note the nRF52840 appears as nRF Connect USB CDC on the COM port.

However, if I try to load the pre-compiled hex form the connectivity folder (\nrf52840\nRF5_SDK_15.3.0_59ac345\examples\connectivity\ble_connectivity\hex\ble_connectivity_s140_usb_hci_pca10059.hex), using the bootloader. The nRF52840 appears as below in the device manager, and is unable to speak to the nRF Connect BLE app. 

What am I missing here??

[Amanda Hsieh]

Hi, 

You should press the RESET button after loading a new image.

The DFU Trigger library can be included in an application to allow the USB host to put the nRF52840 Dongle in DFU mode. This is for instance used in the Connectivity firmware that is used by the nRF Connect BLE app. Most SDK example applications do not include this library, and in that case the dongle must be put in DFU mode by pressing the RESET button.

-Amanda

[Gregor]

Amanda, I don't understand the confusion here. I don't have any problems putting the device into DFU mode. I have problems that the Connectivity firmware doesn't work with the nRF Connect BLE app...

[Gregor]

If you can provide an exact sequence of steps to get ble_connectivity_s140_usb_hci_pca10059.hex to work with nRF Connect BLE app, that would help.

[Amanda Hsieh]

Hi,

The connectivity firmware used by nRF Connect for Desktop is based on the SDK BLE connectivity example (<SDK>\examples\connectivity\ble_connectivity), but includes patches from the pc-ble-driver repo. You can find the details on how to patch and build the connectivity firmware here, and obtain precompiled hex files here. There is no need to program the connectivity firmware manually when using nRF Connect for Desktop though, as it will program it for you.

You need to apply this patch found here, "nRF5_SDK_15.3.0_connectivity.patch"

-Amanda

[Gregor]

Thanks Amanda. I will attempt to build from the pc-ble-driver repo. Is there any plan to move the patched firmware into the mainline SDK?

I have a separate question. In SDK version 15.3.0_59ac345, does the connectivity firmware example (\nrf52840\nRF5_SDK_15.3.0_59ac345\examples\connectivity\ble_connectivity\hex\ble_connectivity_s140_usb_hci_pca10059.hex) talk to any software on the PC? If not, why is it included in the SDK? What is the example used for?