NRF52832 BLE does not work.

RE: NRF52832 BLE does not work.

Sergey — Tue, 07 Mar 2017 05:42:29 GMT

I found an issue in crystal oscillator soldering. Thank you for responses.

RE: NRF52832 BLE does not work.

AmbystomaLabs — Mon, 06 Mar 2017 15:04:16 GMT

If you need specific feedback on potential schematic issues, you will need to share your schematic so it can be reviewed. On the scanner, you might also try using an alternate ble scanning app. There are dozens of free ones on github for iOS and Android. Finally you don't mention testing your code on a Nordic dev board. If possible you should turn off peripheral functions in your code and see if the dev board advertises on your code.

RE: NRF52832 BLE does not work.

Sergey — Mon, 06 Mar 2017 13:07:22 GMT

Thank you for the response.

app_error_fault_handler() is called in scanner example only. No any errors occurred in init sequence in both examples.
I don't have 32kHz oscillator.
Yes, I am using LF_CLK in my test code. I also will try SYNTH clock source.
I tried several chips on the board. Same results.

RE: NRF52832 BLE does not work.

FormerMember — Mon, 06 Mar 2017 12:27:07 GMT

First, to find the reason why app_error_fault_handler() always is called, I would recommend you to run the chip in debug mode, step through the initialization in main(), and check if advertising is successfully started or not.

One suspect is the 32 kHz clock source. Do you have an external 32 kHz crystal on your board? The examples is the SDK are set up to use external 32 kHz crystal by default. I would recommend you the check if the LFCLK clock source is the root cause of the trouble on your board.