Not able to load HEX to nrf52840 dongle (makerdiary) via nRF Connect Programmer

[crasspm]

Hello,

I'm trying to program the Makerdiary nRF52840-MDK USB Dongle with the Bluetooth sample project central_uart but when I load the built HEX file to Programmer file memory layout, it appears as an orange block with region name MBR or Application and the Write button remains ghosted out.

Configuration:

• Makerdiary nRF52840-MDK USB Dongle
• nRF Connect SDK v1.3.0-rc1
• nRF Connect Desktop v3.4.0
• nRF Connect Programmer v3.4.0
• nrf/samples/bluetooth/central_uart
• Built with zephyr/boards/arm/nrf52840dongle_nrf52840 board option
• Tried merged.hex, zephyr.hex, merged_nrf52840dongle_nrf52840.hex

nRF Connect Programmer screenshot:

[Simon]

I've seen this issue before, I think the start address is wrong, which causes this issue. There might be something wrong with the nrf52840 dongle board file. I will try to get to the bottom of it before the weekend.

Best regards,

Simon

[Simon]

This problem should be fixed by this pull request, which should add an offset for the MBR when building examples for nrf52840dongle_nrf52840. Implement that, or check out NCS master and try again. I was able to make it work with the master branch (commit e40135dd9b892e5cde733f24 when writing this).

Best regards,

Simon

[crasspm]

Thanks!  Does it make any difference that this is a Makerdiary model dongle?  https://wiki.makerdiary.com/nrf52840-mdk-usb-dongle/

[Simon]

I don't think so, assuming it is shipped with the same software as the nRF52840 dongle. I don't have an overview of the hardware differences between the boards, and if a new board folder needs to be made in zephyr/boards/arm, but the BLE examples shouldn't be affected by this.

Could you test the example ncs\nrf\samples\bluetooth\peripheral_uart on your device and see if it is advertising?

Best regards,

Simon

[crasspm]

Hi Simon,

I updated the SDK to master and then built central_uart again.  When loaded to Programmer I am presented with an option to Write.  When I do, it writes and then the dongle disconnects.  I think this overwrites the bootloader because I can no loner get the dongle to enumerate.  It also appears the sample isn't running as there is no TTY device created and I see no BLE advertisements...