Previous in Forum: Matlab-Simulink   Next in Forum: Equipment with Different Voltage and Frequency
Close
Close
Close
4 comments
Rate Comments: Nested
Participant

Join Date: Jul 2014
Posts: 1

Problem Unlocking Atmel EEPROM

07/02/2014 4:00 AM

EEPROM (AT28C010-12DK-SV) is having a lock/unlock feature for enable/disable of software write protection. Under locked condition, data cannot be written to the device. Once locked data can be written only after unlocking.

EEPROM is locked by following write sequence.

Data 0xAA to address 0x5555

Data 0x55 to address 0x2AAA

Data 0xA0 to address 0x5555

EEPROM is unlocked by following write sequence.

Data 0xAA to address 0x5555

Data 0x55 to address 0x2AAA

Data 0x80 to address 0x5555

Data 0xAA to address 0x5555

Data 0x55 to address 0x2AAA

Data 0x20 to address 0x5555

These writes has to be performed with a gap of <150us (between writes). While doing so none of these data is physically written to corresponding addresses, instead lock or unlock will be performed (to perform actual data write, there has to be a delay of 10ms between writes).

My system name is PE and it has multiple versions built.

In PE FM, the gap between writes (for lock/unlock sequences) is kept as commandable (multiples of 16us; minimum is 16us). It is found that lock has happened (while lock command was given). Subsequently, unlock is not working. Lock/unlock status is verified by attempting to write a different data to a dummy location.

In PE EM, lock/unlock is working, but upto 48us gap (between writes) only (against the spec of <150us). In another EM where MIL-883 EEPROM is wired, it is seen that lock/unlock works upto 256us delay (meeting the specs). It is felt that the EEPROMs wired in FM (issued from ISAC) could be marginal in this spec. and may need gap less than 16us (which cannot be given PE FM).

Proper loading to EEPROM (before locking) and proper functioning of PE shows that there is no hardware defect (PCB, FPGA, etc). i.e. all normal read/write with EEPROM is OK. Write timings in lock/unlock are verified on scope and found OK. This problem is there with both sections in PE.

So is the problem due to EEPROM out of spec for lock/unlock timings ???

Please Help..

Register to Reply
Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.
Guru

Join Date: Nov 2007
Location: Eastern Arizona mountains on Route 666 about a mile from God's country
Posts: 1676
Good Answers: 122
#1

Re: Problem unlocking Atmel EEPROM

07/02/2014 8:59 AM

It appears you are "looping" the lock-unlock sequence code.

Try entering only the "UNLOCK CODE SEQUENCE" below, wait 10 - 20 seconds then check the EEPROM status.

UNLOCK CODE SEQUENCE:

1. Data 0xAA to address 0x5555

2. Data 0x55 to address 0x2AAA

3. Data 0x80 to address 0x5555

LOCK CODE SEQUENCE:

4. Data 0xAA to address 0x5555

5. Data 0x55 to address 0x2AAA

6. Data 0x20 to address 0x5555

__________________
They said; "Brain size?" I heard; "Train size?" so I said: "I'll take a small one, thank you."
Register to Reply
Anonymous Poster #1
#2
In reply to #1

Re: Problem unlocking Atmel EEPROM

07/03/2014 10:22 AM

In the OP, the lock sequence actually ended in

Data 0xA0 to address 0x5555

not

Data 0x20 to address 0x5555

Register to Reply
Guru
Popular Science - Weaponology - New Member Safety - ESD - New Member Hobbies - Fishing - New Member

Join Date: Sep 2006
Location: Near Frankfurt am Main, Germany. 50.390866N, 8.884827E
Posts: 17996
Good Answers: 200
#3

Re: Problem Unlocking Atmel EEPROM

07/03/2014 1:45 PM

My first question is:-

Is this someone trying to steal propriety code out of this chip?

I am always very suspect when I see such "problems"....

Because, why not simply throw the chip away and use another one? THEY ONLY COST AROUND 10 EACH IN USA CENTS IN SMALL QUANTITIES!!!

There is simply no legal reason that you need to unlock it!!! Simply junk it......buy a new one!!

__________________
"What others say about you reveals more about them, than it does you." Anon.
Register to Reply
Anonymous Poster #1
#4
In reply to #3

Re: Problem Unlocking Atmel EEPROM

07/03/2014 5:09 PM

I too, have often seen posts similar to this in an attempt to reverse engineer a chip or steal IP. I don't think this is one.

In this case, this lock/unlock procedure apparently is to write-protect the chip.

I'm guessing you can always read it. True?

So this sounds like a "legitimate" question.

But to your point Andy, if you have one bad chip - toss it out. But if you are having generic device-interfacing problems, this is a valid question.

Register to Reply
Register to Reply 4 comments

Previous in Forum: Matlab-Simulink   Next in Forum: Equipment with Different Voltage and Frequency

Advertisement