https://devzone.nordicsemi.com/f/nordic-q-a/93210/how-to-use-32-bit-uuid-in-advtising-dataThe nrf52840 dongle how to use 32-bit uuid in advtising data?en-USTelligent Community 13Tue, 25 Oct 2022 14:19:45 GMThttps://devzone.nordicsemi.com/thread/392430?ContentTypeID=1Tue, 25 Oct 2022 14:19:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6d316528-0d3d-4bb6-846c-1e2e68f0ddf3Kenneth<p>Hello,</p> <p>You don&#39;t specify which development platform you are using, but we recommend the nRF Connect SDK for new development:<br />Why? <a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement">https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-sdk-and-nrf5-sdk-statement</a>&nbsp;<br />Getting started? <a href="https://academy.nordicsemi.com/">https://academy.nordicsemi.com/</a>&nbsp;</p> <p>During development you should be using an nRF52840-DK, the nRF52840 Dongle is nice for testing and demo, but for development you need a proper DK with on-board programmer/debugger. So please get yourself an nRF52840-DK if you haven&#39;t already.</p> <p>Searching through the Bluetooth examples for 32-bit UUID I can&#39;t really find any examples that use 32-bit by default. But it should be similiar to using 16-bit or 128-bit UUID in the advertisment packet, so I suggest to for instance take a look at any of those and change it to 32-bit.</p> <p>The \peripheral_uart and \central_uart show for instance how to add a 128-bit UUID to the scan response packet during advertisment, and how to scan for it on the central side. That may be good starting points for reference. A tip: Change BT_DATA_UUID128_ALL() to&nbsp;BT_DATA_UUID32_ALL() in bt_data[].</p> <p>BEst regards,<br />Kenneth</p><div style="clear:both;"></div>