This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nrf52810 not showing even it is advertising

Hi,

I have a custom Nrf52810 board. It was working fine and was advertising well. Somehow ble chip got damaged and I needed to replace it.

After I replaced, I can do debug using Jlink. In the debug windows it says advertising.

But I don't see it in the NRF connect app. I replaced both crystals. Still no change. 

What could be the issue? 

Parents
  • Hello,

    Somehow able chip got damaged and I needed to replace it.

    That is very unfortunate. What happened?

    It the debug windows it sys advertising.

    But I don't see in NRF connect app. I replaced both crystals. Still no change. 

    Could you provide a sniffer trace of the communication, so that we may verify that the advertising is happening as expected?
    You could see the guide for how to get the sniffer trace here.

    Best regards,
    Karl

     

  • Will sniffer do any different than the NRF Connect app?  I don't see the device in any other app also. 

  • Hello,

    Yes, the sniffer will provide a trace of all the BLE communication that is happening around it. This way, you can externally verify that the BLE packages are being sent as expected from your device.
    In this case, we are interested in seeing if your packages are being sent at all, and if they are: if they are according to specification. Perhaps their timing is off, or their content is corrupt?
    Perhaps they are not sent at all.

    These things will help us greatly when finding the source of your error.

    In the case that the sniffer hears nothing from your device, could you ensure that the device functions as expected internally? By this, it would be great if you could verify some non-radio functionality, such as the UART example application.

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Reply
  • Hello,

    Yes, the sniffer will provide a trace of all the BLE communication that is happening around it. This way, you can externally verify that the BLE packages are being sent as expected from your device.
    In this case, we are interested in seeing if your packages are being sent at all, and if they are: if they are according to specification. Perhaps their timing is off, or their content is corrupt?
    Perhaps they are not sent at all.

    These things will help us greatly when finding the source of your error.

    In the case that the sniffer hears nothing from your device, could you ensure that the device functions as expected internally? By this, it would be great if you could verify some non-radio functionality, such as the UART example application.

    Looking forward to resolving this issue together!

    Best regards,
    Karl

Children
No Data
Related