FRDM-KW36 - Extended Advertising

cancel
Showing results for 
Search instead for 
Did you mean: 

FRDM-KW36 - Extended Advertising

161 Views
Contributor II

Hi, NXP expert.

I am testing beacon(extended Advertising) using KW36 Board.

The Gap_SetExtAdvertisingParameters function returns an error while testing an extended Advertising using the beacon example code. (SDK_2.2.3_FRDM-KW36\boards\frdmkw36\wireless_examples\bluetooth\beacon)

--------------------------------------------------------------------------------------------------------------------------------------

* beacon.h
#ifndef gBeaconAE_c
#define gBeaconAE_c 1
#endif

* beacon.c
if (gBleSuccess_c != Gap_SetExtAdvertisingParameters(&gExtAdvParams))
{
    panic(0, 0, 0, 0);
}

--------------------------------------------------------------------------------------------------------------------------------------

Can you tell me why the error occurs?

Thank you.

Labels (2)
Tags (1)
5 Replies

11 Views
Contributor II

Thank you, Sebastian.

I have one more question.

It does not work when the power-down mode is set.

Can the example of beacon be operated in power down mode?

------------------------------------------------------------------------------------------
/* Enable/Disable PowerDown functionality in PwrLib */
#define cPWR_UsePowerDownMode 1

BleApp_HandleKeys()

{

.....


case gKBD_EventPB2_c:
{
   #if defined(cPWR_UsePowerDownMode) && (cPWR_UsePowerDownMode)
   /* When low power is enabled, first press starts legacy advertising */
   if (mAdvertisingOn == FALSE)
   {
      BleApp_Start();
   }

......

}

------------------------------------------------------------------------------------------

0 Kudos

11 Views
NXP TechSupport
NXP TechSupport

Hi Ayden,

 

The BLE Beacon SDK (For SDK version 2.2.3) example can be operated in Power Down mode by configuring the following macro definition:

 

/* Enable/Disable PowerDown functionality in PwrLib */
#define cPWR_UsePowerDownMode           1

When operating in Power Down mode, the LEDs of the application won't light up, but when pressing the advertising button (SW3), advertising starts normally, and scanner devices can see the device.

 

Please let me know if you need any more information.

 

Take care, best regards,

Sebastian

0 Kudos

11 Views
Contributor II

There was an error.

Because I called "shell_init" function in Beacon.

Ble_Initialize()

{

....

   if (osaStatus_Success != Ble_HostTaskInit())
   {
   return gBleOsError_c;  <<==  Error!!
   }

....

}

It's going well now.

Thanks a lot.

0 Kudos

11 Views
NXP TechSupport
NXP TechSupport

Hi Ayden, 

It's good to know you were able to fix the issue!

Please let us know if you need any more information or have any further issues.

Take care, best regards,

Sebastian

0 Kudos

11 Views
NXP TechSupport
NXP TechSupport

Hi Ayden, I hope you're doing well!

 

I'm sorry for the inconveniences this may cause, but unfortunately, the Advertising Extensions BLE 5 Optional Errata is not implemented for the KW36 Family of MCUs.

 

However, the new KW38 family does implement this and other optional errata.

Could you please take a look at the KW38 Family of MCUs for this functionality?

 

There's also some documentation on enabling the advertising extensions on the KW38's SDK examples, here.

 

Please let me know if you need any more information.

 

Take care, best regards,

Sebastian