#nrf52832

Relevance · Date   
[Zephyr-users] What is the process to enable bluetooth so that nrf52832 is disciverable by other device (android phone) By ... · #4764 ·
ticker timer By ... · #4804 ·
ticker timer By Carles Cufi · #4805 ·
I2C cmake errors (v1.13 and v1.12) ? By gurpreet+zephy@... · #5096 ·
I2C cmake errors (v1.13 and v1.12) ? By gurpreet+zephy@... · #5097 ·
BLE stack using PPI channels By robert.konc@... · #5161 ·
BLE stack using PPI channels By Sebastian Boe · #5162 ·
BLE stack using PPI channels By Carles Cufi · #5163 ·
BLE stack using PPI channels By Chettimada, Vinayak Kariappa · #5164 ·
BLE stack using PPI channels By Chettimada, Vinayak Kariappa · #5165 ·
BLE stack using PPI channels By robert.konc@... · #5167 ·
How to flush the HCI_UART to c By prabhakaran@... · #5201 ·
【HCI_UART】hci_uart sample cannot advertise controlled by HCI commands By icephyr · #5356 ·
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By frv · #5364 ·
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By Carles Cufi · #5366 ·
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By frv · #5381 · Edited
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By Carles Cufi · #5385 ·
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By frv · #5386 · Edited
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By Carles Cufi · #5387 ·
Zephyr (v1.13.0) HCI_UART running on nRF52 DK why BD address is always 00:00:00:00:00:00 after power cycle By frv · #5388 ·
1 - 20 of 67