I'd previously written in about "4 DRV2605YZFR parts on the same I2C bus?"
We went forward with our design, made a prototype and wrote the firmware.
Now we are finding that the EN pin being low does not prevent writes to the I2C registers. However, the datasheet writes this should not be the case:
"7.4.1.3 Operation With EN Control"
"The EN pin must be high to write I2C device registers."
Here is snap shot where where 2 parts a programmed with separate haptic sequences and the 2 enable lines should ensure separate programming.
However, we are finding that all haptic parts always execute the last haptic sequence written out, regardless of what the parts EN pin state was at the time of programming.
Are there any possible software solutions that can save this design?