Thingy91 getting "Error on I2C line occurred for message 0" in asset tracker

I'm developing application based on asset tracker, which should use BME680 AQI library and sensor. Everything was working as expected until I once left sensor for about 2h to gather data and it apparently got hanged (data stopped flowing to nRF cloud, even with Pro plan). I tried to flash again SiP firmware (we are using 1.3.3) and clean Asset Tracker app from SDK v2.1.1 - no action, LEDs are off (even with UI module enabled), no data is flowing.

I managed to gather some logs via LTE Monitor and I can see some errors right after switching on the device:

[00:00:00.990,936] [1;31m<err> i2c_nrfx_twim: Error on I2C line occurred for message 0[0m
[00:00:00.990,997] [1;31m<err> board_secure: Could not set buck to 1.8 V, error: -5[0m
[00:00:00.991,027] [1;31m<err> board_secure: power_mgmt_init failed with error: -5[0m
[00:00:00.996,307] [1;31m<err> ADXL362: wrong part_id: 0[0m
*** Booting Zephyr OS build v3.1.99-ncs1  ***
[00:00:02.499,023] [1;31m<err> i2c_nrfx_twim: Error on I2C line occurred for message 0[0m
[00:00:02.503,143] [0m<inf> at_host: UART check failed: 13. Dropping buffer and retrying.[0m
[00:00:02.513,793] [0m<inf> app_event_manager: APP_EVT_START[0m
[00:00:02.520,446] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
[00:00:02.521,118] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
[00:00:02.521,881] [1;31m<err> ext_sensors: Temperature sensor device is not ready[0m
[00:00:02.521,911] [1;31m<err> sensor_module: EXT_SENSOR_EVT_TEMPERATURE_ERROR[0m
[00:00:02.521,911] [1;31m<err> ext_sensors: Humidity sensor device is not ready[0m
[00:00:02.521,942] [1;31m<err> sensor_module: EXT_SENSOR_EVT_HUMIDITY_ERROR[0m
[00:00:02.521,942] [1;31m<err> ext_sensors: Pressure sensor device is not ready[0m
[00:00:02.521,972] [1;31m<err> sensor_module: EXT_SENSOR_EVT_PRESSURE_ERROR[0m
[00:00:02.522,003] [1;31m<err> ext_sensors: Low-power accelerometer device is not ready[0m
[00:00:02.522,033] [1;31m<err> sensor_module: EXT_SENSOR_EVT_ACCELEROMETER_ERROR[0m
[00:00:02.682,342] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
%MDMEV: SEARCH STATUS 1

From what I found on other post, Error on I2C line occurred for message 0, indicates some issues with I2C addressing, but I haven't changed anything on a board - is it possible it's a software issue or does it indicate hardware problem? Should I perform some additional troubleshooting?

  • Hi

    This is just a normal Thingy:91 using one of the internal sensors for I2C, correct? The log file doesn't seem "complete" to me as I'd expect a ***Booting Zephyr OS build *** message at the very top as well. Are you sure you haven't cut out anything of the log here? 

    My guess, since it was running correctly at one point with what I assume was the same firmware (Asset tracker application from NCS v2.1.1 and modem firmware 1.3.3), is that the Thingy:91 has been running on battery power and that the battery is low, causing under voltage on the sensors since they are all failing to be initialized. Can you try recharging the battery or power it with the USB cable? Also perhaps check that the battery is properly connected in the Thingy:91.

    Best regards,

    Simon

  • This is normal Thingy91, but due to battery charging and discharging influencing temperature measurements, I disconnected it and removed from the box .So it's powered only by USB cable. Is it required to have a battery to operate properly?

    As for log trimming - since I'm using LTE Monitor, it disconnects when the device shuts down and after switching on the Thingy I need to quickly re-anable log tracing. And this is the quickest log I could get. I tried also using Trace collectors (v1 and v2), but they worked a bit worse and also need reconnecting after device shutdown. If there is a way to get more logs, I can give it a try

  • Hi,

    From the logs, it seems like the power is what is causing the rest of the errors as far as I can see. I just tested on my end, and it works fine without the battery connected on my end. Unfortunately it seems like the Thingy:91 is damaged somehow. Where did you get the Thingy:91, from one of our distributors or what?

    Best regards,

    Simon

Related