Hi Lwazi,

Thank you very much taking time to test it and confirming that it is
not working.

BTW, by working I mean "ble scanning" was working. I think we need
some better application example on NuttX to test BLE. AFAIK our stack
is too limited currently.

BR,

Alan

On 3/10/23, Lwazi Dube <lwa...@gmail.com> wrote:
> Hi Alan,
> If it is working on other platforms, no problem, I will fix my devices
> later if I get a chance. I will put some details here in case someone
> with my setup runs into the same issue.
> After posting my message I downloaded 9.0.0 and 10.0.0 and tested the
> releases (9 works and 10 is broken). Here is an example of what works
> on my local build. I have two devices running an old NuttX build:
> -----------------------------
> commit 28ac578cd325536e0fbe8eaeebba524827d0e3a6 (origin/master,
> origin/HEAD, master)
> Author: Gregory Nutt <gn...@nuttx.org>
> Date:   Sat May 18 15:18:06 2019 -0600
>
>    Update ReleaseNotes in preparation for the 7.30 release.
> ------------------------------
>
> I use one device to control the other. Let us call them HOST and
> TARGET. TARGET has some BLE services in it: heart rate, current time,
> battery etc. The original Intel source has a sample. I use HOST to
> interrogate TARGET knowing what value to expect. Replace
> XX:XX:XX:XX:XX:XX with the BDAddr found by the "
> bt bnep0 info" command.
>
> NuttShell (NSH)
> nsh> bt bnep0 gatt connect XX:XX:XX:XX:XX:XX public
> Connect pending...
> nsh> btnet_hci_connected: Connected
> bt bnep0 gatt discover XX:XX:XX:XX:XX:XX public 0x180d
> Discovered 1 handles:
> 0.      handle 0x0006 perm: 01
> nsh>
>
> When I update to the latest NuttX (or anything newer than 9.0.0) this
> does not work. The connect command hangs, presumably in the serial
> driver, since you say bt works on other platforms.
>
> Regards,
> Lwazi
>
> On Fri, 10 Mar 2023 at 07:27, Alan C. Assis <acas...@gmail.com> wrote:
>>
>> Hi Lwazi,
>>
>> I don't know about CC2564, but BLE Stack was working recently to
>> ESP32, ESP32C3, nRF52, etc
>>
>> Is it related to this issue: https://github.com/apache/nuttx/issues/8767
>>
>> BR,
>>
>> Alan
>>
>> On 3/9/23, Lwazi Dube <lwa...@gmail.com> wrote:
>> > On Wed, 8 Mar 2023 at 13:16, Alan C. Assis <acas...@gmail.com> wrote:
>> >>
>> >>
>> >> Welcome back go NuttX Lwazi (I'm not been sarcastic, I'm happy to hear
>> >> from you again! You have a great knowledge of BLE can we need! I was
>> >> expecting you to share that working example of BLE application using
>> >> our BLE stack).
>> >>
>> > Thanks, I don't know about "great knowledge", but I am not sure I will
>> > be doing any bt work this time. I checked. The current BLE stack is
>> > broken when I run it on my board with a cc2564 BT chip. The bt command
>> > fails to connect like it does on a 2019 tree that I have. I don't know
>> > what the point of the changes being made to bluetooth is, if such a
>> > basic feature remains broken after a merge. Is anyone really using or
>> > testing the NuttX stack?
>> >
>

Reply via email to