RE: SWD Flash via J-Link on Feather nRF52840 Sense Erases Bootloader (Zephyr v3.0.0), No RTT Logs

Einar Thorsrud — Wed, 28 May 2025 13:50:24 GMT

Hi Anmol,

[quote user=""]Is there a recommended SWD flash sequence or Zephyr project configuration—particularly for Adafruit’s nRF52840 Sense—that will preserve the UF2 bootloader partition?[/quote]

SWD and the nRF52840 are fundamentally the same regardless of board, so no special considerations are needed. If you want to keep a bootloader or anythign else out side of the image you are flashing, you need to program without an erase all. From VS Code, that means not pressing the icon to the right of the Flash action. And if programming using nrfutil device, use:

nrfutil device program --options chip_erase_mode=ERASE_RANGES_TOUCHED_BY_FIRMWARE --firmware merged.hex

(replace merged.hex with the path to your hex file).

That said, the problem here may not be directly related to flashing. The first thing that comes to mind, is that I wonder what boad you build the project for, and if the project is built to accomodate teh UF2 bootloader (so that you don't have anythign starting at address 0)? If tha tis the case, you eithe rneed the UF2 bootlaoder in place, or you change the configuration to place the application (or anothe rbootloade) at addess 0. Can you check this first?

[quote user=""]Are there any Nordic-provided tools, scripts, or linker-script modifications to deploy a Zephyr v3.0.0 build from VS Code without overwriting the bootloader?[/quote]

You can create board files that handle this, or add a static partitioning that places the application at a specific address. This is typically handled in the board fiels, and is for instance done for instance for nRF52840 Dongle (the latter has the old nRF5 SDK USB bootloader). See this thread.

[quote user=""]If SWD-based deployment cannot preserve the UF2 bootloader, can you suggest an alternative programming interface or streamlined workflow for Zephyr development on this board?[/quote]

SWD should not be a problem, but the project you build must accomodate the existing bootlodaer if you want to keep it (it cannot overlap, and need to start where the existing bootloader expect the application to start). Moreover, I have no knowledge of the UF2 bootloader, but it may be that it needs some metadata so that you eithe need to generate that and also flash that, or that it will be easier to update via the bootloader to get that handled by the bootloader (again this is just speculations).

PS: But if you intend to use SWD, perhaps there is no point in keeping the UF2 bootloader?