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

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

Hi Mayank: I had a similar requirement, also without a button on the same Nordic chip. I simply copied this file into my project, and called smp_svr_init() from my main() after bluetooth was up and ru

#ble #hci #nrf52480 #uart

Hi Q1 – no, this mens that higher part of BLE stack runs on HCI client which has no access to nRF52840 flash at all. Q2 – mcuboot serial recovery or your proprietary protocol which can share common ua

#hci #nrf52480 #ble #uart #samples

Thanks Adam, I have upgraded zephyr to latest version (2.1.0) using west update. Now with the configuration of my application as well as mcuboot, i reached at the stage where i can upload the signed a

#ble #bluetoothmesh #nrf52840 #uart

Hi Josef, There is no maximum, neither as a central nor as a peripheral, nor combined. Whatever you can fit in RAM and in multiplexed time (depending on connection intervals, use of slave latency, etc

#uart #ble #hci #nrf52480

Hi Ryan, The UART driver itself uses the GPIO driver internally so I don’t think there should be any issues with your usecase. Regards, Carles From: <devel@...> on behalf of Ryan E

#uart #nrf52480

Hi guys, I met a problem here and hop anyone can help. Thanks. I enable hardware control in menuconfig, build a firmware of hci_uart sample and burn the firmware into nrf52_pca10040 (nrf52832), and th

#uart #nrf52832

Looks like UART flow control is not implemented on stm32f746g_disco. I am going to get that working. Hopefully that makes this setup work.

#uart #bluetoothmesh #hci

Hi guys, I met a problem with official hci_uart sample. Hope anybody can give me any advice,thanks. I use NRF52832's official develop board running hci_uart sample as a controller, I send hci commands

#nrf52832 #uart #hci