• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 180 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP8764-Q1: REG_CR_EN = 1, but CRC value is wrong in the NVM. RECOV_CNT_THR =0. Is there a way to reprogram the device

Bala Mahadeva iyer
Prodigy 190 points
Part Number: LP8764-Q1

We have a LP8764-Q1 based design. In working revision of this design, we had REG_CRC_EN = 0.

We used an USB to I2C dongle (aardvark) to re program the device.

In the updated design file, we have the following setting

REG_CRC_EN =1

RECOV_CNT_THR = 0

but the CRC value was not stored in the expected location. The unit was power cycled. 

Now the PMIC device is not coming up (probably because the CRC does not match) as well as the device keep doing retry as the RECOV_CNT_THR = 0.

We are not able to re program this device.

Is there any way we can re program the device ?  Will we be able to re program the device if we use the PMIC EVM board and the PMIC Scalable GUI interface ?

We have this wrongly part in multiple boards and we are blocked. 

Please let us know if there is anyway we can recover this part without having to replace the part with a new part.

Please treat this as an urgent request

Thanks

  • 0
    TI__Genius 12921 points

    Hello Bala,

    Can you still receive a ACK from the device after the programming, if so I believe you can reprogram the device.

    Did you follow the instructions laid out in the following document? (NVM Update Guide, link here)

    If possible can you list out the steps you have done to see what could've possibly gone wrong from there?

    BR,

    Nicholas

  • 0 in reply to Nicholas McNamara
    Prodigy 190 points

    Hello Nicholas

    I did not create the programming script that was used to update the image using the Aardvark tool (USB to I2C bridge)

    But the software engineer had followed the instruction that is provided in the NVM update guide.

    One thing that he might not have done or done wrongly is that the CRC value was probably not programmed into the location before power cycling. Now the device is not able to be detected on the I2C bus using the Aardvark dongle anymore.

    We have some tool installation issues and hence we are not able to use the PMIC Scalable GUI software along with the LP8764 EVM path. But I have a feeling that, even that may fail.

    Thanks

    Bala

    .

  • 0 in reply to Bala Mahadeva iyer
    TI__Genius 12921 points

    Hello Bala,

    I understand that. That is very much possible as these are values check upon boot and can cause it's like you're seeing.

    Is it possible to see the script to see if there's any mistakes?

    I see, I'm looking back over on the other thread.

    BR,

    Nicholas