• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 181 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28377S: SysConfig support for LaunchPadXL F28377S

A K
Prodigy 20 points

Part Number: TMS320F28377S
Other Parts Discussed in Thread: SYSCONFIG, , C2000WARE, TMS320F28377D

Hi,

the SysConfig tool seems really helpful for configuring peripherals.  Unfortunately, it seems that it does not support the LaunchPadXL F28377S board, only the F28377D.

I was wondering if it possible to add this somewhat older board to SysConfig.

Alternativerly, can I find some resource that tells me the difference between the LaunchPadXL F28377S and F28377D?

Thank you for your assistance,

Alex

  • 0
    Prodigy 20 points

    BTW, I'm running SysConfig 1.28.0+4712 under Linux.

  • 0
    Prodigy 20 points

    Actually, I was just able to run SysConfig with that board by loading gpio_ex2_toggle example, double-clicking on its gpio_ex2_toggle.syscfg file, changing the target to TMS320F28377S and adding the predefined symbol _LAUNCHXL_F28377S in the project properties.

  • +1 in reply to A K
    TI__Expert 6045 points

    Hi AK,

    Adding a new board to SysConfig is not something end users can directly do on their own — board support files for SysConfig are maintained and released by TI's C2000 team as part of C2000Ware. The F28377S device is supported in SysConfig (at the device level), but the specific LAUNCHXL-F28377S board profile may not be listed as a pre-configured board option.
    Your best course of action would be to:
    • Submit a feature request on the TI E2E C2000 forum asking TI to add the LAUNCHXL-F28377S board to SysConfig.
    • In the meantime, you can still use SysConfig with the TMS320F28377S device — just select the device (not a specific board) and manually configure the pin assignments to match the LaunchPad hardware.
      • Requires CCS v11 or later and C2000Ware v4.01.00.00 or later.

    2. Differences Between the LAUNCHXL-F28377S and LAUNCHXL-F28377D

    The key differences stem from the underlying chips — the TMS320F28377S (single-core) vs. the TMS320F28377D (dual-core):
    Feature TMS320F28377S TMS320F28377D
    CPU Architecture Single-core (1× C28x) Dual-core (2× C28x)
    ADC Throughput (12-bit) 3.5 MSPS per unit 14 MSPS (total, dual ADC)
    ADC Throughput (16-bit) 1.1 MSPS per unit 4.4 MSPS (total)
    CLA Clock 200 MHz 200 MHz
    Core Voltage 1.2 V 1.2 V
    I/O Voltage 3.3 V 3.3 V
    SPI Speed 50 MHz 50 MHz
    Board-level differences (LaunchPad hardware):
    • The LAUNCHXL-F28377S routes SCI-A through GPIO84 (TX) / GPIO85 (RX) to the onboard FTDI USB-to-serial chip.
    • The LAUNCHXL-F28377D (F28379D variant) uses GPIO42 (TX) / GPIO43 (RX) for its SCI connection.
    • The predefined symbol for the F28377S board is 
      _LAUNCHXL_F28377S
      , while the F28379D board uses 
      _LAUNCHXL_F28379D
      .
    The primary reason to use the F28377S is when a single-core design suffices and cost/simplicity is a priority. The F28377D is preferred for applications requiring dual-core execution (e.g., one core for control and one for communication/diagnostics).
    For a detailed hardware overview, you can refer to the LAUNCHXL-F28377S User's Guide (SPRUI25) on ti.com: https://www.ti.com/lit/ug/sprui25d/sprui25d.pdf
    Thanks,
    Ira