************************************************************************ ************************************************************************ ** ** ** Application notes for Seiko Instruments Memory devices ** ** ** ** (Informal Document) ** ** ** ** To find the application notes for your device search for the ** ** 'core' part name. As an example using the 25C256A 8 pin TSSOP ** ** you would search this document for the entry "25C256" ** ** ** ************************************************************************ ************************************************************************ ************************************************************************ 25C256A ---------- There are four levels of Block Protection that can be supported on these devices: Start/End Block (BP1), (BP0) Protection Addresses Security Fuse settings: SF2, SF1 25C256A ------------------------------------ ------------- 0, 0 None 0, 1 $6000->$7FFF 1, 0 $4000->$7FFF 1, 1 $0000->$7FFF ----------------------------------------------------------- Enabling the "Erase EE device" option will ONLY remove all block protection. NOTE: The "Erase EE device" option must be enabled when re-programming the device in order to remove the Block Protection. NOTE: The "Erase EE device" option will NOT Erase the device. To re-program the device you must disable Blank/Illegal Bit checks flags. To program the Hardware Write Protection option (WPEN) enable the "Program protect reg." flag. Performing a Load operation will also load the Status Register Protection Bits into the following address locations in User RAM: 25C256A = Address $8000 The data format in the Programmer's User RAM will follow the same format as defined in the corresponding device's data sheet. Status Register Format in relation to the Protection Bits: ------------------------------------------------------- |Bit 7 |Bit 6 |Bit 5 |Bit 4 |Bit 3 |Bit 2 |Bit 1 |Bit 0 | |-------------------------------------------------------| | WPEN | X | X | X | BP1 | BP0 | X | X | ------------------------------------------------------- NOTE: Checksum issues under TaskLink: Performing a LOAD DEVICE operation under TaskLink may produce a Checksum that does NOT match the checksum produced during any other device operations. To make sure Checksums match for all operations please enable "Use Algorithm Checksum." *********************************************************************** ************************************************************************