Hi Kathy, Thank you for your kind response and sorry for my slow reply. I had a look and I feel like our FreeRTOS port is correct. I've been struggling for days now. I'm logging transmissions and everything seems to be correct-- timing, channels, etc-- but the sniffer does see anything after the first LL_FEATURE_REQ packet...
I've been trying to figure out a better sniffer. Does anyone know how to make the sniffer listen only on one channel? Then I could force all transmission onto the same channel and maybe see what is wrong? Thanks, -Mike On Fri, Jun 7, 2024 at 1:39 PM Kathy Giori <kathy.gi...@gmail.com> wrote: > Hi Mike, > > On Fri, Jun 7, 2024 at 10:25 AM Mike Redd <mr...@prodatakey.com> wrote: > >> >> Hello, >> >> We are building a NimBLE controller on FreeRTOS and the Nordic nRF52820 >> chip. (It communicates with a host over the HCI UART interface.) We have a >> reference build with MyNewt, which seems to work, but we are having >> difficulty with FreeRTOS. (We want to use FreeRTOS for compatibility with >> other parts of our application.) >> >> Hoping someone might have a clue.... >> >> Using a BLE sniffer with MyNew, we get: >> >> [image: image.png] >> > > (images didn't come through) > > You can probably also use the BLE sniffer available when running the > MicroBlocks firmware (which uses NimBLE) on an nRF52820-based board. The > MicroBlocks firmware is all open source, so maybe browsing the source > <https://bitbucket.org/john_maloney/smallvm/src/master/>(especially > netPrims.cpp > <https://bitbucket.org/john_maloney/smallvm/src/master/vm/netPrims.cpp>) > may provide a clue for your integration with FreeRTOS. > > >> But with FreeRTOS we get: >> >> [image: image.png] >> >> Thanks in advance for any clues! >> > > Good luck! > kathy > > [image: Mike Redd] <https://www.prodatakey.com/become-a-partner>
