LAUNCHXL-F28379D Overview User's Guide

4.1 Code Composer Studio

4.1.1 Download the Required Software
Code Composer Studio IDE can be downloaded for free for use with the XDS100v2 debug probe on the C2000 LaunchPad. The software is available on the C2000 LaunchPad page at ti.com/launchpad. This site also provides access to c2000Ware, which includes drivers, examples, and other essential support software.

4.1.2 Install the Software
Install Code Composer Studio and the C2000Ware package after downloading.

4.1.3 Install the Hardware
Connect the supplied USB cable to the C2000 LaunchPad and your computer. Windows will detect the hardware and prompt for driver installation. Allow Windows to search for and install the drivers for the integrated XDS100v2 debug probe. Once drivers are successfully installed, the LaunchPad is ready for use.

5.1 Getting Started

Upon the first power-on, the LAUNCHXL-F28379D board automatically starts a demo application. Connect the board to a USB port using the mini-USB cable. LEDs D9 and D10 will blink, indicating the device is active. If the demo does not start, try setting switch S1 to positions 1-UP, 2-UP, 3-DOWN and resetting the board.

5.2 Demo Application, ADC Sampling

The LAUNCHXL-F28379D comes with a pre-programmed TMS320F28379D device. When powered via USB, the demo starts with an LED blink sequence, then switches to an ADC sampling mode. Every second, the ADC samples pin ADCIN14. If the sample is above mid-scale (2048), LED D10 (blue) illuminates. If below mid-scale, LED D9 (red) illuminates.

ADC sample information is also displayed via the USB/UART connection. To view this data:

1. Determine the COM port associated with the LaunchPad in Windows Device Manager (under Ports (COM & LPT)).
2. Download and open a serial terminal program like PuTTY (available at http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html).
3. Configure the serial terminal with the correct COM port and settings: 115200 Baud, 8 data bits, no parity, 1 stop bit.
4. Reset the LaunchPad (S3) and observe the serial terminal for the TI logo in ASCII art.

5.3 Program and Debug the ADC Sample Demo Application

The project and source code for the C2000 Delfino LaunchPad demo are included in the C2000Ware package. Access it via the TI Resource Explorer in Code Composer Studio, navigating to c2000Ware > device_support > f2837xd > examples > LAUNCHXL-F28379D > LaunchPad Demo Application. Follow the steps in the resource explorer to import, build, debug, and run the application.

6.1 ADC Resolution

The F28379D features four independent 16-bit/12-bit ADCs (ADCA, ADCB, ADCC, ADCD). Resolution is software-selectable. ADCA, ADCB, and ADCC are routed to BoosterPack headers, typically used in 12-bit mode with Single Ended (SE) inputs. ADCD is routed to a side connector with a differential amplifier for 16-bit mode with Differential Ended (DE) inputs.

6.2 Power Domain

The LaunchPad has multiple power domains for JTAG isolation. Jumpers JP1, JP2, and JP3 control JTAG isolation and supply GND, 3.3 V, and 5 V. Other jumpers provide alternative powering methods.

Supplying 3.3 V

Configuration 1 derives 3.3 V from the USB's 5 V via an on-board regulator, connecting it to the device side. This is a non-isolated configuration. Configuration 2 isolates the debugger and USB from the device, requiring an external 3.3 V source via BoosterPack headers or J10.

Supplying 5 V

Configuration 1 (Not Isolated): JP2 and JP3 are connected, supplying 5 V directly from USB to the device side. JP6 should not be connected to avoid contention. This 5 V can power BoosterPack headers.

Configuration 2 (Isolated): 3.3 V is supplied externally (not via JP1). JP6 is connected, using the on-board step-up regulator to provide 5 V. Ensure no other 5 V source is connected to BoosterPack headers or J16.

Configuration 3 (Isolated): JP2 and JP3 are not connected. JP6 is disconnected. 5 V must be supplied externally via BoosterPack headers or J16. This configuration does not rely on the 3.3 V supply for 5 V generation.

6.3 Boot Mode Selection

The F28379D device has a boot ROM that checks specific pins to determine the boot mode. Switch S1 configures these pins:

Note: The debug probe requires the device to be in emulation boot mode (TRST switch in the UP-1 position).

6.4 Connecting a BoosterPack

The F2837xD LaunchPad is designed for easy hardware development with BoosterPacks, add-on boards that connect via 0.1-in (2.54-mm) grid connectors. BoosterPacks can access all GPIO and analog signals. Pinouts are detailed in Section 7.1.

6.5 GPIO Routing Between BoosterPack and I/O Expansion Headers

The LaunchPad includes a high-density connector (J9) on the backside for I/O expansion. Many EMIF1, SPI, and I2C signals are available on J9 and also on BoosterPack headers. On Revision 1.x boards, GPIO40 and GPIO41 were dual-mapped, configurable via jumpers J11 and J13.

Revision 2.0 boards allow independent routing of GPIO29, GPIO40, GPIO41, GPIO52, GPIO104, and GPIO105 to either BoosterPack headers or J9 using 0-ohm resistors. By default, these signals are routed only to the BoosterPack headers. Table 4 details the resistor configuration for routing these signals.

7.1 Device Pin Out

Tables 5 through 8 list the pinout and pin multiplexing (mux) options for the C2000 LaunchPad. Additional muxing options are available in the TMS320F2837xD Dual-Core Delfino Microcontrollers Data Manual (SPRS880).

(1) For full pin muxing table and additional options, see the TMS320F2837xD Dual-Core Delfino Microcontrollers Data Manual.

(2) This signal is also routed to the IO expansion header, J9. See Section 6.5 for configuration.

(1) For full pin muxing table and additional options, see the TMS320F2837xD Dual-Core Delfino Microcontrollers Data Manual.

(2) This signal is also routed to the IO expansion header, J9. See Section 6.5 for configuration.

(1) For full pin muxing table and additional options, see the TMS320F2837xD Dual-Core Delfino Microcontrollers Data Manual.

(2) This signal is also routed to the IO expansion header, J9. See Section 6.5 for configuration.

(1) For full pin muxing table and additional options, see the TMS320F2837xD Dual-Core Delfino Microcontrollers Data Manual.

7.2 Schematics

The following figures illustrate the LAUNCHXL-F28379D Rev 2.0 schematic. Schematics for Rev 1.2 are available in C2000Ware.

• Figure 2 (P01_Block Diagram): Shows the overall system architecture, including major functional blocks like the MCU, debug probe, power management, and connectors.
• Figure 3 (P02_XDS100v2): Details the schematic for the on-board XDS100v2 debug probe, including the USB interface, FTDI chip, and isolation circuitry.
• Figure 4 (P03_Power): Illustrates the power supply circuitry, featuring voltage regulators, power distribution, and input/output power connections.
• Figure 5 (P04_ADCIND): Shows the analog-to-digital converter (ADC) input conditioning, including differential amplifier connections and SMA connectors.
• Figure 6 (P05_PWM-DAC): Depicts the Pulse Width Modulation (PWM) and Digital-to-Analog Converter (DAC) output circuitry, including LED drivers.
• Figure 7 (P06_BoosterPack Headers): Presents the pinout diagrams for the BoosterPack expansion connectors (J1-J10), detailing the signals available on each pin.
• Figure 8, 9, 10 (P07_F28379D-PWR, P08_F28379_IO1, P09_F2837_IO2): These figures provide detailed pinout and signal routing for the TMS320F28379D microcontroller and its various interfaces, including GPIO multiplexing options.
• Figure 11 (P10_EX-Headers): Shows the schematics for additional connectors like QEP (Quadrature Encoder Pulse), CAN, and level shifters.

7.3 PCB Layout

Figures 12 through 21 display the LAUNCHXL-F28379D Rev 2.0 PCB layout for various layers, including Top, GND, Route1, Route2, VDD, Bottom, Silkscreen Overlays, and Pad Masters. Gerber files and layout for Rev 1.2 are available in C2000Ware.

7.4 Bill of Materials (BOM)

Table 9 lists the Bill of Materials for the LAUNCHXL-F28379D.