Can I expand the data size of dfu protocal?

[ZHENGXIANG]

Hi,

I am now trying to reduce the total number of packets during the dfu process. After reading all the code about dfu in both app and bootloader, I find that in this process, all the struct limit the data size as 16 Bytes. Is there any example that can help me to expand the data size? I want to use packets with size of 256 Bytes.

Or can I bypass the existing protocal and directly store my dfu packet to the dfu target address?

PS: I do not use the nrfutil tools in PC. I want to send the dfu packets from my cloud server.

Thanks for your prompt response!

Sincerely,

Jin

[Sigurd]

Hi,

What SDK version are you using ?

What bootloader are you using ?

Are you using regular Bluetooth LE, or Bluetooth LE Mesh ?

I find that in this process, all the struct limit the data size as 16 Bytes.

What is the name of this struct?

[ZHENGXIANG]

Hi:

I am sorry that I made a mistake, the struct limit the data size as 16 bits, not 16 bytes.

I use Bluetooth LE Mesh and the SDK version is 3.0.0. The struct means the struct of variables, like bl_cmd in bl_cmd_handler (in bootloader_app_bridge.c). The data size is fixed as 16 bits.

I have read the dfu part in both app and bootloader, I think it is too hard to change the dfu protocal. Therefore, I want to write a new receive protocal to store my packets. Could you please told me how can I get the dfu store address in app part?

If the address is not visible in app, is there any api to get the address for storing dfu data in bootloader?

Thanks for your prompt response!

Sincerely,

Jin

[Joakim Jakobsen]

Hi. 

I've forwarded this to our Mesh developers, and waiting for some feedback from them. 

I'll update the ticket when I have some more information for you.

Br, 
Joakim