This is my thought, yes. I was thinking something along the lines of "read an int at addres xxxx and call it "temperature" type commands.
--Jim On Mon, Mar 8, 2010 at 10:13 AM, Paul Alfille <paul.alfi...@gmail.com> wrote: > So if I understand correctly, the firmware upload not only programs the > slave, it also contains information for OWFS to parse and create the > devices? > > On Mon, Mar 8, 2010 at 11:31 AM, Jim Kusznir <jkusz...@gmail.com> wrote: >> >> Yes, I was intending on this being stored in eeprom on the slave >> device. I believe in most cases, the slave device will be soldered on >> a board with its support electronics for whatever task it is doing. >> As such, its task is not going to change. >> >> I am NOT (currently) proposing that information such as where the >> sensor is located or what its monitoring the temperature of, for >> example, are stored...Just information as to what it is (its a >> temperature and light detector, for example) and how to get data from >> it. >> >> So, in my use case below, a hobbyist who doesn't have the >> microprocessor development kit / JTAG cable / etc, could take a chip >> that has been flashed with the "base", build his device, and plug it >> into a onewire bus. At that point it will show up, but only have one >> or so functions in OWFS: a "file" for firmware load that they can then >> cp the personality file to. That will transfer the personality to the >> chip. Once complete, the user then unplugs the OW device, then plugs >> it back in. When OWFS discovers the device, it will have more info in >> its "configuration" space that will tell OWFS 1) what address >> locations to read on the slave; 2) what type of value its reading (how >> long it is); and 3) what text description to call it in its directory >> tree. >> >> As such, this would allow OWFS to NOT need any special configuration >> for individual slaves. It would allow a completely flexible slave, >> even for hobbyists who don't know/want to get into the full >> microprocessor development. It would even allow such people to >> write/modify their own personalities (compiling with GCC, hopefully, >> or some other SDK freely downloadable) and upload them, or choose from >> a set of "standard" or "example" personalities provided by the open >> source project that's designing / producing the code for the chip. >> >> Of course, people wishing to commercialize this can sell chips >> pre-programmed with the base (or those who have sufficient >> microprocessor facilities can buy their own devices from the >> manufacturer and flash the base on them with JTAG/etc themselves). >> These individuals can even make their own personalities that are >> commercial/copyrighted and people can buy those from the >> individual/company. I'm sure individuals would also want to contract >> with an expert to write personalities for them, too. >> >> I do think its critically important that the core of the project be >> open source. Right now, the fact that the only slave devices >> available are commercial / closed source are a major damper on the >> hobbyist's and researcher/experimenter's ability to grow and use OW / >> OWFS for even cooler things. I know that I need custom work, and I'm >> not going to pay someone else to develop a custom chip that I'd then >> have to buy individually from them and not own the source code. I >> already have a staff of programmers here, and due to university >> policies and procedures, its very difficult if not impossible to pay >> for such services. >> >> --Jim >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
