Modem Shell - nRF915dk build for cloud_coap throws error “undefined boot_write_img_confirmed” with nRF Connect SDK 3.2.1

RE: Modem Shell - nRF915dk build for cloud_coap throws error “undefined boot_write_img_confirmed” with nRF Connect SDK 3.2.1

zpm1066 — Fri, 06 Feb 2026 19:24:13 GMT

Hi Vidar,

Thanks for reviewing the git changes. I guess, the workaround is to include the "overlay-app_fota.conf" or the "overlay-carrier.conf". It's not a big problem.

I think we can close this ticket. Thank you.

Best Regards,
Ravi

RE: Modem Shell - nRF915dk build for cloud_coap throws error “undefined boot_write_img_confirmed” with nRF Connect SDK 3.2.1

Vidar Berg — Fri, 06 Feb 2026 07:06:44 GMT

Hi Ravi,

I'm afraid I don't have a good explanation for what you are observing. I have looked through the git history and was unable to spot any relevant changes for this sample. I also tried building the same modem shell sample in SDK v3.1.0 without "overlay-app_fota.conf" but this resulted in the same linker on my end error since neither CONFIG_IMG_MANAGER or CONFIG_LWM2M_CARRIER got enabled.

Best regards,

Vidar

RE: Modem Shell - nRF915dk build for cloud_coap throws error “undefined boot_write_img_confirmed” with nRF Connect SDK 3.2.1

zpm1066 — Thu, 05 Feb 2026 23:18:20 GMT

Hi Vidar,

Thanks. It's interesting that you included "overlay-app_fota.conf".

When I don't include "overlay-app_fota.conf" with the "overlay-cloud_coap.conf", I get the "“undefined boot_write_img_confirmed”" error in main.c.

It appears that with "overlay-app_fota.conf", CONFIG_LWM2M_CARRIER doesn't get selected. Previously in NCS 3.1.0, this didn't happen.

Best Regards,
Ravi

RE: Modem Shell - nRF915dk build for cloud_coap throws error “undefined boot_write_img_confirmed” with nRF Connect SDK 3.2.1

Vidar Berg — Thu, 05 Feb 2026 13:09:00 GMT

Hello,

I did not manage to reproduce the error here. Below is a picture of the build configurations I used. Do you see anything that is different from your configuration? I also see that the CONFIG_LWM2M_CARRIER symbols gets selected if you include the "overlay-carrier.conf" and it looks like it was the same in SDK v3.1.0.

Best regards,

Vidar