Other Parts Discussed in Thread: MCF8316A, MCF8316AEVM, MCT8316A
I purchased the MCT8316AEVM and want to test the FOC. Can I change the MCT8316AEVM to the MCF8316A with FOC support to evaluate it?
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.
I purchased the MCT8316AEVM and want to test the FOC. Can I change the MCT8316AEVM to the MCF8316A with FOC support to evaluate it?
Hi Hong
I changed the device from MCT8316 to MCF8316A for testing. For a few days, I was able to test without any problem, but suddenly I2C communication between MSP MCU and MCF8316A is not working.
I can't update the EEPROM value, so I can't proceed with the project anymore.
When I try to run the motor, the nFAULT LED turns on, so it doesn't seem like the MCF8316A in the EVM is broken.
The I2C communication waveform measured by Logic Analyzer shows that no ACK is being delivered from the MCF8316A.
Is there any solution?
Thanks.
Hi Yongsu,
Are you using the MCF8316A GUI? There is a possibility that there is a mismatch between the GUI target address and the actual device address (you can see that the communication above is to 0x1). If so, have you tried pressing the "Find Address" button under the I2C controls menu?
This will attempt to communicate to the device iterating through every possible address until it receives a response.
Regards,
Hong