u/awh-emb

context: i have a bmp390 and mpu-6050 running on the same shared I2c bus using the rust embassy framework to essentially use a criticalRawMutex to share the bus, and a lis3mdl on the SPI they were working perfectly fine had them run for 2-hours ish for some graphs and data but then i added my KF (kalman filter) implementation and boom the sensor fusion to it first after about 10-15 seconds stop sending I2C readings? cause the kalman filter starts running on predict only essentially (readings change like 0.001 each dt, then the KF itself runs till about 38-39 seconds, then also boom, no hard panic or fault or anything like that just silence from demft,
can anyone provide some insight???
also i can post defmt logs if that would

context: i have a bmp390 and mpu-6050 running on the same shared I2c bus using the rust embassy framework to essentially use a criticalRawMutex to share the bus, and a lis3mdl on the SPI they were working perfectly fine had them run for 2-hours ish for some graphs and data but then i added my KF (kalman filter) implementation and boom the sensor fusion to it first after about 10-15 seconds stop sending I2C readings? cause the kalman filter starts running on predict only essentially (readings change like 0.001 each dt, then the KF itself runs till about 38-39 seconds, then also boom, no hard panic or fault or anything like that just silence from demft,
can anyone provide some insight???
also i can post defmt logs if that would help