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, 
that is a pretty low-layer call and if the link layer is doing something it 
could grab control again. As long as you are sure the device is not 
advertising, scanning or in a connection that radio should not be used and the 
link layer should not try to start using it.

There are a number of ways you could “hack” this into the code and I could help 
with more information if you need it. And btw: if you do take control of the 
radio and then want to return it to the nimble stack you should perform a 
link-layer reset of the controller. The reason being is that there are some 
radio registers that are only written once and if you change them the device 
may no longer operate correctly.

Awesome that you are doing this! Let us know how it goes.

Will

> On Jun 8, 2017, at 3:23 PM, Jitesh Shah <jit...@liveathos.com> wrote:
> 
> 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 off the radio
> (Others like transmit power, connection interval are trivial to achieve)
> 
> *Question 1: *When we were using the softdevice, we disabled the softdevice
> and took over the radio. With nimBLE, is ble_phy_disable() enough to take
> over the radio control from nimBLE?
> 
> *Question 2: *Optionally, does nimBLE provide any support for the FCC test?
> I scoured the source, but didn't find any. Have any of you guys been
> through the FCC pre-scan using nimBLE?
> 
> Thanks,
> Jitesh
> 
> -- 
> This email including attachments contains Mad Apparel, Inc. DBA Athos 
> privileged, confidential, and proprietary information solely for the use 
> for the addressed recipients. If you are not the intended recipient, please 
> be aware that any review, disclosure, copying, distribution, or use of the 
> contents of this message is strictly prohibited. If you have received this 
> in error, please delete it immediately and notify the sender. All rights 
> reserved by Mad Apparel, Inc. 2012. The information contained herein is the 
> exclusive property of Mad Apparel, Inc. and should not be used, 
> distributed, reproduced, or disclosed in whole or in part without prior 
> written permission of Mad Apparel, Inc.

Reply via email to