Topics

#BluetoothMesh: if Node reprovisioned then it not get stored on SoC flash

vikrant8051 <vikrant8051@...>
 

Hi,

If after complete or partial provisioning, execute node-reset command then in that case I have observe following things :

1) Node get reprovision
2) but after reboot, it boot as unprovisioned device.

Has anybody observe this ?

Thank You !!

vikrant8051 <vikrant8051@...>
 

Hi,

Yes, I confirmed my observation. And happening this every time.

I also tried it with #nRFMesh app. In that case too, if I do
(provision + configuration) -> ( node-reset ) -> (provision + configuration) --> Reset/ Power down the board-> Device found in
unprovisioned state.

Thank You !!

On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <vikrant8051@...> wrote:
Hi,

If after complete or partial provisioning, execute node-reset command then in that case I have observe following things :

1) Node get reprovision
2) but after reboot, it boot as unprovisioned device.

Has anybody observe this ?

Thank You !!


Johan Hedberg
 

Hi Vikrant,

Is this with NFFS or FCB? I remember testing this with FCB and it worked
correctly.

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
Hi,

Yes, I confirmed my observation. And happening this every time.

I also tried it with #nRFMesh app. In that case too, if I do
(provision + configuration) -> ( node-reset ) -> (provision +
configuration) --> Reset/ Power down the board-> Device found in
unprovisioned state.

Thank You !!

On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <@vikrant8051> wrote:

Hi,

If after complete or partial provisioning, execute *node-reset* command
then in that case I have observe following things :

1) Node get reprovision
2) but after reboot, it boot as unprovisioned device.

Has anybody observe this ?

Thank You !!


vikrant8051 <vikrant8051@...>
 

Hi Johan,

It is with default #FCB.

On Wed, Jun 13, 2018 at 6:24 PM, Johan Hedberg <johan.hedberg@...> wrote:
Hi Vikrant,

Is this with NFFS or FCB? I remember testing this with FCB and it worked
correctly.

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
> Hi,
>
> Yes, I confirmed my observation. And happening this every time.
>
> I also tried it with #nRFMesh app. In that case too, if I do
> (provision + configuration) -> ( node-reset ) -> (provision +
> configuration) --> Reset/ Power down the board-> Device found in
> unprovisioned state.
>
> Thank You !!
>
> On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <vikrant8051@...> wrote:
>
> > Hi,
> >
> > If after complete or partial provisioning, execute *node-reset* command
> > then in that case I have observe following things :
> >
> > 1) Node get reprovision
> > 2) but after reboot, it boot as unprovisioned device.
> >
> > Has anybody observe this ?
> >
> > Thank You !! > >
> >

Johan Hedberg
 

Hi Vikrant,

I just tried your exact steps with the mesh_shell app, and it works
correctly (i.e. after the power cycle the board comes back as
provisioned). I used the nRF51 USB dongle, fwiw. Is it possible that
your NVS usage is somehow messing with things?

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
Hi Johan,

It is with default #FCB.

On Wed, Jun 13, 2018 at 6:24 PM, Johan Hedberg <@jhe>
wrote:

Hi Vikrant,

Is this with NFFS or FCB? I remember testing this with FCB and it worked
correctly.

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
Hi,

Yes, I confirmed my observation. And happening this every time.

I also tried it with #nRFMesh app. In that case too, if I do
(provision + configuration) -> ( node-reset ) -> (provision +
configuration) --> Reset/ Power down the board-> Device found in
unprovisioned state.

Thank You !!

On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <@vikrant8051>
wrote:

Hi,

If after complete or partial provisioning, execute *node-reset* command
then in that case I have observe following things :

1) Node get reprovision
2) but after reboot, it boot as unprovisioned device.

Has anybody observe this ?

Thank You !!


vikrant8051 <vikrant8051@...>
 


Hi Johan,

I've completely removed NVS from my local project.
Even after that facing same issue.

If you provision & configure -> reset the board -> then it work as expected.

But I'm not talking about power reset...I'm talking about Provisioner node-reset command.

For e.g.

provision & configured DEVICE using #meshctl  --> send node-reset command via #meshctl  --> unprovision state  --> provision & configure it again --> now do power reset/ hardware reset -> Here device should be
in provisioned state but I always found it in Unprovisioned state.


Thank You !!

On Wed, Jun 13, 2018 at 7:01 PM, Johan Hedberg <johan.hedberg@...> wrote:
Hi Vikrant,

I just tried your exact steps with the mesh_shell app, and it works
correctly (i.e. after the power cycle the board comes back as
provisioned). I used the nRF51 USB dongle, fwiw. Is it possible that
your NVS usage is somehow messing with things?

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
> Hi Johan,
>
> It is with default #FCB.
>
> On Wed, Jun 13, 2018 at 6:24 PM, Johan Hedberg <johan.hedberg@...>
> wrote:
>
> > Hi Vikrant,
> >
> > Is this with NFFS or FCB? I remember testing this with FCB and it worked
> > correctly.
> >
> > Johan
> >
> > On Wed, Jun 13, 2018, Vikrant More wrote:
> > > Hi,
> > >
> > > Yes, I confirmed my observation. And happening this every time.
> > >
> > > I also tried it with #nRFMesh app. In that case too, if I do
> > > (provision + configuration) -> ( node-reset ) -> (provision +
> > > configuration) --> Reset/ Power down the board-> Device found in
> > > unprovisioned state.
> > >
> > > Thank You !!
> > >
> > > On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <vikrant8051@...>
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > If after complete or partial provisioning, execute *node-reset* command
> > > > then in that case I have observe following things :
> > > >
> > > > 1) Node get reprovision
> > > > 2) but after reboot, it boot as unprovisioned device.
> > > >
> > > > Has anybody observe this ?
> > > >
> > > > Thank You !! > > > >
> > > >
> >

Johan Hedberg
 

Hi Vikrant,

I understood what you meant. And those are the steps I followed. I used
Nordic's new iOS mesh app and used its "node reset" feature. Then I
reprovisioned and after that did a power-cycle. After that the node came
back up as provisioned.

Johan

On Wed, Jun 13, 2018, vikrant8051 wrote:
Hi Johan,

I've completely removed NVS from my local project.
Even after that facing same issue.

If you provision & configure -> reset the board -> then it work as
expected.

But I'm not talking about power reset...I'm talking about Provisioner
node-reset command.

For e.g.

provision & configured DEVICE using #meshctl --> send node-reset command
via #meshctl --> unprovision state --> provision & configure it again -->
now do power reset/ hardware reset -> Here device should be
in provisioned state but I always found it in Unprovisioned state.


Thank You !!

On Wed, Jun 13, 2018 at 7:01 PM, Johan Hedberg <@jhe>
wrote:

Hi Vikrant,

I just tried your exact steps with the mesh_shell app, and it works
correctly (i.e. after the power cycle the board comes back as
provisioned). I used the nRF51 USB dongle, fwiw. Is it possible that
your NVS usage is somehow messing with things?

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
Hi Johan,

It is with default #FCB.

On Wed, Jun 13, 2018 at 6:24 PM, Johan Hedberg <@jhe>
wrote:

Hi Vikrant,

Is this with NFFS or FCB? I remember testing this with FCB and it
worked
correctly.

Johan

On Wed, Jun 13, 2018, Vikrant More wrote:
Hi,

Yes, I confirmed my observation. And happening this every time.

I also tried it with #nRFMesh app. In that case too, if I do
(provision + configuration) -> ( node-reset ) -> (provision +
configuration) --> Reset/ Power down the board-> Device found in
unprovisioned state.

Thank You !!

On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <@vikrant8051>
wrote:

Hi,

If after complete or partial provisioning, execute *node-reset*
command
then in that case I have observe following things :

1) Node get reprovision
2) but after reboot, it boot as unprovisioned device.

Has anybody observe this ?

Thank You !!



vikrant8051 <vikrant8051@...>
 

Hi Johan, 
Which app you used for testing ?
Is it samples/boards/nrf52/mesh/onoff-app by adding persistent storage support ?

Could you please test it for PR:8296 by removing NVS from it ? 

Thanks!!

On Wed, Jun 13, 2018, 8:11 PM Johan Hedberg <johan.hedberg@...> wrote:
Hi Vikrant,

I understood what you meant. And those are the steps I followed. I used
Nordic's new iOS mesh app and used its "node reset" feature. Then I
reprovisioned and after that did a power-cycle. After that the node came
back up as provisioned.

Johan

On Wed, Jun 13, 2018, vikrant8051 wrote:
> Hi Johan,
>
> I've completely removed NVS from my local project.
> Even after that facing same issue.
>
> If you provision & configure -> reset the board -> then it work as
> expected.
>
> But I'm not talking about power reset...I'm talking about Provisioner
> node-reset command.
>
> For e.g.
>
> provision & configured DEVICE using #meshctl  --> send node-reset command
> via #meshctl  --> unprovision state  --> provision & configure it again -->
> now do power reset/ hardware reset -> Here device should be
> in provisioned state but I always found it in Unprovisioned state.
>
>
> Thank You !!
>
> On Wed, Jun 13, 2018 at 7:01 PM, Johan Hedberg <johan.hedberg@...>
> wrote:
>
> > Hi Vikrant,
> >
> > I just tried your exact steps with the mesh_shell app, and it works
> > correctly (i.e. after the power cycle the board comes back as
> > provisioned). I used the nRF51 USB dongle, fwiw. Is it possible that
> > your NVS usage is somehow messing with things?
> >
> > Johan
> >
> > On Wed, Jun 13, 2018, Vikrant More wrote:
> > > Hi Johan,
> > >
> > > It is with default #FCB.
> > >
> > > On Wed, Jun 13, 2018 at 6:24 PM, Johan Hedberg <johan.hedberg@...>
> > > wrote:
> > >
> > > > Hi Vikrant,
> > > >
> > > > Is this with NFFS or FCB? I remember testing this with FCB and it
> > worked
> > > > correctly.
> > > >
> > > > Johan
> > > >
> > > > On Wed, Jun 13, 2018, Vikrant More wrote:
> > > > > Hi,
> > > > >
> > > > > Yes, I confirmed my observation. And happening this every time.
> > > > >
> > > > > I also tried it with #nRFMesh app. In that case too, if I do
> > > > > (provision + configuration) -> ( node-reset ) -> (provision +
> > > > > configuration) --> Reset/ Power down the board-> Device found in
> > > > > unprovisioned state.
> > > > >
> > > > > Thank You !!
> > > > >
> > > > > On Wed, Jun 13, 2018 at 4:32 PM, vikrant8051 <vikrant8051@...>
> > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > If after complete or partial provisioning, execute *node-reset*
> > command
> > > > > > then in that case I have observe following things :
> > > > > >
> > > > > > 1) Node get reprovision
> > > > > > 2) but after reboot, it boot as unprovisioned device.
> > > > > >
> > > > > > Has anybody observe this ?
> > > > > >
> > > > > > Thank You !!
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
>
>
>