nRF52840 BLE advertising issue

[ramachandra]

Hi,

   We are developing the BLE product based based on the nrf52840 Chipset and we are facing below problem while testing in the field.

    During our development we have come across the scenario where the BLE chip suddenly stop advertising after Some days for testing.

    This doesn’t happen every time but randomly it stops working and there is no way to discover the device. The only solution to make it to advertise its name is to program it again.

    Your timely support is appreciated to resolve the issue, or let us know if similar issue is faced by anyone in the forum.

Regards,

Ram

 

 

  

[Jared]

Hi,

This doesn’t happen every time but randomly it stops working and there is no way to discover the device. The only solution to make it to advertise its name is to program it again.

1.  Does a reset help?
2. Have you checked that the application isn't asserting i.e in a error handler?
3. Are you using a watchdog?
4. What SDK and Softdevice version are you using? 

regards

Jared 

[ramachandra]

Hi Jared,

  Thanks for supporting, Please find the details below.

1.  Does a reset help? 

                 No Reset didn't help us out, Even after Power Cycle the units doesn't come back to its original state, the Chip never advertise its name until we re-flash/reprogram  the chip.

        2. Have you checked that the application isn't asserting i.e in a error handler?

               We have tried it out, but during the application running we were not able to extract the test logs from the chip using debugger. We will retry once again using different method, meanwhile please suggest if you have any method to access it.

        3. Are you using a watchdog?

            No we are not using Watchdog directly, instead the nRESET pin of nrf52840 is connected to the PIC microcontroller(Master) GPIO which intern can be used to control the reset of the chip

        4.What SDK and Softdevice version are you using?

              SDK which we are using currently are:

               1.  nRF5_SDK_15.3.0_59ac34

                2. nrf5_SDK_for_Mesh_v4.0.0_src

                3. s140nrf52611

[Jared]

Hi,

What debugger tool are you using? It's difficult to find the root cause without understanding what's happening. I'm interested in understanding what happens after a reset. Does the application assert? What exactly is preventing you from using debugger? 

Also, are you saving anything to flash i.e using the peer manager or the fds module? 

ramachandra said:

SDK which we are using currently are:

               1.  nRF5_SDK_15.3.0_59ac34

                2. nrf5_SDK_for_Mesh_v4.0.0_src

                3. s140nrf52611

Are you using Mesh or the normal SDK?  

regards

Jared

[ramachandra]

Hi Jarad,

  Could you please suggest the latest nRF52840 SDK and suitable proxy Mesh APP which can be used so that we can try it once and check it out if the problem still persist.

We need the proxy mesh app which support configuration of Generic On Off server and Generic On Off Client in the single Provisioning APP as shown below.

Reagrds,

Ram

 

[Jared]

Hi,

I'm still not sure whether this is related to a Mesh or Ble device. If it's indeed a Mesh device, are you having the issue before or after the node has been provisioned? 

ramachandra said:

Could you please suggest the latest nRF52840 SDK and suitable proxy Mesh APP

Our mesh app is called nRF Mesh, you can find it both in App store and Google Play. 

best regards

Jared