[prev in list] [next in list] [prev in thread] [next in thread]
List: owfs-developers
Subject: Re: [Owfs-developers] owserver don't detect the ds2482s-800 anymore
From: Colin Reese <colin.reese () gmail ! com>
Date: 2015-09-21 15:36:54
Message-ID: CA+e+J_N4jYnVVocYSLPJgPwxNrG6cwn4J29etco48KjCqOsuHQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I don't think this is it. The device shows up on the i2c bus. If device
tree was the problem, i2c-detect would yield nothing.
C
On Mon, Sep 21, 2015 at 8:34 AM, Jörgen Tegnér <jteg68@gmail.com> wrote:
> I had the same problem on raspberrypi this summer with the same or similar
> error messages. It turns out that there was a kernel change earlier that
> requires a boot parameter change.
>
> More information here
> https://www.raspberrypi.org/documentation/configuration/device-tree.md
>
> Worked for me.
>
> /Jörgen
>
> On Mon, Sep 21, 2015 at 11:43 AM, Nico Bouthoorn <nico@cuora.nl> wrote:
>
> > I've compile the 3.1 version which gives more debug information, looks
> > like broken
> >
> > root@bb01:/opt# /opt/owfs/bin/owserver --i2c=/dev/i2c-1:18 --debug
> > DEBUG MODE
> > libow version:
> > 3.1p0
> > DEBUG: ow_daemon.c:(170) main thread id = 3069607936
> > DEBUG: ow_inotify.c:(80) No configuration files to monitor
> > CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
> > isn't found
> > CALL: ow_parsename.c:(102) path=[]
> > DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
> > adapters)
> > CALL: ow_ds2482.c:(167) DS2482 bus address <18> invalid. Will search.
> > CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
> > DEBUG: ow_ds2482.c:(516) ok
> > CONNECT: 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 19
> > CONNECT: 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 1A
> > CONNECT: 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 1B
> > CONNECT: 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 1C
> > CONNECT: 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 1D
> > CONNECT: 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 1E
> > CONNECT: 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 1F
> > CONNECT: 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-1:18
> > DEFAULT: 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
> >
> >
> >
> > Nico Bouthoorn wrote:
> >
> >
> > I'm really puzzled, last night i've got a main power shortage. I'm running the \
> > owfs on a beaglebone (http://fstab.nl/beaglebone) with linux Debian This was \
> > working fine for years. Now the owserver don't detect the ds2482-800 device \
> > anymore. With /usr/sbin/i2cdetect -r 1 i can see still the device on the i2c bus \
> > (18): owfs version: 2.8p15-1
> >
> > /usr/sbin/i2cdetect -r 1
> > WARNING! This program can confuse your I2C bus, cause data loss and
> > worse! I will probe file /dev/i2c-1 using read byte commands. I will
> > probe address range 0x03-0x77. Continue? [Y/n] 0 1 2 3 4 5 6 7
> > 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- --
> > 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- -- 20: -- -- -- -- --
> > -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- --
> > -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: --
> > -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- --
> > -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I've a second BB
> > running this one is still working. Have anybody seen this before or is the
> > device broken? Thanks, Nico
> >
> > ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Owfs-developers mailing \
> > listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> > --
> > 0623391101
> >
> >
> >
> > ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
> >
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
[Attachment #5 (text/html)]
<div dir="ltr">I don't think this is it. The device shows up on the i2c bus. If \
device tree was the problem, i2c-detect would yield \
nothing.<div><br></div><div>C</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Sep 21, 2015 at 8:34 AM, Jörgen Tegnér <span \
dir="ltr"><<a href="mailto:jteg68@gmail.com" \
target="_blank">jteg68@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">I had the same problem on raspberrypi this \
summer with the same or similar error messages. It turns out that there was a kernel \
change earlier that requires a boot parameter change. <div><br></div><div>More \
information here</div><div><a \
href="https://www.raspberrypi.org/documentation/configuration/device-tree.md" \
target="_blank">https://www.raspberrypi.org/documentation/configuration/device-tree.md</a><br></div><div><br></div><div>Worked \
for me.</div><span class="HOEnZb"><font \
color="#888888"><div><br></div><div>/Jörgen</div></font></span></div><div \
class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div \
class="gmail_quote">On Mon, Sep 21, 2015 at 11:43 AM, Nico Bouthoorn <span \
dir="ltr"><<a href="mailto:nico@cuora.nl" \
target="_blank">nico@cuora.nl</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I've compile the 3.1 version which gives more debug information,
looks like broken<br>
<br>
<div>
<span style="font-family:monospace"><span \
style="color:#000000;background-color:#ffffff">root@bb01:/opt#
/opt/owfs/bin/owserver --i2c=/dev/i2c-1:18 --debug </span><br>
DEBUG MODE
<br>
libow version:
<br>
3.1p0
<br>
DEBUG: ow_daemon.c:(170) main thread id = <a href="tel:3069607936" \
value="+13069607936" target="_blank">3069607936</a> <br>
DEBUG: ow_inotify.c:(80) No configuration files to monitor
<br>
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since
dnssd library isn't found
<br>
CALL: ow_parsename.c:(102) path=[]
<br>
DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and
mock adapters)
<br>
CALL: ow_ds2482.c:(167) DS2482 bus address <18> invalid.
Will search.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 18
<br>
DEBUG: ow_ds2482.c:(516) ok
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 19
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1A
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1B
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1C
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1D
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1E
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E
cannot be reset. Not a DS2482.
<br>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1
address 1F
<br>
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F
cannot be reset. Not a DS2482.
<br>
DEBUG: ow_com_close.c:(42) Unimplemented!!!
<br>
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on
/dev/i2c-1:18
<br>
DEFAULT: owlib.c:(52) No valid 1-wire buses found
<br>
DEBUG: ow_exit.c:(17) Exit code = 1
<br>
CALL: ow_lib_close.c:(21) Starting Library cleanup
<br>
CALL: ow_lib_stop.c:(22) Clear Cache
<br>
DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out
data)
<br>
DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
<br>
DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out
data)
<br>
DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
<br>
CALL: ow_lib_stop.c:(24) Closing input devices
<br>
CALL: ow_lib_stop.c:(26) Closing output devices
<br>
CALL: ow_lib_close.c:(42) Finished Library cleanup
<br>
DEBUG: ow_lib_close.c:(50) Libraries closed<br>
<br>
</span></div>
<br>
<br>
<div>Nico Bouthoorn wrote:<br>
</div>
<blockquote type="cite"><div><div>
<br>
<pre cols="72">I'm really puzzled, last night i've got a main power \
shortage. I'm running the owfs on a beaglebone (<a \
href="http://fstab.nl/beaglebone" target="_blank">http://fstab.nl/beaglebone</a>) \
with linux Debian This was working fine for years. Now the owserver don't \
detect the ds2482-800 device anymore. With <span \
style="color:#000000;background-color:#ffffff"> /usr/sbin/i2cdetect -r 1 i can see \
still the device on the i2c bus (18): owfs version: </span><span \
style="font-family:monospace"><span \
style="color:#000000;background-color:#ffffff">2.8p15-1</span> </span></pre>
<pre cols="72"></pre><div>
<div>
<span style="font-family:monospace"><span \
style="color:#000000;background-color:#ffffff">/usr/sbin/i2cdetect -r 1</span> \
</span></div>
<div>
<span style="font-family:monospace"><span \
style="color:#000000;background-color:#ffffff">WARNING! This program can confuse your \
I2C bus, cause data loss and worse! </span>
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
I've a second BB running this one is still working.
Have anybody seen this before or is the device broken?
Thanks,
Nico
</span></div>
</div>
<pre cols="72"></pre>
<fieldset></fieldset>
</div></div><pre>------------------------------------------------------------------------------
</pre><span>
<fieldset></fieldset>
<pre>_______________________________________________
Owfs-developers mailing list
<a href="mailto:Owfs-developers@lists.sourceforge.net" \
target="_blank">Owfs-developers@lists.sourceforge.net</a> <a \
href="https://lists.sourceforge.net/lists/listinfo/owfs-developers" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/owfs-developers</a> \
</pre>
</span></blockquote><span><font color="#888888">
<pre cols="72">--
0623391101</pre></font></span></div><br>------------------------------------------------------------------------------<br>
<br>_______________________________________________<br>
Owfs-developers mailing list<br>
<a href="mailto:Owfs-developers@lists.sourceforge.net" \
target="_blank">Owfs-developers@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/owfs-developers" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/owfs-developers</a><br> \
<br></blockquote></div><br></div> \
</div></div><br>------------------------------------------------------------------------------<br>
<br>_______________________________________________<br>
Owfs-developers mailing list<br>
<a href="mailto:Owfs-developers@lists.sourceforge.net">Owfs-developers@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/owfs-developers" \
rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/owfs-developers</a><br>
<br></blockquote></div><br></div>
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic