OTA DFU on NORA B1

Hello,

I have a project working on Nora B1, which I am testing on nrf5340DK. It is based on the Peripheral UART Sample, programmed with nfr Connect SDK v1.9.1. Now I need to add the OTA DFU to update the program from the nrf Connect mobile app. I changed the prj.conf and main according to this tutorial

https://getwavecake.com/blog/adding-ota-dfu-to-a-nordic-zephyr-project/

It works perfectly, when I am testing it on the Development Kit, but it does not work at all on the Nora B1. The flash is succesful, but the BLE can't get initialised.

I tried a bit and it seems like the problem is caused by the line

CONFIG_BOOTLOADER_MCUBOOT=y
when I add this to the prj. conf, BLE does not work, even when I did not do any changes in the main.
Is there anything special I should take care about while configuring bootloader on the NoraB1?
Thanks a lot for any answer
Parents
  • Hello,

    You might need to include the clock source for the mcuboot build as well. Could you try to enable the config CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y inside the mcuboot.config? For that, you can create a mcuboot folder inside the child image folder and include the config file there: child_image->mcuboot->mcuboot.config.

    Kind Regards,

    Abhijith

     

  • Hello Abhijith,

    thanks a lot for the tip. It unfortunately does not work and the problem remains.

    One thing I realised: while compiling I got this warning:

    warning: NRF53_RECOVERY_NETWORK_CORE (defined at
    C:/ncs/v2.5.0/nrf/modules/mcuboot/boot/zephyr/Kconfig:130) was assigned the value 'y' but got the
    value 'n'. Check these unsatisfied dependencies: (!NRF53_MULTI_IMAGE_UPDATE) (=n),
    MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD (=n). See
    docs.zephyrproject.org/.../kconfig.html and/or look up
    NRF53_RECOVERY_NETWORK_CORE 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.

    I defined the 

    CONFIG_NRF53_MULTI_IMAGE_UPDATE=y
    like it is in the sample from the Development Academy, but when I try to define 
    CONFIG_MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD in the prj.conf, it gives me Fatal error as unknown symbol.
    when I define it in mcuboot.conf, it does not change anything and I still get the same warning.
    Could it be the reason of this problem, and if it is that case, could you please help me to lose it?
    Kind Regards
    Jiri
Reply
  • Hello Abhijith,

    thanks a lot for the tip. It unfortunately does not work and the problem remains.

    One thing I realised: while compiling I got this warning:

    warning: NRF53_RECOVERY_NETWORK_CORE (defined at
    C:/ncs/v2.5.0/nrf/modules/mcuboot/boot/zephyr/Kconfig:130) was assigned the value 'y' but got the
    value 'n'. Check these unsatisfied dependencies: (!NRF53_MULTI_IMAGE_UPDATE) (=n),
    MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD (=n). See
    docs.zephyrproject.org/.../kconfig.html and/or look up
    NRF53_RECOVERY_NETWORK_CORE 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.

    I defined the 

    CONFIG_NRF53_MULTI_IMAGE_UPDATE=y
    like it is in the sample from the Development Academy, but when I try to define 
    CONFIG_MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD in the prj.conf, it gives me Fatal error as unknown symbol.
    when I define it in mcuboot.conf, it does not change anything and I still get the same warning.
    Could it be the reason of this problem, and if it is that case, could you please help me to lose it?
    Kind Regards
    Jiri
Children
No Data
Related