I can't answer for your specific hardware, but I can tell you about the w1 interface.
On a standard PC, when I plug in a DS9490 (USB bus master) I get the following in dmesg: [1326734.219886] usb 1-1.4.1: new full speed USB device using ehci_hcd and address 15 [1326734.356321] Driver for 1-wire Dallas network protocol. [1326734.363985] usbcore: registered new interface driver DS9490R [1326735.903622] w1_master_driver w1 bus master: Family 81 for 81.000000231bcd.8b is not registered. The 81.00000023 is the imbedded ID chip in the bus master. Adding another slave gives: [1326872.548664] 0x81: count=18, status: 01 00 20 40 05 04 04 00 20 53 00 00 00 01 00 00 a5 a5 [1326872.548688] [1326872.548693] enable flag: 1 [1326872.548699] 1-wire speed: 0 [1326872.548705] strong pullup duration: 20 [1326872.548711] programming pulse duration: 40 [1326872.548717] pulldown slew rate control: 5 [1326872.548722] write-1 low time: 4 [1326872.548728] data sample offset/write-0 recovery time: 4 [1326872.548734] reserved (test register): 0 [1326872.548740] device status flags: 20 [1326872.548746] communication command byte 1: 53 [1326872.548751] communication command byte 2: 0 [1326872.548756] communication command buffer status: 0 [1326872.548761] 1-wire data output buffer status: 0 [1326872.548766] 1-wire data input buffer status: 1 [1326872.548770] reserved: 0 [1326872.548774] reserved: 0 [1326872.548779] new device detect: a5 [1326872.548784] new device detect: a5 [1326874.081541] w1_master_driver w1 bus master: Family 6 for 06.0000002dd68f.6f is not registered. I then run owhttpd (must be root to communicate over netlink and use w1): sudo /opt/owfs/bin/owhttpd --debug --w1 -p 4444 And the pertainant information from owhttpd: DEBUG: ow_w1_list.c:w1_list_masters(54) Sending w1 bus master list message DEBUG: ow_w1_send.c:W1_send_msg(119) Netlink send ----------------- NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=16413 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0 W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0 Byte buffer Data, length=0 DEBUG: ow_w1_dispatch.c:W1_Dispatch(129) Dispatch loop DEBUG: ow_w1_parse.c:Netlink_Parse_Get(114) Wait to peek at message DEBUG: ow_w1_parse.c:Netlink_Parse_Get(122) Pre-parse header: 16 bytes len=52 type=3 seq=0|1 pid=0 DEBUG: ow_w1_parse.c:Netlink_Parse_Get(144) Netlink read ----------------- NLMSGHDR: len=52 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0 CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=0 len=16 flags=25190 W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=4 id=1631085926 Byte buffer Data, length=4 --000: 01 00 00 00 <....> DEBUG: ow_w1_dispatch.c:Dispatch_Packet(92) Sending this packet to root bus DEBUG: ow_w1_dispatch.c:W1_Dispatch(129) Dispatch loop DEBUG: ow_w1_list.c:w1_parse_master_list(64) W1 List 1 masters DEBUG: ow_w1_parse.c:Netlink_Parse_Get(114) Wait to peek at message DEBUG: ow_w1_parse.c:Netlink_Parse_Get(122) Pre-parse header: 16 bytes len=48 type=3 seq=0|1 pid=0 CALL: ow_parsename.c:FS_ParsedName_anywhere(91) path=[] DEBUG: ow_w1_parse.c:Netlink_Parse_Get(144) Netlink read ----------------- NLMSGHDR: len=48 type=3 (NLMSG_DONE) flags=0 seq=0|1 pid=0 DEBUG: ow_w1_addremove.c:CreateIn(48) Created a new bus w1_bus_master1CN_MSG: idx/val=3/1 (CN_W1_IDX) seq=0|1 ack=1 len=12 flags=0 W1_NETLINK_MSG: type=6 (W1_LIST_MASTERS) len=0 id=0 Byte buffer Data, length=0 DEBUG: ow_w1_addremove.c:AddW1Bus(72) Request master be added: w1_master1. DEBUG: ow_add_inflight.c:Add_InFlight(26) Request master be added: w1_bus_master1 DEBUG: ow_w1_dispatch.c:Dispatch_Packet(92) Sending this packet to root bus DEBUG: ow_w1_dispatch.c:W1_Dispatch(129) Dispatch loop DEBUG: ow_w1_parse.c:Netlink_Parse_Get(114) Wait to peek at message DEBUG: ow_w1_list.c:w1_parse_master_list(64) W1 List 0 masters Basically, an actual w1-controlled 1-wire bus master was seen. The w1 module behaves differently from other bus masters. It grabs and presents all the bus masters and all the slaves to owfs. The good part is that w1 supports some embedded controllers. And OWFS doesn't require specific slave support. It is slow, poorly documented, and a little quirky (didn't really work before kernel 2.6.29) Confounding al this is that the OMAP doesnt' use standard Dallas 1-wire, but a TI-based version. What happens when you try running owserver of owhttpd like I did above? The debugging information should be helpful. Paul Alfille On Mon, Mar 21, 2011 at 7:32 AM, Ozan <ozs...@gmail.com> wrote: > Hi, > > I'm new to this list, please excuse me > if this has already been discussed here. > I wasn't able to find whether the > 3530's built-in 1wire bus master is supported > by owfs or not. > > I am currently trying to link my ds2408 and omap3530. > Using the 2.6.37 kernel, > I have activated the omap_hdq > driver and inserted my driver into the module. > I have also chosen the connectors for the user space. > From the moment that I > make the kernel and boot it on > the board, I have a phantom family (without id > and name) > => w1_master_driver w1 bus master: > Family 1 for 01.000000000000.3d is > not registered. > > Besides while looking at the scope, > I have seen a pulse on the 1-wire bus but it > is not a reset/initialization pulse, > more likely a 100 us presence pulse from > the slave. > > I have read man y times the omap datasheet > but nothing gives me a clue to debug > my system. > I have also read that the OMAP 1-wire module is not working very well > and many people have problems. So my questions are : > > -Should I just select the omap_hdq driver > and insert the slave driver as a module? > -Should I just select the master driver > and nothing else on the slaves? > - As I am (very) new to the 1-wire concept > are there any steps that I have missed? > > Any ideas? > > Regards > > > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
