• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 997 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.

DRV3205-Q1: EEPROM CRC diagnostics

masahiko shimizu
Guru 11235 points
Part Number: DRV3205-Q1

Hi,

My customer is using DRV3205-Q1.
He has a issue about EEPROM CRC diagnostics.
He used the following procedure to confirm EEPROM CRC diagnostics.
But He couldn't occur "EEPROM CRC Error".

Could you give me advice how to occur "EEPROM CRC Error" at EEPROM CRC diagnostics, please?

1. Read CRCCALC register at diagnostic state
2. Write CRCCALC register to the error value which is inverted value of the read value at procedure 1.
3. Write EE_CRC_CHK bit to 1.
4. Wait EE_CRC_CHK bit = 0.
5. Confirm EE_CRC_ERR bit.

Best regards,
Shimizu

  • 0
    TI__Expert 3555 points
    Hi Shimizu-san,

    For step 4, read the EE_CRC_ERR bit in STAT3 and verify that it set to 1, which indicates it is working successfully, you do not need to wait for EE_CRC_CHK bit = 0.

    Regards,
    Will Toth
  • 0 in reply to William Toth
    Guru 11235 points
    Hi Toth-san,

    Thank you for your support.
    I will tell customer that customer does not need to wait for EE_CRC_CHK bit = 0.

    And I add a question for EEPROM cheak
    What is the difference of "EE_CRC_CHK bit" and "uC_EE_Trim_Check"?

    Best regards,
    Shimizu
  • 0 in reply to masahiko shimizu
    TI__Expert 3555 points

    Hi Shimizu-san,

    The description in the register map is accurate. One is for diagnostic of EEPROM CRC only checks CRC with CRCCALC (EE_CRC_CHK) and one is for actual check of EEPROM CRC (uC_EE_Trim_Check).

    Please refer to the detailed safety manual for more details on how to implement. If you need more details or descriptions from the documents not on the web feel free to reach out over email and we can answer there.

    Regards,

    Will Toth