Hi, I’ve previously done testing with the HCI UART and USB sample apps (in older Zephyr versions) with an nRF52840 and linux PC and always found it to not work well. It would start fine, could scan fo

#ble #hci #nrf52480 #uart

Hi All, I'm facing issues regarding ble's hci interface. I'm having nrf52840 module on which i run zephyr's hci_uart app for beacon scanning. I have Bluez 5.50 installed on my custom board (imx6ull).

#ble #hci #nrf52480 #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, You might get lucky with disabling hardware flow control, however this standard HCI transport officially requires it (see Vol 4, Part A section 3 in Bluetooth Core Specification 5.2). Yes,

#uart #samples #ble #hci #nrf52480

Hi, > Q1: As i'm not using HW flow control, Can i have any flow control related problem if there will be more number of devices/beacons available for the scanning. Yes, that is the purpose of flow con

#uart #samples #ble #hci #nrf52480

Hi All, I have a doubt regarding one of the sample application of zephyr (samples/bluetooth/hci_uart). This 'hci_uart' application has Hardware flow control enable by default in its nrf.conf file. (CO

#uart #samples #ble #hci #nrf52480

Hi! This is my first message to the Zephyr forum. Well, I started to work with zephyr a few days ago. I followed the steps from the Getting Started Guide and I'd like to perform the debugging of the a

#debug #nrf52480

In version 1.14.1, there appears to be a race condition when updating an indication value. It results in a BUS FAULT, which occurs because a pointer becomes null. Here are the Zephyr ATT print message

#ble #nrf52480

Sorry for the earlier post. This always happens when I've been away from a platform during a major upgrade. I also had an overlay file redirecting spi0 pins that contained "status = "ok"". I successfu

#nrf52480

I'm getting back to an earlier NRF52840 project that uses SPI. Have upgraded to Zephyr 2.1 and finding my way around a few subtle changes. Have encountered the following problem when rebuilding an old

#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

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

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

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

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

Hello! I have had some progress so far. I tried the same configuration setup on the NRF52-PCA10040 dev kit with the HCI-UART sample and everything seems to work as expected. Although I do not necessar

#ble #hci #nrf52480

Hi, I am having some problems with getting two NRF52840 USB dongles to communicate with each other with extended data ACL data lengths. I have flashed both the dongles with the Zephyr HCI-USB samples

#ble #hci #nrf52480

Thanks to Marcio I resolved. The dts overlay was missing. I created nrf52840_pca10059.overlay in the application main folder. &spi1 { compatible = "nordic,nrf-spis"; status = "ok"; sck-pin = <22>; mos

#nrf52480

Hi all, I’m trying to get a simple SPI slave application running on nRF52840-PCA10059 dongle. So far, no success. I tried a couple of things that all lead to compilation error of the kind “symbol unde

#nrf52480