cancel
Showing results for 
Search instead for 
Did you mean: 

EEPROM was M24C64-(Batch_No)K which was working well and the new EEPROM M24C64-(Batch_No)T has been causing problem

SPalr.1
Associate II

Hi,

It's a problem is with device which is designed before 20years.

Intro:

·        The MSP430F4250 is connected with M24C64(EEPROM through I2C) used to log 2 Byte date for every 6 second. This was working with no problems for 15 years.

·        Recently the M24C64 has made some Process technology change, they call it as CMOSF8H+(old processing technology was CMOSF8H). 

·        So the old EEPROM was M24C64-(Batch_No)K which was working well and the new EEPROM M24C64-(Batch_No)T has been causing problem.

Problem Definition:

·        With new EEPROM when I read stored samples (Bytes), when it is less than 250 samples(500Bytes) I'm reading Garbage/Wrong Value for all the samples (Bytes).

·        once the stored samples are greater than 250 samples(500Bytes) and when I read them I can able to read all the Samples (Bytes) with Correct Value.

Observation:

·        I've reviewed the Code and Ckt, and can't able to find any bug namely as it was work well for last 15 years with old M24C64-(Batch_No)K. And Even with M24C64-(Batch_No)T I have no problem if the sample stored is more than 250(500Bytes).

Question:

·        Why I'm I reading Garbage/Wrong Values for samples when the stored sample is less than 250(500Bytes)

·        Suddenly after 250 samples (500Bytes), Let's say the stored sample is more than 251(501Bytes) I can able to read all the 251 samples Correctly.

Can someone help me narrow down this problem?

0 REPLIES 0