SLLU387 August   2024

 

  1.   1
  2.   Description
  3.   Get Started
  4.   Features
  5.   Applications
  6.   6
  7. 1Evaluation Module Overview
    1. 1.1 Introduction
    2. 1.2 Kit Contents
    3. 1.3 Specification
    4. 1.4 Device Information
  8. 2Hardware
    1. 2.1 Quick Start Guide
    2. 2.2 Hardware Setup
    3. 2.3 Hardware Connections Overview – MCF8315RRYEVM
    4. 2.4 Connection Details
    5. 2.5 MSP430FR2355 Microcontroller
    6. 2.6 LED Lights
    7. 2.7 User-Configurable Settings
  9. 3Software
    1. 3.1 Firmware and GUI Application
    2. 3.2 Downloading and Running Motor Studio
    3. 3.3 Downloading Code Composer Studio and Importing GUI Firmware Code
    4. 3.4 Using eZ-FET to Program the Onboard MSP430FR2355
  10. 4Hardware Design Files
    1. 4.1 Schematics
      1. 4.1.1 Main Supply and Pi Filter
      2. 4.1.2 Connectors and Interface
      3. 4.1.3 USB to UART
      4. 4.1.4 MCU Programming and Debug
      5. 4.1.5 MSP430FR2355 MCU
      6. 4.1.6 MCF8315 3-Phase Sensorless FOC Integrated Driver
      7. 4.1.7 Buck Regulator
      8. 4.1.8 Status LEDs
      9. 4.1.9 Switches and Speed Input
    2. 4.2 PCB Layouts
    3. 4.3 Bill of Materials (BOM)
  11. 5Additional Information
    1. 5.1 Trademarks

3.1 Firmware and GUI Application

The MCF8315RRYEVM includes a USB-to-UART interface, using a MSP430FR2355 microcontroller, that serves as a communication bridge between a host PC and the MCF8315 device for configuring various device settings and reading fault diagnostic information.

The MCF8315RRYEVM is supported on the Motor Studio GUI which can be used to configure the MCF8315 though this communication interface. The Motor Studio GUI simplifies the tuning process of the MCF8315 by offering guided tuning instructions, a virtual oscilloscope for real-time variable monitoring, and more. The latest version of the Motor Studio GUI can be downloaded on ti.com.

By default, the onboard MSP430 microcontroller already contains the firmware needed to communicate with the Motor Studio GUI. If there is a firmware update or the GUI does not connect to the EVM, then the user must flash the firmware code into the MSP430 by following the steps outlined in Section 3.4.

Flashing the firmware code onto the MSP430 requires an integrated development environment (IDE) and an eZ-FET Debug Probe. The following example uses the Code Composer Studio™ (CCS) IDE and the MSPEXP430FR2355 LaunchPad™ Development Kit to provide the eZ-FET Debug Probe.