{"id":28721,"date":"2021-07-12T18:41:01","date_gmt":"2021-07-12T16:41:01","guid":{"rendered":"https:\/\/pi3g.com\/?p=28721"},"modified":"2021-07-12T18:41:01","modified_gmt":"2021-07-12T16:41:01","slug":"raspi-config-nonint-do_i2c-1-hangs-forever","status":"publish","type":"post","link":"https:\/\/pi3g.com\/de\/raspi-config-nonint-do_i2c-1-hangs-forever\/","title":{"rendered":"raspi-config nonint do_i2c 1 h\u00e4ngt \"f\u00fcr immer\""},"content":{"rendered":"

While developing PiCockpit<\/a>, and trying to allow the user to turn I2C off from the webinterface, I have run into crashes and problems.<\/p>\n

I am using raspi-config in non-interactive mode (I\u2019ve written about this before)<\/a> to control I2C from the PiCockpit client. <\/p>\n

While debugging the issue, I noted that \u2013 if something was busy accessing the I2C bus, the command (raspi-config) would freeze.<\/p>\n

Investigating with ps aux, I noticed that another command had been started but did not finish to execute:<\/p>\n

\n

dtparam i2c_arm=off<\/p>\n<\/blockquote>\n

This is a compiled binary, no script. But it has a verbose mode.<\/p>\n

running this manually, in verbose mode, while something else would be accessing the I2C bus:<\/p>\n

\n

17:32:55 root@Avalon:\/home\/pi # dtparam -v i2c_arm=off<\/strong><\/p>\n

DTOVERLAY[debug]: using platform ‘bcm2711’<\/em><\/p>\n

DTOVERLAY[debug]: overlay map loaded<\/em><\/p>\n

run_cmd: which dtoverlay-pre >\/dev\/null 2>&1 && dtoverlay-pre<\/em><\/p>\n

run_cmd: dtc -I fs -O dtb -o ‘\/tmp\/.dtoverlays\/base.dtb’ \/proc\/device-tree 1>\/dev\/null 2>&1<\/em><\/p>\n

DTOVERLAY[debug]: loading file ‘\/tmp\/.dtoverlays\/base.dtb’<\/em><\/p>\n

DTOVERLAY[debug]: found override i2c_arm<\/em><\/p>\n

DTOVERLAY[debug]: override i2c_arm: string target ‘status’<\/em><\/p>\n

DTOVERLAY[debug]: wrote 166 bytes to ‘\/tmp\/.dtoverlays\/69_dtparam.dtbo’<\/em><\/p>\n

DTOVERLAY[debug]: wrote 179 bytes to ‘\/sys\/kernel\/config\/device-tree\/overlays\/69_dtparam\/dtbo’<\/em><\/p>\n

run_cmd: which dtoverlay-post >\/dev\/null 2>&1 && dtoverlay-post<\/em><\/font><\/p>\n<\/blockquote>\n

would hang before <\/strong>the last command (highlighted in yellow). <\/p>\n

Once the other application had released the I2C bus, dtparam would finish it\u2019s job and show the last line. <\/p>\n

<\/p>\n

How can you find out which applications are accessing the i2c bus?<\/p>\n

Easily, with lsof:<\/p>\n

\n

sudo lsof \/dev\/i2c-1<\/strong><\/p>\n

lsof: WARNING: can’t stat() fuse.gvfsd-fuse file system \/run\/user\/1000\/gvfs
       Output information may be incomplete.
\nCOMMAND   PID USER   FD   TYPE DEVICE SIZE\/OFF   NODE NAME
\npython3 24772 root   13u   CHR   89,1      0t0 285423 \/dev\/i2c-1<\/em>\n<\/p>\n<\/blockquote>\n

\"image\"<\/a><\/p>\n

in my case depending on the activity of the two apps (CO2 and BME688), the file could be open two times as well:<\/p>\n

\"image\"<\/a><\/p>\n

My recommendation is, since there does not seem to be a workaround for dtparam hanging (and thus raspi-config hanging) when I2C is being accessed \/ open, to check the state of the file descriptors first, and show the user an error message if this is the case (that they will need to disable the applications first for this to work). <\/p>\n

<\/p>\n

NB: for Python\u2019s SMBus, you can simply use bus.close()<\/strong> (if you called your SMBus instance bus)<\/p>\n","protected":false},"excerpt":{"rendered":"

Bei der Entwicklung von PiCockpit und dem Versuch, dem Benutzer die M\u00f6glichkeit zu geben, I2C \u00fcber das Webinterface auszuschalten, bin ich auf Abst\u00fcrze und Probleme gesto\u00dfen. Ich verwende raspi-config im nicht-interaktiven Modus (dar\u00fcber habe ich schon einmal geschrieben), um I2C vom PiCockpit Client aus zu steuern. Beim Debuggen des Problems habe ich festgestellt, dass - wenn etwas mit dem Zugriff auf...<\/p>","protected":false},"author":830,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[400],"tags":[965,955,964],"class_list":["post-28721","post","type-post","status-publish","format-standard","hentry","category-raspberry-pi-embedded-development","tag-dtoverlay","tag-i2c","tag-raspi-config"],"_links":{"self":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/28721","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/users\/830"}],"replies":[{"embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/comments?post=28721"}],"version-history":[{"count":1,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/28721\/revisions"}],"predecessor-version":[{"id":28722,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/posts\/28721\/revisions\/28722"}],"wp:attachment":[{"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/media?parent=28721"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/categories?post=28721"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pi3g.com\/de\/wp-json\/wp\/v2\/tags?post=28721"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}