TI CC1352P Launchpad
Last updated
Was this helpful?
Last updated
Was this helpful?
The Texas Instruments CC1352P Launchpad is a development board equipped with the multiprotocol wireless CC1352P microcontroller. The Launchpad, when paired with the BOOSTXL-SENSORS booster packs, is fully supported by Edge Impulse, and is able to sample accelerometer & microphone data, build models, and deploy directly to the device without any programming required.
If you don't have either booster pack or are using different sensing hardware, you can use the Data forwarder to capture data from any other sensor type, and then follow the [Running your impulse locally]/run-inference/cpp-library/) tutorial to run your impulse. Or, you can clone and modify the open source firmware-ti-launchxl project on GitHub.
The Edge Impulse firmware for this development board is open source and hosted on GitHub: edgeimpulse/firmware-ti-launchxl.
To set this device up in Edge Impulse, you will need to install the following software:
Install the desktop version for your operating system here
Add the installation directory to your PATH
See Troubleshooting for more details
On Linux:
GNU Screen: install for example via sudo apt install screen.
Problems installing the Edge Impulse CLI?
See the Installation and troubleshooting guide.
With all the software in place it's time to connect the development board to Edge Impulse.
To interface the Launchpad with sensor hardware, you will need to either connect the BOOSTXL-SENSORS to collect accelerometer data, or the CC3200AUDBOOST to collect audio data. Follow the guides below based on what data you want to collect.
Accelerometer Hardware Configuration Guide
Connecting the BOOSTXL-SENSORS board to the Launchpad is simple. Just orient the sensor board such that the 3V3 and GND markings on the booster pack line up with the Launchpad, and then attach the booster pack to the top header pins of the Launchpad, as shown below:
Extra Hardware Required
You will need five extra 0.1" jumper wires to connect the CC3200AUDBOOST to the Launchpad, as described in the Texas Instruments documentation.
The CC3200AUDBOOST board requires modifications to interface properly with the CC1352P series of Launchpads. The full documentation regarding these modifications is available from Texas Instruments in their Quick Start Guide, and a summary of the steps to configure the board are shown below.
Disconnect conflicting pins on the Launchpad.
Pins 26-30 on header J3 conflict with the CC3200AUDBOOST pins and need to be disconnected. To do this easily, TI recommends bending the pins down as shown below.
Launchpad modifications are compatible across booster packs
All Edge Impulse supported booster packs do not use pins 26-30 on header J3. If you have modified your Launchpad to interface with the audio booster pack, you can leave these pins disconnected when connecting other boards.
Connect jumper wires to the required pins
The pin connections shown below are required by TI to interface between the two boards. Connect the pins by using jumper wires and following the diagram. For more information see the CC3200AUDBOOST User Guide and Quick Start Guide
With the pins connected, your board should appear as shown below.
Align the P1 pin on the booster pack with 3V3 pin on the Launchpad, and connect the two boards together.
Using Audio and Accelerometer Hardware Simultaneously
In most cases it is possible to connect the sensor and audio booster pack at the same time. Allowing you to quickly switch between accelerometer and audio data collection. The primary constraint is that the BOOSTXL-SENSORS board must not have the TMP007 temperature sensor soldered on, as this conflicts with the audio interface when both booster packs are connected.
Ensure that the TMP007 temperature sensor is not present on the sensor booster pack. The board should have an unpopulated footprint for U5 as shown below:
Perform all modifications to the Launchpad and audio booster pack described in the Audio Hardware Configuration Guide
Connect the BOOSTXL-SENSORS booster pack directly to the Launchpad.
Connect the audio booster pack on top of the sensors booster pack. The final board should appear as shown below:
Use a micro-USB cable to connect the development board to your computer.
The development board does not come with the right firmware yet. To update the firmware:
Download the latest Edge Impulse firmware, and unzip the file.
Open the flash script for your operating system (flash_windows.bat, flash_mac.command or flash_linux.sh) to flash the firmware.
Wait until flashing is complete, and press the RESET button once to launch the new firmware.
From a command prompt or terminal, run:
This will start a wizard which will ask you to log in, and choose an Edge Impulse project. If you want to switch projects run the command with --clean.
Which device do you want to connect to?
The Launchpad enumerates two serial ports. The first is the Application/User UART, which the edge-impulse firmware communicates through. The other is an Auxiliary Data Port, which is unused.
When running the edge-impulse-daemon you will be prompted on which serial port to connect to. On Mac & Linux, this will appear as:
Generally, select the lower numbered serial port. This usually corresponds with the Application/User UART. On Windows, the serial port may also be verified in the Device Manager
If a selected serial port fails to connect. Test the other port before checking troubleshooting for other common issues.
Alternatively, recent versions of Google Chrome and Microsoft Edge can collect data directly from your development board, without the need for the Edge Impulse CLI. See this blog post for more information.
That's all! Your device is now connected to Edge Impulse. To verify this, go to your Edge Impulse project, and click Devices. The device will be listed here.
With everything set up you can now build and run your first machine learning model with these tutorials:
Looking to connect different sensors? The Data forwarder lets you easily send data from any sensor into Edge Impulse, and you can [run your impulse locally]/run-inference/cpp-library/) with custom firmware or sensor data.
Failed to flash
If the UniFlash CLI is not added to your PATH, the install scripts will fail. To fix this, add the installation directory of UniFlash (example /Applications/ti/uniflash_6.4.0 on macOS) to your PATH on:
If during flashing you encounter further issues, ensure:
The device is properly connected and/or the cable is not damaged.
You have the proper permissions to access the USB device and run scripts. On macOS you can manually approve blocked scripts via System Preferences->Security Settings->Unlock Icon
If on Linux you may want to try copying tools/71-ti-permissions.rules to /etc/udev/rules.d/. Then re-attach the USB cable and try again.
Alternatively, the gcc/build/edge-impulse-standalone.out binary file may be flashed to the Launchpad using the UniFlash GUI or web-app. See the Texas Instruments Quick Start Guide for more info.
