Blinky doesn't work on nRF52840-dongle via J-Link

RE: Blinky doesn't work on nRF52840-dongle via J-Link

JONATHAN LL — Mon, 28 Oct 2024 12:30:54 GMT

You should always do a reset either soft or hard after flashing new firmware on the device.

Not sure what is the reason why, but doing a reset will make sure that the device is out of debug mode and might also related to some security thing.

So always good to do a reset to make sure the applications starts correctly.

Regards,
Jonathan

RE: Blinky doesn't work on nRF52840-dongle via J-Link

mlac — Mon, 28 Oct 2024 08:06:31 GMT

It turns out the LED started to blink after I rebooted the board with its reset button.

Why do I have to reset it after flashing it?

devzone.nordicsemi.com/.../0882.zephyr.hex

RE: Blinky doesn't work on nRF52840-dongle via J-Link

Felix Shih — Mon, 28 Oct 2024 07:46:46 GMT

You should check zephyr.hex, zephyr.dts mcuboot address won't change.

The .hex file first line should be

:10000000009B00204D57010053E8020039570100C2

RE: Blinky doesn't work on nRF52840-dongle via J-Link

mlac — Mon, 28 Oct 2024 07:31:44 GMT

I've added the suggested Kconfig options to prj.conf which now contains:

CONFIG_FLASH_LOAD_OFFSET=0x0
CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n

Then, I did a pristine build, and the boot partition has not changed in build/zephyr/zephyr.dts:

					boot_partition: partition@0 {
						label = "mcuboot";
						reg = < 0x0 0x10000 >;
					};

The issue persists.

RE: Blinky doesn't work on nRF52840-dongle via J-Link

Felix Shih — Mon, 28 Oct 2024 06:56:38 GMT

try this

devzone.nordicsemi.com/.../how-to-generate-nrf52840-dongle-hex-file-with-using-external-j-link-to-program-and-run-directly