Owner's manual

DS2705: SHA-1 Authentication Master
15 of 18
Write Data [6Ch, XX]. This command writes data starting at memory address XX. The LSb of the data to be stored
at address XX can be written immediately after the MSb of address has been entered. Because the address is
automatically incremented after the MSb of each byte is written, the LSb to be stored at address XX + 1 can be
written immediately after the MSb to be stored at address XX. If the bus master continues to write beyond address
FFh, the data starting at address 00 is overwritten. Writes to read-only addresses, reserved addresses and locked
EEPROM blocks are ignored. Incomplete bytes are not written. Write Data modifies the shadow RAM. A Copy Data
command is required to transfer data from the shadow to the EEPROM. See the Memory section for more details.
The Write command will cause spurious behavior if issued during an authentication attempt is in progress on the
MDQ pin.
Copy Data [48h]. This command copies the contents of all shadow RAM locations to EEPROM cells. After the
copy command is issued a high voltage pulse must be applied to the VPP pin for a time period of
t
PPW
. See Figure 7
for example bus timing of an EEPROM program function. During the pulse, the bus master can issue read timeslots
on the bus. The DS2705 will respond with ‘0’s while the EEPROM copy is in progress, and ‘1’s after the copy is
complete. A reset on SDQ at any time during the copy sequence will prematurely terminate the operation.
Figure 7. Copy EEPROM Sequence
VPP = 0V
SKIP ROM
Cmd
Copy Data
Cmd
1-Wire
Reset
Presence
Pulse
Non-critical Timing
Bus master may issue read slots during
EEPROM copy. DS2705 responds with
‘0’s during copy , ‘1’s afterwards.
SDQ
VPP = 14.5V MIN
15.0V MAX
t
PPR
t
PPF
t
PPW
VPP
Recall Data [B8h]. This command recalls the contents of all EEPROM cell locations to the shadow RAM memory.
Following the Recall command, SDQ must be driven low for a minimum of t
RSTL
. SDQ can be driven low indefinitely
after the Recall command. The Recall command will cause spurious behavior if issued while an authentication
attempt is in progress on the MDQ pin.