i2c+timer+work keeps getting -22 or -128 and keep crashing

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

ovrebekk — Tue, 21 Nov 2023 14:51:36 GMT

Good luck! Just get back to me when you have more details to share.

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Tue, 21 Nov 2023 09:05:07 GMT

Thanks a lot! I will try to find a way to enable logging.

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

ovrebekk — Tue, 21 Nov 2023 07:25:21 GMT

[quote user="kfcube"]Can the code run on the 52840 DK, which doesn't have the sensor? [/quote]

Do you mean if you get a kit yourself?

Typically you would wire up a sensor board to your DK somehow so you can run on the DK with all the functionality operational.

In case you send code to me I would probably have to comment out the sensor code, or replace it with some other sensor I have laying around.

As for your disconnect issues, are you doing anything in the disconnect callback that could explain the issue?

Most Bluetooth callbacks are run in interrupt context, and if you try to run any blocking function calls from an interrupt it could lead to issues.

In order to debug the crash you should have logging enabled, then you should see a crash report that might give some indication to the cause of the problem.

Best regards
Torbjørn

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Mon, 20 Nov 2023 10:16:42 GMT

Thanks. Can the code run on the 52840 DK, which doesn't have the sensor? The issue is only after the sensor data retrieve. As I have replied earlier, I have figured out the -22 issue. Now the only issue left is chip crash and auto start after the client disconnect, if we retrieved sensor data. If we don't get data, the disconnect worked fine.

If you may please advise some possibilities so I can dig in.

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

ovrebekk — Mon, 20 Nov 2023 10:10:24 GMT

The development platform for the nRF52811 is the nRF52840DK, and it is recommended to get one of those so you can debug the application when needed.

There are board files in the SDK allowing you to build for the nRF52811 on the nRF52840DK.

Thanks for sharing the code. I can't spot any issues in the code you shared that would explain the problem, but the code you shared doesn't show the whole application either. For instance it doesn't show where you call the fetch_and_display(..) function, which could be relevant to the issue.

Would you be able to share the entire project so I can try to run it on my end and reproduce the problem?

I can make the case private if you don't want to share your code in a public ticket.

Best regards
Torbjørn

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Sun, 19 Nov 2023 12:59:20 GMT

hey I figured the reason of the 1st connect can't notify issue. Sorry somehow the client didn't enable notification for the 1st time connect. so its not the chip issue. so the only issue now is why crash after disconnect. if you may know please advise some possibilities for me to dig in. Thanks

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Sun, 19 Nov 2023 02:28:34 GMT

no its not fixed. the problem is still there: 1st connect, can't notify, but can disconnect. 2nd and later, can notify, but disconnect crash the chip.

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

NadiaEira — Sat, 18 Nov 2023 06:44:54 GMT

Thank you for your sharing. It’s great that the problem is finally fixed.

skibidi toilet

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Sat, 18 Nov 2023 02:05:07 GMT

To be more specific, the current issue is: after the 1st connect, the sensor data notify got -22. then the client disconnect, disconnect working fine. the client connect again, the sensor data notify successfully. but when client disconnect again, the chip crashed and auto restart.

In a summary, 1st connect, can't notify, but can disconnect. 2nd and later, can notify, but disconnect crash the chip.

I set the CONFIG_BT_LOG_LEVEL_DBG = y, but no any errors info.

Thanks,

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

kfcube — Sat, 18 Nov 2023 01:55:37 GMT

Hi,

I use timer in order to get sensor data periodically, which actually I learned from here: Zephyr Timer + I2C

the notification does succeed once after the client disconnect once and then connect again.

I am not be able to debug because the 52811 small RAM. Is there anyway that I can only debug ble part?

My code is based on the zephyr/samples/sensor/lsm6dso, and the only change I made is send out sensor data calling bt_gatt_notify

static inline float out_ev(struct sensor_value *val)
{
return (val->val1 + (float)val->val2 / 1000000);
}

static void float2byte(float value, uint8_t *out_data,int len)
{
uint8_t *pdata = (uint8_t *)&value;
for(int i = 0;i < len;i++)
{
out_data[i] = *pdata++;
}
}

const struct device *const mdev = DEVICE_DT_GET_ONE(st_lsm6dsr);

static void fetch_and_display(const struct device *dev)
{

struct sensor_value x, y, z;

float xyz[3];
uint8_t acc_data[12];

trig_cnt++;

/* lsm6dsr accel */
sensor_sample_fetch_chan(dev, SENSOR_CHAN_ACCEL_XYZ);
sensor_channel_get(dev, SENSOR_CHAN_ACCEL_X, &x);
sensor_channel_get(dev, SENSOR_CHAN_ACCEL_Y, &y);
sensor_channel_get(dev, SENSOR_CHAN_ACCEL_Z, &z);

xyz[0] = out_ev(&x);
xyz[1] = out_ev(&y);
xyz[2] = out_ev(&z);
printf("accel x:%f ms/2 y:%f ms/2 z:%f ms/2\n",
xyz[0], xyz[1], xyz[2]);

float2byte(xyz[0],acc_data,4);
float2byte(xyz[1],acc_data+4,4);
float2byte(xyz[2],acc_data+8,4);

bt_set_sensor_data(acc_data,sizeof(acc_data)/sizeof(acc_data[0]));

// printf("accel x:%f ms/2 y:%f ms/2 z:%f ms/2\n",
// out_ev(&x), out_ev(&y), out_ev(&z));

/* lsm6dsr gyro */
sensor_sample_fetch_chan(dev, SENSOR_CHAN_GYRO_XYZ);
sensor_channel_get(dev, SENSOR_CHAN_GYRO_X, &x);
sensor_channel_get(dev, SENSOR_CHAN_GYRO_Y, &y);
sensor_channel_get(dev, SENSOR_CHAN_GYRO_Z, &z);

printf("gyro x:%f rad/s y:%f rad/s z:%f rad/s\n",
out_ev(&x), out_ev(&y), out_ev(&z));

printf("trig_cnt:%d\n\n", trig_cnt);
}

int bt_set_sensor_data(uint8_t * p_data,uint16_t len)
{
int rc;
// printk("len: %d\n",len);
// for(int i=0;i<len;i++){
// printk("data[%d]=0x%d\n",i,p_data[i]);
// }
rc = bt_gatt_notify(mconn, &cube_svc.attrs[1], p_data, len);
printk("rc: %d\n",rc);

return rc == -ENOTCONN ? 0 : rc;
}

Thanks,

RE: i2c+timer+work keeps getting -22 or -128 and keep crashing

ovrebekk — Fri, 17 Nov 2023 12:40:09 GMT

Why do you use a timer to trigger the work item, do you need to add a delay to the sensor readout?

Is the notification ever successful, or will it always return an error?

Have you tried to debug the call to gatt_notify(..) so you can see exactly where in the code the error is returned?
That can usually provide more details than the error code alone.

Would you be able to share the code showing how the sensor is read and the notification sent?

Best regards
Torbjørn