nRF5340 Audio DK: LE Audio and UART2 Concurrently

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

fweinrebe — Thu, 08 Jun 2023 09:36:41 GMT

Finally, it's working. :-)

The key to fixing this was to add the following line in gatt_discover():

default_conn = conn;

This was why the UART (NUS) side complained about the connection. It was probably due to having to disable the call to "bt_enable()" during the setup of the UART (NUS). LE Audio is enabled before the NUS Client therefore LE Audio already makes a connection.

static void gatt_discover(struct bt_conn *conn)

{

int err;

// This is the fix...Because bt_enable was disabled

default_conn = conn;

if (conn != default_conn)

{

return;

}

err = bt_gatt_dm_start(conn,

BT_UUID_NUS_SERVICE,

&discovery_cb,

&nus_client);

if (err)

{

LOG_ERR("could not start the discovery procedure, error code: %d", err);

}

AND

In the NUS Client setup code disable the call to bt_enable():

// err = bt_enable(NULL);

// if (err)

// {

// LOG_ERR("Bluetooth init failed (err %d)", err);

// return;

// }

AND

I also moved the "bt_nus_client_send" related code into a separate thread procedure:

void ble_write_thread(void)

{

int err;

printk("\n*** In ble_write_thread ***\n");

/* Don't go any further until BLE is initialized */

k_sem_take(&ble_init_ok, K_FOREVER);

for (;;)

{

/* Wait indefinitely for data to be sent over Bluetooth */

struct uart_data_t *buf = k_fifo_get(&fifo_uart_rx_data, K_FOREVER);

// Note: Problem here is that "nus_client->conn" does not

contain a valid connection.

// This is fixed by adding a line to procedure "gatt_discover".

err = bt_nus_client_send(&nus_client, buf->data, buf->len);

if (err)

{

printk("Failed to send data over BLE connection(err %d)\n", err);

LOG_WRN("Failed to send data over BLE connection(err %d)", err);

}

else

{

printk("Data sent data over BLE connection\n");

}

err = k_sem_take(&nus_write_sem, NUS_WRITE_TIMEOUT);

if (err)

{

printk("NUS send timeout\n");

LOG_WRN("NUS send timeout");

}

K_THREAD_DEFINE(ble_write_thread_id, STACKSIZE, ble_write_thread, NULL, NULL, NULL, PRIORITY, 0, 4000);

Here is the main() loop:

void main(void)

{

// LE Audio

int ret;

printk("InitLEAudio()\n");

InitLEAudio();

// UART2

/* Don't go any further until LE Audio is initialized */

k_sem_take(&le_audio_ok, K_FOREVER);

printk("InitUART2()\n");

InitUART2();

while (1)

{

// LE Audio

streamctrl_event_handler();

STACK_USAGE_PRINT("main", &z_main_thread);

// UART2

/* Use seperate thread (ble_write_thread) for data to be sent over Bluetooth */

}

k_sem_give(&le_audio_ok); was added to the end of void on_ble_core_ready(void) {...}

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

Amanda Hsieh — Wed, 07 Jun 2023 15:30:00 GMT

Hi,

I think the error is raised from bt_nus_send -> bt_gatt_notify_cb. Please try to debug the bt_gatt_notify_cb function to see where returns - 128, it means ENOTCONN

-Amanda H.

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

fweinrebe — Wed, 07 Jun 2023 06:07:59 GMT

sadly not. When I send the data I still get the error:

"Failed to send data over BLE connection(err -128)

NUS send timeout"

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

Amanda Hsieh — Tue, 06 Jun 2023 19:46:32 GMT

yes, err -120 means Operation is already in progress.

From the second part of the log, it seems you fix the issue, right? There is no error in the second part of the ble_write_thread.

-Amanda H.

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

fweinrebe — Tue, 06 Jun 2023 05:28:38 GMT

[quote user="Amanda"]Please make sure Central and Peripheral UART are connected. [/quote]

If I knew how to I would not have asked for help.

I have disabled the code because it creates another problem:

// printk(" bt_enable.\n");

// err = bt_enable(NULL);

// if (err)

// {

// printk("Failed to Enable UART service (err: %d)", err);

// error();

// }

If I disable the LE Audio code and uncomment the code "bt_enable(NULL);" then it works. But If I enable the LE Audio code again, then It doesn't work anymore.

printk(" bt_enable\n");

err = bt_enable(NULL);

if (err)

{

printk("Bluetooth init failed (err %d)", err);

LOG_ERR("Bluetooth init failed (err %d)", err);

return;

}

*** Booting Zephyr OS build v3.2.99-ncs1 ***

InitLEAudio()

nRF5340 APP core started

bt_dev.drv

atomic_clear_bit

atomic_test_and_set_bit

bt_settings_init

bt_monitor_send

k_work_submit

LE Audio Setup Done.

InitUART2()

Starting Bluetooth Central UART example

bt_conn_auth_cb_register

bt_conn_auth_info_cb_register

bt_enable

bt_dev.drv

atomic_clear_bit

atomic_test_and_set_bit

Bluetooth init failed (err -120)

*** In ble_write_thread ***

Some further testing here is a log with more detail:

*** Booting Zephyr OS build v3.2.99-ncs1 ***

InitLEAudio()

nRF5340 APP core started

bt_dev.drv

atomic_clear_bit

atomic_test_and_set_bit

bt_settings_init

bt_monitor_send

k_work_submit

LE Audio Setup Done.

InitUART2()

Starting Bluetooth Central UART example

bt_conn_auth_cb_register

bt_conn_auth_info_cb_register

Bluetooth initialized

settings_load

module_init

uart_init

UART device is ready

Scan module initialized

NUS Client module initialized

Scanning

Scanning successfully started

UART2 Setup Done.

Filters matched. Address: FC:55:67:78:B1:1F (random) connectable: 1

Connecting failed

connected

bt_addr_le_to_str

Connected: FC:55:67:78:B1:1F (random)

*** In ble_write_thread ***

* Entering Loop *

bt_addr_le_to_str

Security changed: FC:55:67:78:B1:1F (random) level 2

gatt_discover

MTU exchange done

Isn't the Init error related to there being already a LE Audio stream going and BT is already initialized and connected?

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

Amanda Hsieh — Mon, 05 Jun 2023 16:52:39 GMT

[quote user="fweinrebe"]Failed to send data over BLE connection(err -128)[/quote]

Error -128 means that Socket is not connected.

Please make sure Central and Peripheral UART are connected.

-Amanda H.

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

fweinrebe — Mon, 05 Jun 2023 07:19:12 GMT

Hi Amanda,

2.2.0. (Was using 2.3.0 originally but had a problem earlier with the board so I went one version down. )

I tried both (first Central and lastly Peripheral) with the HEADSET, currently Peripheral UART on the HS.

I do not have a 3rd device that can run the sniffer application.

I am having issues with the logging because of the UART2 change. Here is my log, I had to add a lot of printk() lines to log to UART0:

InitUART2()

Starting Bluetooth Central UART example

bt_conn_auth_cb_register

bt_conn_auth_info_cb_register

Bluetooth initialized

settings_load

module_init

Scan module initialized

Scanning successfully started

UART2 Setup Done.

*** In ble_write_thread ***

* Entering Loop *

Failed to send data over BLE connection(err -128)

NUS send timeout

Thank you

Fritz

RE: nRF5340 Audio DK: LE Audio and UART2 Concurrently

Amanda Hsieh — Fri, 02 Jun 2023 14:05:20 GMT

Hi,

Which version of NCS are you using?

Do you test the HEADSET merged with the NUS client and Peripheral UART sample?

Could you provide the output log on both sides and the sniffer log?

Regards,
Amanda H.