Re: Debugging blecent application on nrf52dk

Yes, that is for 4.2. But earlier versions of the specification do not even mention Data Length Update procedure so this would not apply to a 4.1 controller, for instance. There needs to be a generic place in the spec that says “if you receive a LL control opcode that you do not understand,

Re: Debugging blecent application on nrf52dk

Hi Will, Thanks for the explanation. I found it in the BluetoothCore v4.2 spec in section 5.1.9 - Data Length Update Procedure. I agree with your conclusion that it sounds like the controller must accept LL_UNKNOWN_RSP but must not require it. Thanks again this was really very helpful. -Pritish

Re: Debugging blecent application on nrf52dk

I can elaborate. It has been discussed at fair length on the dev list before but I will summarize. The issue is that our controller automatically attempts to do data length extension with a peer. The default configuration sets a larger receive size than the minimum size and this causes the

Re: Debugging blecent application on nrf52dk

Hey Will, That worked!! The blecent is staying connected to the bleprph almost indefinitely now. Can you please elaborate on the reason: "And sure enough, I think this is the same issue we have seen before. The data length update procedure is not completing and the connection is timing out." Do

Re: Debugging blecent application on nrf52dk

BTW: Lukasz did have a really good suggestion for future debugging (why didnt I think of that?) :-) A sniffer with wireshark is a really handy tool. I mentioned the debugger as it was something we could look at really quickly to see if it is an issue that I already know about with some

Re: Debugging blecent application on nrf52dk

Hi Will, Sorry I was mistaken, I jumbled up the issues in my own head. You are correct in that the blecent is running on the nrf52dk and the logs I provided are from the blecent application. As you requested I put the breakpoint at ble_ll_ctrl_proc_rsp_timer_cb() please see the dump below:

Re: Debugging blecent application on nrf52dk

Hi Pritish, On 16 March 2017 at 23:11, Pritish Gandhi wrote: > Hi Will, > I'm not building the controller lib for the image that runs on the > stm32f4Discovery board. I'm building it as a Host Only. So I build the > host, HCI, and uart transport. Broadcom's Bluetooth

Re: Debugging blecent application on nrf52dk

Hi Will, I'm not building the controller lib for the image that runs on the stm32f4Discovery board. I'm building it as a Host Only. So I build the host, HCI, and uart transport. Broadcom's Bluetooth core is really a BlackBox to me, I don't have any way to debug what's going on there (except maybe

Re: Debugging blecent application on nrf52dk

Hi Chris, On Thu, Mar 16, 2017 at 2:30 PM, Christopher Collins wrote: > Hi Pritish, > > On Thu, Mar 16, 2017 at 01:50:12PM -0700, Pritish Gandhi wrote: > > Hi All, > > I'm trying to run blecent on an nrf52dk and am running the bleprph > > application on another BLE module

Re: Debugging blecent application on nrf52dk

I do not think there is a simple way to debug this. As Chris points out, the first problem is a LL control procedure timeout. I think I can help figure some things out there. There is a function called ble_ll_ctrl_proc_rsp_timer_cb. If you set a breakpoint at this function in the debugger when

Re: Debugging blecent application on nrf52dk

Hi Pritish, On Thu, Mar 16, 2017 at 01:50:12PM -0700, Pritish Gandhi wrote: > Hi All, > I'm trying to run blecent on an nrf52dk and am running the bleprph > application on another BLE module (stm32f4discovery talking to a broadcom > BLE core). Anyways, when try to run blecent it seems like I

Debugging blecent application on nrf52dk

Hi All, I'm trying to run blecent on an nrf52dk and am running the bleprph application on another BLE module (stm32f4discovery talking to a broadcom BLE core). Anyways, when try to run blecent it seems like I successfully connect to the peripheral and are able to discover it, however after that