Hi Ram,
On Thu, Mar 15, 2018 at 12:07:55PM +0530, Sriram V wrote:
> Hi,
>
> I have the following doubts on NimBle:
>
> The document says 32+ concurrent connections, multiple connections in
> simultaneous central and peripheral roles. Does that mean the "device
> running Nimble" can connect to 32
Hi Andrzej,
Thank you for your answer. That's what I did first but it did not work.
I have an app that runs as expected using the default LF CLOCK, the
XTAL_32768 used.
When I switch the LF CLOCK to XTAL_32768_SYNTH, the app advertises
correctly. When I try to connect, the app disconnects a
Hi Szymon,
On Thu, Mar 15, 2018 at 12:57 PM, Szymon Janc wrote:
> Hi Andrzej,
>
> On Monday, 12 March 2018 15:30:52 CET Andrzej Kaczmarek wrote:
>> Hi,
>>
>> I created PR for apache-mynewt-core which removes NimBLE code and adds
>> dependency to apache-mynewy-nimble repository:
>> https://github.
Hi Andrzej,
On Monday, 12 March 2018 15:30:52 CET Andrzej Kaczmarek wrote:
> Hi,
>
> I created PR for apache-mynewt-core which removes NimBLE code and adds
> dependency to apache-mynewy-nimble repository:
> https://github.com/apache/mynewt-core/pull/907
>
> With latest changes in newt (thanks, C
Hi Abderrezak,
On Thu, Mar 15, 2018 at 1:40 AM, Abderrezak Mekkaoui wrote:
> Hi All,
>
> I would appreciate any hints regarding the configuration settings that need
> to be changed to use a synthesized LF clock (32.768 KHz) instead of the Xtal
> Oscillator clock.
> This is for a BLE application.
