SPRACZ9A November   2021  – December 2022 TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1

 

  1.   Hardware Design Guide for F2800x Devices
  2.   Trademarks
  3. 1Introduction
  4. 2Typical F2800x System Block Diagram
  5. 3Schematic Design
    1. 3.1 Package and Device Decision
      1. 3.1.1 F2800x Devices
        1. 3.1.1.1 TMS320F28004x
        2. 3.1.1.2 TMS320F28002x
        3. 3.1.1.3 TMS320F28003x
        4. 3.1.1.4 TMS320F280013x
      2. 3.1.2 Migration Guides
      3. 3.1.3 PinMux Tool
      4. 3.1.4 Configurable Logic Block
    2. 3.2 Digital IOs
      1. 3.2.1 General Purpose Input/Outputs
      2. 3.2.2 Integrated Peripherals and X-BARs
      3. 3.2.3 Control Peripherals
      4. 3.2.4 Communication Peripherals
      5. 3.2.5 Boot Pins and Boot Peripherals
    3. 3.3 Analog IOs
      1. 3.3.1 Analog Peripherals
      2. 3.3.2 Choosing Analog Pins
      3. 3.3.3 Internal vs. External Analog Reference
      4. 3.3.4 ADC Inputs
      5. 3.3.5 Driving Options
      6. 3.3.6 Low-Pass/Anti-Aliasing Filters
    4. 3.4 Power Supply
      1. 3.4.1 Power Requirements
      2. 3.4.2 Power Sequencing
      3. 3.4.3 VDD Voltage Regulator
        1. 3.4.3.1 Internal vs. External Regulator
        2. 3.4.3.2 Internal LDO vs. Internal DC-DC Regulator
      4. 3.4.4 Power Consumption
      5. 3.4.5 Power Calculations
    5. 3.5 XRSn and System Reset
    6. 3.6 Clocking
      1. 3.6.1 Internal vs. External Oscillator
    7. 3.7 Debugging and Emulation
      1. 3.7.1 JTAG/cJTAG
      2. 3.7.2 Debug Probe
    8. 3.8 Unused Pins
  6. 4PCB Layout Design
    1. 4.1 Layout Design Overview
      1. 4.1.1 Recommend Layout Practices
      2. 4.1.2 Board Dimensions
      3. 4.1.3 Layer Stack-Up
    2. 4.2 Recommended Board Layout
    3. 4.3 Placing Components
      1. 4.3.1 Power Electronic Considerations
    4. 4.4 Ground Plane
    5. 4.5 Analog and Digital Separation
    6. 4.6 Signal Routing With Traces and Vias
    7. 4.7 Thermal Considerations
  7. 5EOS, EMI/EMC, and ESD Considerations
    1. 5.1 Electrical Overstress
    2. 5.2 Electromagnetic Interference and Electromagnetic Compatibility
    3. 5.3 Electrostatic Discharge
  8. 6Final Details and Checklist
  9. 7References
  10. 8Revision History

Communication Peripherals

The F2800x devices contain varying numbers of the following communication peripherals:

  • Controller Area Network (CAN/DCAN)
  • Modular Controller Area Network (MCAN/CAN FD)
  • Inter-Integrated Circuit (I2C)
  • Power Management Bus (PMBus) Interface
  • Serial Communication Interface (SCI)
  • Serial Peripheral Interface (SPI)
  • Local Interconnect Network (LIN)
  • Fast Serial Interface (FSI)
  • Host Interface Controller (HIC)

Because of the nature of these peripherals and the different means through which they communicate, each system must be designed with the intended comm peripheral support in mind. Board-level interfaces, which include I2C, PMBus, and SPI, are connected to other devices, either on the board or through the system. Because these drivers are normally run directly, be sure to pay close attention to the drive capability and trace length. These factors depend on the selected frequency of these signals.

When making use of CAN, it is recommended to implement an external oscillator on the board as opposed to using the internal oscillator. Depending on the required CAN parameters like bit time settings, bit rate, bus length, and propagation delay, the accuracy of the on-chip zero-pin oscillator may not meet the requirements of the CAN protocol. More information about this can be found in Section 3.6.1 as well as the Programming Examples and Debug Strategies for the DCAN Module.

Notably for I2C, it is recommended that the SDAA and SCLA pins are pulled high using external pull-up resistors. Too strong of a pull-up (smaller resistor value) prevents the I2C pins from effectively being driven low, whereas too weak of a pull-up (larger resistor value) can impact the communication speeds. This value should be selected based on a compromise between power consumption and speed. To calculate the idea pull-up resistor range, refer to application report I2C Bus Pullup Resistor Calculation.

Interfaces that can connect two or more boards running under different processors include SCI, CAN, LIN, and FSI. These ports often require specialized transceiver parts that transform the electrical signal to combat noise and enable communication with the ports on other devices. When using a communication transceiver, some transceivers may require pull-up resistors on the communication pins of the MCU. Verify this requirement with the transceiver's data sheet.

GUID-20211103-SS0I-T1KQ-V4SF-ZQ6QGQP2V4SL-low.png Figure 3-5 CAN Transceiver in LAUNCHXL-F280049C
GUID-EE4C6087-E785-4C33-A164-7A5EF19F49C2-low.gif Figure 3-6 Typical RS-232 Transceiver

The SCI communication peripheral is a 2-wire asynchronous serial port with two external pins, SCITXD (SCI transmit-output) and SCIRXD (SCI receive-input). This protocol is commonly referred to as UART, and the protocol on the C2000 devices use the standard NRZ format. For some transceiver implementations, it is recommended to have a pull-up resistor on the SCI-RX pin to allow for the signal to return to high logic level without being driven. This prevents that GPIO pin from floating between values which would lead to errors and increased current consumption. Verify this pull-up resistor requirement with the data sheet of the specific transceiver being used. The pull-up resistor is especially necessary when using some types of transceivers to ensure deterministic operation of the SCI module. This resistor value should be selectively chosen and tested within the system, as the ideal value is highly dependent on the particular application. Too weak of a pull-up value (larger resistance) would prevent the resistor from actually pulling up a tri-stated or floating output from another device. Likewise, too strong of a pull-up value (smaller resistance) would prevent the output signal from toggling from the other device. A good starting point for experimenting this value would be 10 kΩ. For more information about debugging and troubleshooting SCI transmissions, see the SCI FAQ Thread on E2E.

For additional reference material for various communication peripheral protocols, see the following documentation: