ADC not responsive error

ETHZ-TEC / RocketLogger

Official development repository of the RocketLogger project.

https://github.com/ETHZ-TEC/RocketLogger/wiki

BSD 3-Clause "New" or "Revised" License

14 stars 4 forks source link

ADC not responsive error #36

Closed rdaforno closed 2 years ago

rdaforno commented 2 years ago

After a system update (apt-get dist-upgrade), the RocketLogger daemon does not start properly. Error message: ADC not responsive. By adding an additional delay of ~10 seconds here at the end, the problem seems to disappear.

This happens with the flocklab branch. Not sure whether this problem is specific to Debian 9.

Fix added to branch flocklab.

lsigrist commented 2 years ago

This problem is not confirmed for the official 2.0.0 release from master branch.
Reproduced when using unofficial debian9-backports image based derived from 46f12e3
The linked workaround is not confirmed to be effective for debian9-backports image

The ADC not responsive error typically refers to a PWM configuration issue that leads to unavailable ADC clock signal. This seems to be confirmed in this case by the fact that the PWM modules were unavailable (or remapped) after performing a dist-upgrade.

rdaforno commented 2 years ago

PWM mapping is not the issue here. The RocketLogger service starts too early, hence the additional delay. Alternatively, a manual restart of the RL service also resolves the error.

lsigrist commented 2 years ago

Closing the issue as not reproduced with any official release. The here described problem hinted at a different issues #50 in case of service start up problems, blocking automatic restart in case of start up problems.