JLink Firmware for nrf52840DK Shows Board as nrf52DK

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

roasted_duck — Thu, 23 Jan 2020 14:54:00 GMT

I debugged through the code, long story short:

Depending on the firmware producer a different kind of product id is used. I close this.

Edit: I do not know why it did not show up in my google search till now, but apparently someone already had the same problem, and reported it to the mbed os device (issue link). They have a workaround, but it does not solve the base problem, which is the firmware apparently.

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

Håkon Alseth — Thu, 23 Jan 2020 11:57:50 GMT

If mbed overrides your wanted settings, I'd recommend asking on the mbed forums about this. It sounds like a issue on the mbed side, if this is a warning/issue through their systems.

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

roasted_duck — Wed, 22 Jan 2020 13:16:13 GMT

The problem is not the flashing per se, but 'mbed os' saying: "We compiled it for the NRF52840_DK, but we only found a NRF52_DK. We do not want to break anything, so we are not flashing your program."

I think we are going in two different directions. I actually wanted to use this post as kind of a bug report. The thing is:

- I want to use the mbed os cli

- I want it to be recognised by 'mbed detect' as NRF52840_DK

- I would like to use JLink firmware

- I would like to avoid any further tooling, such as nrfjprog

If you say: "Yeah, not possible. We build a generic firmware for all nrf52xx platform, and this intentionally led to mbed os detecting them as nrf52DK." It is fine. It makes my work a bit harder, but I can work around it. Then I need to find a way to modify my setup so I can keep things automated.

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

Håkon Alseth — Tue, 21 Jan 2020 08:26:00 GMT

You should not use nrfjprog to program the on-board-debugger.

In order to switch out the debugger IF (reprogram the Atmel IC near the USB plug) to either MBED or JLINK, you should hold down the "IF BOOT/RESET" while you power on the nRF52-DK.

At this point, a drive will enumerate with the label "BOOTLOADER".

Drag and drop the wanted .bin file over to this drive, wait 10 seconds, then power cycle your board again.

To use nrfjprog, you need the above sequence to be loaded with the J-Link OB*.bin file.

Once the above sequence is performed, and the jlink.bin file is successfully loaded, you can use nrfjprog like this:

nrfjprog --program path\to\hex\file.hex --sectorerase -f nrf52 --reset

Note: The .hex file should be a compiled program for nrf52, as you're targeting the nRF52 now.

Kind regards,

Håkon

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

roasted_duck — Mon, 20 Jan 2020 18:07:03 GMT

Could you verify me to the command? I currently have only a single dev board, and I do not want to brick it by accident.

nrfjprog --family NRF52 --reset --program "J-Link OB-SAM3U128-V2-NordicSemi 170724.hex" # hex created from bin

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

Håkon Alseth — Fri, 17 Jan 2020 08:42:11 GMT

It sounds like there's an issue with the programming process here. Could you try to use nrfjprog instead?

Kind regards,

Håkon

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

roasted_duck — Thu, 16 Jan 2020 15:19:35 GMT

Sorry for the late answer.

[quote userid="2115" url="~/f/nordic-q-a/56457/jlink-firmware-for-nrf52840dk-shows-board-as-nrf52dk/228785"]This sounds like the project is configured for nrf52832 instead of nrf52840.[/quote]

The project is configured for the nrf52840DK. If I am using ARM's DAPLink the board gets correctly recognised as NRF52840_DK and everything works without problems.

The JLink fimware causes the problem at the moment. I double checked today, downloading and flashing the JLink firmware again. My nrf52840DK shows up as nrf52DK when calling "mbed detect". With ARM's DAPLink my nrf52840DK shows up correctly.

RE: JLink Firmware for nrf52840DK Shows Board as nrf52DK

Håkon Alseth — Mon, 13 Jan 2020 12:28:50 GMT

The IF firmware itself, which can be downloaded from here (extra drop-down meny for mbed IF), shall work for all nRF5x devices, regardless of the reported usb strings.

[quote user=""]Resulting in the problem, that some code cannot be properly compiled by mbed os[/quote]

This sounds like the project is configured for nrf52832 instead of nrf52840.

According to this page:

https://os.mbed.com/platforms/Nordic-nRF52840-DK/

The nRF52840 is supported as a target (nrf52840_dk).

I would recommend you check with the mbed community if you still have issues.

Kind regards,

Håkon