28, 2017 6:38 AM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi,
On 28 March 2017 at 12:10, Łukasz Rymanowski <lukasz.rymanow...@codecoup.pl>
wrote:
> Hi all,
>
> Just had a need to run my nrf52 dev board with blehci and faced same
> issues
-Original Message-
From: Łukasz Rymanowski [mailto:lukasz.rymanow...@codecoup.pl]
Sent: Tuesday, March 28, 2017 6:38 AM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi,
On 28 March 2017 at 12:10, Łukasz Rymanowski <lukasz.rymanow...@codecoup.pl>
wrote:
&g
; On 27 February 2017 at 19:52, Alan Graves <agra...@deltacontrols.com>
> wrote:
>
>> Thanks, I did see that over the weekend. Someone must be looking over my
>> shoulder :)
>>
>> -Original Message-
>> From: Szymon Janc [mailto:szymon.j...@codeco
[mailto:ch...@runtime.io]
Sent: Friday, February 24, 2017 4:54 PM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi Alan,
On Sat, Feb 25, 2017 at 12:21:15AM +, Alan Graves wrote:
> Well my conclusion is that the HCI mode is frustrating at best to use on the
>
Thanks, I did see that over the weekend. Someone must be looking over my
shoulder :)
-Original Message-
From: Szymon Janc [mailto:szymon.j...@codecoup.pl]
Sent: Sunday, February 26, 2017 11:19 AM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi,
On 25
Hi Alan,
On Sat, Feb 25, 2017 at 12:21:15AM +, Alan Graves wrote:
> Well my conclusion is that the HCI mode is frustrating at best to use on the
> BlueZ stack!
>
> In my initial attempts to talk to the controller I use this command:
> $ sudo btmgmt --index 1
> [sudo] password for alan:
>
yNewt :O
ALan
-Original Message-
From: Alan Graves
Sent: Wednesday, February 22, 2017 5:25 PM
To: dev@mynewt.incubator.apache.org
Subject: RE: BLE HCI support on NRF52DK
I have an update on my progress with the HCI testing. I did as Chris suggested
and rebuilt the BlueZ from source to disable th
I haven't done
very extensive testing yet.
ALan
-Original Message-
From: Alan Graves [mailto:agra...@deltacontrols.com]
Sent: Friday, February 10, 2017 2:00 PM
To: dev@mynewt.incubator.apache.org
Subject: RE: BLE HCI support on NRF52DK
Yes thanks I also got that from the discussion
). The BLE hardware + Host must
come up correctly every time or it will be a serious problem.
ALan
-Original Message-
From: will sanfilippo [mailto:wi...@runtime.io]
Sent: Friday, February 10, 2017 1:23 PM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hello
itialized by driving the RESET signal with a GPIO line.
>
> ALan
>
> -Original Message-
> From: will sanfilippo [mailto:wi...@runtime.io]
> Sent: Monday, February 06, 2017 5:55 PM
> To: dev@mynewt.incubator.apache.org
> Subject: Re: BLE HCI support on NRF52DK
&g
-Original Message-
From: will sanfilippo [mailto:wi...@runtime.io]
Sent: Monday, February 06, 2017 5:55 PM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Ah ok; that is quite interesting. I did not realize that was the case and I was
thinking of an external board
er initial NOP was received.
> >>> Linux on the other hand assumes that once device is attached it is
> >>> ready to
> >>> receive initial HCI Reset.
> >>>
> >>>> ALan
> >>>>
> >>>> -Original Mes
>> 121.112600
>>>>> HCI Event: Command Complete (0x0e) plen 3 [hci0]
>> 126.168513
>>>> NOP (0x00|0x) ncmd 1
>>>> = Close Index: 00:00:00:00:00:00 [hci0]
>> 131.246188
>>
Linux will not try sending another command before getting Command
> > Status for it.
> > And that will never happen since command was ignored ie. Zephyr has
> > special config option when used with Mynewt based BT firmware to
> > handle this
> > exact situation - se
d it is
ready to
receive initial HCI Reset.
> ALan
>
> -Original Message-
> From: Szymon Janc [mailto:szymon.j...@codecoup.pl]
> Sent: Thursday, February 02, 2017 12:18 PM
> To: dev@mynewt.incubator.apache.org
> Subject: Re: BLE HCI support on NRF52DK
>
> Hi Alan,
>
> On
-Original Message-
From: Christopher Collins [mailto:ccoll...@apache.org]
Sent: Thursday, February 02, 2017 12:23 PM
To: dev@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi Alan,
On Thu, Feb 02, 2017 at 06:16:42PM +, Alan Graves wrote:
> Thanks for rechecking. I know
Hi Alan,
On Thu, Feb 02, 2017 at 06:16:42PM +, Alan Graves wrote:
> Thanks for rechecking. I know I'm not setup with RTS/CTS handshaking on the
> custom board so that is probably going to be a problem. When I get a chance
> I'll repeat my tests with a complete serial signal set on the
r NOP event was emitted).
> ALan
>
> -Original Message-
> From: Christopher Collins [mailto:ccoll...@apache.org]
> Sent: Wednesday, February 01, 2017 4:00 PM
> To: dev@mynewt.incubator.apache.org
> Subject: Re: BLE HCI support on NRF52DK
>
> Hi Alan,
>
> O
@mynewt.incubator.apache.org
Subject: Re: BLE HCI support on NRF52DK
Hi Alan,
On Wed, Feb 01, 2017 at 11:05:23PM +, Alan Graves wrote:
> Hi,
>
> I've spent some time trying to get nRF52832 DK running the 'blehci' code
> communicating with Xubuntu 16.10 (under VMware) with not much lu
Hi,
I've spent some time trying to get nRF52832 DK running the 'blehci' code
communicating with Xubuntu 16.10 (under VMware) with not much luck.
I'm currently running the following development setup:
$ git status
On branch develop
Your branch is up-to-date with 'origin/develop'.
$ go version
20 matches
Mail list logo
