Unable to connect (bond) to nrf52810 using nrfConnect

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Mon, 13 Aug 2018 09:52:10 GMT

Thank you!

My device works!

I changed the SoftDevice calibration timer interval from:

#define NRF_SDH_CLOCK_LF_RC_CTIV 0

To:

#define NRF_SDH_CLOCK_LF_RC_CTIV 16

RE: Unable to connect (bond) to nrf52810 using nrfConnect

Vidar Berg — Mon, 13 Aug 2018 07:38:51 GMT

Strange, I don't see any relevant differences with your approach compared to what I did. Are you testing with a "clean" SDK copy, or is it possible that there are other changes in your code base? Attached is the code I used here.

devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_15.0.0_5F00_52810_5F00_hts.zip

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Fri, 10 Aug 2018 10:45:06 GMT

I have done the following steps.

1. Downloaded sdk v15
2. Point toolchain to gcc folder
3. Commented out buttons_leds_init(&erase_bonds);
-> And removed the -Werror flag to hide the unused function warning
4. Commented out the two DDEVELOP_IN_NRF52832 flags in the Makefile
5. Made these changes to the sdk_config
-> Set CLOCK_CONFIG_LF_SRC to RC
-> Set NRFX_CLOCK_CONFIG_LF_SRC to RC
-> Set NRF_SDH_CLOCK_LF_SRC to NRF_CLOCK_LF_SRC_RC
-> Set NRF_SDH_CLOCK_LF_ACCURACY to NRF_CLOCK_LF_ACCURACY_500_PPM

Then I did the following

make clean
make erase
make flash_softdevice
make flash

I am still having issues. Is there something I am missing. There must be some reason why your hex file works perfectly. Can you think of what other step I should do?

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Thu, 09 Aug 2018 14:49:41 GMT

Hmm, when I commented out the buttons_led_init(&erase_bonds) the device didn't even advertise. Perhaps I will try that again just in case.

I might send a copy of my pin out when I get the chance. I haven't changed any default pins from the downloaded sdk.

I have re-flashed your .hex a number of times and it works perfectly every time. Perhaps the sdk_config is different? I can send copy of my sdk_config if you think that might help?

RE: Unable to connect (bond) to nrf52810 using nrfConnect

Vidar Berg — Thu, 09 Aug 2018 14:18:19 GMT

I just commented out buttons_leds_init(&erase_bonds); in main so that the IOs did not get initialized. Meant to type RCOSC (RC oscillator).

So it appears that the problem might be related to the pinout, or have you changed the default pins already?

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Thu, 09 Aug 2018 12:44:13 GMT

I tried using the RC oscillator (using the sdk_config tool). This did not change anything.

Your hex works perfectly on my hardware, I am able to connect without any issues!

I re-downloaded the sdk v15 and commented out the DEVELOP_IN_NRF52832 define. Then I flashed the example without any modifications. I had the same issues on my nrf52810.

Perhaps this is an issue with my LEDs and Buttons or maybe the RSOSC. What is the RSOSC and how do I enable it?

What did you do to disable the Buttons and LEDs?

RE: Unable to connect (bond) to nrf52810 using nrfConnect

Vidar Berg — Thu, 09 Aug 2018 08:32:31 GMT

I tried the ble_peripheral/bls_app_hts from SDK 15.0.0 on 52810 without DEVELOP_IN_NRF52832, and did not experience the connection problem. Maybe this could be HW related. Are you using an external crystal for the low frequency clock? In that case, could you try to use the internal RC oscillator? Inaccurate frequency may explain why the phone fails to connect.

Here is the .hex file I used for test (LEDs and Buttons disabled and RSOSC enabled):

devzone.nordicsemi.com/.../nrf52810_5F00_hts_5F00_w_5F00_softdevice.hex

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Thu, 09 Aug 2018 07:49:00 GMT

Yes, DEVELOP_IN_NRF52832 is only being used in system_nrf52810.c

If It helps, I am have code that is using the saadc.

To be clear, the nrf52810 can advertise correctly. But It hangs when trying to connect. See the picture below.

I am currently developing from the ble_peripheral/bls_app_hts example.

RE: Unable to connect (bond) to nrf52810 using nrfConnect

Vidar Berg — Thu, 09 Aug 2018 06:44:56 GMT

Looks like you are using the correct flags at least. Just to confirm, the exact same application .hex (without DEVELOP_IN_NRF52832) and s112 runs fine on the 52832)? Could you search through your project to see if DEVELOP_IN_NRF52832 is being used other places in your code (not just system_nrf52810.c)?

RE: Unable to connect (bond) to nrf52810 using nrfConnect

mredp — Thu, 09 Aug 2018 02:24:50 GMT

I used the s132 soft device originally, however, when I flash the nrf52832 with the s112 soft device it works fine aswell.

Is this the part of the Makefile that your after?

# Libraries common to all targets
LIB_FILES += \

# Optimization flags
OPT = -Os -g3
# Uncomment the line below to enable link time optimization
#OPT += -flto

# C flags common to all targets
CFLAGS += $(OPT)
CFLAGS += -DBOARD_PCA10040
CFLAGS += -DCONFIG_GPIO_AS_PINRESET
# CFLAGS += -DDEVELOP_IN_NRF52832
CFLAGS += -DFLOAT_ABI_SOFT
CFLAGS += -DNRF52810_XXAA
CFLAGS += -DNRF52_PAN_74
CFLAGS += -DNRF_SD_BLE_API_VERSION=6
CFLAGS += -DS112
CFLAGS += -DSOFTDEVICE_PRESENT
CFLAGS += -DSWI_DISABLE0
CFLAGS += -mcpu=cortex-m4
CFLAGS += -mthumb -mabi=aapcs
CFLAGS += -Wall -Werror
CFLAGS += -mfloat-abi=soft
# keep every function in a separate section, this allows linker to discard unused ones
CFLAGS += -ffunction-sections -fdata-sections -fno-strict-aliasing
CFLAGS += -fno-builtin -fshort-enums

# C++ flags common to all targets
CXXFLAGS += $(OPT)

# Assembler flags common to all targets
ASMFLAGS += -g3
ASMFLAGS += -mcpu=cortex-m4
ASMFLAGS += -mthumb -mabi=aapcs
ASMFLAGS += -mfloat-abi=soft
ASMFLAGS += -DBOARD_PCA10040
ASMFLAGS += -DCONFIG_GPIO_AS_PINRESET
# ASMFLAGS += -DDEVELOP_IN_NRF52832
ASMFLAGS += -DFLOAT_ABI_SOFT
ASMFLAGS += -DNRF52810_XXAA
ASMFLAGS += -DNRF52_PAN_74
ASMFLAGS += -DNRF_SD_BLE_API_VERSION=6
ASMFLAGS += -DS112
ASMFLAGS += -DSOFTDEVICE_PRESENT
ASMFLAGS += -DSWI_DISABLE0

# Linker flags
LDFLAGS += $(OPT)
LDFLAGS += -mthumb -mabi=aapcs -L$(SDK_ROOT)/modules/nrfx/mdk -T$(LINKER_SCRIPT)
LDFLAGS += -mcpu=cortex-m4
# let linker dump unused sections
LDFLAGS += -Wl,--gc-sections
# use newlib in nano version
LDFLAGS += --specs=nano.specs

nrf52810_xxaa: CFLAGS += -D__HEAP_SIZE=2048
nrf52810_xxaa: CFLAGS += -D__STACK_SIZE=2048
nrf52810_xxaa: ASMFLAGS += -D__HEAP_SIZE=2048
nrf52810_xxaa: ASMFLAGS += -D__STACK_SIZE=2048

# Add standard libraries at the very end of the linker input, after all objects
# that may need symbols provided by these libraries.
LIB_FILES += -lc -lnosys -lm


.PHONY: default help

# Default target - first one defined
default: nrf52810_xxaa

RE: Unable to connect (bond) to nrf52810 using nrfConnect

Vidar Berg — Wed, 08 Aug 2018 11:25:52 GMT

Hi,

When you developed your application on the 52832, did you use the s132 or s112 softdevice? Also, can you provide a list of the defines you have in your Makefile? Reason I ask is that I wonder if the application might be using APIs not available in s112.