SPRUJE4D August   2024  – June 2025 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Description
  3.   Get Started
  4.   Features
  5.   5
  6. 1Evaluation Module Overview
    1. 1.1 Introduction
    2. 1.2 Kit Contents
    3. 1.3 Specification
    4. 1.4 Device Information
  7. 2Hardware
    1. 2.1  Quick Start Setup
      1. 2.1.1 Configuration 1: Stand-alone Configuration
      2. 2.1.2 Configuration 2: C2000 controlCARD Compatibility Configuration Using HSEC180ADAPEVM
      3. 2.1.3 Configuration 3: Baseboard Configuration
    2. 2.2  Design Details
      1. 2.2.1 Power Tree
      2. 2.2.2 Clocking
      3. 2.2.3 Reset
      4. 2.2.4 Board ID EEPROM
    3. 2.3  Power Requirements
    4. 2.4  Configuration Options
      1. 2.4.1 Boot Mode Selection
      2. 2.4.2 ADC Voltage Reference Selection
      3. 2.4.3 MCAN-A Boot Support
      4. 2.4.4 FSI DLT Support
      5. 2.4.5 EtherCAT PHY Clock Selection
    5. 2.5  Header Information
      1. 2.5.1 Baseboard Headers (J1, J2, J3)
      2. 2.5.2 XDS Debug Header (J4)
      3. 2.5.3 DLT Header (J5)
    6. 2.6  Push Buttons
    7. 2.7  User LEDs
    8. 2.8  Debug Information
    9. 2.9  Test Points
    10. 2.10 Best Practices
  8. 3Software
    1. 3.1 Software Description
    2. 3.2 Software Installation
      1. 3.2.1 Install SDK
      2. 3.2.2 Install Additional Software
        1. 3.2.2.1 Install Python
        2. 3.2.2.2 Install OpenSSL
    3. 3.3 Software Development
    4. 3.4 Developing an Application
  9. 4Hardware Design Files
    1. 4.1 Schematics
    2. 4.2 PCB Layouts
    3. 4.3 Bill of Materials (BOM)
  10. 5Additional Information
    1. 5.1 Known Hardware or Software Issues
      1. 5.1.1 Usage Note Matrix
      2. 5.1.2 Advisories Matrix
      3. 5.1.3 Usage Notes
        1. 5.1.3.1 Parallel I/O Boot Can Cause Watchdog Timer Timeout if No Host Is Connected to EVM
        2. 5.1.3.2 Device GPIOs Dedicated to PMIC SPI Bus Should Be Used for SPI Function If Used On Baseboard
      4. 5.1.4 Advisories
        1. 5.1.4.1  MCU Flash Is Not Supported, All Code Must Execute From RAM
        2. 5.1.4.2  Incorrect Package Marking on MCU Package
        3. 5.1.4.3  Internal Oscillator (INTOSC2) on MCU Defaults to 6MHz
        4. 5.1.4.4  By Default, GPIO4 Configured as ERRORSTS by ROM Code and Driven High
        5. 5.1.4.5  MCU Fault State Possible When On-Board 25MHz Clock is Enabled
        6. 5.1.4.6  25MHz X1 Clock Is Disabled, INTOSC Must Be Used as MCU Clock Source and EtherCAT Is Not Supported
        7. 5.1.4.7  PMIC Monitoring of MCU Reset Signal (XRSN) Is Disabled
        8. 5.1.4.8  ADC VREFHIAB and VREFHICDE Incorrectly Shorted Together When S3 and S4 Are Both Set to Internal VREF Mode
        9. 5.1.4.9  Incorrect Voltage on VREFHIAB and VREFHICDE Pins When External VREF Mode Is Selected
        10. 5.1.4.10 MCU Reset Signal (XRSN) Can Remain Asserted on Power-On
        11. 5.1.4.11 FSI Signals on the Data Logging and Trace Connector (J5) May Interfere With Some Advanced Debuggers
    2. 5.2 Trademarks
  11. 6References
  12. 7Revision History

2.1.2 Configuration 2: C2000 controlCARD Compatibility Configuration Using HSEC180ADAPEVM

The backward compatibility configuration is used for cases that require the controlSOM to interface to a C2000 controlCARD compatible baseboard or docking station. A HSEC adapter board (HSEC180ADAPEVM) is required for this configuration. The HSEC adapter board is sold separately.

The HSEC adapter board provides these features:

  • Backward compatibility to C2000 controlCARD baseboard through standard 180-pin HSEC interface
  • 2 ˟ DP83826 10/100-Mbps Industrial Ethernet PHY with 2 x RJ-45 Ethernet jacks for EtherCAT evaluation
  • Fast serial interface (FSI) header
  • ADC filtering and ESD protection for dedicated analog HSEC pins

When the F29H85x controlSOM is used with the HSEC adapter board, power must be provided to the controlSOM and adapter board through the baseboard. An emulation debug-probe such as the XDS110ISO-EVM is required to provide debug connectivity to the MCU. The XDS110 debug-probe is sold separately.

In this configuration, Code Composer Studio™ IDE connects to the controlSOM using JTAG and enables software development. The XDS110 debug-probe also enumerates a virtual COM port (VCP) for communication with the MCU using UART.

Follow these steps to enable this configuration:

  1. The following equipment is required:
    1. F29H85x controlSOM (F29H85X-SOM-EVM)
    2. HSEC-180 adapter board (HSEC180ADAPEVM)
    3. C2000 controlCARD compatible baseboard or HSEC-180 docking station (TMDSHSECDOCK)
    4. XDS110 isolated debug probe (XDS110ISO-EVM)
    5. 2 USB Type-C® cables (3 meters or less)
    6. (Optional) DC 5V power supply
  2. Verify the switch settings are correct on each EVM.
    1. F29H85X-SOM-EVM:
      1. Use S1 to select the desired boot mode.
      2. Use S3/S4 to select the desired ADC voltage reference mode.
    2. XDS110ISO-EVM:
      1. S1 selects JTAG mode – set to JTAG mode.
      2. S2 enables UART/SPI connection – set RXD to ON mode and POCI to OFF mode.
  3. Attach the controlSOM to the HSEC-180 adapter board.
  4. Make sure the controlSOM is correctly oriented. The J1 header on the controlSOM must connect with the J1 header on the HSEC-180 adapter board.
  5. Insert the HSEC-180 adapter board into the baseboard or TMDSHSECDOCK docking station.
  6. Connect the XDS110ISO-EVM into the connector J7 of the HSEC-180 adapter board.
  7. Connect the USB cable into connector J5 on the XDS110 isolated debug probe. The XDS110 isolated probe is powered on.
  8. Connect a USB cable into the connector J17 on the TMDSHSECDOCK.
  9. Flip S1 to the USB-ON position on the TMDSHSECDOCK.
  10. Verify the power status LEDs (LED1 and LED2) on the controlSOM are turned on.
  11. The controlSOM is ready for use. Follow the steps in the Software section to get started developing software.
F29H85X-SOM-EVM C2000 controlCARD Compatibility Configuration Using HSEC180ADAPEVM Figure 2-2 C2000 controlCARD Compatibility Configuration Using HSEC180ADAPEVM

The prototype headers on the HSEC-180 docking station (TMDSHSECDOCK) provide easy access to many of the MCU ADC and GPIO signals. These headers can be used for prototyping custom firmware and for running F29H85X-SDK examples. TheF29H85x controlSOM pinout map provides a list of the MCU pins available on the TMDSHSECDOCK prototype headers.

Note: Not all MCU ADC and GPIO pins are available on the TMDSHSECDOCK prototype headers. Refer to the F29H85x controlSOM pinout map for more information.