nRF9160 DK mcuboot custom app based on the UDP example

[DavidKaplan]

Shalom!

 I have a nRF9160 DK board that I am using before our custom hardware prototype is ready.  My application is based on the UDP example code skeleton along with code pulled in from other examples. I can run the application in the SES IDE debugger and it connects to our server. I wanted to get application (priority) and modem (delta) OTA working on the SDK. I tried adding "CONFIG_BOOTLOADER_MCUBOOT=y" but when running the application by way of the debugger I get an immediate hard fault. I tried adding defines from the application_update.

I tried compiling the http_update application_update example but I get "opening dependency file modules\mcuboot\boot\bootutil\zephyr\CMakeFiles\..__bootloader__mcuboot__boot__bootutil__zephyr.dir\C_\ncs\v1.5.1\bootloader\mcuboot\boot\bootutil\src\bootutil_public.c.obj.d: No such file or directory". There is no file in the path. I installed the Connect SDK in its default path. The mcuboot (under tests) and the dfu_target-mcuboot both compile.

How can I compile my application with the bootloader in order to test OTA on the nRF9160 DK?

Without the CONFIG_BOOTLOADER_MCUBOOT=y define after resetting the SDk, my code does not run.

How can at least get the code to run at startup?

[DavidKaplan]

Shalom!

 I saw that the asset_tracker example compiles and runs fine on the nRF9160 DK, and that in its my child_image folder there is a mcuboot.conf file.I copied the child_image and  configuration folders from the asset_tracker.

I also addedin the CMakeLists.txt file

set(PM_STATIC_YML_FILE
  ${CMAKE_CURRENT_SOURCE_DIR}/configuration/${BOARD}/pm_static.yml
  )

Now my application runs without the hard fault from the debugger and also after nRF9160 DK reset.

Thanks David

[Marte Myrvold]

Hi David,

I am glad to hear that you solved it!

Thank you for sharing how you fixed the problem here, so if others have a similar problem they can find this!

Best regards,

Marte