# Debug The following resources describe a few common issues and the techniques available to analyze and troubleshoot these issues. Note The `` should be considered as one of the existing paths on the device: `/etc/sensors/registry/registry/` or `/var/cache/sensors/registry/registry/`. ## The `ssc_sensor_info` tool is unable to list sensors This error indicates a failure in parsing the sensor registry, rendering the sensor unavailable for listing using the `ssc_sensor_info` tool. Do the following to resolve this error: > > > Note > > > Verify that the read and write permissions for the files are enabled for User mode, and read-only permission is enabled for Group and Others modes. Ensure that the User and Group mode names are `system system`. > > > 1. Ensure that `/etc/sensors/sns_reg_config` and `/etc/sensors/config/json.lst` files are present with the required permissions > as shown in the following example: > > > > > > > > > > root@qcm6490:~# ls -l /etc/sensors/sns_reg_config > > -rw-r--r--. 1 system system 226 Mar 9 2018 /etc/sensors/sns_reg_config > > Copy to clipboard > > > > > > root@qcm6490:~# ls -l /etc/sensors/config/json.lst > > -rw-r--r--. 1 system system 1452 Mar 9 2018 /etc/sensors/config/json.lst > > Copy to clipboard > > > 2. Ensure that `/etc/sensors/config/` directory contains the sensor JSON file with the required permissions. > > > > > > > > > > root@qcm6490:/etc/sensors/config# ls -l > > total 548 > > -rw-r--r--. 1 system system 1452 Mar 9 2018 json.lst > > -rw-r--r--. 1 system system 5638 Mar 9 2018 kodiak_ak991x_0.json > > -rw-r--r--. 1 system system 2837 Mar 9 2018 kodiak_bu52053nvx_0.json > > -rw-r--r--. 1 system system 5480 Mar 9 2018 kodiak_default_sensors.json > > -rw-r--r--. 1 system system 293 Mar 9 2018 kodiak_dynamic_sensors.json > > -rw-r--r--. 1 system system 392 Mar 9 2018 kodiak_idp_ak991x_0.json > > -rw-r--r--. 1 system system 384 Mar 9 2018 kodiak_idp_lsm6dst_0.json > > -rw-r--r--. 1 system system 384 Mar 9 2018 kodiak_idp_lsm6dst_1.json > > .. > > -rw-r--r--. 1 system system 302 Mar 9 2018 qcm6490_power_0.json > > -rw-r--r--. 1 system system 7952 Mar 9 2018 qcm6490_rbx_icm4x6xx_0.json > > -rw-r--r--. 1 system system 5922 Mar 9 2018 qcm6490_rbx_navmez_ak991x_0.json > > -rw-r--r--. 1 system system 7957 Mar 9 2018 qcm6490_rbx_navmez_icm4x6xx_0.json > > -rw-r--r--. 1 system system 7957 Mar 9 2018 qcm6490_rbx_navmez_rev2_icm4x6xx_0.json > > -rw-r--r--. 1 system system 3688 Mar 9 2018 qcm6490_rbx_navmezz_icp101xx_0.json > > Copy to clipboard > > > 3. Ensure that `` directory is accessible and contains the corresponding parsed file. > > > > > > > > > > root@qcm6490:/var/cache/sensors/registry/registry# ls -l > > total 524 > > -rw-r--r--. 1 system system 3 Jan 1 00:00 DIR > > -rw-r--r--. 1 system system 902 Apr 28 2022 qcm6490_default_sensors.json.default_sensors > > -rw-r--r--. 1 system system 86 Apr 28 2022 qcm6490_default_sensors.json.default_sensors.accel > > -rw-r--r--. 1 system system 133 Apr 28 2022 qcm6490_default_sensors.json.default_sensors.accel.attr_0 > > -rw-r--r--. 1 system system 90 Apr 28 2022 qcm6490_default_sensors.json.default_sensors.accel_cal > > .. > > -rw-r--r--. 1 system system 84 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.temp > > -rw-r--r--. 1 system system 232 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.temp.config > > -rw-r--r--. 1 system system 346 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform > > -rw-r--r--. 1 system system 95 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel > > -rw-r--r--. 1 system system 146 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal > > -rw-r--r--. 1 system system 183 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.bias > > -rw-r--r--. 1 system system 445 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.corr_mat > > -rw-r--r--. 1 system system 863 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.config > > Copy to clipboard ## SUID lookup failures This error indicates a custom code failure in retrieving SUID for a specified sensor. Do the following to resolve this error: > > > 1. Run the `ssc_sensor_info` tool to check if the specified sensor is available. > > > > > > > > > > - If the sensor list is empty, see the first debugging method described in [The ssc\_sensor\_info tool is unable to list sensors](https://docs.qualcomm.com/doc/80-70017-7/topic/debug.html#troubleshooting-ssc-sensor-info). > > - If only the specified sensor is unavailable, proceed with the following checks: > > > > > > > > > > > > > > > > > 1. Ensure that the sensor is listed in `/etc/sensors/config/json.lst` file, as shown in the following example: > > > > > > > > > > > > > > > > > > > > > > > > root@qcm6490:~# cat /etc/sensors/config/json.lst > > > > kodiak_ak991x_0.json > > > > qcm6490_default_sensors.json > > > > qcm6490_power_0.json > > > > qcm6490_rbx_icm4x6xx_0.json > > > > qcm6490_rbx_navmez_icm4x6xx_0.json > > > > qcm6490_rbx_navmezz_icp101xx_0.json > > > > qcm6490_rbx_navmez_ak991x_0.json > > > > Copy to clipboard > > > > > > > > > 2. Verify that the configuration file for the specified sensor is parsed and present in the `parsed_file_list.csv` file, as shown in the following example: > > > > > > > > > > > > > > > > > > > > > > > > root@qcm6490:/var/cache/sensors/registry# cat parsed_file_list.csv > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.config > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.orient > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal.corr_mat > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal.bias > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.corr_mat > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.bias > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal > > > > qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel > > > > Copy to clipboard > > > > > > > > > 3. Verify that the configuration file for the specified sensor is parsed and present in the `` directory, as shown in the following example: > > > > > > > > > > > > root@qcm6490:/var/cache/sensors/registry/registry# ls -l > > > total 524 > > > -rw-r--r--. 1 system system 248 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0 > > > -rw-r--r--. 1 system system 85 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.accel > > > -rw-r--r--. 1 system system 233 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.accel.config > > > -rw-r--r--. 1 system system 88 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.freefall > > > -rw-r--r--. 1 system system 236 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.freefall.config > > > -rw-r--r--. 1 system system 84 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.gyro > > > -rw-r--r--. 1 system system 232 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.gyro.config > > > -rw-r--r--. 1 system system 82 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.md > > > -rw-r--r--. 1 system system 230 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.md.config > > > -rw-r--r--. 1 system system 84 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.temp > > > -rw-r--r--. 1 system system 232 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0.temp.config > > > -rw-r--r--. 1 system system 346 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform > > > -rw-r--r--. 1 system system 95 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel > > > -rw-r--r--. 1 system system 146 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal > > > -rw-r--r--. 1 system system 183 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.bias > > > -rw-r--r--. 1 system system 445 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.accel.fac_cal.corr_mat > > > -rw-r--r--. 1 system system 863 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.config > > > -rw-r--r--. 1 system system 94 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro > > > -rw-r--r--. 1 system system 145 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal > > > -rw-r--r--. 1 system system 182 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal.bias > > > -rw-r--r--. 1 system system 444 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.gyro.fac_cal.corr_mat > > > -rw-r--r--. 1 system system 91 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.md > > > -rw-r--r--. 1 system system 192 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.md.config > > > -rw-r--r--. 1 system system 174 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.orient > > > -rw-r--r--. 1 system system 536 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.placement > > > -rw-r--r--. 1 system system 94 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.temp > > > -rw-r--r--. 1 system system 142 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.temp.fac_cal > > > -rw-r--r--. 1 system system 102 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.temp.fac_cal.bias > > > -rw-r--r--. 1 system system 103 Apr 28 2022 qcm6490_rbx_navmez_icm4x6xx_0.json.icm4x6xx_0_platform.temp.fac_cal.scale > > > Copy to clipboard > > > 2. If the preceding validations did not result in any anomalies, then there could be an issue with your own Apps side custom code implementation that uses the QSH client APIs. ## Sensor is listed but unable to receive sensor data This error indicates failure of the sample or custom code, or a sensor tool to receive events for a specified sensor. Do the following to resolve this error: > > > - Run the following command to stream the specified sensor: > - `see_workhorse [-sensor=][-sample_rate=] [-batch_period=] [-calibrated=<0 | 1>] [-wakeup=<0 | 1>]` > For example, > `see_workhorse -sensor=accel -sample_rate=max -duration=30 -display_events=1` See [Tools](https://docs.qualcomm.com/doc/80-70017-7/topic/test_tools.html#test-tools-54), for more information. Last Published: Dec 24, 2024 [Previous Topic Platform](https://docs.qualcomm.com/bundle/publicresource/80-70017-7/topics/platform.md) [Next Topic References](https://docs.qualcomm.com/bundle/publicresource/80-70017-7/topics/references.md)