NRF52832 questions

RE: NRF52832 questions

Ibery — Thu, 06 Feb 2020 22:10:31 GMT

Hi,

Finally I solved the problems, here are what I found:

1) Hardware problem - The 3.3V is not stable because the capacitor is too low (2.2uF). If connected to debugger, the debugger has +3.3V to support the target board so it works fine. But if the debugger is removed, the 3.3V fails to start up because of the poor transient response of the capacitor so it keeps resetting. I changed the capacitor to 10uF tant. cap. and it works fine now.

2) Modified as per your suggestion. It works fine

3) Still working on it. Seems that the nRF Connect not able to connect to the central.

4) Modified as per your suggestion. It works fine.

Thanks for your help.

RE: NRF52832 questions

Ibery — Thu, 06 Feb 2020 02:43:56 GMT

Thanks for your reply. When I connected to the debugger, the program runs correctly. If I pull the USB cable of the debugger out, the board just keep resetting. I am check the reset and watchdog now. May be it is hardware problem.

Thanks for your help.

RE: NRF52832 questions

Einar Thorsrud — Wed, 05 Feb 2020 12:46:37 GMT

Hi,

1). How have you verified that the device resets when not having a debugger connected? The ble_app_multilink_central examples process logs in idle_state_handle(). Therefore it is expected that you do not see any logs if you do not call it. If you do not want to process logs in the idle_state_handle(), but want to process them immediately instead, you should set NRF_LOG_DEFERRED to 0 in the projects sdk_config.h.

2) BLE_GAP_TX_POWER_ROLE_SCAN_INIT will not affect the Tx power when advertising. For that, you must use BLE_GAP_TX_POWER_ROLE_ADV.

3) The example scans for devices with the name "Nordic_Blinky", and will only connect if such a device is found. If you want to filter on something else, you should modify the filter configuration in scan_init().

4) Please build a debug build (by selecting "Debug" from the build configuration dropdown if using SES, or defining DEBUG as a preprocessor symbol if usign another toolchain). Then you will get a log output specifying details about the error (filename, line number and error code).