• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 395 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MCT8316A: some issues regarding EEPROM and RAM to read

Cherry Zhou
Mastermind 22235 points
Part Number: MCT8316A

Hi team,

Here's some issues from the customer may need your help:

1) As the figure below, the manual states that EEPROM reads and writes are to be performed while the motor is stationary. Dose that mean when the motor speed is not 0, read and write will fail? The only judgment is if the motor is stationary. Correct? But if reading and writing to EEPROM with motor speed other than 0, how to tell if the read data is abnormal?

2) If reading the RAM registers, is there any limitations? For example, reading the MOTOR_SPEED field of the SYS_STATUS2 Register (Address = EAh) register, what are the limitations?

Could you help check this case? Thanks!

Best Regards,

Cherry

  • 0
    TI__Genius 9220 points

    Hi Cherry,

    I will check with our design team and get back to you tomorrow.

    Regards,
    Eric C.

  • +1
    TI__Genius 9220 points

    Hi Cherry,

    1) If the motor is spinning, EEPROM read/write command is held until the motor stops and enters idle state, then the EEPROM write/read is executed. User would need to read back the EEPROM register after the write command has been issued to verify that the EEPROM write has completed successfully. After setting the EEPROM_READ or EEPROM_WRT bit, the user can also check and see of these bits are automatically reset to 0, which indicates that EEPROM read/write is completed.

    Please also keep in mind that the EEPROM_WRITE_ACCESS_KEY needs to be set to 0xA5 while setting the EEPROM_WRT bit in order for the write command to take effect.

    2) The only limitation that I'm aware of is that there needs to be a minimum 100μs delay between byte to byte transaction, otherwise the device may lose I2C communication, requiring a power cycle to reset.

    Regards,
    Eric C.