1. devel@lists.zephyrproject.org
Topics

[Zephyr-users] Device Firmware Update + Zephyr + #bluetoothmesh

vikrant8051 <vikrant8051@...>
 



On Sat, Apr 14, 2018, 11:18 AM Vikrant More <vikrant8051@...> wrote:
Hi Rodrigo,

You can start with this,


You have to integrate SMP_Server demo example in your current #BluetoothMesh project.

It will be tedious process, so my advice is to start with simple example.

For example, edit $zephyr/samples/subsys/mgmt/mcumgr/smp_svr so that it will blink LED1 on your board & flash it along with mcuboot as per link I have provided.

Then re-edit same smp_svr, so that it will blink LED2 on your board & now try to upgrade this using #DFU_OTA feature. This will help you lot to understand over all process. 

Regards, 
vikrant

On Sat, Apr 14, 2018, 3:07 AM Rodrigo Peixoto <rodrigopex@...> wrote:

Hi guys,

is it possible to use the Nordic DFU feature in conjunction to Zephyr. I need to upgrade the nodes of a BT mesh network and it would be amazing if I could.

If it isn't, is there any alternative to that?

Thank you. Best regards,

Rodrigo Peixoto. Ayna - [Embedded systems design house]
Rodrigo Peixoto <rodrigopex@...>
 

That is great Vikrant.

I was thinking they couldn't work together. I will do as you said.

Thank you. 

Best regards,
Rodrigo Peixoto 

Ayna - [Embedded systems design house]


On Sat, 14 Apr 2018 at 02:49 Vikrant More <vikrant8051@...> wrote:


On Sat, Apr 14, 2018, 11:18 AM Vikrant More <vikrant8051@...> wrote:
Hi Rodrigo,

You can start with this,


You have to integrate SMP_Server demo example in your current #BluetoothMesh project.

It will be tedious process, so my advice is to start with simple example.

For example, edit $zephyr/samples/subsys/mgmt/mcumgr/smp_svr so that it will blink LED1 on your board & flash it along with mcuboot as per link I have provided.

Then re-edit same smp_svr, so that it will blink LED2 on your board & now try to upgrade this using #DFU_OTA feature. This will help you lot to understand over all process. 

Regards, 
vikrant

On Sat, Apr 14, 2018, 3:07 AM Rodrigo Peixoto <rodrigopex@...> wrote:

Hi guys,

is it possible to use the Nordic DFU feature in conjunction to Zephyr. I need to upgrade the nodes of a BT mesh network and it would be amazing if I could.

If it isn't, is there any alternative to that?

Thank you. Best regards,

Rodrigo Peixoto. Ayna - [Embedded systems design house]
vikrant8051 <vikrant8051@...>
 

Hi Rodrigo,

Working on #DFU_OTA feature is not at top of my priority list. I had just checked it & try to understand overall mechanism. 

Now I will prefer to wait till 
1) Zephyr #BluetoothMesh stack allow us to save Provisioning & Configuration details on SoC flash

2) plus it should also take care of saving data like sequence no. &  Model states on SoC flash on periodic basis

This is important, because Device firmware upgrade OTA should not changed those data if overall process is going to be automatic for end-user perspective.

There will be roughly four section in SoC flash-

1. for MCUboot
2. for flash memory (which will acts like eeprom)
3. slot_0 (current image)
4. slot_1 ( temporary location for new image after DFU )

This is not yet defined. Plus we don't know how to do DFU_OTA using Android or iOS App. 

So let's us go step by step. Hope upcoming LTS 1.12 come up as complete solution.

Meanwhile, we can work on Friend & Low Power Node implementation, design Models which are mentioned in attached image.

Regards,
Vikrant

On Fri, Apr 27, 2018, 7:44 PM Rodrigo Peixoto <rodrigopex@...> wrote:

Hi vikrant.

I could do the integration! Now the SMP_Server sample is integrated to the mesh one. I need to play a little more with it. I have already tested the mcumgr a lot, but not too much the mesh one after the integration. I am considering the possibility of creating a sample with the integrated code.

What do you think? Necessary?

Best regards, Rodrigo Peixoto.
Rodrigo Peixoto <rodrigopex@...>
 

Vikrant,
answering inline. 

Working on #DFU_OTA feature is not at top of my priority list. I had just checked it & try to understand overall mechanism. 

Ok.
 
Now I will prefer to wait till 
1) Zephyr #BluetoothMesh stack allow us to save Provisioning & Configuration details on SoC flash

2) plus it should also take care of saving data like sequence no. &  Model states on SoC flash on periodic basis

This is important, because Device firmware upgrade OTA should not changed those data if overall process is going to be automatic for end-user perspective.

There will be roughly four section in SoC flash-

1. for MCUboot
2. for flash memory (which will acts like eeprom)
3. slot_0 (current image)
4. slot_1 ( temporary location for new image after DFU )

This is not yet defined. Plus we don't know how to do DFU_OTA using Android or iOS App. 

So let's us go step by step. Hope upcoming LTS 1.12 come up as complete solution.

I really need that.
 
Meanwhile, we can work on Friend & Low Power Node implementation, design Models which are mentioned in attached image.

Do you need help on that? I am a little bit confusing. 
I was willing to create the sample related to OTA and mesh. But if there is other sample as you said related to mesh, it would be a pleasure to help.

Is there any thing I can do?

Best regards,
Rodrigo Peixoto.
1 - 4 of 4