Hi, I want to do an DFU OTA in nRF52840 BLE chip. I have flashed mcuboot bootloader and also flashed hci_uart (To scan BLE beacons) application. This will be one time flash using JTAG. Now, I want to

#hci #nrf52480 #ble #uart #samples

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

Hello All, Right now I'm exploring the best way to do DFU OTA. I would like to ask that how i can do the DFU by booting the mcuboot bootloader in serial recovery mode. I have one nrf52840_pca10056 chi

#ble #hci #nrf52480 #uart

Hello, I have nrf52840_pca10056 chip connected to imx6ul processor via uart (Both are embedded on my custom board) as shown in attached image. I'm using mcuboot bootloader on nrf52840 chip, now i want

#ble #hci #nrf52480 #uart

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

Hello, I am trying to configure Zephyr as a HCI UART host. My setup: nrf52840_pca10056 nordic dev kit running zephyr/samples/bluetooth/hci_uart. This seems pretty straight forward. stm32f746g_disco de

#uart #bluetoothmesh #hci

Hi, This is a valid and quite common set up. The most important thing you'll need to enable is the host-side UART HCI driver using CONFIG_BT_H4=y. Johan

#uart #bluetoothmesh #hci

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 here and hop anybody can help. I want to enable the config CONFIG_BT_PRIVACY, and according to the official document, the config depends on BT_SMP BT_CONN BT_HCI_HOST BT_HCI a

#nrf52832 #hci

Hi there, If you are building the hci_uart then CONFIG_BT_PRIVACY is irrelevant because it’s only tied to the Host. What you need is CONFIG_BT_CTLR_PRIVACY, which enables privacy in the controller. Ca

#nrf52832 #hci

Thanks Carles, I have realized it.

#nrf52832 #hci

Hi, Basically the code is assuming that the packet is valid, but the buffer sizes have simply been defined too small to fit the packet. In such a case discarding the rx.remaining bytes would be the co

#hci

Hi, I have a HCI host and controller setup. When the host starts, and the controller had already been running, it sometimes begins reading in the middle of a HCI message from the controller. It reads

#hci

Hi, I am evaluating the use of nRF52 (HCI with BlueZ/Linux) as BLE central device. Does anyone know the maximum number of concurrent connections which Zephyr supports? Many thanks, Jos

#uart #ble #hci #nrf52480

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 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

In the current implementation, BLE HCI_EVENT is processed on a dedicated RX_THREAD and called back in the same context. I want to handle HCI_EVENT (eg advvertise_report) directly in my thread. Is ther

#hci #nrf52840 #ble

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, We are willing to do the LE USB controller with the nrf52840 dongle By looking into this case https://devzone.nordicsemi.com/f/nordic-q-a/46036/mac-address-ranges. I came to know that there will b

#hci #ble #nrf52 #nrf52840

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