Hi Jitesh,
On 9 Jun 2017, at 7:27, Jitesh Shah wrote:
> Great!
> So then ble_ll_reset() followed by ble_phy_disable() should take care of
> most cases, right?
>
> As far as giving back control to the nimBLE stack is concerned - that
> probably won't be necessary. FCC is a pretty controlled
Jitesh:
Sorry, I probably did not explain myself all that well.
1) The ble_ll_reset() call was mentioned in case you wanted to do something
after the FCC test. This way you could be sure that the radio registers are all
initialized properly after your special FCC test code messes with them (if
Question 2: Unless it got added recently and I did not catch it, currently the
nimble stack does not provide support for the FCC test.
Question 1: I guess it depends what you mean by take over control. The call to
ble_phy_disable() will certainly halt anything going on in the radio. However,
Hey all,
We'll be going through the FCC pre-scan soon with 1.0 version of the nimBLE
stack. yay!
Of all the things needed for pre-scan the two which are the most important
are:
1) Ability to blast packets on only one of the 40 channels (and the ability
to choose which channel)
2) Ability to shut
On Thu, Jun 8, 2017 at 3:30 AM, Justin Mclean wrote:
> Hi,
>
>> 1: Is this approach correct to integrate the Eclipse Paho's Library
>> to implement MQTT client ? It is distributed under both EPL[3] and
>> EDL[4] licensing models and is left on the user to decide, which
Hi Chris,
Thanks very much for this useful information about the initialization
sequence and how newt handles that. This is really awesome and flexible but
as you remarked, developers might feel losing control to the generated code
:)
I am still unclear about some issues, will really appreciate
Hi Amit,
On Wed, Jun 7, 2017 at 17:28 amit mehta wrote:
> ...
> 2: If the answer for Q1 is 'yes', then should the MQTT library be put
> under 'net' directory; same place where nimble, Wifi etc are located
> in the apache-mynewt-core directory structure ?
>
Yes, that