The Delfino F28379D controlCARD (TMDSCNCD28379D) from Texas Instruments (TI) provides a great
way to learn and experiment with the F2837x device family within TI’s C2000™ family of microcontrollers
(MCUs). This 180-pin controlCARD is intended to provide a well-filtered robust design that is capable of
working in most environments. This document provides the hardware details of the F28379D controlCARD
and explains the functions, locations of jumpers, and connectors present on the board.
Delfino, C2000, Code Composer Studio are trademarks of Texas Instruments.
All other trademarks are the property of their respective owners.
1Introduction
As of January 2016, all kits based on the F28377D MCU will now be replaced with the new F28379D
superset device. These two MCUs are identical except for the addition of the CLB on the F28379D MCU
to enable Position Manager. If the CLB is not a requirement in your application, that feature can be left
untouched and the MCU will perform like the F28377D.
Each controlCARD comes with a Hardware Developer’s Kit, a full set of files necessary to evaluate and
develop with a C2000 device. These files include:
•Schematics – Designed in Mentor PADS Logic
•Bill of Materials (BOM)
•Layout PCB files - Designed in Mentor layout
•Gerber files
NOTE: This kit is designed to explore the functionality of the F2837x microcontroller. Even though
the controlCARD can be treated as a good reference design, it is not intended to be a
complete customer design. Full compliance to safety, EMI/EMC, and other regulations are
left to the designer of the final customer’s system.
www.ti.com
List of Tables
2Errata
Current revision of controlCARD as of 2-Oct-2015: PCB rev - R1.3, ASSY rev - B.
NOTE: The Letter B on the controlCARD's Serial Number sticker denotes ASSY rev – B.
2.1Warnings/Notes/Errata
Notes for all controlCARDs:
•The F28379D controlCARD supports USB host/device connectivity. However, the micro-USB port, J8,
is not isolated from the board ground. Care should be taken when this controlCARD is being used in a
high-power application and this USB port is also being used. Note that external USB isolation buffers
may be required for these types of applications.
•The F28379D Experimenter’s Kit ships with a USB cable and is designed to be powered via USB.
However, in extreme cases the board/controlCARD may require more power than the 5V @ 500mA a
computer’s USB port can provide (<0.01% of use cases). This is especially true when additional
circuitry has been added to the docking station.
In such cases, it is recommended to use an external 5V power supply (2.5 mm inner diameter x 5.5
mm outer diameter) and plug it into J1. A compatible supply could be the: Phihong PSAC05R-050(P)R-C2 + Phihong RPBAG.
•In Boot-from-SCI mode the MCU will, by default, expect GPIO84 and GPIO85 to be the IO pins
responsible for sending the program to the device. These GPIOs are different from the GPIOs that
connect to the isolated USB-to-serial interface via the FTDI chip, which uses GPIO28 and GPIO29. To
use GPIO28 and 29 instead:
– Change the boot mode to Get Mode and then, in your main flashed code, you can decide to call the
bootloader for SCIBoot IOOption2 (in the bootROM) always, or based on whatever is desired.
– Change the boot mode to Get Mode and configure the OTP such that SCIBoot IOOption2 is called.
This is really only an option if you always want to boot from SCI or Parallel GPIO, because you will
be overwriting your ability to boot from Flash.
– With an emulator connected (TRSTn = 1), registers can be set such that SCIBoot’s IOOption2 boot
mode is called.
For more information, see the device-specific TRM.
•R83 on the controlCARD is populated to allow a customer to evaluate the controlCARD without a
baseboard if desired. Because R83 is populated, the controlCARD putd more capacitance on the USB
5V supply than the USB specification allows. R83 should be removed in order to meet the
specification.
2.2Warnings About Specific controlCARD Revisions
Warnings about R1.0a revision F28377D controlCARDs:
•Among many other changes made, the pinout of the R1.1 F28377D controlCARD is different from the
pinout of the pre-release R1.0a controlCARDs. When porting code, see the kit documentation and
schematics in the C2000Ware install on your computer in the /boards/controlCARDs subdirectory.
Warnings about R1.1 and earlier F28377D controlCARDs:
•The F28377D MCU is not 5 V tolerant. Because of this, some additional protection is needed between
the USB port J8 and the MCU. In particular, resistor R72 should change from 0R0 to 100K and resistor
R74 should change from 0R0 to 10K. This effectively limits the voltage/current received by the MCU
pin. This issue was fixed in R1.1a and later revision controlCARDs.
•If used, the crystal X1 should be acceptable in most applications. However, it can fail under some
worst case conditions. To assure proper operation, see the TMS320F2837xD Dual-Core Delfino™
MCUs Silicon Errata. This issue was fixed in R1.1a and later revision controlCARDs.
•Several name changes were made to pins on the device and are now reflected in R1.1a controlCARD
documentation. No functionality was affected.
Warnings about R1.1a and earlier F28377D controlCARDs:
•The circuitry used to drive the C2000 MCU’s voltage references is not ideal. Instead, it is
recommended that users use the voltage reference driving circuitry found in the R1.3 controlCARD.
Warnings about R1.3 of F28379D controlCARD:
•R51-R54 were mistakenly populated with 100 MΩ resistors instead of 100 mΩ resistors. With 100 MΩ
resistors used, the voltage references for the analog-to-digital converters (ADCs) may not be held
adequately constant and the accuracy/precision of ADC results may be affected during
sampling/conversion. It is recommended that customers replace R51-R54 with 100 mΩ, 0603, 5%
tolerance (or better) resistors. For evaluation of the controlCARD in a lab environment, it is also
acceptable to short R51-R54 using 0 Ω resistors or solder bridges, however, populating with 100 mΩ is
preferred. For more information, see the following E2E post:
•Delfino F28379D Microcontroller – High performance C2000 microcontroller is located on the
controlCARD.
•180-pin HSEC8 Edge Card Interface – Allows for compatibility with all of C2000’s 180-pin
controlCARD-based application kits and controlCARDs. Compatibility with 100-pin controlCARDs can
be accomplished using the TMDSADAP180TO100 adapter card (sold separately).
•Built-in Isolated JTAG Emulation – An xds100v2 emulator provides a convenient interface to Code
Composer Studio™ without additional hardware. Flipping a switch allows an external JTAG emulator to
be used.
•Connectivity – The controlCARD contains connectors that allow the user to experiment with USB, a
microSD card, and isolated UART/SCI with the F2837x MCU. A hi-density connector is also provided
to experiment with external memory.
•Key Signal Breakout – Most GPIO, ADC and other key signals routed to hard gold connector fingers.
•Robust Power Supply Filtering – Single 5 V input supply powers an on-CARD 3.3 V LDO. All MCU
inputs are then decoupled using LC filters near the device.
•ADC Clamping – ADC inputs are clamped by protection diodes.
•Anti-Aliasing Filters – Noise filters (small RC filters) can be easily added on several ADC input pins.
3.2Assumed Operating Conditions
This kit is assumed to run at standard room conditions. The EVM should run at approximately standard
ambient temperature and pressure (SATP) with moderate-to-low humidity.
3.3Using the controlCARD
In order for the controlCARD to work, the controlCARD’s MCU must be powered. This is most often done
by inputting 5 V through the HSEC connector via an accompanying baseboard. For example, if using a
docking station baseboard, 5VDC should be input into the docking station’s J1 or J17. Then, SW1 needs
to be toggled to the appropriate position.
Optionally, the MCU could also be powered via the micro-USB connector on the controlCARD.
Based on the way the controlCARD will be used, additional hardware settings are necessary, see Table 1.
www.ti.com
Table 1. Getting Started Reference
Debug Using CCS and the On-Card
A:SW1 (controlCARD)Position 1: ON (up)Position 1: OFF (down)Position 1: OFF (down)
A:J1 (controlCARD)Connect a mini USB cable between
SW1 (controlCARD)Position 1: OFF (up)
Baseboard’s JTAG
connector
(J2 on the Docking Station
baseboard)
A:J1 and your computer.
In CCS, use this target configuration:
TMS320F28379D device with an
xds100v2 emulator.
Position 2: ON (down)
Putting the C2000 device into Wait
Mode can reduce the risk of
connectivity issues.
---Connect an external emulator.---
xds100v2 Emulator
Debug Using CCS and an
External Emulator via the
Baseboard
------
Position 1: OFF (up)
Position 2: ON (down)
Putting the C2000 device into
Wait Mode can reduce the risk of
connectivity issues.
Set SW1 as desired
Standalone
(Boot from FLASH or other
boot mode)
Code Composer Studio is an Integrated Development Environment (IDE) used to debug and develop
software for the C2000 series of MCUs.
CCS can be downloaded from the following URL: http://processors.wiki.ti.com/index.php/Download_CCS.
For users new to C2000’s F28x7x series of devices and CCS, TI’s Technical Training Organization
provides several workshops (online and in person) that may be helpful:
The following PDF documents are provided to describe where each of the F2837x MCU’s pins will appear
on the controlCARD connector/docking station:
•TTMDSCNCD28379D_180cCARD_pinout_R1_3 – tells where each MCU pin will go on the HSEC
controlCARD connector or the 120/180-pin controlCARD docking station.
•TMDSCNCD28379D_100DIMmap_R1_3 – tells where each MCU pin will go to on the DIM100
controlCARD connector or the DIM100 docking station. This assumes that the TMDSADAP180TO100
adapter card is used.
More information on the controlCARD docking station can be found at the following locations:
All key examples for the F28379D MCU can be found within controlSUITE at:
\controlSUITE\device_support\f2837xD\
This example software package includes many projects that allow the user to experiment with the ADC,
PWM, and other C2000 peripherals.
4Special Notes on Connectivity
4.1xds100v2 Emulator and SCI/UART Connectivity
The F28379D controlCARD provides emulation and USB-to-UART adapter functionality on the
controlCARD. This allows for a convenient method to debug and demo the F2837x MCU.
Note that the FTDI chip, its support circuitry, and associated isolation components are placed in Macro A,
the left section of the controlCARD. Each of these components contains an additional A within the
component reference designator (that is, A:R2 for resistor 2 in Macro A), see Figure 2.
Each F28379D controlCARD’s xds100v2 is programmed with a fixed serial number. If a debug session
needs to involve two or more F28379D controlCARDs, each controlCARD needs to have a unique serial
number and some need to be reprogrammed, see:
The configuration of the switches on A:SW1 determine whether the on-board emulator is active, whether
an external emulator can be used, or whether the device will boot from FLASH/peripherals, see Table 2.
Getting Familiar With the controlCARD
Figure 2. xds100v2 Emulation Circuitry and Isolation Circuitry is Denoted by A
External connector, J9, can be used to connect the controlCARD to another board. The ability to connect
up to EMIF2, SPI-C, I2C-A, and 2 GPIO are provided – although any peripheral mux option provided on
these GPIOs is technically possible.
Note that the GPIOs (122-125) that attach to the SPI portions of this connector, also go to the microSD
connector. At any specific time, only one should be used to avoid contention.
Note that the GPIOs (53-68) that attach to the EMIF data lines of this connector and GPIOs (91 and 92)
that attach to the I2C portions of this connector also go to the baseboard via the HSEC connector. These
GPIOs should either be used to connect to the baseboard OR utilized on this header to avoid contention.
Figure 3 shows the connector that mates with J9 is the Hirose DF40HC(4.0)-60DS-0.4V(51).