MCT8329EVM: I couldn't start communication

Hi Liu/Tom,

Could you please try relaunching the GUI, and before connecting the MCT8329EVM, configure the I2C Target Address in the right side panel to 0x00:

Then connect the MCT8329EVM and try communicating/reading registers again. If this works, it means the I2C Target Address stored in the MCT8329's EEPROM register is set to 0x00.

If desired, the customer can change the I2C Target Address value in the device EEPROM from 0x00 to 0x60 to avoid having to change the GUI setting in the side panel each time after launching GUI.

1. Configure GUI to use 0x00 as I2C Target Address
2. Navigate to Guided Tuning Settings
3. Navigate to Essential Controls
4. Navigate to Recommended Default Values
5. Click on Restore Recommended Values (wait for a few seconds)
6. Write to EEPROM
7. Power cycle
8. GUI can now use 0x60 as I2C Target Address in the side-panel

Regards,
Eric C.

Hi Eric,

Thank you for your reply.

I conducted the procedure which you have given us. After this process, I wrote to EEPROM, however I couldn’t confirm whether it was updated correctly.

How can I check I2C target address which is updated to 0x00 or 0x60 correctly?

After this procedure, I tried to work BLDC motor, however the motor couldn’t work.

And also, I couldn’t confirm the switching waveform from three phase output (A/B/C) of this MCT8329EVM.

Could you please let me know, how can I work BLDC motor with analog POT and I2C.

I think that the manual which you provided is not so sufficient to confirm the test procedure of motor driver MCT8329A and MCT8329EVM.

Best Regards,
Tom

Hi Tom,

If you're able to read/write to the device without seeing the connectivity error window popup in the GUI, then that means the I2C target address configured in the GUI matches with the I2C target address written inside the device's EEPROM.

You can confirm this by power-cycling the MCT8329A then connect to the GUI and read the PIN_CONFIG2 register:

To use analog POT or I2C to control the speed, you'd need to configure the SPEED_CTRL_MODE register:

In I2C speed input mode, the DEVICE_CTRL.SPEED_CTRL register can be used to control the speed command.

Did you follow the Essential Controls section step-by-step to spin up the motor? Does any fault get triggered?

Regards,
Eric C.

Hi Eric,

Does the MSP430 with MCT8329EVM have firmware written before shipping?

I am not sure if it is communicating and also cannot check the USB serial communication waveform.

Also, I2C is not working. It stays High all the time.

Current situation are follows.

I conducted following trial.

1) Uninstall and reinstall TI's browser extensions (TIcloudagent) on Google Chrome

2) Re-write MSP430 FW

3) Match I2C address settings with EEPROM (maybe)

However, after returning to work, the communication is stopped again.

Probably I think that TI's browser extensions (TIcloudagent) may be problem.

Could you please let me know how to use MCT8329EVM with BLDC smoothly?

Best Regards,
Tom

Hi Liu Yang, 

Eric is currently out of office but will be back next week to address your questions

Best Regards, 
Andrew 

Hi Liu/Tom,

Yes the MCT8329EVM are all programmed with the MSP430 firmware and tested with the GUI before shipping. When you plug in the USB on the EVM, one of the LED next to the MSP430FR2355 should light up, indicating that the firmware is running. Do you see this LED light up?

You had mentioned that you conducted the procedure that I provided in my first response to set the I2C address to 0x60. Did any communication error pop up during the steps 1 ~ 6? If no error popped up during that process, such as after clicking on the RESTORE RECOMMENDED VALUES button, then that meant the EVM was communicating correctly.

Regards,
Eric C.

LED is lighting up red color. And also I had conducted the procedure which you mentioned. and I tried to change I2C address from 0x00 to 0x60, and from 0x60 to 0x00, however the motor didn't work. is this EVM board broken?

How much is the appropriate BaudRates? In case of 9600 bps, Connectivity Issue is occured. In case of 115200bps, connectiviry issue window is not appeared.

After reproramming MSP430 by MSP430 LaunchPad Development Kits, the EVM could work BLDC with Baud Rate 9600 bps and I2C Target Address:0x00.

Why? You mentioned the MSP430 is programmed before shipping to customer side. right?

Hi Eric,

I have similar issue with I2C target address and EERPOM is not written permanently (chip does not behave the same after power cycle the board).

One issue I have root cause is that the EVM board is programmed at 0x0 not 0x60( as in manual) right out of the box. 
I will re-test the EEPROM issue after reprogram MSP430

Hi Hung-Chen,

Were you able to communicate with the device when the GUI is configured to use 0x00 in the I2C Controls side panel?

If so, what happens when you use the register map page to set the I2C Target Address to 0x60 and press the write to EEPROM button as shown below?

Regards,
Eric C.