Support Forum

hello everyone,

in the morning at 9:50 AM my board stops working (everything was fine bevor). Nothing special happend, no reboot, no system update, or something else...

I see the board on the console at address 0x18:

[root@1-wire ~]# i2cdetect -y 1     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f00:                         -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --                         

But my 1-wire server give up...

[root@1-wire ~]# owserver --foreground --i2c=/dev/i2c-1 --error_level=9  DEBUG: ow_daemon.c:(170) main thread id = 547805967488  DEBUG: ow_inotify.c:(80) No configuration files to monitorCONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found   CALL: ow_parsename.c:(174) path=[]  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters)  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0x7f8c45f1d0  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0x7f8c45f210  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0x7f8c45f250  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0x7f8c45f290  DEBUG: ow_regex.c:(24) Reg Ex expression <^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$> compiled to 0x7f8c45f2d0  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to 0x7f8c45f310]*$> compiled to 0x7f8c45f350Ex expression <^ *([^ ]+)[ ]*$> compiled to 0x7f8c45f390Ex expression <^ *([^ ]+) *: *([^ ]+)[ ]*$> compiled to 0x7f8c45f3d0Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^ ]+)[   DEBUG: ow_regex.c:(53) Not found  DEBUG: ow_regex.c:(53) Not found  DEBUG: ow_regex.c:(100) 0: 0->10 found <></dev/i2c-1><>  DEBUG: ow_regex.c:(100) 1: 0->10 found <></dev/i2c-1><>  DEBUG: ow_parse_address.c:(87) Text </dev/i2c-1>  DEBUG: ow_parse_address.c:(142) First </dev/i2c-1>CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18  DEBUG: ow_ds2482.c:(516) okCONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1ACONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1BCONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1CCONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1DCONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1ECONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be reset. Not a DS2482.CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1FCONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be reset. Not a DS2482.  DEBUG: ow_com_close.c:(42) Unimplemented!!!CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1DEFAULT: owlib.c:(52) No valid 1-wire buses found  DEBUG: ow_exit.c:(17) Exit code = 1   CALL: ow_lib_close.c:(21) Starting Library cleanup   CALL: ow_lib_stop.c:(22) Clear Cache  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.   CALL: ow_lib_stop.c:(24) Closing input devices   CALL: ow_lib_stop.c:(26) Closing output devices   CALL: ow_lib_close.c:(42) Finished Library cleanup  DEBUG: ow_lib_close.c:(50) Libraries closed

Is there any other way to check what happened or whether or not the board is working correctly?

[root@1-wire ~]# cat /boot/config.txt | grep dtparamdtparam=i2c_arm=on#dtparam=i2s=ondtparam=spi=offdtparam=audio=on[root@1-wire ~]# cat /boot/cmdline.txt console=tty1 root=PARTUUID=07a63d15-02 fsck.repair=yes rootwait dtparam=i2c_baudrate=400000[root@1-wire ~]# i2cdetect -li2c-20	i2c       	Broadcom STB :                  	I2C adapteri2c-1	i2c       	bcm2835 (i2c@7e804000)          	I2C adapteri2c-21	i2c       	Broadcom STB :                  	I2C adapter[root@1-wire ~]# raspi-config nonint get_i2c0

regards Lutz

OK, so I disconnected all cables from the board and reset all components and the Pi...
now everything seems to be working again...
but unfortunately I don't know what or why it happened...

Hello Lutz

If the board started working again after a reset it may have been a software bug in owfs or the i2c driver that caused the I2C bus to stop responding. Normally if it was a hardware fault the board would not appear on i2cdetect.

If it happens again try running "sudo apt-get update" and "sudo apt-get upgrade" to check for a newer version of owfs.