Using the nRF52840 Dongle (PCA10059) as a USB serial-to-BLE port

[SteveHx]

I have already read thru past inquiries along this line, and I see that many others are trying to do the same thing, but Nordic is still not providing appropriate example code. My product (actual several products for several clients) needs to use the BLE UART capability to get data into a PC. The most obvious application of the Dongle is for just this purpose. I also see that others have thought of trying to merge the USB-serial example with the UART-central example, none successfully that I found. Will Nordic provide such an example?

[SteveHx]

"However, the project does not have the DFU trigger library so when the application is started (after completing DFU and resetting) nRF Connect Programmer will not find it, and therefor you get the error message."

A search finds some 100 files installed on my computer with "dfu_trigger" as part of the filename. How do i incorporate those into the multi-NUS project? Will the lack of that module prevent the multi-NUS app from running from a cold boot?

[Einar Thorsrud]

Hi,

SteveHx said:

The source code to run multi-NUS on the Dongle (and I think also on the 52840 DevKit) is fine, but without a project file which would set the appropriate options etc. I have downloaded and unzipped the code, but I find no way to open it under either the nRF Connect SDK nor under SES.

I am requesting a simple, step-by-step approach to actually running this example code, using either SES or nRF Connect SDK. Thank you.

Which example are you referring to now? The code WesC linked to is for the nRF5 SDK and will not work with the nRF Connect SDK. I assumed that was what you were testing, but that was perhaps not the case? If not, perhaps you can elaborate? (Also, the DFU trigger library I referred to is for the nRF5 SDK, as the bootloader the nRF52840 dongle ships with is nRF5 SDK based).

SteveHx said:

Will the lack of that module prevent the multi-NUS app from running from a cold boot?

No. The lack of the DFU trigger library only has two consequences:

1. it causes the nRF Connect programmer to output and error after programming.
2. You have to press the (sideways) reset button on the dongle in order to enter DFU mode when you want to program it.

SteveHx said:

"However, the project does not have the DFU trigger library so when the application is started (after completing DFU and resetting) nRF Connect Programmer will not find it, and therefor you get the error message."

Unless you find the above two points very annoying or problematic for your application, I suggest ignoring this (at least for now). If you want to add it at some point you can refer to examples/connectivity/ble_connectivity/main.c to see and example of it bing used.