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.

DRV3901-Q1: Problem on CONFIG_CRC_W trigger

Part Number: DRV3901-Q1

Tool/software:

Hi team, 

1. Customer feedbacked that the CONFIG_CRC_W was triggered after they configure the CONFIGx register. And they checked the read register value can match with write register value. 

CONFIG_CRC_W can be triggered every time. Could you provide some ideas to figure out the root cause and how should we solve this warning problem. 

2. Regarding to off-state diagnostic configuration 1&2 register, could you provide some guidance or documents that how should we set these different parameter? For example, for OFF_DIAG_WK_PD_VSEL, which application scenario we should use 1.5V? Or 1.8V? 

Thanks!

Ethan Wen

  • Hello Ethan,

    Thanks for your questions.

    1. Customer feedbacked that the CONFIG_CRC_W was triggered after they configure the CONFIGx register. And they checked the read register value can match with write register value. 

    CONFIG_CRC_W can be triggered every time. Could you provide some ideas to figure out the root cause and how should we solve this warning problem.

    Can you confirm what was the register values written and the corresponding CRC register value in CONFIG4.

    2. Regarding to off-state diagnostic configuration 1&2 register, could you provide some guidance or documents that how should we set these different parameter? For example, for OFF_DIAG_WK_PD_VSEL, which application scenario we should use 1.5V? Or 1.8V? 

    The default values should be working if the customer has no additional circuitry in the output. Has the customer evaluated with the default settings?

    Thanks,

    Ibinu