Chip vs Chip

nRF54L15 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 nRF54L15 and CC2652R BLE SoCs.

    
    

      
    

  


  
  
  

    
      

        A
        
nRF54L15

      

      

    
    
      

        B
        
CC2652R

      

      

    
  

  

  
  

  






  
  

    
nRF54L15 vs CC2652R


The Nordic nRF54L15 and Texas Instruments CC2652R are both serious ultra-low-power BLE SoCs, but the CC2652R adds IEEE 802.15.4 (Zigbee, Thread) and proprietary sub-1 GHz protocols, making it a multi-protocol competitor to Nordic's nRF5340 family. Comparing nRF54L15 against CC2652R reveals a tradeoff between BLE generation and multi-protocol breadth.




Overview


Nordic nRF54L15 is Nordic's next-generation BLE 5.4 SoC with a Cortex-M33 + RISC-V architecture, targeting ultra-low power and the newest BLE capabilities including Channel Sounding. It supports BLE and DECT NR+ but lacks IEEE 802.15.4 radio hardware.


Texas Instruments CC2652R is the multi-protocol evolution of the CC2642R series, adding IEEE 802.15.4 support (Thread, Zigbee, 6LoWPAN) alongside BLE 5.2. It features a 48 MHz Cortex-M4F application core, a Cortex-M0 sensor controller, and TI's proprietary RF core — a dedicated MCU that handles all radio PHY and MAC processing independently. CC2652R can switch between BLE and IEEE 802.15.4 protocols dynamically, enabling products like Thread + BLE commissioning flows central to Matter.




Key Differences


    

  • Multi-protocol: CC2652R supports BLE + Zigbee + Thread (IEEE 802.15.4) + proprietary 2.4 GHz. nRF54L15 supports BLE + DECT NR+ only — no 802.15.4.
    • 

  • BLE version: nRF54L15 supports BLE 5.4 with Channel Sounding; CC2652R supports BLE 5.2.
    • 

  • RF core: CC2652R uses a dedicated Cortex-M0 RF core for all radio processing, enabling guaranteed real-time radio behavior independent of application core load. nRF54L15 uses its RISC-V core for network processing.
    • 

  • Sensor controller: CC2652R includes TI's AUX domain Cortex-M0 sensor controller for autonomous peripheral sampling. nRF54L15 relies on hardware-triggered peripherals.
    • 

  • CPU performance: nRF54L15's M33 at 128 MHz vs CC2652R's M4F at 48 MHz. nRF54L15 has significantly more application processing power.
    • 

  • Matter via Thread: CC2652R is used in numerous Thread-based Matter devices (SmartThings dongle, Amazon Echo with Thread, Eve devices). nRF54L15 alone cannot implement Matter over Thread.
    • 

  • Security: nRF54L15 has TrustZone on M33; CC2652R has hardware crypto and secure boot but no TrustZone.
    • 

  • Memory: CC2652R offers 352 KB Flash + 80 KB SRAM. nRF54L15 is expected to be comparable or better.
    • 

  • Ecosystem: Both have mature SDKs — TI SimpleLink SDK vs nRF Connect SDK. For Thread/Zigbee, TI has extensive Matter SDKs.
    • 





Use Cases


nRF54L15 Strengths


    

  • BLE 5.4 Channel Sounding: Precise proximity measurement for access control and digital keys — not available on CC2652R.
    • 

  • Ultra-low-power pure BLE: When the application is BLE-only and maximum battery life with latest BLE features is the priority.
    • 

  • Higher application compute: 128 MHz M33 handles more complex application logic than CC2652R's 48 MHz M4F.
    • 

  • LC3 codec and Auracast." data-category="LE Audio">LE Audio: BLE LE Audio capabilities are more mature in nRF54L15's generation.
    • 



CC2652R Strengths


    

  • Matter-native Thread devices: CC2652R is a proven Thread border router and Thread end device chip used across the Matter ecosystem.
    • 

  • Zigbee infrastructure products: Building automation devices requiring Zigbee 3.0 in addition to BLE use CC2652R's dual-protocol support.
    • 

  • Sensor-driven ultra-low power: The AUX domain sensor controller enables always-on sensor monitoring with sub-µA main core current.
    • 

  • Multi-protocol smart home: Products acting as Zigbee + BLE bridges benefit from CC2652R's hardware support for both stacks simultaneously.
    • 

  • Long lifecycle industrial designs: TI's proven multi-protocol platform with extended product support lifecycle.
    • 





Verdict


If your product requires Zigbee or Thread alongside BLE — particularly for Matter ecosystems — the CC2652R is the appropriate choice, as nRF54L15 cannot provide 802.15.4 radio hardware. If your product is BLE-only and needs the latest BLE 5.4 features (Channel Sounding, LE Audio) with more application processing power, the nRF54L15 is superior. For pure BLE applications, nRF54L15's generational BLE advantage is significant; for multi-protocol smart home and building automation, CC2652R remains highly relevant.

  

  

  
  

  
  

    




  
자주 묻는 질문


  

    
    

      
      

        
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.