I tried it, and seem to have gotten the same results. Again, the
debug just shows programming pulse = 0; it never = 1.
If there's an easy way to verify what version of owfs I'm running (to
ensure its the one with your chnages), I'd like to do that to make
sure.
Also, I'm assuming you write to memory in the same way: echo -n
"whatever" > memory
If I'm misunderstanding this as well, please let me know. It seems
like somewhat of an awkward interface for a add-only burn.....
Thanks again for all your help!!
------- debug output ---------
unique: 54, opcode: LOOKUP (1), nodeid: 3, insize: 47
LOOKUP /uncached/12.588636000000/memory
CALL: FSTAT path=/uncached/12.588636000000/memory
CALL: PARSENAME path=[/uncached/12.588636000000/memory]
DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4
DEBUG: value found in cache
CALL: ATTRIBUTES path=/uncached/12.588636000000/memory
DEBUG: ParsedName_destroy /uncached/12.588636000000/memory
NODEID: 4
unique: 54, error: 0 (Success), outsize: 136
unique: 55, opcode: SETATTR (4), nodeid: 4, insize: 128
CALL: TRUNCATE path=/uncached/12.588636000000/memory
CALL: FSTAT path=/uncached/12.588636000000/memory
CALL: PARSENAME path=[/uncached/12.588636000000/memory]
DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4
DEBUG: value found in cache
CALL: ATTRIBUTES path=/uncached/12.588636000000/memory
DEBUG: ParsedName_destroy /uncached/12.588636000000/memory
unique: 55, error: 0 (Success), outsize: 112
unique: 56, opcode: OPEN (14), nodeid: 4, insize: 48
CALL: OPEN path=/uncached/12.588636000000/memory
unique: 56, error: 0 (Success), outsize: 32
OPEN[0] flags: 0x8001 /uncached/12.588636000000/memory
unique: 57, opcode: WRITE (16), nodeid: 4, insize: 91
WRITE[0] 27 bytes to 0
CALL: WRITE path=/uncached/12.588636000000/memory size=27 offset=0
DEBUG: FS_OWQ_create of /uncached/12.588636000000/memory
CALL: PARSENAME path=[/uncached/12.588636000000/memory]
DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4
DEBUG: value found in cache
OWQ OneWireQuery structure of /uncached/12.588636000000/memory
OneWireQuery size=27 offset=0, extension=0
Byte buffer OneWireQuery buffer, length=27
-- 3C 46 41 4D 49 4C 59 3D 4D 4F 54 49 4F 4E 3E 3C
-- 56 45 52 53 49 4F 4E 3D 30 31 3E
<<FAMILY=MOTION><VERSION=01>>
OneWireQuery I=27 U=27 F=1.33398E-322 Y=27 D=Wed Dec 31 16:00:27 1969
--- OneWireQuery done
DEBUG: Selecting a path (and device)
path=/uncached/12.588636000000/memory SN=12 58 86 36 00 00 00 18 last
path=00 00 00 00 00 00 00 00
DATA: DS9490_reset
DATA: DS9490_reset: ok
DEBUG: Transaction select = 0
DEBUG: Transaction send = 0
DEBUG: Transaction readin = 0
DATA: DS9490_level 2 (old = 0)
DATA: DS9490_level 0 (old = 2)
DATA: DS9490_HaltPulse
DATA: DS9490_HaltPulse: loop
DATA: DS9490_HaltPulse: ok
DEBUG: Transaction program pulse = 0
DEBUG: Transaction readin = 0
DEBUG: Transaction end = 0
DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil) index=-1 size=4
DEBUG: value found in cache
DEBUG: Selecting a path (and device)
path=/uncached/12.588636000000/memory SN=12 58 86 36 00 00 00 18 last
path=00 00 00 00 00 00 00 00
DATA: DS9490_reset
DATA: DS9490_reset: ok
DEBUG: Transaction select = 0
DEBUG: Transaction send = 0
DEBUG: Transaction readin = 0
DATA: DS9490_level 2 (old = 0)
DATA: DS9490_level 0 (old = 2)
DATA: DS9490_HaltPulse
DATA: DS9490_HaltPulse: loop
DATA: DS9490_HaltPulse: ok
DEBUG: Transaction program pulse = 0
DEBUG: Transaction readin = 0
DEBUG: Transaction end = 0
DEBUG: Selecting a path (and device)
path=/uncached/12.588636000000/memory SN=12 58 86 36 00 00 00 18 last
path=00 00 00 00 00 00 00 00
DATA: DS9490_reset
DATA: DS9490_reset: ok
DEBUG: Transaction select = 0
DEBUG: Transaction send = 0
DEBUG: Transaction readin = 0
DATA: DS9490_level 2 (old = 0)
DATA: DS9490_level 0 (old = 2)
DATA: DS9490_HaltPulse
DATA: DS9490_HaltPulse: loop
DATA: DS9490_HaltPulse: ok
DEBUG: Transaction program pulse = 0
DEBUG: Transaction readin = 0
DEBUG: Transaction end = 0
DEBUG: FS_OWQ_destroy of /uncached/12.588636000000/memory
DEBUG: ParsedName_destroy /uncached/12.588636000000/memory
unique: 57, error: -22 (Invalid argument), outsize: 16
unique: 58, opcode: RELEASE (18), nodeid: 4, insize: 64
RELEASE[0] flags: 0x8001
CALL: RELEASE path=/uncached/12.588636000000/memory
unique: 58, error: 0 (Success), outsize: 16
------- end output ----------
On 9/27/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Can you try the CVS now? My next iteration. In the past we disabled and
> enabled the strong pull-up (and program pulse can get reset at same time).
> The code is now simpler, works for the standard case (reading data and
> temperatures) and might wirk for program pulses.
>
> Paul Alfille
>
>
> On 9/27/07, Jim Kusznir <[EMAIL PROTECTED]> wrote:
> > Any news on this? My best reading of the output was that owfs didn't
> > actually initiate the programming pulse.
> >
> > --Jim
> >
> > On 9/25/07, Jim Kusznir <[EMAIL PROTECTED] > wrote:
> > > Hi:
> > >
> > > Here's the debug dump from an attempt at:
> > >
> > > echo -n "Testing" > memory
> > >
> > > ----------
> > > unique: 103, opcode: LOOKUP (1), nodeid: 2, insize: 47
> > > LOOKUP /12.588636000000/memory
> > > CALL: FSTAT path=/12.588636000000/memory
> > > CALL: PARSENAME path=[/12.588636000000/memory]
> > > DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
> > > DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil)
> index=-1 size=4
> > > DEBUG: value found in cache
> > > CALL: ATTRIBUTES path=/12.588636000000/memory
> > > DEBUG: ParsedName_destroy /12.588636000000/memory
> > > NODEID: 3
> > > unique: 103, error: 0 (Success), outsize: 136
> > > unique: 104, opcode: SETATTR (4), nodeid: 3, insize: 128
> > > CALL: TRUNCATE path=/12.588636000000/memory
> > > CALL: FSTAT path=/12.588636000000/memory
> > > CALL: PARSENAME path=[/12.588636000000/memory]
> > > DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
> > > DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil)
> index=-1 size=4
> > > DEBUG: value found in cache
> > > CALL: ATTRIBUTES path=/12.588636000000/memory
> > > DEBUG: ParsedName_destroy /12.588636000000/memory
> > > unique: 104, error: 0 (Success), outsize: 112
> > > unique: 105, opcode: OPEN (14), nodeid: 3, insize: 48
> > > CALL: OPEN path=/12.588636000000/memory
> > > unique: 105, error: 0 (Success), outsize: 32
> > > OPEN[0] flags: 0x8001 /12.588636000000/memory
> > > unique: 106, opcode: WRITE (16), nodeid: 3, insize: 71
> > > WRITE[0] 7 bytes to 0
> > > CALL: WRITE path=/12.588636000000/memory size=7 offset=0
> > > DEBUG: FS_OWQ_create of /12.588636000000/memory
> > > CALL: PARSENAME path=[/12.588636000000/memory]
> > > DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
> > > DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil)
> index=-1 size=4
> > > DEBUG: value found in cache
> > > OWQ OneWireQuery structure of /12.588636000000/memory
> > > OneWireQuery size=7 offset=0, extension=0
> > > Byte buffer OneWireQuery buffer, length=7
> > > -- 54 65 73 74 69 6E 67
> > > <Testing>
> > > OneWireQuery I=7 U=7 F=3.45846E-323 Y=7 D=Wed Dec 31 16:00:07 1969
> > >
> > > --- OneWireQuery done
> > > DEBUG: Selecting a path (and device) path=/12.588636000000/memory
> > > SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00
> > > DATA: DS9490_reset
> > > DATA: DS9490_reset: ok
> > > DEBUG: Transaction select = 0
> > > DEBUG: Transaction send = 0
> > > DEBUG: Transaction readin = 0
> > > DATA: DS9490_level 2 (old = 0)
> > > DATA: DS9490_level 0 (old = 2)
> > > DATA: DS9490_HaltPulse
> > > DATA: DS9490_HaltPulse: loop
> > > DATA: DS9490_HaltPulse: ok
> > > DEBUG: Transaction program pulse = 0
> > > DEBUG: Transaction readin = 0
> > > DEBUG: Transaction end = 0
> > > DEBUG: Cache_Get_Device 12 58 86 36 00 00 00 18
> > > DEBUG: Get from cache sn 12 58 86 36 00 00 00 18 pointer=(nil)
> index=-1 size=4
> > > DEBUG: value found in cache
> > > DEBUG: Selecting a path (and device) path=/12.588636000000/memory
> > > SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00
> > > DATA: DS9490_reset
> > > DATA: DS9490_reset: ok
> > > DEBUG: Transaction select = 0
> > > DEBUG: Transaction send = 0
> > > DEBUG: Transaction readin = 0
> > > DATA: DS9490_level 2 (old = 0)
> > > DATA: DS9490_level 0 (old = 2)
> > > DATA: DS9490_HaltPulse
> > > DATA: DS9490_HaltPulse: loop
> > > DATA: DS9490_HaltPulse: ok
> > > DEBUG: Transaction program pulse = 0
> > > DEBUG: Transaction readin = 0
> > > DEBUG: Transaction end = 0
> > > DEBUG: Selecting a path (and device) path=/12.588636000000/memory
> > > SN=12 58 86 36 00 00 00 18 last path=00 00 00 00 00 00 00 00
> > > DATA: DS9490_reset
> > > DATA: DS9490_reset: ok
> > > DEBUG: Transaction select = 0
> > > DEBUG: Transaction send = 0
> > > DEBUG: Transaction readin = 0
> > > DATA: DS9490_level 2 (old = 0)
> > > DATA: DS9490_level 0 (old = 2)
> > > DATA: DS9490_HaltPulse
> > > DATA: DS9490_HaltPulse: loop
> > > DATA: DS9490_HaltPulse: ok
> > > DEBUG: Transaction program pulse = 0
> > > DEBUG: Transaction readin = 0
> > > DEBUG: Transaction end = 0
> > > DEBUG: FS_OWQ_destroy of /12.588636000000/memory
> > > DEBUG: ParsedName_destroy /12.588636000000/memory
> > > unique: 106, error: -22 (Invalid argument), outsize: 16
> > > unique: 107, opcode: RELEASE (18), nodeid: 3, insize: 64
> > > RELEASE[0] flags: 0x8001
> > > CALL: RELEASE path=/12.588636000000/memory
> > > unique: 107, error: 0 (Success), outsize: 16
> > >
> > > Thanks!
> > > --Jim
> > >
> > > On 9/25/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> > > > Have you tried running owfs with debugging enabled?
> > > >
> > > > owfs --error_level=9 --foreground -m mountpoint -u
> > > >
> > > > That will give you lots of output.
> > > > I don't think the DS2490 can tell if it has 12V available. It oes need
> the
> > > > 12 Programing explicitly enabled (I think I did that), and the
> duration set
> > > > (default 512 usec, the datasheet says 480usec, I use 480 but perhaps
> the
> > > > default is more appropriate under real-world conditions).
> > > >
> > > > Can you post your debugging output?
> > > >
> > > > Paul Alfille
> > > >
> > > >
> > > > On 9/24/07, Jim Kusznir <[EMAIL PROTECTED]> wrote:
> > > > > Hi Paul:
> > > > >
> > > > > Thanks for the fast responce!
> > > > >
> > > > > I pulled in the CVS version just about 20 minutes ago using:
> > > > > cvs
> > > > -d:pserver:[EMAIL PROTECTED]
> :/cvsroot/owfs
> > > > co owfs
> > > > > (I couldn't figure out how to tell what revision I'm at...)
> > > > >
> > > > > I'm seeing the same behavior I was as before:
> > > > >
> > > > > [EMAIL PROTECTED] pages]# echo -n "This is a test" > page.1
> > > > > -bash: echo: write error: Invalid argument
> > > > > [EMAIL PROTECTED] pages]# cd ..
> > > > > [EMAIL PROTECTED] 12.588636000000]# echo -n "testing" > memory
> > > > > -bash: echo: write error: Invalid argument
> > > > >
> > > > > Unfortunately, I haven't found any debugging output, espicially
> wether
> > > > > or not it detected the 12V available. If you could point me toward
> > > > > how to get the debugging output, I'll get more information (and make
> > > > > sure owfs sees my hardware as I think it should :) )
> > > > >
> > > > > Thanks!
> > > > > --Jim
> > > > >
> > > > > On 9/22/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> > > > > > If you're willing to try the CVS version, I put in support.
> Untested,
> > > > but
> > > > > > should follow the datasheet closely.
> > > > > >
> > > > > > Paul Alfille
> > > > > >
> > > > > >
> > > > > > On 9/21/07, Paul Alfille < [EMAIL PROTECTED]> wrote:
> > > > > > > Hi Jim,
> > > > > > >
> > > > > > > I don't think 12V eprom program has ever been tested. As you
> notice,
> > > > it's
> > > > > > hard to find an appropriate adapter.
> > > > > > >
> > > > > > > It looks only like the DS2406, DS2502 and DS2505 need the
> program
> > > > pulse
> > > > > > (480usec).
> > > > > > >
> > > > > > > The DS2490 datasheet does say that it supports 12V programming.
> > > > > > http://datasheets.maxim-ic.com/en/ds/DS2490.pdf
> > > > > > >
> > > > > > > Only not in the DS9490 device.
> > > > > > >
> > > > > > > I'll try to add support and get you to test.
> > > > > > >
> > > > > > > Paul Alfille
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 9/21/07, Jim Kusznir < [EMAIL PROTECTED] > wrote:
> > > > > > > > Hi all:
> > > > > > > >
> > > > > > > > I've been trying for about a week to write to the DS2406's
> EPROM
> > > > using
> > > > > > > > OWFS. I realize that the bus master needs to have +12 VPP,
> and have
> > > > > > > > been working on this.
> > > > > > > >
> > > > > > > > I currently am trying to write using:
> > > > > > > >
> > > > > > > > echo "test" > memory
> > > > > > > >
> > > > > > > > from within my owfs chip's directory. I get an error message
> from
> > > > echo.
> > > > > > > >
> > > > > > > > I have two bus masters: DS9490R (USB) and DS9097E ("passive").
> The
> > > > > > > > 9097E has the connecter for +12, which I've put on it.
> > > > Unfortunately,
> > > > > > > > it looks like OWFS doesn't see it as the E version, but a
> version
> > > > > > > > which does not have +12 which I believe is responsible for it
> not
> > > > > > > > allowing me to write.
> > > > > > > >
> > > > > > > > I have also opened up one of my 9094R's, lifted the VPP pin
> and
> > > > > > > > applied +12 externally. Unfortunately, I am still unable to
> write
> > > > > > > > through OWFS.
> > > > > > > >
> > > > > > > > In all my endevors to write so far, the only sucess I've had
> is to
> > > > > > > > bring up my 9097E in windows (on a hardware serial port -- I
> found
> > > > usb
> > > > > > > > serial adaptors don't work), and writing one nibble at a time
> (more
> > > > > > > > that that fail).
> > > > > > > >
> > > > > > > > Based on reading the data sheet for the DS2490 (the chip the
> 9094R
> > > > is
> > > > > > > > based on), it sounds like it may require a register or other
> setting
> > > > > > > > to be set to enable programming. I looked and looked through
> owfs
> > > > and
> > > > > > > > read every piece of documentation I could find, but could not
> find
> > > > any
> > > > > > > > information on setting the programming enabled info, or even
> > > > > > > > retreaving information on wether programming voltage is
> detected.
> > > > > > > >
> > > > > > > > So, my questions:
> > > > > > > >
> > > > > > > > 1) how do I write to EPROMS requiring the +12VPP?
> > > > > > > > 2) What adaptors have others sucessfully used?
> > > > > > > > 3) Can I configure an adaptor such as the 9094R as
> write-enabled
> > > > after
> > > > > > > > I physically modified it to include +12 VPP? Do I need to?
> > > > > > > >
> > > > > > > > Any other relevent comments?
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> -------------------------------------------------------------------------
> > > > > > > > This SF.net email is sponsored by: Microsoft
> > > > > > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > > > > >
> > > >
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > > > >
> _______________________________________________
> > > > > > > > Owfs-developers mailing list
> > > > > > > > Owfs-developers@lists.sourceforge.net
> > > > > > > >
> > > > > >
> > > >
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> -------------------------------------------------------------------------
> > > > > > This SF.net email is sponsored by: Microsoft
> > > > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > > >
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > > _______________________________________________
> > > > > > Owfs-developers mailing list
> > > > > > Owfs-developers@lists.sourceforge.net
> > > > > >
> > > >
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> -------------------------------------------------------------------------
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > >
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > _______________________________________________
> > > > > Owfs-developers mailing list
> > > > > Owfs-developers@lists.sourceforge.net
> > > > >
> > > >
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> > > > >
> > > >
> > > >
> > > >
> -------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Microsoft
> > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > >
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > _______________________________________________
> > > > Owfs-developers mailing list
> > > > Owfs-developers@lists.sourceforge.net
> > > >
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> > > >
> > > >
> > >
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Owfs-developers mailing list
> > Owfs-developers@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
