Searched refs:advertise (Results 1 – 25 of 25) sorted by relevance
| /Zephyr-Core-3.5.0/samples/subsys/mgmt/mcumgr/smp_svr/src/ |
| D | bluetooth.c | 26 static void advertise(struct k_work *work) in advertise() function
74 k_work_init(&advertise_work, advertise); in start_smp_bluetooth_adverts()
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | proxy.rst | 11 Nodes with the Proxy feature enabled can advertise with Network Identity and Node Identity,
20 advertise with Private Network Identity and Private Node Identity types, which is controlled by the
32 solicited to advertise connectable advertising events without enabling the Private GATT Proxy state.
|
| D | od_cli.rst | 12 defines how long a node will advertise Mesh Proxy Service with Private Network Identity type after
|
| D | core.rst | 118 All mesh stack bearers advertise data with the :c:macro:`BT_ID_DEFAULT` local identity.
|
| D | provisioning.rst | 95 via any available OOB mechanism (e.g. the device may advertise a packet
|
| /Zephyr-Core-3.5.0/samples/bluetooth/central_past/ |
| D | README.rst | 28 the Zephyr tree on another board that will advertise and await a periodic
|
| /Zephyr-Core-3.5.0/samples/bluetooth/broadcast_audio_sink/ |
| D | Kconfig | 28 Time to advertise connectable for a Broadcast Assistant to connect
|
| /Zephyr-Core-3.5.0/subsys/net/l2/bluetooth/ |
| D | bluetooth_shell.c | 117 SHELL_CMD(advertise, NULL,
|
| /Zephyr-Core-3.5.0/tests/net/lib/mqtt_sn_packet/src/ |
| D | mqtt_sn_packet.c | 30 static uint8_t advertise[] = { 5, 0x00, 42, 0xDE, 0xAD }; variable
101 MQTT_SN_DECODE_TEST(advertise),
104 .params.advertise = {
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/shell/ |
| D | bap_scan_delegator.rst | 38 uart:~$ bt advertise on
|
| D | mcp.rst | 87 used - :code:`bt init` followed by :code:`bt advertise on` (or
115 uart:~$ bt advertise on
388 type>` (or :code:`bt advertise on` if the server is advertising).
|
| D | ccp.rst | 95 uart:~$ bt advertise on
|
| D | bap.rst | 113 uart:~$ bt advertise on
|
| /Zephyr-Core-3.5.0/subsys/net/lib/mqtt_sn/ |
| D | mqtt_sn_msg.h | 200 struct mqtt_sn_param_advertise advertise; member
|
| D | mqtt_sn_decoder.c | 334 return decode_msg_advertise(buf, ¶ms->params.advertise); in mqtt_sn_decode_msg()
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/audio/ |
| D | Kconfig.bap | 222 periodic advertise or a broadcast isochronous stream.
262 to sync to a periodic advertise or a broadcast isochronous stream.
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/ |
| D | bluetooth-shell.rst | 144 Begin advertising by using the :code:`bt advertise on` command. This will use the default parameters
145 and advertise a resolvable private address with the name of the device. You can choose to use the
146 identity address instead by running the :code:`bt advertise on identity` command. To stop
147 advertising use the :code:`bt advertise off` command.
168 You may notice that with this, the custom advertiser does not advertise the device name; you need to
|
| D | bluetooth-audio-arch.rst | 21 GAF uses GAP to connect, advertise and synchronize to other devices.
|
| D | bluetooth-arch.rst | 302 advertise specific advertising data, but the type of advertising will be
|
| /Zephyr-Core-3.5.0/doc/releases/ |
| D | release-notes-1.10.rst | 432 * :github:`4544` - [BLE Mesh] Error: Failed to advertise using Node ID
|
| D | release-notes-2.5.rst | 717 * When privacy has been enabled in order to advertise towards a
1926 * :github:`13244` - How to encrypt advertise packet with zephyr and nrf52832 ？
|
| D | release-notes-2.3.rst | 907 * :github:`25016` - BT_LE_ADV_NCONN_NAME doesn't actually advertise name
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/host/ |
| D | Kconfig | 772 identity address the scanner will receive directed advertise reports
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/shell/ |
| D | bt.c | 4019 SHELL_CMD_ARG(advertise, NULL,
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/mesh/ |
| D | Kconfig | 1433 advertise the Private Network Identity type after receiving a Solicitation PDU.
|
