Hi Robert, Can you raise a github issue with these détails? We'll have a look when possible. Otherwise, have you tried to use one of d'amples/bluetooth/peripheral* applications ? I've tested those rec

#bluetooth #ble #stm32

We have some questions regarding the BLE MESH, So kindly go through below hardware and software setup and please guide us about our queries. Your quick response will be highly appreciated. Hardware se

#ble #bluetoothmesh #hci #zephyrbluetoothmesh #uart

Hi Carl, Thank you for reporting the issue. You may send a pull request to fix accordingly and I will be glad to review the same. As this is a bug, we could get this in for the 2.6 release. Regards, V

#ble

Hi, I have problem using function bt_passkey_set(). Even if I use this function pairing use random number. In application I use BT_SECURITY_L4 level. This is my config for Ble. CONFIG_BT=y CONFIG_BT_S

#ble #nrf52480

Hello Community, We are using nordic's nrf52840_pca10056 chip on our custom board and on top of that zephyr's 'hci_uart' application is running. (Zephyr version v2.1.0).On our custom board, the host s

#hci #nrf52480 #uart #ble #bluetooth

Hi Ryan, This is still TBD, I will soon call a meeting to decide on this year’s qualification plans. Thanks, Carles

#ble #nrf52840

in bluetooth/host/gatt.c, the notify member of bt_gatt_subscribe_params is called without checking for a null pointer. In my central, the peripheral disconnected while I was subscribed to an attribute

#ble

Hi Community, I have one custom board on which I'm having Nordic's nrf52840_pca10056 chip on which i have flashed zephyr's 'hci_uart' sample application for the beacon scanning purpose. "hci_uart" app

#ble #hci #nrf52480 #uart

Hello All, I have one question regarding the ability of zephyr's hci_uart sample app. I am using this application on nrf52840_pca10056 for scanning the ble beacons. Scenario is i can see "hci0" interf

#uart #ninja #ble #hci #nrf52480

The ZEBRA RFC (see RFC: https://github.com/zephyrproject-rtos/zephyr/issues/23465) is a feature proposal for a simple way to add secure authentication between two Bluetooth devices. ZEBRA is not part

#ble

Yes previously I posted same issue, but iam not creating any threads in my application

#ble #nrf52840

But i'm not using any threads in my application, did you mean ble created threads

#ble #nrf52840

You can use nRF sniffer found here: https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE And check the wireshark logs for advertising interval and channels. If

#ble #hci #nrf52480 #samples #uart

Hi Vinayak, Thank you for the support. I have created the GH issue for the same https://github.com/zephyrproject-rtos/zephyr/issues/23319 Thanks, Mayank

#ble #hci #nrf52480 #uart

Hi Narendar, Please create a github bug report, with details on how to build your application and reproduce the issue. You may share a branch in the GH issue if that is faster for me or others to repr

#ble #nrf52840 #uart

Hi Johan, Should i go with the Hardware flow control as enable to solve the buffer flow issue ? Not using HWFC could have any other adverse effect? As my current implementation is based on flow contro

#uart #samples #ble #hci #nrf52480

In version 1.14.1, there appears to be a race condition when updating an indication value. It results in a BUS FAULT, which occurs because a pointer becomes null. Here are the Zephyr ATT print message

#ble #nrf52480

OK I was create a github issue. thank you.

#ble

Hi Venkatesh, hciconfig uses a legacy ioctl kernel interface which is only able to retrieve the public address of a controller. nRF controllers do not come with any public address by default, which is

#hci #ble #nrf52 #nrf52840

Hi Mayank, I am surprised to say this doesn't appear to be covered in the MCUboot documentation. David, did I miss it somewhere? Mayank: you need at least three pins connecting the i.MX and nRF chips:

#ble #hci #nrf52480 #uart