nRF52 & Fanstel EV-BT832F

[MikeDale]

all BT example projects from web hang down this call string bt_enable -> bt_settings_init -> settings_subsys_init

blinky example runs fine

[Jared]

Hi Michael,

Do you have an external low frequency crystal on your custom board?

If not, then you have to configure the board to use the internal RC oscillator instead. 

Add this to your project config file:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

regards

Jared 

[MikeDale]

the Fanstel EV-BT832F does have a 32k xtal installed on P000 and P001.

I put the two lines of code into files: prj.conf & prj_minimal.conf

no change

[MikeDale]

trying to connect from android terminal 

"connect failed gatt status 133"

[MikeDale]

added printk to main

pristine build

uart init succeeds

trying to connect from android terminal 

"connect failed gatt status 62"

also LED1 is blinking - 1 sec rate

[Jared]

Hi Michael,

MikeDale said:

uart init succeeds

trying to connect from android terminal 

"connect failed gatt status 62"

MikeDale said:

Just the nRF52 Development Kit.  Hangs up & resets at  err = bt_enable(NULL)

Ok, I'm assuming that you're able to get the device advertising since you're trying to connect to it from the android phone, and that the device doesn't reset at bt_enable() as before. What application are you using on your android phone, is it nRF Connect mobile app or are you still testing with the Fanstel mobile apps? What phone are you using?

MikeDale said:

Not sure what NCS is

It stands for nRF Connect SDK (NCS), what NCS version are you using? GATT Status 62 (BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED) is a general error code which can be caused by multiple reasons such as the peer not responding to the connection request. 

regards

Jared 

[MikeDale]

Still fails at the same place.

I deleted all nordic apps and directory's from my windows 11 pc.

Reinstalled - no change

Tried older toolchain - no change

it's not advertising - my android terminal emulator remembered it from the factory ship pairing

[Jared]

Do you have an android phone that you can test this with? If the board is blinking then it usually indicates that the board is advertising. Please try to scan the device running unmodified peripheral_uart on the DK, and use the nRF Connect mobile to scan for the advertisement. 

Also, make sure that you aren't running the sample in debug mode with breakpoints set. 

One more thing, the gatt status error code, did you read this from the android app or from the log output from the nRF5340?

regards

Jared 

[MikeDale]

tried again and your right

- my deleting and reinstalling all Nordic stuff seems to have gotten me past the fail at bt_enable().  Just stepped past in debugger.

Where does the LOG_INF statement log to - I see no results in my terminal window

[Jared]

Ok, so now you're able to get it advertising? Do you see the board advertising in the nRF Connect mobile app? 

The log statements goes out on the serial terminal, if you're using the nRF52832 development kit then you should see the log output on the same virtual port that the Zephyr boot log is printed on.

regards
Jared