RE: Flashing example .hex file to NRF52840 dongle (PCA10059) to achieve UART over BLE

coen — Wed, 14 Sep 2022 11:03:20 GMT

Dear Sigurd,

Due to vacation it took some time to get back to you, but thank you for providing such a detailed reply. It looks like the desired functionality is not available in the sample code that I could flash to the dongle. This would mean that I would need to alter the code and have to use the DK instead of dongle as that would allow debugging and flashing.

For now I have found a quick alternative solution by using a CSR BC417143 based board. It is intended for serial communication and preloaded with serial port profile (SPP) firmware. This is not the most configurable solution, but it does the job for now.

When I find some free time in-between project work I will keep on playing with the Nordic boards. It will take a bit more time, but on the long term this enables to build more complex projects.

Once again thanks for the reply,

Many thanks,

Regards,

Coen

RE: Flashing example .hex file to NRF52840 dongle (PCA10059) to achieve UART over BLE

Sigurd Hellesvik — Mon, 15 Aug 2022 08:04:36 GMT

Hi Coen,

Two different SDKs

I will start by addressing a common misunderstanding, which I suspect is present here.

We have two different Software Development Kits (SDKs):

The nRF5 SDK (old)
The nRF Connect SDK (New, recommended for new projects)

This is explained in more depth in our nRF Connect SDK and nRF5 SDK statement.

For your case specifically, VS Code is for the nRF Connect SDK, while the infocenter sample you have linked to are for the nRF5 SDK.

Since you are starting a new project here, I strongly recommend using the nRF Connect SDK.

For a step-by-step guide on how to set up + basics for the nRF Connect SDK, see https://academy.nordicsemi.com/.

Samples for the nRF Connect SDK can be found in our nRF Connect SDK docs:

nRF Connect SDK nRF samples, for nRF specific samples. Look here first
nRF Connect SDK Zephyr samples, for generic zephyr samples. Usually useful for hardware drivers or Zephyr features
For your specific need, see the Bluetooth: Peripheral UART sample. I do not think we have a pre-made hex file for this, so you must build this yourself.

nRF52840 Dongle vs nRF52840 Development Kit (DK)

While the nRF52840 Dongle you use are fine for doing testing for the nRF52840, the nRF52840DK is arguably better.

The main difference between the Dongle and the DK is that the DK has an onboard Debugger chip, making it easier to program.

As you have already discovered, you can not just program the Dongle using VS Code.
This is because VS Code uses "west flash", which invokes nrfjprog to program the nRF52840.
nrfjprog uses a debugger to directly flash the nRF52840.

The Dongle on the other hand, must have a bootloader running as part of its firmware, to be able to load applications.
To load a new application onto the Dongle, you must write to it using UART requires nrfutil. But worry not, the nRF Connect for Desktop Programmer app should work for this as well.

If you want some more in-depth on Dongle programming, here is a guide on how to manual nRF52840 Dongle Programming Tutorial.

Summary

I recommend that you stick to the nRF Connect SDK, get started by using https://academy.nordicsemi.com/.
Using the Dongle should be fine, but the nRF52840DK will make your life easier.
Try to use the Bluetooth: Peripheral UART sample, and see if you can program the Dongle in that case?

If you have any questions to this, let me know!

Regards,
Sigurd Hellesvik