Zigbee OTA on bootloader

[Rwae]

For my graduation project i'm developing an improved version of the Nordic Secure DFU Boot loader. I'm trying to integrate something like the Zigbee OTA client inside the boot loader. Currently i'm working on an attempt for a kind of dual boot. I'm trying to use the standard partition layout with the supplied MBR, my plan is to integrate the Zigbee OTA client on 0x0000 1000 right after the MBR and an application right after the OTA client. I've modified the boot loader in such a way it will boot the OTA client when the DFU button is pressed and the application for normal boot operation.

Given these facts i've come up with two options:

Option 1:

Try integrate the OTA client inside the boot loader but i doubt if that is possible, perhaps someone can provide me with some information on if it's possible or if there are some serious limitations.

Option 2:

Continue like i've described at the top, in such case i'm thinking it would be ideal if i could implement the OTA client like some kind of soft device. But i'm thinking that is not possible since the provided soft devices inside the SDK are not open source.

Let me summarize this, my first question is: Can i integrate a Zigbee OTA client inside the boot loader or are there some serious limitations? Is it possible to implement the Zigbee-stack as soft device? Or should i continue with what i'm doing now?

Used products:

IDE: Segger Embedded Studio 4.19

OS: Ubuntu 19.04 with linux-image-5.0.0-13-generic

SDK: nRF SDK for Thread and Zigbee

Hardware: 3x nRF 52840 PCA10056 and 1x nRF 52840 PCA10059 (Mainly for packet sniffing)

Thank you in advance.

Kind Regards,

Raoul

[AndreasF]

Hi.

Sorry for the late reply, I have been out of office.

Have you looked at the documentation for the example client in the SDK?

The memory layout for example:

States that the example client starts at 0x1000.

Best regards,

Andreas

[Rwae]

Yes i have looked at it, i was using this example as guideline for the implementation. Currently i've succesfully implemented the zigbee OTA client inside the bootloader. When the OTA button is pressed, it wil start listening for updates. The only issue i was having is when adjusting the bootloader start address, i should have noticed the page size of 0x1000 which is required.

At the moment i am looking into the process of receiving updates and storing them on the correct memory location.

So far so good. 

I have one more question regarding the memory layout, how and where are the zigbee settings stored? I can't seem to find where it is written and how.

[AndreasF]

Hi again.

You can take a look here about the memory layout.

Zigbee stack flash usage configuration.

Zigbee stack RAM usage configuration.

Best regards,

Andreas