• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 29 subscribers
  • Views 147 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MCF8315A: [Programmer]confirmation

Allen Lu
Intellectual 1890 points
Part Number: MCF8315A
Other Parts Discussed in Thread: MCF8316AEVM, MCF8316A

Tool/software:

Hi Team,

 my customer target to evaluate the MCF8315A device for 10W fan EE, when we check the EVM with GUI, we can see there is a  MSP430 to transfer some command from USB to IIC, but for the production, customer can reserve the IIC IOs for program purpose but can not accept with the MSP430 together.

 but if is there any easy way for customer to burn the code into it or easy debug without the EVM help?

 in other words， if customer do not have the EVM and MSP430 demo , how can we debug the MCF8315 with GUI?

 tks for the checking.

  • 0
    TI__Genius 9210 points

    Hi Allen,

    Please refer to this E2E FAQ for instructions on how to use a MSP430 LaunchPad to read/write to the MCx device registers. However, the LaunchPad doesn't work with the GUI, since the GUI requires a specific MSP430 firmware and the EVM's USB interface to function correctly.

    One way to use the GUI with a custom MCF8315A PCB is to jumper wire the I2C SDA, I2C SCL, and GND from the EVM's USB/MSP430 interface to the custom PCB.

    Regards,
    Eric C.

  • 0 in reply to Eric Chen
    TI__Intellectual 1890 points

    Hi Eric,

    tks for the comments here. 

    so summary is that:

     1. if we need to use the GUI ,we need specific MSP430 firmware like demo board to support  this function. there is no others way to supporting this debug purpose with GUI?

    2. if customer work well with GUI, then customer export the register and use external MCU for program purpose?

    3. how about others customer program the software into this MCF device?  also using external MCU to connect IIC and burn into it ?

  • 0 in reply to Allen Lu
    TI__Genius 9210 points

    Hi Allen,

    1. The GUI specifically works with the USB FTDI interface on the EVM and the firmware on the MSP430. This is because of the custom serial UART protocol used between the GUI and the MSP430.

    2. Yes, once the customer uses the GUI and EVM to optimize the tuning for their motor, they can save the register settings. And use an external MCU to write the register settings via I2C to the MCF8315 during production.
    3. Some customers use their MCU to check the register content on the MCF device on every power-up, and if the register settings are different, they use the MCU to write the custom register settings into the MCF's EEPROM.

      Once the EEPROM is written in the MCF device, they won't change unless a EEPROM write command is triggered. So some customers use an external MCU, like the MSP430 LaunchPad, as a MCF programmer to write the MCF's EEPROM before populating onto their custom PCB. 

    Regards,
    Eric C.

  • 0 in reply to Eric Chen
    TI__Intellectual 1890 points

    Hi Eric,

     Tks for the supplement here, it is more clear to understand it. 

     one more question is that , we use the MCF8316AEVM with MCF8316A_GUI,  it works. but cannot work with MOTOR GUI.

     or do we need burn new code for MCF8316AEVM and they have below relastionship?

    MCXEVM-MSP430FR2355-MOTORSTUDIO-FW — MCxEVM MSP430FR2355 Motor Studio GUI firmware

    for motor GUI ?

    MCX83XXEVM-MSP430FR2355-GUI-FIRMWARE — MCx83xxEVM MSP430FR2355 GUI Firmware

    default code for MCF8316AEVM, only works in MCF8316A_GUI?

     

  • 0 in reply to Allen Lu
    TI__Genius 9210 points

    Hi Allen,

    Please see this E2E FAQ for MSP430 Firmware and GUI compatibility. Because of changes and improvements to the serial UART communication protocol, the GUIs and MSP430 firmware are not cross compatible between the old and new GUIs.

    Regards,
    Eric C.