gatttool and multiple devices connected
Hi guys,
I was just testing the LE functionality a bit and decided to connect to two different LE devices at the same time using gatttool in interactive mode (two different terminals). Connection to the two devices went well, but when I tried to get primary services on the devices it was only possible to do so on one of the devices. Connecting to them one by one showed that it was actually possible to get the primary service listing of both devices - just not when both are connected at the same time.
I guess this is a bug somewhere in the primary-service lookup code but have yet to look more into the details of this.
Just thought that you might wanted to know about this.
cheers
Kim
Hi Kim,
Quoted 12 lines · Kim Schulz
Hi guys,
I was just testing the LE functionality a bit and decided to connect to two different LE devices at the same time using gatttool in interactive mode (two different terminals). Connection to the two devices went well, but when I tried to get primary services on the devices it was only possible to do so on one of the devices.
Connecting to them one by one showed that it was actually possible to get the primary service listing of both devices - just not when both are connected at the same time.
I guess this is a bug somewhere in the primary-service lookup code but have yet to look more into the details of this.
Quoted 1 line
Just thought that you might wanted to know about this.
Which kernel version are you running? Older kernels had a LE connection routing issue which I believe was fixed long ago.
And what do you mean with not being able to get services? which error did you get?
Do you have hcidump logs from these sessions?
Regards,
Signature · 3 lines
Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil
Quoted 1 line · Anderson Lizardo
Which kernel version are you running? Older kernels had a LE connection routing issue which I believe was fixed long ago. And what do you mean with not being able to get services? which error did you get? Do you have hcidump logs from these sessions? Regards,
The Bluez code is one taken from git a few days ago. I don't recall which kernel version (will have to check at the office tomorrow) but it is one of the latest that we compiled for this test. We do have some logs of the session and I will be looking at those more thoroughly tomorrow.
kim
Den 2012-10-16 16:51, Kim Schulz skrev:
Quoted 12 lines · Anderson Lizardo
Quoted 4 lines
Which kernel version are you running? Older kernels had a LE connection routing issue which I believe was fixed long ago. And what do you mean with not being able to get services? which error did you get? Do you have hcidump logs from these sessions? Regards,
The Bluez code is one taken from git a few days ago. I don't recall which kernel version (will have to check at the office tomorrow) but it is one of the latest that we compiled for this test. We do have some logs of the session and I will be looking at those more thoroughly tomorrow.
Quoted 5 lines
kim
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
Turns out that the guy compiling our kernel choose a version 3.4.0.030400 so not really the
bleeding edge version.
Do you have any recommendation on what version of the kernel we should aim for?
Signature · 1 line
Kim Schulz
Hi Kim,
Quoted 5 lines · Kim Schulz
Turns out that the guy compiling our kernel choose a version 3.4.0.030400 so not really the
bleeding edge version.
Do you have any recommendation on what version of the kernel we should aim for?
This kernel is actually not that old (as long as it is based on the official 3.4.0 one). Did you have hcidump logs for the attempt to discover primary services on device B while connected to device A?
Regards,
Signature · 3 lines
Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil
Hi Lizardo,
Quoted 10 lines · Anderson Lizardo
Quoted 5 lines · Kim Schulz
Turns out that the guy compiling our kernel choose a version 3.4.0.030400 so not really the
bleeding edge version.
Do you have any recommendation on what version of the kernel we should aim for?This kernel is actually not that old (as long as it is based on the official 3.4.0 one). Did you have hcidump logs for the attempt to discover primary services on device B while connected to device A?
Actually I'd say that it is too old for LE usage. E.g. the address type field to the L2CAP socket address was introduced in 3.5 which is quite important from an LE standpoint.
Johan
Hi Johan,
Quoted 7 lines · Johan Hedberg
Quoted 3 lines
This kernel is actually not that old (as long as it is based on the official 3.4.0 one). Did you have hcidump logs for the attempt to discover primary services on device B while connected to device A?
Actually I'd say that it is too old for LE usage. E.g. the address type field to the L2CAP socket address was introduced in 3.5 which is quite important from an LE standpoint.
Ok, my mistake. I thought it was introduced still on 3.4.0. In this case, Better use the latest mainline (3.6.*).
Regards,
Signature · 3 lines
Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil