Daplink software released by arm-mbed for nrf52840 dk does not detect external target

[madblue]

Hi,

I need to upload compiled binaries from mbed studio to my custom board based on nrf52840 using nrf52840 dk.

I have replaced the jlink software(J-Link OB-SAM3U128-V2-NordicSemi 170724.bin) on nrf52 dk with daplink software for nrf52840 dk released by arm-mbed.

By making this change, I was able to upload from mbed studio compiled binaries to the nrf52840 dk and it worked well.

Now the problem is that, i am not able to upload the mbed compiled binaries to my custom board. I have tried to connect it with nrf52840 dk as we use it with jlink(By connecting the swd lines of dk to my custom board) but it didn't work. it is getting uploaded to dk.

The daplink  software for nrf52840dk released by arm-mbed is shown below, (i have used this one)

armmbed.github.io/.../0253_sam3u2c_mkit_dk_dongle_nrf5x_0x5000.bin

i want to know what is the best way to use mbed studio with nrf52840 boards ?

(fyi, i am able to upload to my custom board using nrfjprog and everything is fine. )

[awneil]

Note quite clear what you're doing here?

DAPLink isn't a bootloader - it's a programmer, using the SWD interface.

Also, as the linked page says, it's just a software project - so what actual hardware are you using?

Perhaps post a diagram of what you're doing; and some good, clear, in-focus photographs ?

[madblue]

Thanks for the response,

i am sorry for not providing a proper description of my issue.

what i want to do:

I need to upload compiled binaries from mbed studio to my custom board using nrf52840 dk.

Currently jlink support on mbed studio is not good but with daplink it looks very nice. so the easy way is to use daplink to upload the mbed compiled binaries.

The link i have shared has software which has the daplink software for nrf52840(released by arm-mbed). 

It is similar to jlink software that runs on the samd processor of dk (jlink software: J-Link OB-SAM3U128-V2-NordicSemi 170724.bin)

The daplink  software for nrf52840 released by armbed is shown below, (i have used this one)

armmbed.github.io/.../0253_sam3u2c_mkit_dk_dongle_nrf5x_0x5000.bin

The problem is that i am not able to upload to my custom board  through nrf dk. it is not detecting the external target as jlink does it by checking the state of vtg pin.

When i upload the binaries, it directly programs the nrf52840 dk instead of my custom board.

(fyi, i am able to upload to my custom board using nrfjprog and everything is fine)

My board : nrf52840 based board designed for an iot application.

Also, please note: i am able to upload the binaries from mbed studio to nrf52840 through daplink.

i hope this gives clarity on my issues.

[awneil]

I'm still not at all clear what you're actually doing - again, a diagram would help.

madblue said:

The daplink  software for nrf52840 released by armbed is shown below

So you're trying to load DAPLink onto the nRF52840 chip on an nRF52840-DK ?

But, on the nRF52840-DK, it is the interface MCU that drives the 'programming-out' connector - not the nRF52840 chip

So you would need to do some mods to the DK to disconnect the interface MCU, and re-wire the nRF52840 chip to drive the 'programming-out' connector.

Have you done that?

madblue said:

Currently jlink support on mbed studio is not good but with daplink it looks very nice

Don't Segger provide a DAPLink update for the interface chip?

Or just use a separate microcontroller as a DAPLink ?

[madblue]

Hi awneil, 

Thanks for the help.

what i wanted to do was, use nrf52840 dk as daplink programmer to upload to external nrf52 target.

The daplink software i have mentioned is for the samd controller (interface controller that runs jlink software)

Of course a separate micro-controller or any daplink programmer will do it.

Wouldn't it be a good feature if this can be done through the dk itself ?(especially those who use dk as programmer for nrf52840 targets).

jlink Software in the interface mcu is able detect an external target based on the voltage level of vtg pin without making any other changes. so i just wanted to know why the same thing cannot be achieved for the daplink ?

I have posted this question here because this looked to be a common issue for those who use mbed rather than the native nrf52 sdk.