On Sunday 10 July 2005 10:52 pm, Matthew Percival wrote: > G'Day, > > Thanks for the suggestions: it has made things a lot easier to work > through! I had actually skipped those files (ow_ds9097.c, etc) assuming > they were 1-Wire devices, rather than adaptors --- I did not think I > would find anything useful in them. Was I ever wrong! > > I have written ow_omap.c as well as made a variety of additions to > other files here and there, and am now able to add `-o /dev/wire' to the > command line when I load owfs. When I mount owfs, I get bus.0/, and > when I cat the files in system/adapter/ I now get the information I > would expect to see. I do not, however, get any devices in bus.0/ --- > obviously I am still lacking something.
I assume you've altered ow_opt for special parameters and configuration for your adapter type, and added the adapter type to the enum. > > My first, key, question is this: where does the actual polling for > devices occur, and what do I have to ensure I do/have to be able to get > it to at least recognise the existence of the device? Polling uses the 1-wire protocol search routine. Some devices do it in hardware, others (like the 9097) set the bus powered and unpowered for the requisite time. The 9097 is a little tricky, the baud rate is changed for the reset command, and then changed back so that individual bits are at the right speed for 1-wire. I'm afraid you're going to have to read the 1-wire Application Notes. Suggestions: Look at code for the PIC microprocessor (it's sufficiently low-level, I think) http://www.maxim-ix.com/appnots.cfm/appnote_number/2420 Using a serial port: http://www.maxim-ix.com/appnots.cfm/appnote_number/214 And the search algorithm: http://www.maxim-ix.com/appnots.cfm/appnote_number/187 The reset command is essential, it effectively resets the bus and starts the next transaction. Reset and bit write/read (read is writing a "1" and reading if the bus actually stays high) are the essential commands. The search/select command can be made from these smaller parts (though accelerated by hardware in some adapters). > > Secondly, I currently have `f->reset' set to a dummy function, as I was > not sure what the purpose of this was, and if it really applied to my > device at all. If someone could just tell be the basic purpose of this > function, I will be able to work out what to do with it. > > Thanks for the help again: I feel I am on the verge of being able to > see my device, and it is entirely due to the assistance here! > > -- Matthew > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest > in dual core and dual graphics technology at this free one hour event > hosted by HP, AMD, and NVIDIA. To register visit > http://www.hp.com/go/dualwebinar > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
