1. I am writing SPI driver for DRV8245 and testing it on pre-production chip samples. So far I am getting random values from device ID requests. This could be a bug in my communication code, but it is hard to tell for sure.
What device ID should I expect from pre-production samples?
2. Could not make driver to work so far. The control signals have correct 20kHz PWM on EN pin and direction signal on PH pin. However nFAULT pin stays asserted, despite setting CLR_FLT bit in HDR2 byte of every SPI packet. I also tried reading FAULT_SUMMARY registers and bits POR and VMOV are always set. Again, this could be a bug in my communication code, since VM is only 24V.
Do I need to send separate COMMAND register write request with CLR_FLT bit after startup, or is global CLR_FLT bit embedded into HDR2 is sufficient?
3. The datasheet is not clear about MSB bit of the command byte. It says "MSB bit indicates frame type (bit B15 = 0 for standard frame).", but it says nothing about daisy chain frame, except "The command, data, status and report bytes remain the same as described in the standard frame format".
So, if the command byte remains the same, why does it have frame type bit?
