CC3220SF LAUNCHXL Settings and Resources
The CC3220SF LAUNCHXL board contains a CC3220SF device.
Jumper Settings
- Set RX and TX to provide UART communications via the onboard USB debugger.
Board Resources Used in Driver Examples
The following table lists the Board names of the resources used by the driver examples, and their corresponding pins. Note that there may be other resources configured in the board files that are not used by any driver example. Only the example resources are listed in the table.
Board Resource | Pins |
---|---|
Board_ADC0 |
P59 (Connect to analog signal) |
Board_ADC1 |
P60 (Connect to analog signal) |
Board_CAPTURE0 |
P04 |
Board_CAPTURE1 |
P05 |
Board_GPIO_LED0 |
P64 (LED EN must be jumpered) |
Board_GPIO_LED1 |
P64 (LED EN must be jumpered) |
Board_GPIO_LED2 |
P64 (LED EN must be jumpered) |
Board_GPIO_BUTTON0 |
P15 (SW2 ) |
Board_GPIO_BUTTON1 |
P04 (SW3 ) |
Board_I2C0 |
P01 - SCL , P02 - SDA |
Board_I2C_TMP |
P01 - SCL , P02 - SDA (SCL & SDA must be jumpered) |
Board_I2S0 |
P50 - XR1 , P53 - CLK , P62 - CLKX , P63 - FSX , P64 - XR0 |
Board_PWM0 |
P01 (LED EN must be jumpered) |
Board_PWM1 |
P02 (LED EN must be jumpered) |
Board_SD0 |
P06 - DATA , P07 - CLK , P08 - CMD |
Board_SDFatFS0 |
P06 - DATA , P07 - CLK , P08 - CMD |
Board_SPI0 |
P05 - CLK , P06 - MISO , P07 - MOSI , P08 - CS |
Board_UART0 |
P57 - RX , P55 - TX (UART provided through emulation, RX and TX must be jumpered) |
Board_UART1 |
P08 - RX , P07 - TX |
BoosterPacks
The following examples require BoosterPacks.
Example | BoosterPack |
---|---|
fatsd | SD Card BoosterPack |
fatsdraw | SD Card BoosterPack |
i2secho | Audio BoosterPack |
portable | BOOSTXL-SENSORS Sensors BoosterPack (optional) |
sdraw | SD Card BoosterPack |
For the fatsd, fatsdraw and sdraw examples, modifications must be made to the SD Card BoosterPack. See the section below for details.
SD Card BoosterPack Modifications
Scratch out the following traces:
- 1 -
SJ3
- 2 -
SJ1
- 3 -
SJ4
- 4 -
SJ2
Solder shorts for the following:
- 5 -
J2.4
- 6 -
J2.5
- 7 -
J2.8
ADC Examples Pin Connections
Important: The inputs to the ADC are required to be well within 1.4V to avoid clipping, which will cause distortion. The ADC inputs can be damaged if an input voltage higher than 1.8V is applied to these pin. The 1.8V hard limit must be considered from both the SW and HW points of view. Always add a resistor divider/buffer to bring down the measurement signal voltage to within the ADC limits. See the CC32xx ADC Appnote for more details.
The CC3220SF LAUNCHXL has a protective circuit to allow an input of 3.3VDC. The 5V
should NOT be used for this may damage the ADC inputs. For testing, the following jumpers must be present: J5
= OPAMP EN
, J10
= GND
, J13
= BRD
.
Note: There are duplicate pins P59 and P60 on the board. Choose the ones connected to the Booster Pack headers (the pins not connected to the Booster Pack headers have an asterisk next to them).
Peripherals Used
The following list shows which CC3220SF peripherals are used by driver and kernel applications. Driver examples control which peripherals (and which ports) are used.
- TI-RTOS Kernel (SYS/BIOS). Uses the first general-purpose timer available and that timer’s associated interrupts. Generally, this will be Timer_A0. The TI-RTOS Kernel manages the interrupt controller statically without an interrupt dispatcher.
- Drivers.
- I2C: The I2C driver is configured to support various BoosterPacks.
- PWM: The PWM driver uses the onboard LEDs (P01 and P02). These pins are configured for the PWM driver. While these pins can also be used by the GPIO driver, your application’s board file must ensure that the pins are not simultaneously used by the GPIO and PWM drivers.
- SD: The SD driver is used to communicate with a SD card.
Board_SD0
is used to send data to-and-from the SD card. - SDFatFS: The SDFatFS driver relies on a SD driver instance to communicate with a SD card;
Board_SDFatFS0
uses theBoard_SD0
driver instance. - SPI: The SPI driver is configured for SPI communications.
- Timer: The Timer and PWM driver uses the timer peripheral.
- UART: The UART driver uses UART0, which is attached to the onboard emulator to facilitate serial communications.
- Watchdog: The Watchdog driver example uses the Watchdog Timer peripheral.