RE: Nrf52832/52810 advertising Name issue

Einar Thorsrud — Fri, 03 May 2019 08:28:12 GMT

You can for instance do it as shown in this diff:

devzone.nordicsemi.com/.../ble_5F00_advdata.diff

This demonstrates how it can be done, and I expect it will work, but I have not tested it.

RE: Nrf52832/52810 advertising Name issue

bevis — Fri, 03 May 2019 07:45:13 GMT

How to add support inadv_data_encode?

RE: Nrf52832/52810 advertising Name issue

Einar Thorsrud — Mon, 29 Apr 2019 13:32:28 GMT

Hi,

[quote user=""]When I run the example, I use short-name(BLE_ADVDATA_SHORT_NAME) advertising always "Fatal error",It's no use reducing payload. [/quote]

Have you tried to build with "DEBUG" defined? With the debug build you will see the file name, line number and error code printed in the log, and this will usually give a good indication about the problem.

[quote user=""]On the other hand, how to add custom private AD type data like this ???[/quote]

I don't know how you build the advertising packet, but typically it is built by populating a ble_advdata_t instance that is provided to ble_advdata_encode(). Type 0x88 and 0x89 are non standard, so I assume those are what you refer to? If so and you use adv_data_encode, then it probably makes most sense to adapt adv_data_encode to add support for these private types.