Paul Alfille <paul.alfille <at> gmail.com> writes: > > Hi Igor, > > I'vwe been looking at the Datasheet, and there are a pair of > instructions, "Unlock NV1" and "Lock NV1" -- from this I assumed that > only "locked" NV memory would need to be unlocked. > > Is that not the case? How did your memory get locked? > > The bigger question is how should OWFS handle this? Possible ways are: > 1. Discrete lock and unlock commands. Write only. > 2. Unlock automatically before any write, but dont lock afterwards. > 3. Unlock before a write and lock afterwards. > > case 1 adds the most complexity to the user, while the other two cases > make the locking superfluous. To be honest, I don't really understand > the purpose of the locking in the first case. Sending a write sequence > as noise on the line seems unlikey, and if you have access to write, > you have access to unlock. >
Hi! Thank you for answer! I need to write data at NV1. Exactly for this page there is function lock&unlock. I do not understand why is this function needed too... :) At the site Maxim/dallas in datasheet for evalution kit ds2436K there is a picture for NV1 - "USER MEMORY SCREEN Figure 3". You can look it also at this link http://disk.tom.ru/rjveszt/1/8337d/pict.png This is an illustration for "lock/unlock" and "copy SP1 to NV1" command. Can you get me a code which is work like on this picture? Or any way that you like. Best regards, Igor ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
