
Preliminary
PSD813F Family
123
Discrepancy
–
Anytime the MCU changes the state of SDP mode from disabled to
enabled, it must write three command bytes (AAh, 55h, A0h), then write a single dummy
byte to a reserved address space of 128 bytes in length. The dummy byte can be any
pattern. The MCU should not use method 1 or method 2 shown above to enable SDP
mode.
This is only necessary when going from SDP mode disabled to SDP mode enabled.
If SDP mode is already enabled (enabled from the MCU or a stand-alone device
programmer), then the command sequences in Table 9 of the data sheets may be used
to write byte(s) into the EEPROM (no dummy write to reserved space is needed). If the
MCU disables SDP mode, then enables SDP mode again, a dummy write to the
reserved address space is needed to get SDP mode enabled again.
Interim Solution
–
Reserve an address range 128 bytes in length within an unused portion of EEPROM.
This 128-byte space can be in any of the four EEPROM segments, and must begin on a
128-byte address boundary.
To enable SDP mode (only after previously being disabled), the MCU must write the
command sequence AAh, 55h, A0h to any valid EEPROM sector at addresses X555h,
XAAAh, X555h respectively. But then it must write a single dummy byte to the first
location within the reserved 128-byte address space. Example (you don
’
t have to use
these exact addresses or dummy byte value):
AAh >> 8555h
55h >> 8AAAh
A0h >> 8555h
EEh >> 8080h
Just like data PSD813F sheet so far.
Dummy byte EEh is written to reserved address block starting
at 8080h (block is from 8080h to 80FFh).
From this point forward, SDP mode is enabled, until disabled by the MCU or a device
programmer.
If you cannot locate 128 bytes of unused space in your EEPROM memory map, then
you can use populated EEPROM memory. However, you must first read the existing
128 bytes in the reserved space, enable SDP mode with the single dummy write, then
write the original 128 bytes back into the reserved address space.
Temporary
Exceptions to
Specifications
(cont.)