Are both owfs and your application trying to access directly /dev/i2c-2:0 ? Has
the owcapi application the privileges for reading /dev/i2c?
If you run owfs, application programs should access sensors via the filesystem
(not owcapi).
Maybe a better approach is to run owserver (instead of owfs) to access the bus
and have application programs use ownet (see examples in
module/ownet/c/src/example).
From 'man owserver'
owserver (1) is the backend component of the OWFS 1-wire bus control
system. owserver (1) arbitrates access to the bus from multiple client
processes. The physical bus is usually connected to a serial or USB
port, and other processes connect to owserver (1) over network sockets
(tcp port). Communication can be local or over a network. Secure tun-
neling can be implemented using standard techniques.
Frontend clients include a filesystem representation: owfs (1) , and a
webserver: owhttpd (1). Direct language bindings are also available,
e.g: owperl (3). Several instances of each client can be initiated.
Each client can also connect directly to the physical bus, skipping
owserver (1) but only one client can connect to the physical bus
safely.
bye, Stefano
On 10 Sep 2014, at 17:43, Howell, Larry (Contractor) <larry.how...@stryker.com>
wrote:
> Our project is developing an embedded system running Linux 2.6.35 on an
> i.MX53. Fuse is built in to the kernel. The system utilizes plugin devices
> that store configuration data on internal DS2505s. We’re using owfs-2.8p15
> and writing application code based on the owcapi. The system uses a
> DS2482-800 bus master and the initialization parameters are ‘i2c=/dev/i2c-2:0
> –m mnt/1wire --allow_other’. The filesystem mounts with expected
> permissions, and non-root users can access the filesystem with no problem
> from the bash shell. However, the application code fails all attempts at
> filesystem access with a ‘permission denied’ error. Searching the owfs man
> pages hasn’t provided any clues about this problem. Any pointers or
> suggestions would be greatly appreciated.
>
> Thanks for your help!
>
> Larry Howell
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
