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,
Hi,
On 17 March 2017 at 16:53, Christopher Collins wrote:
>
> On Fri, Mar 17, 2017 at 08:36:01AM -0300, Fabio Utzig wrote:
> > On Fri, Mar 17, 2017, at 08:24 AM, then yon wrote:
> > > Dear Chris,
> > >
> > > When i put sudo newtmgr -c BT01 stat list, it gave me sudo: newtmgr:
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
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
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
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
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:
On Fri, Mar 17, 2017 at 08:36:01AM -0300, Fabio Utzig wrote:
> On Fri, Mar 17, 2017, at 08:24 AM, then yon wrote:
> > Dear Chris,
> >
> > When i put sudo newtmgr -c BT01 stat list, it gave me sudo: newtmgr:
> > command not found.
>
> It looks like sudo is not preserving your user path, you
On Fri, Mar 17, 2017, at 08:24 AM, then yon wrote:
> Dear Chris,
>
> When i put sudo newtmgr -c BT01 stat list, it gave me sudo: newtmgr:
> command not found.
It looks like sudo is not preserving your user path, you could try:
sudo "PATH=$PATH" newtmgr -c BT01 stat list
Dear Chris,
When i put sudo newtmgr -c BT01 stat list, it gave me sudo: newtmgr:
command not found.
Dear Andrzej,
I get the following error with you suggestion.
$ sudo setcap cap_net_admin=+ep 'which newtmgr' [sudo] password for dev:
Failed to set capabilities on file `which newtmgr'
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
11 matches
Mail list logo