Dnia 08.04.2012 o 14:55 Paul Alfille <paul.alfi...@gmail.com> Paul Alfille <paul.alfi...@gmail.com> napisał(a):
> Well, there certainly shouldn't be a seg fault in the detection code! > > I see that the debug message actually is the culprit. The CVS version is > now corrected. Can you pull from that or should I send you version to > test? Could you send me that version. I have problems with compiling from cvs cvs -d:pserver:anonym...@owfs.cvs.sourceforge.net:/cvsroot/owfs co owfs ./bootstrap and then I get some errors > > Paul Alfille > > On Sun, Apr 8, 2012 at 7:06 AM, Patryk <p4tr...@o2.pl> wrote: > >> I'm trying to get DS2482-800(i2c-1wire) co runnings. The easiest way to >> test it seemed to be using VGA connector i2c. I connected it all on a >> breadboard but when I start owfs I get errors. >> >> modprobe i2c-dev >> owfs --debug --i2c=ALL:ALL /mnt/owfs >> I get no valid devices found >> If I run it with debug I get >> root@belafonte:/home/patryk/motion# /opt/owfs/bin/owfs --debug >> --i2c=ALL:ALL /mnt/owfs/ >> CONNECT: owfs.c:(100) fuse mount point: /mnt/owfs/ >> some >> DEBUG: ow_avahi_link.c:(75) Avahi support: libavahi-client loaded >> successfully >> DEBUG: ow_avahi_link.c:(77) Avahi library function found: >> avahi_client_errno >> DEBUG: ow_avahi_link.c:(78) Avahi library function found: >> avahi_client_free >> DEBUG: ow_avahi_link.c:(79) Avahi library function found: >> avahi_client_new >> DEBUG: ow_avahi_link.c:(80) Avahi library function found: >> avahi_client_get_domain_name >> DEBUG: ow_avahi_link.c:(81) Avahi library function found: >> avahi_entry_group_add_service >> DEBUG: ow_avahi_link.c:(82) Avahi library function found: >> avahi_entry_group_commit >> DEBUG: ow_avahi_link.c:(83) Avahi library function found: >> avahi_entry_group_is_empty >> DEBUG: ow_avahi_link.c:(84) Avahi library function found: >> avahi_entry_group_new >> DEBUG: ow_avahi_link.c:(85) Avahi library function found: >> avahi_entry_group_reset >> DEBUG: ow_avahi_link.c:(87) Avahi library function found: >> avahi_service_resolver_free >> DEBUG: ow_avahi_link.c:(88) Avahi library function found: >> avahi_service_resolver_new >> DEBUG: ow_avahi_link.c:(89) Avahi library function found: >> avahi_service_browser_free >> DEBUG: ow_avahi_link.c:(90) Avahi library function found: >> avahi_service_browser_new >> DEBUG: ow_avahi_link.c:(102) Avahi support: libavahi-common loaded >> successfully. >> DEBUG: ow_avahi_link.c:(104) Avahi library function found: >> avahi_simple_poll_free >> DEBUG: ow_avahi_link.c:(105) Avahi library function found: >> avahi_simple_poll_get >> DEBUG: ow_avahi_link.c:(106) Avahi library function found: >> avahi_simple_poll_loop >> DEBUG: ow_avahi_link.c:(107) Avahi library function found: >> avahi_simple_poll_new >> DEBUG: ow_avahi_link.c:(108) Avahi library function found: >> avahi_simple_poll_quit >> DEBUG: ow_avahi_link.c:(109) Avahi library function found: >> avahi_strerror >> CALL: ow_parsename.c:(95) path=[] >> DEBUG: owlib.c:(79) Globals temp limits 0C 100C (for simulated >> adapters) >> CONNECT: ow_ds2482.c:(350) [Is a directory] Could not open i2c device >> (null) >> CONNECT: ow_ds2482.c:(350) [Is a directory] Could not open i2c device >> (null) >> CONNECT: ow_ds2482.c:(363) Found an i2c device at /dev/i2c-0 address 18 >> CONNECT: ow_ds2482.c:(392) i2c device at (null) address 18 cannot be >> reset. Not a DS2482. >> CONNECT: ow_ds2482.c:(363) Found an i2c device at /dev/i2c-0 address 19 >> Naruszenie ochrony pamięci(Segmentation fault) >> >> >> >> Is there a way to determine that the chip is connected. >> I test it on my old laptop it has radeon x600 graphic card. The voltage >> on >> 5V pin is about 4.5V. >> Maybe the >> >> >> -- >> p4trykx >> >> >> ------------------------------------------------------------------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-d2dvs2 >> _______________________________________________ >> Owfs-developers mailing list >> Owfs-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> -- p4trykx ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
