Thanks for checking that. We will give the latest release a try. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: Thursday, May 18, 2006 7:25 PM To: [email protected] Subject: Re: [Owfs-developers] RE: problem writing to DS1996
The current version seems to work. (I found a 1996 and tested it.) Paul On 5/17/06, Spade, Rod <[EMAIL PROTECTED]> wrote: > Paul, > > Thanks for your quick response. > > The problem happens whether I copy a small file to pages/page.n via the > shell, or use a compiled C program to write to "memory" after doing an > lseek. > > It appears that the offset of the first byte written into a page is > being used as the most significant byte of the address. So if I start > writing at 0x0414, the data is stored at 0x1414 instead. 0x1304 goes to > 0x0404. If the data extends beyond the end of the first page, the > subsequent pages are always written to 0x00nn. > > Rod > > > -----Original Message----- > From: Paul Alfille <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: [Owfs-developers] problem writing to DS1996 > Date: Tue, 16 May 2006 15:42:33 -0400 > Reply-To: [email protected] > > Thanks for the report. > > A couple questions: > 1. Can you analyze where the data is actually being written? > 2. Are you using "memory" or "pages/page.n" are the target? > > Paul Alfille > > On Tuesday 16 May 2006 03:29 pm, Spade, Rod wrote: > > I'm having a problem using OWFS 2.2p3 to write to a 64kb DS1996. > > Writing into the first 256 bytes of the "memory" file works OK, but > when > > I write to other locations, the data ends up at the wrong address. If > I > > immediately read back the data it looks OK, but if I do an uncached > read > > (or wait for the cache to time out), I don't get back what was > written. > > > > I think that reading the memory is OK. If I use the 1wire public > domain > > library "memutil" sample to write, I can read the data back with OWFS > > and everything looks good. But when I write something to the same > > location via OWFS, reading everything back shows that the data was > > written to the wrong location in the memory. > > > > Has anyone else experienced this? > > > > Thanks for the help! > > > > Rod > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642 > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
