I have got the answer at Nordic DevZone: https://devzone.nordicsemi.com/f/nordic-q-a/48346/is-it-possible-to-implement-concurrent-link-with-mutiple-roles-one-device-provide-both-peripheral-and-central

#nrf52832 #ble

Hi Robert, You could try using BT_LE_ADV_OPT_ONE_TIME with bt_le_adv_start(). That should ensure that the stack doesn’t automatically restart advertising after a disconnection event. Johan

#ble

Hi Henry, I wonder if this could be related to the lack of buffers on the host, I assume you would use bt_gatt_notify with NULL conn which will take care of notifying each connection but that may end

#ble #nrf52840

Hi Henry, This is news to me and, although it might be expected, I would like to check with a couple of people. So I think this deserves being tracked. Would you mind opening a “Question” issue on Git

#nrf52840 #ble

Hi Henry, Take a look at the configuration used in Nordic’s throughput sample: https://github.com/tejlmand/fw-nrfconnect-nrf/blob/master/samples/bluetooth/throughput/prj.conf I think you are missing s

#ble #nrf52 #nrf52832 #nrf52840

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 guys, I'd like to encrypt the advertise packet since some secure fields in the payload. But I did not find any clue yet. So anybody knows how to implement this feature with zephyr? Thank a lot if y

#ble #nrf52832

Hi, I am making a program in a slave (peripheral) device. I can get a master (central) device connect to the slave (peripheral) device. But, how can I make the slave device to get the device name of t

#ble #nrf52480

Hi all, I'm developing a system with Zephyr that has been configured to have 4 Bluetooth connections and 4 paired devices for a Nordic nRF52832 SoC. CONFIG_BT_MAX_CONN=4 CONFIG_BT_MAX_PAIRED=4 I'm fin

#ble

Hi. It looks that you have HFCLK running all the time. This is probably caused by small issue in power management code. Please try to remove the calls to nrf_power_task_trigger() from soc/arm/nordic_n

#ble #nrf52480

Hi Robert, Can you please open a GitHub issue and assign it to @jhedberg ? Thanks, Carles

#ble #bluetoothmesh

Hi Vinayak, I merge the patch, host (nRF Connect) get update connection parameter request. After CI change to 30ms, it can keep connection a bit longer but it still disconnect after few minutes (dista

#nrf52840 #ble

Hi, We had builded the HCI_UART to nrf52832(since our device take only .zip file) and tried to flush to Nordic Development kit, but couldnt able to while doing make flush. could you please recommend w

#ble #nrf52832

Hi Charles We need 6 PPI channels to drive BLDC motor. For now I'm modify radio_nrf5_ppi.h. So I could work. File si also attached. In begginig of file is #define CONFIG_BT_NRF52X_RADIO_EVENT_TIMER wh

#ble #nrf52832

Hi Dhananjay, When you refer to subscribe I suppose you are talking about writes to CCC? Those are persistent if you have paired the device which I believe is mandatory in case of HID, clearing the su

#ble

Update the nrf52_pca10040.overlay file. For your custom board, place a new file <custom_board>.overlay file in your application folder with the desired DT settings/overrides. https://github.com/zephyr

#ble

Thanks guys，I resloved this problem already.The usb2uart chip cannot cover baudrate of 1000000，when I configured baudrate of hci_uart to 115200，it worked fine. 发自我的华为手机

#ble

Hi there, I copied Vinayak who is the original author of the ticker. There is no real material available publicly at this point. Regards, Carles

#nrf52840 #ble #nrf52832

Hi Rajat, This could be helpful https://devzone.nordicsemi.com/b/blog/posts/nrf-blinky-compatible-firmware-using-zephyr-blueto You've to make changes as per your Board design. regards, vikrant

#bluetoothmesh #nrf52832 #ble

Hi Vikrant, Advertising on Coded PHY needs the implementation of Extended Advertising feature of BT V5.0. This feature has not been implementation, only a initial effort was attempted. That said, any

#bluetoothmesh #ble