GitHub

Hardware / Bluetooth, Zigbee and Thread / Step 2 of 2

LP-EM-CC2755P10 (CC2755P10)

The CC2755P10 is a wireless microcontroller in TI's CC27xx family: 96 MHz Arm Cortex-M33, 1 MB of flash, 162 kB of RAM, BLE 6.0, Zigbee 3.0, Thread, Matter.

CC2755P1096 MHzLP-EM-CC2755P10

Quick facts

BoardLP-EM-CC2755P10
ChipCC2755P10
CoreCortex-M33 + FPU, TrustZone-M
Clock96 MHz
Flash1 MB
RAM162 kB
RadioBLE 6.0 (qualified, Channel Sounding), Zigbee 3.0 (certified), Thread, Matter, proprietary 2.4 GHz, multi-protocol
Notable peripheralsHSM (AES-256, ECC-521, RSA-3072, SHA-2-512); 96 kB flash reserved for HSM firmware; CDE + APU math accelerator; +20 dBm PA (143 mA at +20 dBm); 12-bit ADC 1.2 Msps, 8 inputs; 2 UART, 2 SPI, I2C, I2S
On-board debug probeSold separately (LP-XDS110ET at TI.com)
Where to buyTI.com
Toolchains that ranTI compilers, FreeRTOS, ESPHome, CCStudio

Get it running

  1. Clip the LP-XDS110ET probe onto the board and plug the probe's USB cable into your computer.

  2. In Chrome or Edge, open the browser bench and click Connect.

  3. Pick Bluetooth light: set its colors from this page, no cable and click Flash. The page writes it to the board.

    You should see: The LEDs change a moment after you tap a color or a pattern.

    The board needs the light program on it once: the button below puts it there.

What works

  • CoreMark: 426.31 (4.44 per MHz) (TI Arm Clang, bare metal, -O3; 96 MHz; 3 runs)
  • Flash to Bluetooth advertising: 0.90 s
  • Bluetooth connect and discover services: 0.55 s (Mac as central through bleak; connect and discover services; 3 runs)
  • Boot to joined network: 5.7 s (2 runs)
  • Radio command to state change, median: 87 ms
  • RAM left after linking the radio stack: 137.1 kB (same build; 162 kB SRAM; link only, not flashed)
  • Interrupt latency, pend to first handler line: 21 cycles (bare metal; 96 MHz; 3 runs)
  • GPIO toggle: 3.99 cycles (bare metal, -O3; 96 MHz; 3 runs)
  • Blink image size: 7 kB of flash, 10.1 kB of RAM (bare metal)
  • Room-occupancy AI model, one inference: 0.952 ms (-O2; 96 MHz; 3 runs)

Download every result for this board (CSV), or compare it on this board on the Benchmarks page.

Projects and ports that ran here

Fixes

  • If you see FRL-E099 FAILED: KeyError: 'deviceid' from frl identify --board cc2755p10, use frl identify --probe <serial>; it names the chip (CC2755P105E0WRHAR).
  • If you see the portable app on this board (TI Drivers), build with portability/three-ways/tidrivers/build_cc2755p10.sh (SysConfig 1.28.0 here).
  • If you see Error -2001 right after a TI example such as zigbee/rf_test ran, with debug authentication "not required", unplugging the probe's USB for ten seconds is not run; docs/remote-board-recovery.md shows how to read the boot status.
  • If you see undefined node label 'boosterpack_spi' from west build --shield ti_bp_cc140xp, build with no --shield; pass -DEXTRA_DTC_OVERLAY_FILE=ports/cc1407p-zephyr/boards/lp_em_cc2755p10.overlay.
  • If you see a CC1407P host image prints nothing, or stops after its first line, fit the radio (red LED jumper off, wire from header pin 23 to pin 10) or add your own timeout.
  • If you see TI Drivers example from the CC2340R5 on this board, copy the CC2755P10 project and overwrite its .c files; the log example needs 3,000,000 baud, every other UART example 115200.
  • If you see sysconfig_cli.sh: not found in ot-ti's script/build, export TI_SYSCONFIG_ROOT.
  • If you see <cerrno> tried including <errno.h> but didn't find libc++'s <errno.h>, use -idirafter on source/ti/posix/ticlang for C++ files.

Every fix for this board in its FAQ

For AI assistants

Point your assistant at this board's AGENTS.md (build, flash and fix notes) and the repository's llms.txt (the index).

Sources: cc2755p10/README.md, cc2755p10/AGENTS.md, cc2755p10/FAQ.md, data/results/cc2755p10.csv, site/data/portfolio.json, site/data/projects.json, site/data/ports.json.