Problem with compiling of the owfs on a raspberry pi

classic Classic list List threaded Threaded
35 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Problem with compiling of the owfs on a raspberry pi

Ritchie
Dear all,

I am trying to compile the actual version (owfs-3.1p5) of owfs on a
raspberry pi and get the following error message during "make".

owusbprobe.o: In function `list_usb_devices_iter':
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined
reference to `libusb_strerror'
owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182:
more undefined references to `libusb_strerror' follow


Configure shows the following configuration at the end:

Current configuration:

     Deployment location: /opt/owfs

Compile-time options:
                       USB is enabled
                     AVAHI is enabled
                       I2C is enabled
                        W1 is enabled
     Parallel port DS1410E is enabled
            FTDI (LinkUSB) is DISABLED
          Zeroconf/Bonjour is enabled
              Debug-output is enabled
                Mutexdebug is enabled
                 Profiling is DISABLED
Tracing memory allocation is DISABLED

Module configuration:
                     owlib is enabled
                   owshell is enabled
                      owfs is enabled
                   owhttpd is enabled
                    owftpd is enabled
                  owserver is enabled
                owexternal is enabled
                     ownet is enabled
                  ownetlib is enabled
                     owtap is enabled
                     owmon is enabled
                    owcapi is enabled
                      swig is enabled
                    owperl is enabled
                     owphp is DISABLED
                  owpython is enabled
                     owtcl is enabled

               unit tests are DISABLED

is this a problem ?
 >checking if libftdi is available... auto (default)
 >configure: WARNING: libftdi not found, LinkUSB native will be disabled

I still have done:

apt-get update
apt-get upgrade
apt-get dist-update


Any Idea what is missing ?

Best regards
R.




------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with compiling of the owfs on a raspberry pi

Johan Ström-3
Sounds like libusb is not found, but the include is there..
Try a search in the archives if you have not yet done so, I think this has been up before.

Johan

On January 9, 2017 6:55:27 PM GMT+01:00, Ritchie <[hidden email]> wrote:
Dear all,

I am trying to compile the actual version (owfs-3.1p5) of owfs on a
raspberry pi and get the following error message during "make".

owusbprobe.o: In function `list_usb_devices_iter':
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined
reference to `libusb_strerror'
owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182:
more undefined references to `libusb_strerror' follow


Configure shows the following configuration at the end:

Current configuration:

Deployment location: /opt/owfs

Compile-time options:
USB is enabled
AVAHI is enabled
I2C is enabled
W1 is enabled
Parallel port DS1410E is enabled
FTDI (LinkUSB) is DISABLED
Zeroconf/Bonjour is enabled
Debug-output is enabled
Mutexdebug is enabled
Profiling is DISABLED
Tracing memory allocation is DISABLED

Module configuration:
owlib is enabled
owshell is enabled
owfs is enabled
owhttpd is enabled
owftpd is enabled
owserver is enabled
owexternal is enabled
ownet is enabled
ownetlib is enabled
owtap is enabled
owmon is enabled
owcapi is enabled
swig is enabled
owperl is enabled
owphp is DISABLED
owpython is enabled
owtcl is enabled

unit tests are DISABLED

is this a problem ?
checking if libftdi is available... auto (default)
configure: WARNING: libftdi not found, LinkUSB native will be disabled

I still have done:

apt-get update
apt-get upgrade
apt-get dist-update


Any Idea what is missing ?

Best regards
R.






Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi


Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with compiling of the owfs on a raspberry pi

Mick Sulley

I think it is libusb-dev that is missing.

But do you really need 3.1p5  as you can easily get 3.1p4 from the repro using the notes that Jan kindly provided -

Edit (or create) your /etc/apt/preferences to contain:
--------------------------------------------------------------------------
Package: *
Pin: release o=Raspbian,a=stable
Pin-Priority: 500

Package: *
Pin: release o=Raspbian,a=testing
Pin-Priority: 300
--------------------------------------------------------------------------
This is important so you keep stable (Jessie) for all packages but the ones
explicitly taken from testing (Stretch).

Then, add a line
--------------------------------------------------------------------------
deb http://mirrordirector.raspbian.org/raspbian/ testing main contrib non-free rpi
--------------------------------------------------------------------------
to your /etc/apt/sources.list to get access to the Raspbian testing repository.

Do an

$ sudo apt-get update

to read the package metadata, then check

$ sudo apt-cache policy

whether the testing repo is there with priority 300. Then

$ sudo apt-get install -t testing owserver owhttpd ow-shell

That should install all you need, including the startup files and systemd units.
Note you have to edit /etc/owfs.conf again to contain (this and only this)
--------------------------------------------------------------------------
!server: server = localhost:4304
server: device=/dev/i2c-1
--------------------------------------------------------------------------
Restart the owserver and owhttpd service after that.




On 09/01/17 18:51, Johan Ström wrote:
Sounds like libusb is not found, but the include is there..
Try a search in the archives if you have not yet done so, I think this has been up before.

Johan

On January 9, 2017 6:55:27 PM GMT+01:00, Ritchie [hidden email] wrote:
Dear all,

I am trying to compile the actual version (owfs-3.1p5) of owfs on a 
raspberry pi and get the following error message during "make".

owusbprobe.o: In function `list_usb_devices_iter':
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined 
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined 
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined 
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined 
reference to `libusb_strerror'
/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined 
reference to `libusb_strerror'
owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182: 
more undefined references to `libusb_strerror' follow


Configure shows the following configuration at the end:

Current configuration:

     Deployment location: /opt/owfs

Compile-time options:
                       USB is enabled
                     AVAHI is enabled
                       I2C is enabled
                        W1 is enabled
     Parallel port DS1410E is enabled
            FTDI (LinkUSB) is DISABLED
          Zeroconf/Bonjour is enabled
              Debug-output is enabled
                Mutexdebug is enabled
                 Profiling is DISABLED
Tracing memory allocation is DISABLED

Module configuration:
                     owlib is enabled
                   owshell is enabled
                      owfs is enabled
                   owhttpd is enabled
                    owftpd is enabled
                  owserver is enabled
                owexternal is enabled
                     ownet is enabled
                  ownetlib is enabled
                     owtap is enabled
                     owmon is enabled
                    owcapi is enabled
                      swig is enabled
                    owperl is enabled
                     owphp is DISABLED
                  owpython is enabled
                     owtcl is enabled

               unit tests are DISABLED

is this a problem ?
checking if libftdi is available... auto (default) configure: WARNING: libftdi not found, LinkUSB native will be disabled
I still have done: apt-get update apt-get upgrade apt-get dist-update Any Idea what is missing ? Best regards R.
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi
Owfs-developers mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/owfs-developers
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with compiling of the owfs on a raspberry pi

Ritchie
Dear Sulley,

the usblib-dev is already installed:

sudo apt-get install libusb-1.0.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libusb-1.0-0-dev' for regex 'libusb-1.0.0-dev'
libusb-1.0-0-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I need the version to modify the source code in this way, that I
can see the traffic of the 1-wire bus.

Best regards
R.



Am 09.01.2017 um 23:29 schrieb Mick Sulley:

> I think it is libusb-dev that is missing.
>
> But do you really need 3.1p5  as you can easily get 3.1p4 from the repro
> using the notes that Jan kindly provided -
>
> Edit (or create) your /etc/apt/preferences to contain:
> --------------------------------------------------------------------------
> Package: *
> Pin: release o=Raspbian,a=stable
> Pin-Priority: 500
>
> Package: *
> Pin: release o=Raspbian,a=testing
> Pin-Priority: 300
> --------------------------------------------------------------------------
> This is important so you keep stable (Jessie) for all packages but the ones
> explicitly taken from testing (Stretch).
>
> Then, add a line
> --------------------------------------------------------------------------
> deb http://mirrordirector.raspbian.org/raspbian/ testing main contrib
> non-free rpi
> --------------------------------------------------------------------------
> to your /etc/apt/sources.list to get access to the Raspbian testing
> repository.
>
> Do an
>
> $ sudo apt-get update
>
> to read the package metadata, then check
>
> $ sudo apt-cache policy
>
> whether the testing repo is there with priority 300. Then
>
> $ sudo apt-get install -t testing owserver owhttpd ow-shell
>
> That should install all you need, including the startup files and
> systemd units.
> Note you have to edit /etc/owfs.conf again to contain (this and only this)
> --------------------------------------------------------------------------
> !server: server = localhost:4304
> server: device=/dev/i2c-1
> --------------------------------------------------------------------------
> Restart the owserver and owhttpd service after that.
>
>
>
>
> On 09/01/17 18:51, Johan Ström wrote:
>> Sounds like libusb is not found, but the include is there..
>> Try a search in the archives if you have not yet done so, I think this
>> has been up before.
>>
>> Johan
>>
>> On January 9, 2017 6:55:27 PM GMT+01:00, Ritchie <[hidden email]> wrote:
>>
>>     Dear all,
>>
>>     I am trying to compile the actual version (owfs-3.1p5) of owfs on a
>>     raspberry pi and get the following error message during "make".
>>
>>     owusbprobe.o: In function `list_usb_devices_iter':
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined
>>     reference to `libusb_strerror'
>>     owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182:
>>     more undefined references to `libusb_strerror' follow
>>
>>
>>     Configure shows the following configuration at the end:
>>
>>     Current configuration:
>>
>>          Deployment location: /opt/owfs
>>
>>     Compile-time options:
>>                            USB is enabled
>>                          AVAHI is enabled
>>                            I2C is enabled
>>                             W1 is enabled
>>          Parallel port DS1410E is enabled
>>                 FTDI (LinkUSB) is DISABLED
>>               Zeroconf/Bonjour is enabled
>>                   Debug-output is enabled
>>                     Mutexdebug is enabled
>>                      Profiling is DISABLED
>>     Tracing memory allocation is DISABLED
>>
>>     Module configuration:
>>                          owlib is enabled
>>                        owshell is enabled
>>                           owfs is enabled
>>                        owhttpd is enabled
>>                         owftpd is enabled
>>                       owserver is enabled
>>                     owexternal is enabled
>>                          ownet is enabled
>>                       ownetlib is enabled
>>                          owtap is enabled
>>                          owmon is enabled
>>                         owcapi is enabled
>>                           swig is enabled
>>                         owperl is enabled
>>                          owphp is DISABLED
>>                       owpython is enabled
>>                          owtcl is enabled
>>
>>                    unit tests are DISABLED
>>
>>     is this a problem ?
>>
>>         checking if libftdi is available... auto (default) configure:
>>         WARNING: libftdi not found, LinkUSB native will be disabled
>>
>>
>>     I still have done:
>>
>>     apt-get update
>>     apt-get upgrade
>>     apt-get dist-update
>>
>>
>>     Any Idea what is missing ?
>>
>>     Best regards
>>     R.
>>
>>
>>
>>
>>     ------------------------------------------------------------------------
>>
>>     Developer Access Program for Intel Xeon Phi Processors
>>     Access to Intel Xeon Phi processor-based developer platforms.
>>     With one year of Intel Parallel Studio XE.
>>     Training and support from Colfax.
>>     Order your platform today. http://sdm.link/xeonphi
>>     ------------------------------------------------------------------------
>>
>>     Owfs-developers mailing list
>>     [hidden email]
>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>>
>> _______________________________________________
>> Owfs-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with compiling of the owfs on a raspberry pi

Ritchie
In reply to this post by Mick Sulley
Dear Johan,

I guess this is the answer. I does not work on raspberry pi.

https://sourceforge.net/p/owfs/mailman/message/35268610/

Best regards

R.


> I think it is libusb-dev that is missing.
>
> But do you really need 3.1p5  as you can easily get 3.1p4 from the repro
> using the notes that Jan kindly provided -
>
> Edit (or create) your /etc/apt/preferences to contain:
> --------------------------------------------------------------------------
> Package: *
> Pin: release o=Raspbian,a=stable
> Pin-Priority: 500
>
> Package: *
> Pin: release o=Raspbian,a=testing
> Pin-Priority: 300
> --------------------------------------------------------------------------
> This is important so you keep stable (Jessie) for all packages but the ones
> explicitly taken from testing (Stretch).
>
> Then, add a line
> --------------------------------------------------------------------------
> deb http://mirrordirector.raspbian.org/raspbian/ testing main contrib
> non-free rpi
> --------------------------------------------------------------------------
> to your /etc/apt/sources.list to get access to the Raspbian testing
> repository.
>
> Do an
>
> $ sudo apt-get update
>
> to read the package metadata, then check
>
> $ sudo apt-cache policy
>
> whether the testing repo is there with priority 300. Then
>
> $ sudo apt-get install -t testing owserver owhttpd ow-shell
>
> That should install all you need, including the startup files and
> systemd units.
> Note you have to edit /etc/owfs.conf again to contain (this and only this)
> --------------------------------------------------------------------------
> !server: server = localhost:4304
> server: device=/dev/i2c-1
> --------------------------------------------------------------------------
> Restart the owserver and owhttpd service after that.
>
>
>
>
> On 09/01/17 18:51, Johan Ström wrote:
>> Sounds like libusb is not found, but the include is there..
>> Try a search in the archives if you have not yet done so, I think this
>> has been up before.
>>
>> Johan
>>
>> On January 9, 2017 6:55:27 PM GMT+01:00, Ritchie <[hidden email]> wrote:
>>
>>     Dear all,
>>
>>     I am trying to compile the actual version (owfs-3.1p5) of owfs on a
>>     raspberry pi and get the following error message during "make".
>>
>>     owusbprobe.o: In function `list_usb_devices_iter':
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined
>>     reference to `libusb_strerror'
>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined
>>     reference to `libusb_strerror'
>>     owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182:
>>     more undefined references to `libusb_strerror' follow
>>
>>
>>     Configure shows the following configuration at the end:
>>
>>     Current configuration:
>>
>>          Deployment location: /opt/owfs
>>
>>     Compile-time options:
>>                            USB is enabled
>>                          AVAHI is enabled
>>                            I2C is enabled
>>                             W1 is enabled
>>          Parallel port DS1410E is enabled
>>                 FTDI (LinkUSB) is DISABLED
>>               Zeroconf/Bonjour is enabled
>>                   Debug-output is enabled
>>                     Mutexdebug is enabled
>>                      Profiling is DISABLED
>>     Tracing memory allocation is DISABLED
>>
>>     Module configuration:
>>                          owlib is enabled
>>                        owshell is enabled
>>                           owfs is enabled
>>                        owhttpd is enabled
>>                         owftpd is enabled
>>                       owserver is enabled
>>                     owexternal is enabled
>>                          ownet is enabled
>>                       ownetlib is enabled
>>                          owtap is enabled
>>                          owmon is enabled
>>                         owcapi is enabled
>>                           swig is enabled
>>                         owperl is enabled
>>                          owphp is DISABLED
>>                       owpython is enabled
>>                          owtcl is enabled
>>
>>                    unit tests are DISABLED
>>
>>     is this a problem ?
>>
>>         checking if libftdi is available... auto (default) configure:
>>         WARNING: libftdi not found, LinkUSB native will be disabled
>>
>>
>>     I still have done:
>>
>>     apt-get update
>>     apt-get upgrade
>>     apt-get dist-update
>>
>>
>>     Any Idea what is missing ?
>>
>>     Best regards
>>     R.
>>
>>
>>
>>
>>     ------------------------------------------------------------------------
>>
>>     Developer Access Program for Intel Xeon Phi Processors
>>     Access to Intel Xeon Phi processor-based developer platforms.
>>     With one year of Intel Parallel Studio XE.
>>     Training and support from Colfax.
>>     Order your platform today. http://sdm.link/xeonphi
>>     ------------------------------------------------------------------------
>>
>>     Owfs-developers mailing list
>>     [hidden email]
>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>>
>> _______________________________________________
>> Owfs-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with compiling of the owfs on a raspberry pi

Colin Law
In reply to this post by Ritchie
On 10 January 2017 at 17:09, Ritchie <[hidden email]> wrote:
> Dear Sulley,
>
> the usblib-dev is already installed:
>
> sudo apt-get install libusb-1.0.0-dev

Try
sudo apt-get install libusb-dev

Colin

> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'libusb-1.0-0-dev' for regex 'libusb-1.0.0-dev'
> libusb-1.0-0-dev is already the newest version.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> I need the version to modify the source code in this way, that I
> can see the traffic of the 1-wire bus.
>
> Best regards
> R.
>
>
>
> Am 09.01.2017 um 23:29 schrieb Mick Sulley:
>> I think it is libusb-dev that is missing.
>>
>> But do you really need 3.1p5  as you can easily get 3.1p4 from the repro
>> using the notes that Jan kindly provided -
>>
>> Edit (or create) your /etc/apt/preferences to contain:
>> --------------------------------------------------------------------------
>> Package: *
>> Pin: release o=Raspbian,a=stable
>> Pin-Priority: 500
>>
>> Package: *
>> Pin: release o=Raspbian,a=testing
>> Pin-Priority: 300
>> --------------------------------------------------------------------------
>> This is important so you keep stable (Jessie) for all packages but the ones
>> explicitly taken from testing (Stretch).
>>
>> Then, add a line
>> --------------------------------------------------------------------------
>> deb http://mirrordirector.raspbian.org/raspbian/ testing main contrib
>> non-free rpi
>> --------------------------------------------------------------------------
>> to your /etc/apt/sources.list to get access to the Raspbian testing
>> repository.
>>
>> Do an
>>
>> $ sudo apt-get update
>>
>> to read the package metadata, then check
>>
>> $ sudo apt-cache policy
>>
>> whether the testing repo is there with priority 300. Then
>>
>> $ sudo apt-get install -t testing owserver owhttpd ow-shell
>>
>> That should install all you need, including the startup files and
>> systemd units.
>> Note you have to edit /etc/owfs.conf again to contain (this and only this)
>> --------------------------------------------------------------------------
>> !server: server = localhost:4304
>> server: device=/dev/i2c-1
>> --------------------------------------------------------------------------
>> Restart the owserver and owhttpd service after that.
>>
>>
>>
>>
>> On 09/01/17 18:51, Johan Ström wrote:
>>> Sounds like libusb is not found, but the include is there..
>>> Try a search in the archives if you have not yet done so, I think this
>>> has been up before.
>>>
>>> Johan
>>>
>>> On January 9, 2017 6:55:27 PM GMT+01:00, Ritchie <[hidden email]> wrote:
>>>
>>>     Dear all,
>>>
>>>     I am trying to compile the actual version (owfs-3.1p5) of owfs on a
>>>     raspberry pi and get the following error message during "make".
>>>
>>>     owusbprobe.o: In function `list_usb_devices_iter':
>>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:149: undefined
>>>     reference to `libusb_strerror'
>>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:159: undefined
>>>     reference to `libusb_strerror'
>>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:154: undefined
>>>     reference to `libusb_strerror'
>>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:132: undefined
>>>     reference to `libusb_strerror'
>>>     /usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:135: undefined
>>>     reference to `libusb_strerror'
>>>     owusbprobe.o:/usr/src/owfs-3.1p5/module/owshell/src/c/owusbprobe.c:182:
>>>     more undefined references to `libusb_strerror' follow
>>>
>>>
>>>     Configure shows the following configuration at the end:
>>>
>>>     Current configuration:
>>>
>>>          Deployment location: /opt/owfs
>>>
>>>     Compile-time options:
>>>                            USB is enabled
>>>                          AVAHI is enabled
>>>                            I2C is enabled
>>>                             W1 is enabled
>>>          Parallel port DS1410E is enabled
>>>                 FTDI (LinkUSB) is DISABLED
>>>               Zeroconf/Bonjour is enabled
>>>                   Debug-output is enabled
>>>                     Mutexdebug is enabled
>>>                      Profiling is DISABLED
>>>     Tracing memory allocation is DISABLED
>>>
>>>     Module configuration:
>>>                          owlib is enabled
>>>                        owshell is enabled
>>>                           owfs is enabled
>>>                        owhttpd is enabled
>>>                         owftpd is enabled
>>>                       owserver is enabled
>>>                     owexternal is enabled
>>>                          ownet is enabled
>>>                       ownetlib is enabled
>>>                          owtap is enabled
>>>                          owmon is enabled
>>>                         owcapi is enabled
>>>                           swig is enabled
>>>                         owperl is enabled
>>>                          owphp is DISABLED
>>>                       owpython is enabled
>>>                          owtcl is enabled
>>>
>>>                    unit tests are DISABLED
>>>
>>>     is this a problem ?
>>>
>>>         checking if libftdi is available... auto (default) configure:
>>>         WARNING: libftdi not found, LinkUSB native will be disabled
>>>
>>>
>>>     I still have done:
>>>
>>>     apt-get update
>>>     apt-get upgrade
>>>     apt-get dist-update
>>>
>>>
>>>     Any Idea what is missing ?
>>>
>>>     Best regards
>>>     R.
>>>
>>>
>>>
>>>
>>>     ------------------------------------------------------------------------
>>>
>>>     Developer Access Program for Intel Xeon Phi Processors
>>>     Access to Intel Xeon Phi processor-based developer platforms.
>>>     With one year of Intel Parallel Studio XE.
>>>     Training and support from Colfax.
>>>     Order your platform today. http://sdm.link/xeonphi
>>>     ------------------------------------------------------------------------
>>>
>>>     Owfs-developers mailing list
>>>     [hidden email]
>>>     https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>>
>>> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>>>
>>> ------------------------------------------------------------------------------
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>>
>>> _______________________________________________
>>> Owfs-developers mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>>
>>
>>
>> _______________________________________________
>> Owfs-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Ritchie
In reply to this post by Ritchie
Hi all,

since I tried the actual version on my raspi, I damaged the installation.

The owserver version 2.8 does not start.

I compiled the version 2.9p5, which should the be one of the latest
version (may 3.0.. as well), which is running on the raspi, so far I
could see in the internet.

Now I try to get my system back t run and get the following message.


/usr/src $ sudo /opt/owfs/bin/owserver --foreground --debug
--error_print=2 --error_level=9 -c /etc/owfs.conf
DEBUG MODE
libow version:
         2.9p5
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:1) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:2) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:3) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:4) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:5) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:6) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:7) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:8) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:9) Program=,
Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:10)
Program=Not server, Option=server, Value=localhost:4304
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:11)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:12)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:13)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:14)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:15)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:16)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:17)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:18)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:19)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:20)
Program=server, Option=device, Value=/dev/ttyUSB0
   DEBUG: ow_opt.c:(335) Configuration file (/etc/owfs.conf:20) Option
device recognized as device. Value=/dev/ttyUSB0
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:21)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:22)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:23)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:24)
Program=http, Option=port, Value=2121
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:25)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:26)
Program=ftp, Option=port, Value=2120
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:27)
Program=, Option=, Value=
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:28)
Program=server, Option=port, Value=localhost:4304
   DEBUG: ow_opt.c:(335) Configuration file (/etc/owfs.conf:28) Option
port recognized as port. Value=localhost:4304
   DEBUG: ow_opt.c:(290) Configuration file (/etc/owfs.conf:29)
Program=, Option=, Value=
   DEBUG: ow_daemon.c:(166) main thread id = 3070153232
   DEBUG: ow_avahi_link.c:(71) Avahi support: libavahi-client loaded
successfully
   DEBUG: ow_avahi_link.c:(73) Avahi library function found:
avahi_client_errno
   DEBUG: ow_avahi_link.c:(74) Avahi library function found:
avahi_client_free
   DEBUG: ow_avahi_link.c:(75) Avahi library function found:
avahi_client_new
   DEBUG: ow_avahi_link.c:(76) Avahi library function found:
avahi_client_get_domain_name
   DEBUG: ow_avahi_link.c:(77) Avahi library function found:
avahi_entry_group_add_service
   DEBUG: ow_avahi_link.c:(78) Avahi library function found:
avahi_entry_group_commit
   DEBUG: ow_avahi_link.c:(79) Avahi library function found:
avahi_entry_group_is_empty
   DEBUG: ow_avahi_link.c:(80) Avahi library function found:
avahi_entry_group_new
   DEBUG: ow_avahi_link.c:(81) Avahi library function found:
avahi_entry_group_reset
   DEBUG: ow_avahi_link.c:(83) Avahi library function found:
avahi_service_resolver_free
   DEBUG: ow_avahi_link.c:(84) Avahi library function found:
avahi_service_resolver_new
   DEBUG: ow_avahi_link.c:(85) Avahi library function found:
avahi_service_browser_free
   DEBUG: ow_avahi_link.c:(86) Avahi library function found:
avahi_service_browser_new
   DEBUG: ow_avahi_link.c:(98) Avahi support: libavahi-common loaded
successfully.
   DEBUG: ow_avahi_link.c:(100) Avahi library function found:
avahi_simple_poll_free
   DEBUG: ow_avahi_link.c:(101) Avahi library function found:
avahi_simple_poll_get
   DEBUG: ow_avahi_link.c:(102) Avahi library function found:
avahi_simple_poll_loop
   DEBUG: ow_avahi_link.c:(103) Avahi library function found:
avahi_simple_poll_new
   DEBUG: ow_avahi_link.c:(104) Avahi library function found:
avahi_simple_poll_quit
   DEBUG: ow_avahi_link.c:(105) Avahi library function found: avahi_strerror
    CALL: ow_parsename.c:(102) path=[]
   DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters)
   DEBUG: ow_ds9097U.c:(287) Attempt 0 of 3 to initialize the DS9097U
   DEBUG: ow_ds9097U.c:(381) Send the initial reset to the bus master.
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1
   DEBUG: ow_tcp_read.c:(64) attempt 1 bytes Time: 5.000000 seconds
   DEBUG: ow_tcp_read.c:(114) read: 1 - 0 = 1


How can i make sure that all libs and programs are corrct installed.
Configure runs proper and compiling was also not problem. But the
server does not run. Even the one how was delived from raspberry.

Thanks for any help

R.









------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Jan Kandziora
Am 11.01.2017 um 18:38 schrieb Ritchie:
>
> /usr/src $ sudo /opt/owfs/bin/owserver --foreground --debug
> --error_print=2 --error_level=9 -c /etc/owfs.conf
>
We need /etc/owfs.conf and a list which owfs services you run in
parallel to help you.

Kind regards

        Jan

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Ritchie
Dear Jan,

I just decide to reinstall the system new, which is easier than try to
fix it.

Best regards
R.

> Am 11.01.2017 um 18:38 schrieb Ritchie:
>>
>> /usr/src $ sudo /opt/owfs/bin/owserver --foreground --debug
>> --error_print=2 --error_level=9 -c /etc/owfs.conf
>>
> We need /etc/owfs.conf and a list which owfs services you run in
> parallel to help you.
>
> Kind regards
>
> Jan
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Colin Law
On 12 January 2017 at 16:29, Ritchie <[hidden email]> wrote:
> Dear Jan,
>
> I just decide to reinstall the system new, which is easier than try to
> fix it.

Install owfs from the 'testing' repository using the technique in
https://sourceforge.net/p/owfs/mailman/message/35357871/

Colin

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Ritchie
Dear Colin,

how can I get the source code of the version, described in the message,
because I need to modify the code, to see what happen on the 1-wire bus.
Because I am working on a 1-wire Slave AVR based for a DS2450.

Best regards
R.


> On 12 January 2017 at 16:29, Ritchie <[hidden email]> wrote:
>> Dear Jan,
>>
>> I just decide to reinstall the system new, which is easier than try to
>> fix it.
>
> Install owfs from the 'testing' repository using the technique in
> https://sourceforge.net/p/owfs/mailman/message/35357871/
>
> Colin





------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owserver on a raspberry pi (does not start)

Colin Law
On 13 January 2017 at 16:16, Ritchie <[hidden email]> wrote:
> Dear Colin,
>
> how can I get the source code of the version, described in the message,
> because I need to modify the code, to see what happen on the 1-wire bus.
> Because I am working on a 1-wire Slave AVR based for a DS2450.

https://sourceforge.net/projects/owfs/ is the official repository I
think. Does not owserver already handle the DS2450?

Colin

>
> Best regards
> R.
>
>
>> On 12 January 2017 at 16:29, Ritchie <[hidden email]> wrote:
>>> Dear Jan,
>>>
>>> I just decide to reinstall the system new, which is easier than try to
>>> fix it.
>>
>> Install owfs from the 'testing' repository using the technique in
>> https://sourceforge.net/p/owfs/mailman/message/35357871/
>>
>> Colin
>
>
>
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Ritchie
In reply to this post by Ritchie
Hi to All,

I just reinstalled my raspberry Pi (1) with jessie.

After that I installed the owserver owfs-3.0p2 from source code,
because I guess this is the latest running version of owfs on raspberry
pi without any problems so far.

- recompile with no failure
- installed with no failure

Here is my /etc/owfs.conf

--------------------------------
# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
#server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
server: usb = /dev/ttyUSB0
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################

http: port = 2121

####################### OWFTPD ##########################

ftp: port = 2120

####################### OWSERVER ########################

server: port = localhost:4304
------------------------------------------

Here is a log of my command for testing


~ $ sudo /etc/init.d/owserver restart
[ ok ] Restarting owserver (via systemctl): owserver.service.
~ $ sudo /etc/init.d/owserver status
● owserver.service - Backend server for 1-wire control
    Loaded: loaded (/lib/systemd/system/owserver.service; disabled)
    Active: inactive (dead)
      Docs: man:owserver(1)

Jan 14 14:07:16 fhem3 systemd[1]: Stopped Backend server for 1-wire control.
Jan 14 14:14:17 fhem3 systemd[1]: Starting Backend server for 1-wire
control...
Jan 14 14:14:17 fhem3 systemd[1]: Started Backend server for 1-wire control.
~ $ sudo /etc/init.d/owhttpd status
● owhttpd.service - Tiny webserver for 1-wire control
    Loaded: loaded (/lib/systemd/system/owhttpd.service; disabled)
    Active: inactive (dead)
      Docs: man:owhttpd(1)
~ $ sudo /etc/init.d/owhttpd restart
[ ok ] Restarting owhttpd (via systemctl): owhttpd.service.

~ $ sudo /etc/init.d/owserver restart
[ ok ] Restarting owserver (via systemctl): owserver.service.
~ $ sudo /etc/init.d/owhttpd restart
[ ok ] Restarting owhttpd (via systemctl): owhttpd.service.

~ $ sudo /etc/init.d/owserver status
● owserver.service - Backend server for 1-wire control
    Loaded: loaded (/lib/systemd/system/owserver.service; disabled)
    Active: inactive (dead)
      Docs: man:owserver(1)

Jan 14 14:07:16 fhem3 systemd[1]: Stopped Backend server for 1-wire control.
Jan 14 14:14:17 fhem3 systemd[1]: Starting Backend server for 1-wire
control...
Jan 14 14:14:17 fhem3 systemd[1]: Started Backend server for 1-wire control.
Jan 14 14:16:58 fhem3 systemd[1]: Starting Backend server for 1-wire
control...
Jan 14 14:16:59 fhem3 systemd[1]: Started Backend server for 1-wire control.
~ $ sudo /etc/init.d/owhttpd restart
[ ok ] Restarting owhttpd (via systemctl): owhttpd.service.

~ $ sudo /etc/init.d/owhttpd status
● owhttpd.service - Tiny webserver for 1-wire control
    Loaded: loaded (/lib/systemd/system/owhttpd.service; disabled)
    Active: failed (Result: exit-code) since Sat 2017-01-14 14:17:40
CET; 5s ago
      Docs: man:owhttpd(1)
   Process: 1034 ExecStart=/opt/owfs/bin/owhttpd --foreground
--server=127.0.0.1 (code=exited, status=217/USER)
  Main PID: 1034 (code=exited, status=217/USER)

Jan 14 14:17:40 fhem3 systemd[1]: Started Tiny webserver for 1-wire control.
Jan 14 14:17:40 fhem3 systemd[1034]: Failed at step USER spawning
/opt/owfs/bin/owhttpd: No such process
Jan 14 14:17:40 fhem3 systemd[1]: owhttpd.service: main process exited,
code=exited, status=217/USER
Jan 14 14:17:40 fhem3 systemd[1]: Unit owhttpd.service entered failed state.


I am using the startup scripts of this website:
http://palsbo.com/pi/owfs.html

Why does the httpd not start.

Even I do not see any of this type of start command:
ExecStart=/opt/owfs/bin/owhttpd --foreground --server=127.0.0.1

in the Start up script

Thanks for any type of help

Ritchie


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Martin Patzak (GMX)


On 01/14/2017 02:33 PM, Ritchie wrote:
> Hi to All,
>
> I just reinstalled my raspberry Pi (1) with jessie.
>
> After that I installed the owserver owfs-3.0p2 from source code,
> because I guess this is the latest running version of owfs on raspberry
> pi without any problems so far.

there is no need to compile from source.
Just follow the advice Colin gave you already with this:

Install owfs from the 'testing' repository using the technique in
https://sourceforge.net/p/owfs/mailman/message/35357871/

Colin




------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Ritchie
In reply to this post by Ritchie
Hi,
the problem is, that I have to modify the source code because of some debugging function to analyse the 1-wire bus. I need to see the running protocol on the bus.

Best regards
Ritchie


-------- Ursprüngliche Nachricht --------
Von: "Martin Patzak (GMX)"
Datum:14.01.2017 16:08 (GMT+01:00)
An: "OWFS (One-wire file system) discussion and help"
Betreff: Re: [Owfs-developers] Problem with owhttpd on a raspberry pi (owfs-3.0p2)



On 01/14/2017 02:33 PM, Ritchie wrote:
> Hi to All,
>
> I just reinstalled my raspberry Pi (1) with jessie.
>
> After that I installed the owserver owfs-3.0p2 from source code,
> because I guess this is the latest running version of owfs on raspberry
> pi without any problems so far.

there is no need to compile from source.
Just follow the advice Colin gave you already with this:

Install owfs from the 'testing' repository using the technique in
https://sourceforge.net/p/owfs/mailman/message/35357871/

Colin




------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Colin Law
In reply to this post by Ritchie
On 14 January 2017 at 13:33, Ritchie <[hidden email]> wrote:

>
> ~ $ sudo /etc/init.d/owhttpd restart
> [ ok ] Restarting owhttpd (via systemctl): owhttpd.service.
>
> ~ $ sudo /etc/init.d/owhttpd status
> ● owhttpd.service - Tiny webserver for 1-wire control
>     Loaded: loaded (/lib/systemd/system/owhttpd.service; disabled)
>     Active: failed (Result: exit-code) since Sat 2017-01-14 14:17:40
> CET; 5s ago
>       Docs: man:owhttpd(1)
>    Process: 1034 ExecStart=/opt/owfs/bin/owhttpd --foreground
> --server=127.0.0.1 (code=exited, status=217/USER)
>   Main PID: 1034 (code=exited, status=217/USER)
>
> Jan 14 14:17:40 fhem3 systemd[1]: Started Tiny webserver for 1-wire control.
> Jan 14 14:17:40 fhem3 systemd[1034]: Failed at step USER spawning
> /opt/owfs/bin/owhttpd: No such process
> Jan 14 14:17:40 fhem3 systemd[1]: owhttpd.service: main process exited,
> code=exited, status=217/USER
> Jan 14 14:17:40 fhem3 systemd[1]: Unit owhttpd.service entered failed state.
>
>
> I am using the startup scripts of this website:
> http://palsbo.com/pi/owfs.html
>
> Why does the httpd not start.
>
> Even I do not see any of this type of start command:
> ExecStart=/opt/owfs/bin/owhttpd --foreground --server=127.0.0.1
>
> in the Start up script

What is in the file /lib/systemd/system/owhttpd.service?

Colin

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Ritchie
In reply to this post by Ritchie
Hi all,


the owserver is running now, but the owhttpd does not start.
see messages:


$ sudo service owserver status
(green)● owserver.service - Backend server for 1-wire control
    Loaded: loaded (/lib/systemd/system/owserver.service; disabled)
    Active: active (running) since Sun 2017-01-15 12:48:39 CET; 1min 30s ago
      Docs: man:owserver(1)
  Main PID: 509 (owserver)
    CGroup: /system.slice/owserver.service
            └─509 /opt/owfs/bin/owserver -c /etc/owfs.conf

Jan 15 12:48:37 fhem3 owserver[509]: DEFAULT: ow_opt.c:(675) systemd
mode -- ignore 'p' option
Jan 15 12:48:39 fhem3 systemd[1]: Started Backend server for 1-wire control.

$ sudo service owhttpd status
(white)● owhttpd.service - Tiny webserver for 1-wire control
    Loaded: loaded (/lib/systemd/system/owhttpd.service; disabled)
    Active: inactive (dead)
      Docs: man:owhttpd(1)

Jan 15 12:48:41 fhem3 systemd[1]: Starting Tiny webserver for 1-wire
control...
Jan 15 12:48:41 fhem3 systemd[1]: Started Tiny webserver for 1-wire control.


I am using this "/lib/systemd/system/owhttpd.service"

[Unit]
Description=Tiny webserver for 1-wire control
Documentation=man:owhttpd(1)
After=owserver.service

[Service]
ExecStart=/opt/owfs/bin/owhttpd -c /etc/owfs.conf
#User=ow
#Group=ow

[Install]
WantedBy=multi-user.target


Is this a problem on the owserver
-- ignore 'p' option

Any hint for this ?

Best regards

Ritchie


> Hi,
> the problem is, that I have to modify the source code because of some
> debugging function to analyse the 1-wire bus. I need to see the running
> protocol on the bus.
>
> Best regards
> Ritchie
>
>
> -------- Ursprüngliche Nachricht --------
> Von: "Martin Patzak (GMX)"
> Datum:14.01.2017 16:08 (GMT+01:00)
> An: "OWFS (One-wire file system) discussion and help"
> Betreff: Re: [Owfs-developers] Problem with owhttpd on a raspberry pi
> (owfs-3.0p2)
>
>
>
> On 01/14/2017 02:33 PM, Ritchie wrote:
>> Hi to All,
>>
>> I just reinstalled my raspberry Pi (1) with jessie.
>>
>> After that I installed the owserver owfs-3.0p2 from source code,
>> because I guess this is the latest running version of owfs on raspberry
>> pi without any problems so far.
>
> there is no need to compile from source.
> Just follow the advice Colin gave you already with this:
>
> Install owfs from the 'testing' repository using the technique in
> https://sourceforge.net/p/owfs/mailman/message/35357871/
>
> Colin
>
>
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Colin Law
On 15 January 2017 at 11:56, Ritchie <[hidden email]> wrote:
> Hi all,
>
>
> the owserver is running now, but the owhttpd does not start.
> see messages:

Was my suggestion to look at the systemd service file helpful?

>
>
> $ sudo service owserver status

With systemd you should be using
sudo systemctl status owserver
though the old commands still work.

> (green)● owserver.service - Backend server for 1-wire control
>     Loaded: loaded (/lib/systemd/system/owserver.service; disabled)
>     Active: active (running) since Sun 2017-01-15 12:48:39 CET; 1min 30s ago
>       Docs: man:owserver(1)
>   Main PID: 509 (owserver)
>     CGroup: /system.slice/owserver.service
>             └─509 /opt/owfs/bin/owserver -c /etc/owfs.conf
>
> Jan 15 12:48:37 fhem3 owserver[509]: DEFAULT: ow_opt.c:(675) systemd
> mode -- ignore 'p' option
> Jan 15 12:48:39 fhem3 systemd[1]: Started Backend server for 1-wire control.
>
> $ sudo service owhttpd status
> (white)● owhttpd.service - Tiny webserver for 1-wire control
>     Loaded: loaded (/lib/systemd/system/owhttpd.service; disabled)
>     Active: inactive (dead)
>       Docs: man:owhttpd(1)

Have you started owhttpd?
sudo systemctl start owhttpd
If so what do you see in /var/log/syslog when you start it?

Colin

>
> Jan 15 12:48:41 fhem3 systemd[1]: Starting Tiny webserver for 1-wire
> control...
> Jan 15 12:48:41 fhem3 systemd[1]: Started Tiny webserver for 1-wire control.
>
>
> I am using this "/lib/systemd/system/owhttpd.service"
>
> [Unit]
> Description=Tiny webserver for 1-wire control
> Documentation=man:owhttpd(1)
> After=owserver.service
>
> [Service]
> ExecStart=/opt/owfs/bin/owhttpd -c /etc/owfs.conf
> #User=ow
> #Group=ow
>
> [Install]
> WantedBy=multi-user.target
>
>
> Is this a problem on the owserver
> -- ignore 'p' option
>
> Any hint for this ?
>
> Best regards
>
> Ritchie
>
>
>> Hi,
>> the problem is, that I have to modify the source code because of some
>> debugging function to analyse the 1-wire bus. I need to see the running
>> protocol on the bus.
>>
>> Best regards
>> Ritchie
>>
>>
>> -------- Ursprüngliche Nachricht --------
>> Von: "Martin Patzak (GMX)"
>> Datum:14.01.2017 16:08 (GMT+01:00)
>> An: "OWFS (One-wire file system) discussion and help"
>> Betreff: Re: [Owfs-developers] Problem with owhttpd on a raspberry pi
>> (owfs-3.0p2)
>>
>>
>>
>> On 01/14/2017 02:33 PM, Ritchie wrote:
>>> Hi to All,
>>>
>>> I just reinstalled my raspberry Pi (1) with jessie.
>>>
>>> After that I installed the owserver owfs-3.0p2 from source code,
>>> because I guess this is the latest running version of owfs on raspberry
>>> pi without any problems so far.
>>
>> there is no need to compile from source.
>> Just follow the advice Colin gave you already with this:
>>
>> Install owfs from the 'testing' repository using the technique in
>> https://sourceforge.net/p/owfs/mailman/message/35357871/
>>
>> Colin
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> _______________________________________________
>> Owfs-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>>
>>
>>
>> _______________________________________________
>> Owfs-developers mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Jan Kandziora
In reply to this post by Ritchie
Am 15.01.2017 um 12:56 schrieb Ritchie:
> the owserver is running now, but the owhttpd does not start.
>
Please, we need to see your /etc/owfs.conf.

Kind regards

        Jan


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: Problem with owhttpd on a raspberry pi (owfs-3.0p2)

Ritchie
Dear Jan,

please see here my /etc/owf.conf file

# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
!server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
#server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
#server: device = /dev/ttyUSB0
server: device = /dev/ttyUSB0
#
# Serial port: DS9097
#server: device = /dev/ttyS1
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
#mountpoint = /mnt/1wire
#allow_other
#
####################### OWHTTPD #########################

http: port = 2121

####################### OWFTPD ##########################

ftp: port = 2120

####################### OWSERVER ########################

server: port = 4304


Best regards

Ritchie

Am 15.01.2017 um 15:35 schrieb Jan Kandziora:

> Am 15.01.2017 um 12:56 schrieb Ritchie:
>> the owserver is running now, but the owhttpd does not start.
>>
> Please, we need to see your /etc/owfs.conf.
>
> Kind regards
>
> Jan
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Owfs-developers mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
12