RE: USB CDC + BLE NUS will cause the BT function unstable

yclin — Wed, 05 Jun 2024 07:09:43 GMT

Hi Sigurd:

I found the root cause that will cause the timer trigger every 5 sec that will call the work to the workqueue and BT RX recevice the command it will also use the work to do the collect the sensor data then use the nus_send_data to send the data out. Thus i guess the timer maybe got the high priority to do the work first but i do not know why the BT work will stop. Do you have any suggest to prevent this problem happens thanks.

In my code:

struct k_work charging_led_work;

struct k_work_q d1stream_q;

struct k_work d1stream_work;

#define STACKSIZE 16384

#define PRIORITY -6

K_THREAD_STACK_DEFINE(stack_area, STACKSIZE);

/* Initial the system work queue for d1stream work task*/

void sys_work_q_init(){

k_work_queue_init(&d1stream_q);

k_work_queue_start(&d1stream_q, stack_area, K_THREAD_STACK_SIZEOF(stack_area), PRIORITY, NULL);

}

void handle_sc_cmd(uint8_t* cmd_data, int length){

//char *token;

//char *array[3];

//int i = 0;

int err = 0;

int sysparm_ret = 0;

int sysparm_id = 0;

// 1. First try to open the connection.

SDS_HANDLE handle = sds_Open();

if (is_SDS_HANDLE(handle)) {

#ifdef Debug_log

LOG_INF("[handle_sc_cmd] Open handle success (0x%x)\n", (P2UI)handle);

#endif

} else {

LOG_ERR("[handle_sc_cmd]ERROR sds_Open() FAILED\n");

}

// 2. check the cmd param[0] (ex: sysparam , getreg, setreg)

//scom_cmd = cmd_data[0];

if(cmd_data[0] == scom_AddCmd_D1Stream){

//if(cmd_data[0] == 0x61){

d1stream_loop = ((int)cmd_data[4])<< 24 |

((int)cmd_data[3])<< 16 |

((int)cmd_data[2])<< 8 |

((int)cmd_data[1]);

if(d1stream_loop == 65535){

d1stream_stop = SDS_STAT_ERR;

} else if(d1stream_loop == 0xffffffff){

d1stream_loop = -1;

sds_Close(handle);

k_work_submit_to_queue(&d1stream_q, &d1stream_work);

} else {

sds_Close(handle);

k_work_submit_to_queue(&d1stream_q, &d1stream_work);

}

static void bt_receive_cb(struct bt_conn *conn, const uint8_t *const data,

uint16_t len)

{

char addr[BT_ADDR_LE_STR_LEN] = {0};

bt_addr_le_to_str(bt_conn_get_dst(conn), addr, ARRAY_SIZE(addr));

#ifdef Debug_log

LOG_INF("Received data from: %s", (addr));

for(int i = 0; i < len; i++){

LOG_INF("data : 0x%02x", data[i]);

}

LOG_INF("len = %d ", len);

#endif

handle_sc_cmd(data, len);

}

static struct bt_nus_cb nus_cb = {

.received = bt_receive_cb,

.send_enabled = bt_send_enabled_cb,

};

void charging_led_work_cb(struct k_work *work){

int32_t val_mv = adc_reading();

if(val_mv >= BATTERY_CHARGE_90){

hmb_set_leds_state(HMB_ALL_LEDS_MSK,HMB_ALL_LEDS_MSK);

} else if((val_mv >= BATTERY_CHARGE_70 )){

for(int i = 0 ;i < 3; i++){

hmb_set_leds_state(HMB_LED2_MSK|HMB_LED3_MSK|HMB_LED5_MSK|HMB_LED6_MSK, HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

hmb_set_leds_state(HMB_ALL_LEDS_MSK,HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

}

} else if(val_mv >= BATTERY_CHARGE_30){

for(int i = 0 ;i < 3; i++){

hmb_set_leds_state(HMB_LED3_MSK|HMB_LED6_MSK,HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

hmb_set_leds_state(HMB_LED3_MSK|HMB_LED6_MSK|HMB_LED2_MSK|HMB_LED5_MSK,HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

}

} else if(val_mv >= BATTERY_CHARGE_0){

for(int i = 0 ;i < 3; i++){

hmb_set_leds_state(HMB_LED3_MSK|HMB_LED6_MSK,HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

hmb_set_leds_state(HMB_NO_LEDS_MSK, HMB_ALL_LEDS_MSK);

k_sleep(K_MSEC(1000));

}

void charging_led(struct k_timer *timer_id){

k_work_submit(&charging_led_work);

}

void main(){

...

sys_work_q_init();

k_timer_start(&m_charging_timer, K_SECONDS(5), K_SECONDS(5));

}

K_TIMER_DEFINE(m_charging_timer, charging_led, NULL);

K_WORK_DEFINE(charging_led_work, charging_led_work_cb);

K_WORK_DEFINE(d1stream_work, d1stream_work_cb);

Stanly

RE: USB CDC + BLE NUS will cause the BT function unstable

yclin — Wed, 29 May 2024 07:50:04 GMT

Hi,

I didn't get any error from my usb cdc acm log, should i turn on any settings of bt module. I can try to capture log again. the SDK version is v2.4.2, Zephyr version 3.3.99.

Stanly

RE: USB CDC + BLE NUS will cause the BT function unstable

Sigurd — Tue, 28 May 2024 14:25:47 GMT

Do you have any logs from that?

Also, what version of nRF Connect SDK are you using?

RE: USB CDC + BLE NUS will cause the BT function unstable

yclin — Tue, 28 May 2024 13:29:10 GMT

I just plug in the usb to monitor the log print out and enable the ble nus send the data at the same time but suddenly the bt not send the data out after 5sec. After that the usb cdc port seems disconnect and flush the device manager again. If i use the uart0 device that's no this issue happened.

Stanly

RE: USB CDC + BLE NUS will cause the BT function unstable

Sigurd — Tue, 28 May 2024 13:01:56 GMT

Hi!

Could you explain these "data unstable problem" ? What's the issue?