This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP8860-Q1: LP8860-Q1(D version) EEPROM ISSUE

Part Number: LP8860-Q1

My customer is using LP8860-Q1 (D version) applied to AVN.
There is currently a product with a problem with changing EEPROM Setting Data.
LP8860-Q1 (Dversion) According to the application, there is no problem with mass production products, but there is a problem while considering applying it to the new model.
attachments will be modified EEPROM Read value.

A customer writes an EEPROM at the first start, and rewrites the EEPROM when the read value becomes a problem.
I think it's been over 1000 cycles since I started rewriting without EEPROM lock.

The following questions need to be checked.

1. The customer will change it to 0xFA (the default value of 0xF8 of type D) at 0x66 and save it to the EEPROM.

    However, is the behavior changed if the 0x66 value is sent every time without writing to the EEPROM?

    The action I want is to write 10 on BRT_MODE.

2. What causes the EEPROM Register value to change when the data is not written after EEPROM_UNLOCK?

3. Is there a way to check the number of EEPROM writes?

Back Light_EEPROM Read Data.xlsx

  • Hi CHO,

    1.Can you clarify the question "is the behavior changed if the 0x66 value is sent every time without writing to the EEPROM?"? Do you mean write value to 0X66 EEPROM register after power up is effective or not?

    2. You can always change the EEPROM register value by writing to it through I2C or SPI after power up. The EEPROM register will just load the default value from the EEPROM.

  • Hi CHO,

    I will close this thread temporarily since you don't have reply to me for a long time. You can ask questions here if you get any feedback from customer and the threads will open again.