DRV10987: EEPROM is not ready

Hi Ken Zhang,

Thanks for sharing the details. One quick check is to confirm whether the device is driving the motor when EEPROM operations are attempted?

Also, we don't need to write to EEPROM every power up? What is the reason for writing to EEPROM every time? We need to consider EEPROM write endurance cycles.

Thanks and Best Regards

Venkatadri S

Venkatadri

NOT driving the Motor when EEPROM operations are attempted.

As the project is a medial application, customer wants to write EEPROM every power up to assure the configure right.

Background:

Customer had used DRV10975 with the same way (write DRV10975's EEPROM every power up) in other project before, but no issue with DRV10975.

(DRV10987 is p2p with DRV10975, but support higher current.)

the minimum EEPROM endurance of DRV10987 is 1000 cycle. what is the minimal cycle of EEPROM endurance of DRV10975?

Hi Zhang,

I need to verify endurance information for DRV10975 and confirm.

I will review differences between DRV109875/DRV10987 and update you.

Can you email me, we will continue discussion.

Thanks and Best Regards

Venkatadri S

Hi Zhang,

Have they tried 1000 time already and seeing this issue? If they have crossed 1000 cycles eeprom time out behavior can be possible.

Endurance is minimum 1000 cycles and not guaranteed.

Suggestion: Writing to EEPROM not recommended every power up considering endurance cycle.

Thanks and Best Regards

Venkatadri S

Venkatadri,

customer didn't record how many times EEPROM was written when DRV10987 EEPROM was failure. They will do some experiment to record the writing EEPROM times when DRV10987 is failure later.

do you already verify endurance information for DRV10975?

Hi Zhang,

I have not verified it, let me take this action and reply to you soon.

Thanks and Best Regards

Venkatadri S

Vendatadri

any update?

Hi Zhang,

Unfortunately I have not followed up on this. This might take some time because of dependency.

Can you email to me.

Thanks and Best Regards

Venkatadri S