nrf52840 dongle flashing via Segger J-link and VSCode

RE: nrf52840 dongle flashing via Segger J-link and VSCode

Sigurd Hellesvik — Mon, 18 Dec 2023 08:27:01 GMT

The nRF52840 Dongle has the nRF5 Bootloader loaded by default.

See nRF52840 Dongle docs for information on how to flash the Dongle.

If you want to add both NSIB (CONFIG_SECURE_BOOT) and MCUboot to the dongle, you must program it using an external debugger.

EDIT added: In that case, you must also create custom board files for the non- nRF5 bootloader dongle, as the standard dongle boardfiles assumes nRF5 Bootloader

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Mon, 18 Dec 2023 05:46:48 GMT

Weird, never got a notification of your message Sigurd Hellesvik ... Anyways my example repo in the above post is generate from the nrf example application repo

RE: nrf52840 dongle flashing via Segger J-link and VSCode

Sigurd Hellesvik — Tue, 12 Dec 2023 13:43:24 GMT

[quote user="parksj10"]I pulled down the nrf connect template repo:[/quote]

Can you link to the repo?

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Sat, 09 Dec 2023 06:23:34 GMT

Thanks Sigurd Hellesvik , I pulled down the nrf connect template repo:

Note I redacted main.c to the following to avoid build errors with other boards:

/*
 * Copyright (c) 2021 Nordic Semiconductor ASA
 * SPDX-License-Identifier: Apache-2.0
 */

#include <zephyr/kernel.h>
#include <zephyr/drivers/sensor.h>
#include <app_version.h>

#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(main, CONFIG_APP_LOG_LEVEL);

int main(void)
{
	printk("Zephyr Example Application %s\n", APP_VERSION_STRING);

	while (1)
	{

		k_sleep(K_MSEC(1000));
	}

	return 0;
}

It builds fine when I run

west build -b nrf52840dk_nrf52840 app --pristine

it also builds fine when I add the following configs to prj.conf:

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_SECURE_BOOT=y

However, when use the following command to build:

west build -b nrf52840dongle_nrf52840 app --pristine

I get this error output:

╰─ west build -b nrf52840dongle_nrf52840 app --pristine                                                               ─╯
-- west build: making build dir /Users/josh/Code/hw/scratch/ncs-example-application/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /Users/josh/Code/hw/scratch/ncs-example-application/app
-- CMake version: 3.27.3
-- Using NCS Toolchain 2.5.20231017.141038581733 for building. (/opt/nordic/ncs/toolchains/20d68df7e5/cmake)
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/bin/python3 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/josh/Library/Caches/zephyr
-- Zephyr version: 3.4.99 (/Users/josh/Code/hw/scratch/ncs-example-application/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf52840dongle_nrf52840
-- Found host-tools: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/20d68df7e5/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840.dts
-- Generated zephyr.dts: /Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/dts.cmake
Parsing /Users/josh/Code/hw/scratch/ncs-example-application/app/Kconfig
Loaded configuration '/Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840_defconfig'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/app/prj.conf'
Configuration saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/.config'
Kconfig header saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:28 (message):
  CONFIG_USB_DEVICE_PID has default value 0x100.

  This value is only for testing and MUST be configured for USB products.



=== child image b0 -  begin ===
loading initial cache file /Users/josh/Code/hw/scratch/ncs-example-application/build/b0/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /Users/josh/Code/hw/scratch/ncs-example-application/nrf/samples/bootloader
-- CMake version: 3.27.3
-- Using NCS Toolchain 2.5.20231017.141038581733 for building. (/opt/nordic/ncs/toolchains/20d68df7e5/cmake)
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/bin/python3 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/josh/Library/Caches/zephyr
-- Zephyr version: 3.4.99 (/Users/josh/Code/hw/scratch/ncs-example-application/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf52840dongle_nrf52840
-- Found host-tools: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/20d68df7e5/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840.dts
-- Generated zephyr.dts: /Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/dts.cmake

warning: HW_STACK_PROTECTION (defined at arch/Kconfig:264) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: ARCH_HAS_STACK_PROTECTION (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_HW_STACK_PROTECTION and/or look up
HW_STACK_PROTECTION in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

Parsing /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/Kconfig
Loaded configuration '/Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840_defconfig'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/nrf/samples/bootloader/prj.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/.config'
Kconfig header saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:28 (message):
  CONFIG_USB_DEVICE_PID has default value 0x100.

  This value is only for testing and MUST be configured for USB products.


CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/lib/flash_patch/CMakeLists.txt:8 (message):
  

        ----------------------------------------------------------
        --- WARNING: To maintain the integrity of secure boot, ---
        --- enable CONFIG_DISABLE_FLASH_PATCH in production.   ---
        ----------------------------------------------------------


-- Configuring done (3.7s)
-- Generating done (0.1s)
-- Build files have been written to: /Users/josh/Code/hw/scratch/ncs-example-application/build/b0
=== child image b0 -  end ===

CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/bootloader/cmake/debug_keys.cmake:36 (message):
  

      --------------------------------------------------------------
      --- WARNING: Using generated NSIB public/private key-pair. ---
      --- It should not be used for production.                  ---
      --- See CONFIG_SB_SIGNING_KEY_FILE                         ---
      --------------------------------------------------------------
      

Call Stack (most recent call first):
  /Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/bootloader/cmake/provision_hex.cmake:47 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/CMakeLists.txt:20 (include)


-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/bin/python3 (found version "3.9.6") found components: Interpreter 

=== child image mcuboot -  begin ===
loading initial cache file /Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/child_image_preload.cmake
Loading Zephyr default modules (Zephyr base).
-- Application: /Users/josh/Code/hw/scratch/ncs-example-application/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.27.3
-- Using NCS Toolchain 2.5.20231017.141038581733 for building. (/opt/nordic/ncs/toolchains/20d68df7e5/cmake)
-- Found Python3: /opt/nordic/ncs/toolchains/20d68df7e5/bin/python3 (found suitable version "3.9.6", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/josh/Library/Caches/zephyr
-- Zephyr version: 3.4.99 (/Users/josh/Code/hw/scratch/ncs-example-application/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf52840dongle_nrf52840
-- Found host-tools: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/20d68df7e5/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840.dts
-- Found devicetree overlay: /Users/josh/Code/hw/scratch/ncs-example-application/nrf/modules/mcuboot/usb.overlay
-- Generated zephyr.dts: /Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/dts.cmake

warning: LOG_DEFAULT_LEVEL (defined at subsys/logging/Kconfig.filtering:13) was assigned the value
'0' but got the value ''. Check these unsatisfied dependencies: LOG (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_DEFAULT_LEVEL and/or look up
LOG_DEFAULT_LEVEL in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: USB_COMPOSITE_DEVICE (defined at subsys/usb/device/Kconfig:51) was assigned the value 'n'
but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_USB_COMPOSITE_DEVICE and/or look up
USB_COMPOSITE_DEVICE in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: The choice symbol MCUBOOT_LOG_LEVEL_INF (defined at
subsys/logging/Kconfig.template.log_config:17) was selected (set =y), but no symbol ended up as the
choice selection. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_LOG_LEVEL_INF
and/or look up MCUBOOT_LOG_LEVEL_INF in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.


warning: The choice symbol LOG_MODE_MINIMAL (defined at subsys/logging/Kconfig.mode:28) was selected
(set =y), but no symbol ended up as the choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_MODE_MINIMAL and/or look up
LOG_MODE_MINIMAL in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /Users/josh/Code/hw/scratch/ncs-example-application/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration '/Users/josh/Code/hw/scratch/ncs-example-application/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840_defconfig'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/bootloader/mcuboot/boot/zephyr/prj.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/bootloader/mcuboot/boot/zephyr/boards/nrf52840dongle_nrf52840.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/bootloader/image/multi_image_mcuboot.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/bootloader/image/fw_info.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/nrf/subsys/partition_manager/partition_manager_enabled.conf'
Merged configuration '/Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/.config'
Kconfig header saved to '/Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/subsys/usb/device/CMakeLists.txt:28 (message):
  CONFIG_USB_DEVICE_PID has default value 0x100.

  This value is only for testing and MUST be configured for USB products.


CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/lib/flash_patch/CMakeLists.txt:8 (message):
  

        ----------------------------------------------------------
        --- WARNING: To maintain the integrity of secure boot, ---
        --- enable CONFIG_DISABLE_FLASH_PATCH in production.   ---
        ----------------------------------------------------------


MCUBoot bootloader key file: /Users/josh/Code/hw/scratch/ncs-example-application/bootloader/mcuboot/root-ec-p256.pem
-- Configuring done (3.8s)
-- Generating done (0.1s)
-- Build files have been written to: /Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot
=== child image mcuboot -  end ===

CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/modules/mcuboot/CMakeLists.txt:320 (message):
  

          ---------------------------------------------------------
          --- WARNING: Using default MCUBoot key, it should not ---
          --- be used for production.                           ---
          ---------------------------------------------------------
          



CMake Warning at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/cmake/partition_manager.cmake:79 (message):
  

          ---------------------------------------------------------------------
          --- WARNING: Using a bootloader without pm_static.yml.            ---
          --- There are cases where a deployed product can consist of       ---
          --- multiple images, and only a subset of these images can be     ---
          --- upgraded through a firmware update mechanism. In such cases,  ---
          --- the upgradable images must have partitions that are static    ---
          --- and are matching the partition map used by the bootloader     ---
          --- programmed onto the device.                                   ---
          ---------------------------------------------------------------------
          

Call Stack (most recent call first):
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/cmake/modules/kernel.cmake:247 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:8 (find_package)


Traceback (most recent call last):
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 2045, in <module>
    main()
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 1034, in main
    solution.update(solve_region(pm_config, region, region_config,
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 977, in solve_region
    get_region_config(partitions, region_config, static_partitions, system_reqs=pm_config)
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 764, in get_region_config
    solve_complex_region(pm_config, start, size, placement_strategy, region_name, device, static_conf, dp, system_reqs)
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 871, in solve_complex_region
    solution, sub_partitions = resolve(pm_config, dp, system_reqs)
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 313, in resolve
    solve_direction(reqs, sub_partitions, unsolved, solution, 'after')
  File "/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py", line 199, in solve_direction
    anchor = current if current in solution else next(solved for solved in reversed(solution)
StopIteration
CMake Error at /Users/josh/Code/hw/scratch/ncs-example-application/nrf/cmake/partition_manager.cmake:323 (message):
  Partition Manager failed, aborting.  Command:
  /opt/nordic/ncs/toolchains/20d68df7e5/bin/python3;/Users/josh/Code/hw/scratch/ncs-example-application/nrf/scripts/partition_manager.py;--input-files;/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/zephyr/include/generated/pm.yml;/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/modules/nrf/subsys/partition_manager/pm.yml.nrf5_mbr;/Users/josh/Code/hw/scratch/ncs-example-application/build/b0/modules/nrf/subsys/partition_manager/pm.yml.secure_boot_storage;/Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/zephyr/include/generated/pm.yml;/Users/josh/Code/hw/scratch/ncs-example-application/build/mcuboot/modules/nrf/subsys/partition_manager/pm.yml.nrf5_mbr;/Users/josh/Code/hw/scratch/ncs-example-application/build/zephyr/include/generated/pm.yml;/Users/josh/Code/hw/scratch/ncs-example-application/build/modules/nrf/subsys/partition_manager/pm.yml.nrf5_mbr;--regions;sram_primary;flash_primary;--output-partitions;/Users/josh/Code/hw/scratch/ncs-example-application/build/partitions.yml;--output-regions;/Users/josh/Code/hw/scratch/ncs-example-application/build/regions.yml;--sram_primary-size;0x40000;--sram_primary-base-address;0x20000000;--sram_primary-placement-strategy;complex;--sram_primary-dynamic-partition;sram_primary;--flash_primary-size;0x100000;--flash_primary-base-address;0x0;--flash_primary-placement-strategy;complex;--flash_primary-device;flash_controller;--flash_primary-default-driver-kconfig;CONFIG_SOC_FLASH_NRF
Call Stack (most recent call first):
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/cmake/modules/kernel.cmake:247 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /Users/josh/Code/hw/scratch/ncs-example-application/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:8 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /Users/josh/.pyenv/shims/cmake -DWEST_PYTHON=/Users/josh/.pyenv/versions/3.9.6/Library/Frameworks/Python.framework/Versions/3.9/bin/python -B/Users/josh/Code/hw/scratch/ncs-example-application/build -GNinja -DBOARD=nrf52840dongle_nrf52840 -S/Users/josh/Code/hw/scratch/ncs-example-application/app
                                                                                                                  ─╯

this seems to be board specific, but I can't identify what the issue is... and it still seems like it will build an image that isn't compatible with external debuggers unless I use fstab_debugger.dtsi based on this comment

Also note, when I only have CONFIG_BOOTLOADER_MCUBOOT=y enabled, the dongle still fails to build with a different error,

/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `text' will not fit in region `FLASH'
/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 10972 bytes
collect2: error: ld returned 1 exit status

making me thing it's a dongle dts error, perhaps something like this?:

Noting for later: seems like the dongle has a smaller partition for boot than the dk. Initial attempts at manually changing map in nrf local west folder fstab-stock.dtsi did not help...

Note: in order to make this more easy for you to reproduce, simply pull down this repo:
https://github.com/parksj10/nrfdongle_build_error/tree/main

and follow the README...

Digging farther, it seems like A) there's a misconfiguration in the dongle dts's somewhere (, or b) there is a bug in the partition_manager.py

RE: nrf52840 dongle flashing via Segger J-link and VSCode

Sigurd Hellesvik — Fri, 08 Dec 2023 14:31:11 GMT

The default method here is to enable MCUboot in a project, and then the project will be build as two parts: MCUboot and the application. Both these will be merged into merged.hex, which is automatically flashed to the nRF chip when you flash it.

[quote user="parksj10"]Maybe you have links for where to figure this out? I was looking in the Zephyr docs (https://docs.zephyrproject.org/latest/boards/arm/nrf52840dongle_nrf52840/doc/index.html) and they were saying you need to modify the .dts files for the boards, which I would like to avoid doing...[/quote]

See official docs on bootloaders or my unofficial explanations.

The nRF Connect SDK use the Partition Manager and Multi-Image builds to automatically handle a lot of this, so you would generally not need to do any of that yourself.

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Fri, 08 Dec 2023 07:15:53 GMT

Hi Sigurd Hellesvik ,

I've been giving this a shot as I come back around to the project (got very sidetracked on an I2S implementation).

You said

The alternative is of course just to use MCUboot instead, which will nicely integrate with the nRF Connect SDK, and lets you program using J-Link and West to program without issue.

However, I'm not quite figuring out how to do this. Do I need to do a one-time flash of the MCUboot loader? When I build an NCS project, is this not included directly? Do you know if there's a way to make this included in the compiled binary so that when anyone on the project builds/flashes, it automatically insures the devices has the MCU bootloader? Maybe you have links for where to figure this out? I was looking in the Zephyr docs (https://docs.zephyrproject.org/latest/boards/arm/nrf52840dongle_nrf52840/doc/index.html) and they were saying you need to modify the .dts files for the boards, which I would like to avoid doing...

RE: nrf52840 dongle flashing via Segger J-link and VSCode

Sigurd Hellesvik — Wed, 30 Aug 2023 06:50:54 GMT

[quote user="parksj10"]Thanks for the detailed response. I'm amazed at how much documentation you guys have, it's really great. I also really appreciated your "unofficial" documentation.[/quote]

And thank you for the kind words

[quote user="parksj10"] FYI I can flash and run with no nRF bootloader, so that's my working solution for the time being[/quote]

Yep, for developing the application, you don't really need a bootloader, as you can use an external debugger(The other chip on your DK) to program the nRF chip.
The use-case for a bootloader and DFU is mostly to enable you to program the devices in the field, when you do not have an external bootloader available.
Bootloaders also have some security benefits, which I guess you can learn about if you google something along the lines of "Why use an immutable bootloader microcontrollers".

[quote user="parksj10"]I'll give this a shot when I get time[/quote]

Good luck!

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Tue, 29 Aug 2023 18:56:17 GMT

Thanks for the detailed response. I'm amazed at how much documentation you guys have, it's really great. I also really appreciated your "unofficial" documentation.

I'll give this a shot when I get time (seems like quite a bit of up front work to learn and implement), and let you know if I have anymore questions. FYI I can flash and run with no nRF bootloader, so that's my working solution for the time being

RE: nrf52840 dongle flashing via Segger J-link and VSCode

Sigurd Hellesvik — Mon, 28 Aug 2023 11:37:58 GMT

Hi,

We have two separate SDKs, the nRF5 SDK(old) and nRF Connect SDK(new).
These come with different default bootloaders:
nRF5 SDK: nRF5 Bootloader
nRF Connect SDK: MCUboot

nRF5 Bootloader

The dongles come pre-programmed with the nRF5 Bootloader.
If you want this bootloader, you must program it using the nRF5 SDK, or at least use a hex from the nRF5 SDK. I beleive you should find pre-compiled hex files inside the nRF5 SDK examples folder.
Then if you build with CONFIG_BOARD_HAS_NRF5_BOOTLOADER=y and the dongle board, it will automatically set FLASH_LOAD_OFFSET to make your hex-file start after the nRF5 bootloader. It also reserves that space using the partition manager.
With this, you should be able to flash your application using J-Link, as long as you do not erase everything:

nrfjprog --sectorerase --program build/zephyr/zephyr.hex

Or you could just use the nRF Programmer app / nrfutil to upload your new firmware using DFU.

MCUboot

The alternative is of course just to use MCUboot instead, which will nicely integrate with the nRF Connect SDK, and lets you program using J-Link and West to program without issue.
See official docs on bootloaders or my unofficial explanations.

Did this make sense?

Regards,
Sigurd Hellesvik

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Sun, 27 Aug 2023 23:30:16 GMT

Got it running from Jlink Flash by adding the following to the prj.conf

CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n

(found that here)

However, I'm still curious how I can get this whole thing to work while keeping the dfu bootloader intact

RE: nrf52840 dongle flashing via Segger J-link and VSCode

parksj10 — Sun, 27 Aug 2023 23:22:19 GMT

Just for reference, this is the output I get when I flash after doing the recover:

Flashing build to 260117435
/bin/sh -c west flash -d /Users/josh/Code/hw/nrf/lights/blinky/build --skip-rebuild --dev-id 260117435

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: /Users/josh/Code/hw/nrf/lights/blinky/build/zephyr/zephyr.hex
[ ######               ]   0.000s | Erase file - Check image               [ #####                ]   0.000s | Check image validity - Initialize devic[ ##########           ]   0.000s | Check image validity - Check region 0 s[ ###############      ]   0.000s | Check image validity - block 1 of 2    [ #################### ]   0.009s | Check image validity - Finished        [ #############        ]   0.000s | Erase file - Erasing                   [ ##########           ]   0.000s | Erasing non-volatile memory - block 1 o[ #################### ]   0.000s | Erasing non-volatile memory - Erase suc[ #################### ]   1.261s | Erase file - Done erasing                                                          
[ ######               ]   0.000s | Program file - Checking image          [ #####                ]   0.000s | Check image validity - Initialize devic[ ##########           ]   0.000s | Check image validity - Check region 0 s[ ###############      ]   0.448s | Check image validity - block 1 of 2    [ #################### ]   0.005s | Check image validity - Finished        [ #############        ]   0.000s | Program file - Programming             [ ##########           ]   0.000s | Programming image - block 1 of 1       [ #################### ]   0.000s | Programming image - Write successful   [ #################### ]   0.302s | Program file - Done programming                                                    
[ ######               ]   0.000s | Verify file - Check image              [ #####                ]   0.000s | Check image validity - Initialize devic[ ##########           ]   0.000s | Check image validity - Check region 0 s[ ###############      ]   0.578s | Check image validity - block 1 of 2    [ #################### ]   0.006s | Check image validity - Finished        [ #############        ]   0.000s | Verify file - Verifying                [ ##########           ]   0.000s | Verifying image - block 1 of 1         [ #################### ]   0.000s | Verifying image - Verify successful    [ #################### ]   0.317s | Verify file - Done verifying                                                       
Enabling pin reset.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 260117435 flashed successfully.