Thanks Andzrej. As per your suggestions I followed the same steps.
I am using following commands in btshell: I have to use extended advertisement so I am keeping legacy = 0 unset set addr_type=public addr=01:02:03:04:05:06 advertise-configure scannable=1 when I enter advertise-set-adv-data name=xyz it throws error saying: error setting advertisement data; rc=3 but when I configure with legacy =1 it accepts all advertise-set-adv-data commands. I have to check data (more than 31 byte) on extended advertisement channels which is not possible with legacy. I think I am missing something. Regards, Swapnil ________________________________ From: Andrzej Kaczmarek <[email protected]> Sent: Tuesday, April 24, 2018 5:42:14 PM To: [email protected] Subject: Re: extended advertsing with btshell Hi swapnil, You need to set BLE_EXT_ADV_MAX_SIZE syscfg to required value, e.g.: > newt target amend <your_target> syscfg=BLE_EXT_ADV=1:BLE_EXT_ADV_MAX_SIZE=1650 Default is 31, max is 1650 (as above). Best, Andrzej On Tue, Apr 24, 2018 at 5:35 PM, swapnil kadam <[email protected]> wrote: > > > Hello, > I am using btshell for advertsing with nrf52. > > When I use 31 bytes, mfg_data accepts the data with extended advertsing. But > when I use more than that, mfg_data doesn’t accept. is 251 byte payload > supported in extended advertising? > How could I send more than 251 byte payload on extended advertsing? > > Thank you, > > Regards, > swapnil >
