Jack Porter

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

5 years, 7 months ago.

Why use Mbed Daplink instead of on-board Segger J-Link ?

nRF52840-DK page "'https://os.mbed.com/platforms/Nordic-nRF52840-DK/" says "The latest Arm Mbed DAPLink interface firmware for the nRF52-DK is available at ...". Do I need to overwrite the OB Segger J-Link with Daplink ? What does Daplink provide that OB J-Link doesn't ? Thanks

Question relating to:

Last updated: 18 Nov 2019
The nRF52840 Development Kit is a single-board development kit for Bluetooth low energy, ANT, 802.15.4, and 2.4 GHz proprietary applications using the nRF52840 SoC.

3 Answers

Shibiao Wu
5 years, 7 months ago.

Hi, Jack. I am sorry for the previous wrong answer here.

Paul Staron
5 years, 7 months ago.

I think Shibiao has asked a question here by mistake.

Jack, I don't have this board, however generally the Mbed firmware enables the drag n' drop flashing and serial debug functions. The Segger firmware would probably be for their flashing/debug adapters.

I would update to the Mbed firmware if you are going to use here, you can always re-flash back to the Segger version.

Dirk Akemann
5 years, 7 months ago.

Hi Paul, hi Jack, Actually the J-Link OB Firmware of the Nordic Boards should be capable to support mbed directly. They have drag'n'drop flashing enabled and have a VCOM port that would enable serial debug functions. So there should be no need to reflash. Best regards, Dirk Akemann

Hi Paul and Dirk, thanks for your responses. I've played with both and they both support drag'n'drop and VCOM port. The only downside to Daplink is you lose compatibility with Segger's J-Flash and J-Link Commander software and Nordic's nrfjprog software. I don't see any reason not to use the OB J-Link. Thanks, Jack

posted by Jack Porter 30 Apr 2019