Invalid advertising data message when scanning with nRF52840 Dongle

RE: Invalid advertising data message when scanning with nRF52840 Dongle

jeg223 — Tue, 08 Oct 2019 13:23:41 GMT

Hello Ken,

ad_list = [2, 1, 6, 25, 255, 49, 1, 151, 48, 207, 67, 234, 54, 0, 79, 80, 69, 78, 138, 11, 93, 155, 141, 132, 0, 0, 0, 0, 1, 0, 0]

Parsing it shows the 0s at the end don't make any sense. So I'll have to track down the device sending this.

RE: Invalid advertising data message when scanning with nRF52840 Dongle

kere — Tue, 08 Oct 2019 11:05:57 GMT

Hi jeg223,

Do you have the raw advertising packet data so I can try to reproduce the issue?

BR,
-Ken.

RE: Invalid advertising data message when scanning with nRF52840 Dongle

jeg223 — Mon, 07 Oct 2019 21:54:20 GMT

Hello Einar,

Thank you for the response. I printed out the advertising data that caused this message. The data causes the BLEAdvData.from_c method to go into an infinite loop. I can post the full data if you want, but essentially the ad_list ends with 0, 0.

It gets interpreted as ad_len = 0, ad_type = 0. index is never updated, so the method never exits.

Thanks,

Jim

RE: Invalid advertising data message when scanning with nRF52840 Dongle

Einar Thorsrud — Mon, 07 Oct 2019 13:02:08 GMT

Hi,

The SoftDevice will filter out any packets with CRC errors, so the invalid packets actually have a valid CRC but are invalid (or rather not one of the specified types (see definition of class Types(Enum) in ble_driver.py). You can probably verify this by printing the type value, and seeing that it is not one of the listed types. What is the value typically in these cases (when it is not one of the listed)?