How to born nrf_desktop's image to nrf52840dongle

[sam]

I'm now trying to test dongle on nrf52840dongle board：

  1.   west build -b nrf52840dongle_nrf52840 -- -DCONF_FILE=prj_4llpmconn.conf

  2.  open nRF Connect for Desktop's  Programmer.

  3. add the build\zephyr\merged.hex to Programmer.

  4. start write to nrf52840 dongle board.

  5. Prompt to select softdevice, and i select "0x100(s140_nrf52_7.2.0)".

  6. get message"Error: Failed with exit code 1. One or more program tasks failed. Message: Failed, [sdfu]."

  7. try other softdevice, get the same result.

   Am I overlooking something or a step?

    **Environment

• OS: Windows
• Toolchain: Zephyr SDK 0.16.3, python 3.10.11, west 1.2.0
• nrf connect SDK v2.5
• nrf52840 dongle (PCA10059)
• nRF Connect for Desktop 4.2.0 ,  Programmer 4.0.1

[Simonr]

Hi

This sounds like some kind of misunderstanding, when using the nRF Connect SDK and Zephyr there is no need for a SoftDevice .hex file as well. The merged .hex file you get after building a project will include the SoftDevice/Zephyr controller as well as the application code. Does the Programmer app also fail if you just try flashing the merged.hex file without choosing a SoftDevice? Can you also go through this guide on how we recommend programming and debugging th enRF52840 Dongle in the nRF Connect SDK please?

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/zephyr/boards/arm/nrf52840dongle_nrf52840/doc/index.html  

Best regards,

Simon

[sam]

 Simonr  Can you repeat my steps one more time? I followed your suggestion and still can't burn.

The second picture is the prompt box that appeared in the process after I clicked the "write" button.

"This sounds like some kind of misunderstanding, when using the nRF Connect SDK and Zephyr there is no need for a SoftDevice .hex file as well"

I also think so, maybe a dongle should be provided without a softdevice to use.

Below is the description of the nrf52840dongle that I excerpted from the official website.

[Simonr]

Hi

Okay, I was just able to reproduce this on my end as well, and it seems like this is an issue with the nRF Programmer app not recognizing the file having a SoftDevice Controller for some reason. This seems to be the case for older NCS versions as well unfortunately, so I have reported this to the development team. In the meantime you can use either nrfutil or an external debugger to program the nRF52840 Dongle.

I'll let you know of any updates to the internal ticket that's been created on this.

Thank you for your thorough explanation!

Best regards,

Simon

[david_owtschinnikow]

Hi, is there any updte on this subject? I find the same problem.

Thank you

Best regards

David 

[Lorenzo Amicucci]

Hi 
nRF Desktop in general uses B0 or MCUboot, when you build default configurations. if you get the hex file from default configurations for dongle, you need to use SWD to flash it into the dongle.

if, instead, you want to build an image that can go on top of the native bootloader which is in the dongle (the old nrf5 bootloader), you can try to add the following in your proj.conf file

CONFIG_FLASH_LOAD_OFFSET=0x1000
CONFIG_BOARD_HAS_NRF5_BOOTLOADER=y

Plesae confirm if it works or which error you get

BR
LA