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.
Hi guys,
My customer wants to use the LP8545 but they have a question. They need to enable the Iset pin to set the current threshold, but according to the datasheet the Iset pin is inactive until enabled via EEPROM. However, there is a note about the EEPROM:
"EEPROM NVM can be programmed or read by customer for bench validation. Programming for production devices should be done in TI production test, where appropriate checks will be performed to confirm EEPROM validity. Writing to EEPROM Control register of production devices is not recommended. If special EEPROM configuration is required, please contact the TI Sales Office for availability."
So, can they use a host MCU to adjust settings in EEPROM after the parts boot up? or are they supposed to tell you guys what settings they want and are stuck with them after production test?
This note is confusing, so some elaboration would be nice on what that means exactly. Is it just that "EEPROM Control Register" with address 72h that is off limits, and the rest of the device settings are fine to change at will?
Thanks,
Brian
Sean,
Sorry, but your answer doesnt really clear anything up. You are saying that the EEPROM is only supposed to be programmed once, by TI, during production? And the custom settings will remain there forever, even between power cycles?
They already have a prototype with this part, so while there still is time to change it, I only want to recommend that if it is completely necessary. If the answer to my above question is "yes," then ok I will recommend the other devices.
Thanks,
Brian
Sean,
Yes, they have an MCU sitting next to their LP8545. I have to say, I am pretty confused by your comments.
Is it recommended by TI to use an MCU to adjust register settings within this part's EEPROM, or is it not recommended and they should choose another LED Driver?
Thanks,
Brian