MCF8316AEVM: Use EXP-MSP430FR2355 as GUI-to-board link

Part Number: MCF8316AEVM
Other Parts Discussed in Thread: MCT8329A, MCT8329EVM, MSP-EXP430FR2355, MSP430FR2355

I have been trying to do something similar [to the related question] with an MCT8329A and an EXP-MSP430FR2355 development board, for portability.  I couldn't get it to work.  After some digging I found that the big difference was the FT232RL and suspected that the GUI does not recognize the COM port without the FT232RL; so, the referenced post answered my question.  

So, I'm curious:  is there a way around this?

-or-

Has, by chance, the GUI ever been updated to recognize serial COMs without the need for the FT232RL?

-if not-

Will it ever be?

-or-

Does there exist a board that contains only the necessary components to link the MCT/MCF to the GUI [that is, the 2355 and the FT232RL, and whatever supporting components are required]? 

If not, I think a good suggestion would be for TI to make this item available.  I would certainly benefit from it, and suspect others would as well.  Working with a custom design and having to cart around the Eval board just for the linker can be quite cumbersome.  A more portable design with only the linker would be wonderful.  I've thought about prototyping it myself [just for personal use] using the design files provided with the MCT8329EVM and the GUI software.  It would be very easy but would be too costly at the individual level. 

Thank you.

  • Hi Ben,

    Apologies for the delayed response.

    The GUI specifically recognizes and only opens the FT232RL FTDI USB VCP device for 2 main reasons:

    • To avoid opening the wrong port if other Virtual COM Port devices are connected
    • The FT232RL can easily support the UART baud rate of 460800 used for the Motor Studio communication, while the LaunchPad eZ-FET can only support up to 115200.

    The firmware on the MSP430 could be modified to configure at lower baud rate to support the MSP-EXP430FR2355 with the GUI, but we don't plan on implementing and releasing this.

    Unfortunately, we don't provide a board that only contains the USB to I2C serial communication bridge. The row of jumpers/headers on the MCx EVMs allow you to jumper wire the I2C signals and use the GUI to configure a MCx driver on a custom PCB using the EVM's communication bridge.

    If you want to just use the MSP430FR2355 LaunchPad to communicate with a custom MCx board without the GUI, this E2E FAQ contains a MSP430 firmware project that can be easily modified to send any I2C read/write commands.

    Regards,
    Eric C.

  • Thank you for the detailed response.  I have already implemented a an I2C read/write program using an external IC which seems to work quite well.

    Cheers!

  • Hi Ben,

    Thanks for the update and glad you were able to implement I2C on your external IC.

    Regards,
    Eric C.