Chip vs Chip

nRF52840 vs CC2652R

<\/script>\n
'; }, get iframeSnippet() { const domain = '{ SITE_DOMAIN }'; const type = '{ embed_type }'; const slug = '{ embed_slug }'; return ''; }, get activeSnippet() { return this.method === 'script' ? this.scriptSnippet : this.iframeSnippet; }, copySnippet() { navigator.clipboard.writeText(this.activeSnippet).then(() => { this.copied = true; setTimeout(() => { this.copied = false; }, 2000); }); } }" @keydown.escape.window="open = false" @click.outside="open = false">

Embed This Widget

Theme


      
    


    
    

      Widget powered by
      .
      Free, no account required.
    

  




    
    
Side-by-side comparison of nRF52840 and CC2652R BLE SoCs.

    
    

      
    

  


  
  
  

    
      

        A
        
nRF52840

      

      

    
    
      

        B
        
CC2652R

      

      

    
  

  

  
  

  






  
  

    
nRF52840 vs CC2652R: Nordic's BLE+Thread King vs TI's Concurrent Multi-Protocol Powerhouse


The nRF52840 and CC2652R represent perhaps the closest head-to-head competition in the professional multi-protocol BLE SoC market. Both support BLE 5.0, IEEE 802.15.4 (Thread and Zigbee), and are widely deployed in smart home hubs, building automation, and industrial IoT. The differences lie in RF core architecture, Flash capacity, USB support, and the approach to concurrent multi-protocol scheduling.




Overview


nRF52840 (Nordic Semiconductor) is a 64 MHz Arm Cortex-M4F with 1 MB Flash, 256 KB RAM, BLE 5.0 + 802.15.4, USB 2.0, and the Zephyr-based nRF Connect SDK ecosystem. Pre-certified modules are widely available from multiple vendors, and the chip is the highest-volume professional BLE SoC in production.


CC2652R (Texas Instruments) is a 48 MHz Arm Cortex-M4F paired with an autonomous Cortex-M0 RF core — a distinct architectural advantage. The RF core operates completely independently, supporting BLE 5.0, 802.15.4 (Zigbee and Thread), and proprietary 2.4 GHz simultaneously via TI's Dynamic Multi-protocol Manager (DMM). It has 352 KB Flash and 256 KB RAM.




Key Differences


    

  • RF core and concurrent protocols: CC2652R's autonomous M0 RF core executes the entire MAC and PHY stack independently, enabling truly concurrent BLE + Zigbee + proprietary operation via DMM without measurable impact on the application M4F. nRF52840 uses time-division multiprotocol scheduling on a shared core, which introduces connection-event timing constraints when switching between BLE and 802.15.4.
    • 

  • Flash: nRF52840's 1 MB Flash is nearly 3× the CC2652R's 352 KB, enabling robust dual-bank OTA with generous application firmware space alongside full BLE and Thread stacks.
    • 

  • Sleep current: CC2652R achieves approximately 0.85 µA vs nRF52840's approximately 1.5 µA — a modest but meaningful sleep power advantage for multi-year primary-cell nodes.
    • 

  • USB: nRF52840 has native USB 2.0 FS; CC2652R does not.
    • 

  • TX power: nRF52840 reaches up to +8 dBm; CC2652R up to +5 dBm — Nordic has a clear advantage for long-range outdoor BLE links using Coded PHY.
    • 

  • BLE features: Both support BLE 5.0 including 2M PHY and Coded PHY for long range, but neither supports LC3 codec and Auracast." data-category="LE Audio">LE Audio (BLE 5.2+) or Advertising">Direction Finding (BLE 5.1+) in these variants.
    • 

  • Ecosystem breadth: Nordic's community is substantially larger for standalone BLE and Thread product development; TI's community is stronger for Zigbee coordinator and proprietary RF designs.
    • 





Use Cases


When nRF52840 Excels


    

  • Large, OTA-upgradeable firmware: 1 MB Flash comfortably supports dual-bank OTA with application, bootloader, BLE stack, and Thread stack without flash-bank juggling.
    • 

  • USB BLE dongles and combo HID devices needing wired USB connectivity alongside BLE on a single chip.
    • 

  • Maximum TX power for outdoor BLE: +8 dBm combined with Coded PHY S=8 provides the best link budget for outdoor asset tracking.
    • 

  • Zephyr RTOS projects leveraging Nordic's extensive upstream Zephyr contributions and nRF Connect SDK examples.
    • 



When CC2652R Excels


    

  • Zigbee coordinator and router roles in dense home automation or building management networks — the RF core's deterministic scheduling ensures Zigbee beacon timing is never disrupted by application tasks.
    • 

  • Simultaneous BLE + Zigbee + proprietary 2.4 GHz using TI's DMM scheduler, bridging multiple wireless ecosystems concurrently on one chip.
    • 

  • TI ecosystem integration with Sitara processors, TI-RTOS, and Code Composer Studio in existing multi-protocol product lines.
    • 

  • Battery-sensitive Zigbee end-devices where the 0.85 µA sleep current over multi-year deployments saves meaningful battery capacity.
    • 





Verdict


The nRF52840 and CC2652R are remarkably balanced. The CC2652R's autonomous RF core is architecturally superior for concurrent multi-protocol scheduling and offers slightly better sleep and TX radio power efficiency. The nRF52840 wins on Flash capacity, TX range, USB support, and community ecosystem breadth. For a smart home hub bridging BLE, Zigbee, and proprietary RF simultaneously with deterministic timing, the CC2652R RF core architecture is compelling. For wearables, USB peripherals, large-firmware applications, or designs targeting the Zephyr ecosystem, the nRF52840 is the stronger platform.

  

  

  
  

  
  

    




  
Frequently Asked Questions


  

    
    

      
      

        
Our comparisons use verified datasheet specifications to create side-by-side tables. Each comparison includes a verdict explaining when to choose each option based on your project requirements.