Hi Maureen, > The final release remains scheduled for 25 Sep. I see that one of my PR has not been merged, because there was a merge conflict introduced due to another PR that was merged. PR: https://

> I think it will integrate better with the new design but let me continue with the current master for the time being. Current master has not accepted any new control procedure code except for bug fix

Hi Khaled, Control procedures is a major implementation in the controller, the new overhaul work is already into its 10th calendar month. I would not consider adding new control procedures to be ever

Hi Khaled, Currently the link layer is undergoing a major overhaul of the control procedure design. You can refer to the changes in the topic-ble-llcp branch. That said, you are welcome to send a draf

Please create a github issue with details of building your application and steps to reproduce the issue. Do specify the commit hash, and if you have a branch, do mention that too. I see you have re-se

#ble #nrf52840

Sorry, forgot to paste the link: https://github.com/zephyrproject-rtos/zephyr/pull/23258 -Vinayak

#ble #nrf52840

Please identify and increase thread stack size based on your application code. You can use the implementation in this PR to analyse stack usage. -Vinayak

#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

Please provide the details of: # arm-none-eabi-addr2line -e <path to zephyr.elf file> 0x000390ee -Vinayak

#ble #nrf52840

Ok, Please create a GH issue and mentioned as much details as possible to help me reproduce the issue. Vinayak

#ble #hci #nrf52480 #uart

Hi Jamie, All the disconnects are Host Bluetooth stack initiated. I will need some help from BlueZ guys to throw some light here. Regards, Vinayak

#ble #hci #nrf52480 #uart

Hi Jamie, A btmon log would help identify the reason for disconnection. > the connection parameter update still fails but even minutes later I am still connected to the remote device. This is weird, t

#ble #hci #nrf52480 #uart

Hi, Both Mayank and Jamie, I am interested in the way the HCI packets are transported to the Host Bluetooth stack. In case of use of nRF DKs and Dongle, if using JLink debugger host firmware, you need

#ble #hci #nrf52480 #uart

Hi Mayank, Are you using any host debugger firmware to convert to USB? or using 3v TTL connections to your custom board from nRF52840? For those using USB_UART conversion, I am assuming you are using

#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 biwa, I am assuming that you wish to get the BLE radio channel number used in the scan window as part of the advertisement report like in the lines of RSSI. But as this information is not part of s

#ble

Hi Tommy, To test 2M Phy please use LE Receiver Test Command [v2] with OCF 0x0033 instead of the v1 command you are using. Regards, Vinayak

Hi Jos, Currently, by default all BLE connections default to 2Mbps if supported by both local and peer device. If you have mixed peers with support for 2 Mbps absent in some of them, then you will not

Hi David, You can try adding the device to “USB Device filters” in the VirtualBox guest’s settingsàports à USB. Usually, if the Segger firmware has updates, the JLink will try firmware upgrade hence w

Hi Tommy, Sorry, I am not able to try out your usecase on Bluez, as it has been quite sometime that I have been using with Bluez, due to my priorities, you may have to wait or ask someone else on the