fix(nimble): Fix ble_multi_adv example to show correct UUIDs information

This commit is contained in:
Rahul Tank
2026-02-11 12:18:28 +05:30
parent 9cf49269aa
commit 8abbd1b6c8
4 changed files with 83 additions and 10 deletions
@@ -13,6 +13,13 @@ It starts 4 types of advertising:
* Scannable legacy
* Legacy with specified duration(5 sec)
## Service UUID Notes
* The example registers two 16-bit GATT services and one custom 128-bit GATT service.
* All advertising instances include the two 16-bit service UUIDs.
* The connectable advertiser also includes the 128-bit service UUID.
* UUID values in advertising payloads are populated from the same UUID definitions used in the GATT server.
## How to Use Example
Before project configuration and build, be sure to set the correct chip target using: