The API takes a signed int as a parameter as I usually just like using ‘int’ as
opposed to ‘int8_t’ in functions. However, the lower-layer phy driver stores
the power as a signed, 8-bit integer as that is all that is needed at the lower
layer (just as you say Kevin).
Certainly we can change
On Thu, May 19, 2016 at 11:12:39AM -0700, James Howarth wrote:
> Hi Chris,
>
> I think it needs to be a signed int right, as txpwer can be negative, does
> that sound right?
Yes, good catch (thanks also, Kevin!).
In that case, you should declare the tx power variable as an int8_t.
Chris
A single signed 8-bit integer will cover most radios I'm familiar with, yes.
On 19/05/16 20:12, James Howarth wrote:
Hi Chris,
I think it needs to be a signed int right, as txpwer can be negative, does
that sound right?
Cheers
James
On Thu, May 19, 2016 at 11:10 AM, Christopher Collins
Hi Chris,
I think it needs to be a signed int right, as txpwer can be negative, does
that sound right?
Cheers
James
On Thu, May 19, 2016 at 11:10 AM, Christopher Collins
wrote:
> On Thu, May 19, 2016 at 11:03:22AM -0700, Christopher Collins wrote:
> > > > On May 19,
Hi,
Is there a special procedure for changing power level of the BLE radio on
an nRF52 PDK?
Can I just do something like the following in my callback:
static int txpwer_to_set[1] ;
memcpy(txpwer_to_set, ctxt->chr_access.data,
sizeof txpwer_to_set);
ble_phy_txpwr_set(*txpwer_to_