Hello, I'm working with BLE Mesh using NRF52840
- Our setup: NRF-Connect-SDK 2.1.0
- Summary of our project.
+ Provisioner node to control lightness for all nodes in the network system. Our provisioner code which I custom from an example \zephyr\samples\bluetooth\mesh_provisioner to add one client to send message to the server (on another node).
+ Lightness node: used to control the lightness of the LED. Our lightness node code which I use from an example \nrf\samples\bluetooth\mesh\light_ctrl.
1. If I have sent a message with ack type from the provisioner node to the lightness node.
if (bt_mesh_model_pub_is_unicast(light_cli[0].client.model))
{
err = bt_mesh_lightness_cli_light_set(&light_cli[0].client, NULL,
&set, NULL);
if(err)
{
LOG_INF("Client Failed to public state change: %d", err);
}
else
{
light_cli[0].lvl = set.lvl;
LOG_INF("Public address: 0x%04x - lightness %d - test idx %d", light_cli[0].client.model->pub->addr, set.lvl, test_idx++);
// Wait for the semaphore from server response callback about 2 seconds
err = k_sem_take(&sem_srv_rsp, K_MSEC(2000));
if (err == -EAGAIN)
{
LOG_INF("Failed to take the semaphore from light status handler, address = 0x%04x", light_cli[0].client.model->pub->addr);
}
else if(!err)
{
continue;
}
}
}
Then, the Provisioner node received a response (callback) in the light status function that we registered when initialing the client control. Including current value and target value
struct bt_mesh_lightness_status {
/** Current Lightness level. */
uint16_t current;
/** Target Lightness level. */
uint16_t target;
/**
* Time remaining of the ongoing transition in milliseconds, or
* @em SYS_FOREVER_MS. If there's no ongoing transition,
* @c remaining_time is 0.
*/
int32_t remaining_time;
}; . And the result was as I expected.
For instance: When the Provisioner node sends "1", then it receives "current value = 0, target value = 1",
When the Provisioner node sends "2", then it receives "current value =1, target value =2", etc
2. If I enable CONFIG_BOOTLOADER_MCUBOOT=y in prj.conf file of provisioner node code to add MCUBOOT and for updating firmware purposes. I run code and test and have an issue.
In particular about the issue:
+ current value = 0, target value = 1 was wrong
+ I checked in light status function at lightness_cli.c file, it is the received handler and callback to light status function on the application.
static int light_status(struct bt_mesh_model *model, struct bt_mesh_msg_ctx *ctx,
struct net_buf_simple *buf, enum light_repr repr)
{
LOG_INF("[Quoc] light_repr: %d", repr);
if (buf->len != BT_MESH_LIGHTNESS_MSG_MINLEN_STATUS &&
buf->len != BT_MESH_LIGHTNESS_MSG_MAXLEN_STATUS) {
return -EMSGSIZE;
}
struct bt_mesh_lightness_cli *cli = model->user_data;
struct bt_mesh_lightness_status status;
struct bt_mesh_lightness_status *rsp;
LOG_INF("[Quoc] Raw buf len: %d", buf->len);
status.current = repr_to_light(net_buf_simple_pull_le16(buf), repr);
if (buf->len == 3) {
LOG_INF("[Quoc] buf->len == 3");
status.target =
repr_to_light(net_buf_simple_pull_le16(buf), repr);
status.remaining_time =
model_transition_decode(net_buf_simple_pull_u8(buf));
} else {
LOG_INF("[Quoc] Else: %d", buf->len);
status.target = status.current;
status.remaining_time = 0;
}
if (bt_mesh_msg_ack_ctx_match(&cli->ack_ctx, op_get(LIGHTNESS_OP_TYPE_STATUS, repr),
ctx->addr, (void **)&rsp)) {
*rsp = status;
bt_mesh_msg_ack_ctx_rx(&cli->ack_ctx);
}
LOG_INF("[Quoc] Status - target = %d, current = %d", status.target, status.current);
if (cli->handlers && cli->handlers->light_status) {
cli->handlers->light_status(cli, ctx, &status);
}
return 0;
}
and the condition if (buf->len == 3) was wrong). The buf->len is equal to 0 and it goes to the else case and leads to the current value and target value wrong on the application.
Could you investigate and help me with this case? It seems to be related to the bt stack when I enable MCUBOOT or other reasons.
Thank you in advance and appreciate your support.
Tôi đã kiểm tra
