samples: bluetooth: mesh: Add new mesh_blob_shell sample, Fix mesh private key generation starvation

- Add new example samples/bluetooth/mesh_blob_shell showing how to use mesh BLOB feature
- Bugfix for mesh private key generation causing starvation of other tasks

Signed-off-by: Cameron Soviero <cam@ti.com>
Signed-off-by: Caleb Overbay <c-overbay@ti.com>
Signed-off-by: Ging Gonzalez <g-gonzalez@ti.com>

Author: Cameron Soviero

samples/bluetooth/mesh_blob_shell/CMakeLists.txt

@@ -0,0 +1,17 @@
+# SPDX-License-Identifier: Apache-2.0
+
+cmake_minimum_required(VERSION 3.20.0)
+set(QEMU_EXTRA_FLAGS -s)
+
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(mesh)
+
+target_sources(app PRIVATE src/main.c)
+
+target_sources(app PRIVATE src/board.c)
+
+if (CONFIG_BUILD_WITH_TFM)
+  target_include_directories(app PRIVATE
+    $<TARGET_PROPERTY:tfm,TFM_BINARY_DIR>/api_ns/interface/include
+  )
+endif()

samples/bluetooth/mesh_blob_shell/README.rst

@@ -0,0 +1,131 @@
+.. _ble_mesh_blob_shell:
+
+Bluetooth: Mesh BLOB Shell
+##########################
+
+Overview
+********
+
+This sample demonstrates Bluetooth Mesh's BLOB Models. It has the BLOB Client
+Model and the BLOB Server Model in addition to standard mesh models, and it
+supports provisioning over both the Advertising and the GATT Provisioning Bearers
+(i.e. PB-ADV and PB-GATT). The Mesh BLOB Shell sample is designed for transfering
+Binary Large OBjects (BLOB) in the mesh network using the standard BLOB Models.
+It includes a serial console built to allow sending of commands, such as to setup
+and start a BLOB transfer from a BLOB Client to a BLOB Server.
+
+
+Requirements
+************
+
+* 2 boards with Bluetooth LE support
+* Terminal Emulator (i.e., PuTTY or Tera Term)
+
+User Interface
+**************
+LEDs:
+   Used to identify the device being provisioned.
+
+Terminal Emulator:
+   Used to interacting with the sample's Mesh Shell.
+
+Building and Running
+********************
+
+This sample can be found under :zephyr_file:`samples/bluetooth/mesh_blob_shell` in the
+Zephyr tree.
+
+See :ref:`bluetooth samples section <bluetooth-samples>` for details on how
+to run the sample inside QEMU.
+
+For other boards, build and flash the application as follows:
+
+.. zephyr-app-commands::
+   :zephyr-app: samples/bluetooth/mesh_blob_shell
+   :board: <board>
+   :goals: flash
+   :compact:
+
+Refer to your :ref:`board's documentation <boards>` for alternative
+flash instructions if your board doesn't support the ``flash`` target.
+
+Interacting with the sample
+***************************
+
+1. Use PuTTY (or other serial terminal) to open a serial connection to the boards.
+2. From there, you can send mesh commands to the boards using the Bluetooth Mesh
+   Shell. For full reference on supported commands, refer to this
+   `page <https://docs.zephyrproject.org/latest/connectivity/bluetooth/api/mesh/shell.html>`_.
+
+To provision and test, continue to the sections below.
+
+.. _provisioning-section:
+
+Provisioning
+************
+
+The sample can be provisioned into an existing mesh network with an external
+provisioner device. The provisioner must give the device an Application Key and
+bind it to the BLOB Client and BLOB Server models.
+
+If using Texas Instrument's SimpleLink Connect Mobile App, refer to the
+`SimpleLink Mesh Guide <simplelink_connect_mesh_guide>`_ for information on how
+to provision and configure a mesh device.
+
+Before getting started:
+* Add an Application Key
+
+The first device will act as the BLOB Client
+* Bind the BLOB Client Model to the Application Key
+
+The second device will act as the BLOB Server
+* Bind the BLOB Server Model to the Application Key
+
+.. _testing-section:
+
+Testing
+*******
+
+After provisioning the mesh nodes and configuring the BLOB models, you can start
+a BLOB transfer from the BLOB Client to the BLOB Server. With serial terminals (PuTTY)
+open for both of the nodes, follow the steps below:
+
+NOTE: The following commands are just examples. To get more information on the
+blob command parameters, refer to this
+`page <https://docs.zephyrproject.org/latest/connectivity/bluetooth/api/mesh/shell.html>`_.
+
+BLOB Server
+===========
+1. Initialize the mesh shell
+
+   .. code-block:: bash
+
+      mesh init
+
+2. Prepare node for receiving a BLOB
+
+   .. code-block:: bash
+
+      mesh models blob srv rx 1 10
+
+BLOB Client
+===========
+1. Initialize the mesh shell
+
+   .. code-block:: bash
+
+      mesh init
+
+2. Add the BLOB Server as a target
+
+   .. code-block:: bash
+
+      mesh models blob cli target 0x0004
+
+3. Start BLOB transfer
+
+   .. code-block:: bash
+
+      mesh models blob cli tx 1 4096 10 65 0x0000 pull 10
+
+   NOTE: It may take several minutes to finish the BLOB transfer.

samples/bluetooth/mesh_blob_shell/SimpleLinkConnectMeshGuide.rst

@@ -0,0 +1,50 @@
+.. _simplelink_connect_mesh_guide:
+
+SimpleLink Connect Mesh Feature Guide
+#####################################
+
+Configuring Mesh Network
+************************
+
+On the landing page, tap on the `Mesh Network` button. This will take you to the
+mesh network page where you can add nodes and make configurations.
+
+Adding a Network Key
+====================
+1. Tap on the menu button (three dots icon on the top right)
+2. Tap `Configure network keys`
+3. Tap `Add new key`
+4. On the pop-up, tap `Save`
+
+Adding an Application Key
+=========================
+1. Tap on the menu button (three dots icon on the top right)
+2. Tap `Configure app keys`
+3. Tap `Add new key`
+4. On the pop-up, tap `Save`
+
+Adding a Provisioner
+====================
+
+1. Tap on the menu button (three dots icon on the top right)
+2. Tap `Provisioners`
+3. Tap `Add new provisioner`
+4. On the pop-up, confirm information and tap `Save`
+
+Adding a Mesh Node
+==================
+1. In the Mesh Network, tap on the `Add Node` button
+2. Tap the node you want to provision
+3. Tap on the `Provision` button
+
+Configuring a Mesh Node
+***********************
+
+Binding an Application Key to a Model
+=====================================
+
+1. In the Mesh Network, tap on the node you want to configure
+2. At the bottom section, select the Element that contains the Model
+   you want to configure
+3. Select the Model
+4. Under `Bind Application Key`, select the Application Key to bind to the model

samples/bluetooth/mesh_blob_shell/prj.conf

@@ -0,0 +1,49 @@
+CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
+
+CONFIG_BT_SETTINGS=y
+CONFIG_FLASH=y
+CONFIG_FLASH_MAP=y
+CONFIG_NVS=y
+CONFIG_SETTINGS=y
+CONFIG_HWINFO=y
+
+CONFIG_BT=y
+CONFIG_BT_L2CAP_TX_BUF_COUNT=5
+CONFIG_BT_PERIPHERAL=y
+CONFIG_BT_OBSERVER=y
+CONFIG_BT_BROADCASTER=y
+
+CONFIG_BT_CTLR_DUP_FILTER_LEN=0
+CONFIG_BT_CTLR_LE_ENC=n
+CONFIG_BT_CTLR_LE_PING=n
+CONFIG_BT_DATA_LEN_UPDATE=n
+CONFIG_BT_PHY_UPDATE=n
+CONFIG_BT_CTLR_MIN_USED_CHAN=n
+CONFIG_BT_CTLR_PRIVACY=n
+CONFIG_BT_CTLR_CHAN_SEL_2=n
+
+CONFIG_BT_MESH=y
+CONFIG_BT_MESH_MODEL_EXTENSIONS=y
+CONFIG_BT_MESH_RELAY=y
+CONFIG_BT_MESH_FRIEND=y
+CONFIG_BT_MESH_PB_GATT=y
+CONFIG_BT_MESH_PB_ADV=y
+CONFIG_BT_MESH_GATT_PROXY=y
+
+CONFIG_BT_MESH_SUBNET_COUNT=2
+CONFIG_BT_MESH_APP_KEY_COUNT=2
+CONFIG_BT_MESH_MODEL_GROUP_COUNT=2
+CONFIG_BT_MESH_LABEL_COUNT=3
+
+CONFIG_BT_DEVICE_NAME="Zephyr BLOB"
+CONFIG_SHELL=y
+CONFIG_LOG_CMDS=y
+CONFIG_BT_EXT_ADV=n
+CONFIG_BT_MESH_SHELL=y
+CONFIG_BT_MESH_BLOB_CLI=y
+CONFIG_BT_MESH_SHELL_BLOB_CLI=y
+CONFIG_BT_MESH_BLOB_SRV=y
+CONFIG_BT_MESH_SHELL_BLOB_SRV=y
+CONFIG_BT_MESH_RX_SEG_MAX=10
+CONFIG_BT_MESH_TX_SEG_MAX=10
+CONFIG_BT_MESH_BLOB_BLOCK_SIZE_MIN=1024

samples/bluetooth/mesh_blob_shell/sample.yaml

@@ -0,0 +1,10 @@
+sample:
+  name: Bluetooth Mesh BLOB Shell
+tests:
+  sample.bluetooth.mesh_blob_shell:
+    harness: bluetooth
+    platform_allow:
+      - lp_em_cc2340r53
+    integration_platforms:
+      - qemu_x86
+    tags: bluetooth

samples/bluetooth/mesh_blob_shell/src/board.c

@@ -0,0 +1,77 @@
+/* board.c - Generic HW interaction hooks */
+
+/*
+ * Copyright (c) 2021 Nordic Semiconductor
+ * Copyright (c) 2025 Texas Instruments Incorporated
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+#include <zephyr/bluetooth/mesh.h>
+#include <zephyr/drivers/gpio.h>
+#include "board.h"
+
+/* Locate led0 as alias or label by that name */
+#if DT_NODE_EXISTS(DT_ALIAS(led0))
+#define LED0 DT_ALIAS(led0)
+#elif DT_NODE_EXISTS(DT_NODELABEL(led0))
+#define LED0 DT_NODELABEL(led0)
+#else
+#define LED0 DT_INVALID_NODE
+#endif
+
+#if DT_NODE_EXISTS(LED0)
+#define LED0_DEV DT_PHANDLE(LED0, gpios)
+#define LED0_PIN DT_PHA(LED0, gpios, pin)
+#define LED0_FLAGS DT_PHA(LED0, gpios, flags)
+
+static const struct device *const led_dev = DEVICE_DT_GET(LED0_DEV);
+#endif /* LED0 */
+
+static int led_init(void)
+{
+#if DT_NODE_EXISTS(LED0)
+	int err;
+
+	if (!device_is_ready(led_dev)) {
+		return -ENODEV;
+	}
+
+	err = gpio_pin_configure(led_dev, LED0_PIN,
+				 LED0_FLAGS | GPIO_OUTPUT_INACTIVE);
+	if (err) {
+		return err;
+	}
+#else
+	printk("WARNING: LEDs not supported on this board.\n");
+#endif
+
+	return 0;
+}
+
+int board_init()
+{
+	int err;
+
+	err = led_init();
+	if (err) {
+		return err;
+	}
+
+	return 0;
+}
+
+void board_led_set(bool val)
+{
+#if DT_NODE_EXISTS(LED0)
+	gpio_pin_set(led_dev, LED0_PIN, val);
+#endif
+}
+
+void board_output_number(bt_mesh_output_action_t action, uint32_t number)
+{
+}
+
+void board_prov_complete(void)
+{
+}

samples/bluetooth/mesh_blob_shell/src/board.h

@@ -0,0 +1,16 @@
+/* board.h - Board-specific hooks */
+
+/*
+ * Copyright (c) 2017 Intel Corporation
+ * Copyright (c) 2025 Texas Instruments Incorporated
+ *
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+void board_output_number(bt_mesh_output_action_t action, uint32_t number);
+
+void board_prov_complete(void);
+
+int board_init();
+
+void board_led_set(bool val);