Hi Andrej,

>
> Are you sure that you parse data from packet which has mfg data? With
> active scan and scannable packets you will have ADV_IND and SCAN_RSP
> as separate events so mfg data may be in the other one - you need to
> parse both.
>

Thank you for the response. I am parsing both ADV_IND and SCAN_RSP packets.
I believe I made some headway though.

filter_duplicates seems to do something strange. When filter_duplicates is
turned on, I don't get SCAN_RSP packets. Execution won't even
reach ble_ll_hci_send_adv_report:ble_ll_scan.c.

With filter_duplicates turned off, I can get SCAN_RSP packets up to the
application layer and manuf data seems alright.

Is it possible that filter_duplicate is filtering out SCAN_RSP packet
thinking its a dup?

Jitesh


> If this is not the problem, can you share raw data from advertising
> and scan response packets to see what could go wrong parsing them?
>
> > Jitesh
>
> Best regards,
> Andrzej
>
>
> > On Tue, Nov 14, 2017 at 12:30 AM, Jitesh Shah <[email protected]>
> wrote:
> >
> >> Hey guys,
> >> I have a peripheral running Nordic softdevice (BLE 4.0 protocol).
> Central
> >> is running nimBLE stack 1.0 (0db6321a75deda126943aa187842da6b977cd1c1).
> >>
> >> The peripheral advertises manufacturing data. I am trying to get to it
> >> from the central. I never get the mfg data though. The advertisement
> packet
> >> looks like this at the central:
> >>
> >>> (gdb) p/x *fields
> >>> $1 = {flags = 0x6, uuids16 = 0x0, num_uuids16 = 0x0,
> uuids16_is_complete
> >>> = 0x0, uuids32 = 0x0, num_uuids32 = 0x0, uuids32_is_complete = 0x0,
> >>>   uuids128 = 0x20006750, num_uuids128 = 0x1, uuids128_is_complete =
> 0x1,
> >>> name = 0x0, name_len = 0x0, name_is_complete = 0x0, tx_pwr_lvl = 0x0,
> >>>   tx_pwr_lvl_is_present = 0x0, slave_itvl_range = 0x0, svc_data_uuid16
> =
> >>> 0x0, svc_data_uuid16_len = 0x0, public_tgt_addr = 0x0,
> >>>   num_public_tgt_addrs = 0x0, appearance = 0x0, appearance_is_present =
> >>> 0x0, adv_itvl = 0x0, adv_itvl_is_present = 0x0, svc_data_uuid32 = 0x0,
> >>>   svc_data_uuid32_len = 0x0, svc_data_uuid128 = 0x0,
> svc_data_uuid128_len
> >>> = 0x0, uri = 0x0, uri_len = 0x0, mfg_data = 0x0, mfg_data_len = 0x0}
> >>
> >>
> >> Everything else adds up, except no mfg data. Worth noting that I can see
> >> the mfg data if I use another BLE central to scan.
> >>
> >> My discovery parameters are as follows:
> >> disc_params.filter_duplicates = 1;
> >> disc_params.passive = 0; // active scan
> >> /* Use defaults for the rest of the parameters. */
> >> disc_params.itvl = 0;
> >> disc_params.window = 0;
> >> disc_params.filter_policy = 0;
> >> disc_params.limited = 0;
> >>
> >> Any ideas or hints as to how I can debug?
> >>
> >> 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.
>

-- 
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