Chip vs Chip

nRF5340 vs CYW20820

<\/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 nRF5340 and CYW20820 BLE SoCs.

    
    

      
    

  


  
  
  

    
      

        A
        
nRF5340

      

      

    
    
      

        B
        
CYW20820

      

      

    
  

  

  
  

  






  
  

    
nRF5340 vs CYW20820


The Nordic nRF5340 and Infineon CYW20820 target overlapping but distinct segments of the BLE market. The nRF5340 is a multi-protocol IoT SoC with powerful application processing; the CYW20820 is a dual-mode Bluetooth SoC (Classic + BLE) with automotive-grade options, targeting more traditional Bluetooth applications such as audio, HID, and automotive connectivity.




Overview


Nordic nRF5340 is a dual Cortex-M33 BLE 5.3 SoC supporting BLE, Thread, Zigbee, and Bluetooth Mesh simultaneously. It is designed for complex IoT applications where multi-protocol wireless and hardware security are primary requirements. The application core runs at 128 MHz with TrustZone isolation; the network core handles all wireless processing independently.


Infineon CYW20820 (formerly Cypress) is a dual-mode Bluetooth SoC combining Classic Bluetooth and BLE on a single chip with an integrated Arm Cortex-M4 application core. It supports BLE 5.0 and Classic Bluetooth BR/EDR, making it suitable for HID (keyboards, mice), A2DP audio streaming, and automotive BLE applications. The CYW20820 is part of Infineon's AIROC Bluetooth portfolio, which emphasizes automotive and industrial robustness, including AEC-Q100 qualified variants.




Key Differences


    

  • Classic Bluetooth: CYW20820 supports both Classic Bluetooth (BR/EDR) and BLE — enabling A2DP audio streaming, HFP hands-free profiles, and HID over Classic BT. nRF5340 is BLE-only (no BR/EDR).
    • 

  • BLE version: nRF5340 supports BLE 5.3 with LC3 codec and Auracast." data-category="LE Audio">LE Audio; CYW20820 supports BLE 5.0.
    • 

  • Multi-protocol IoT: nRF5340 adds Thread and Zigbee for mesh networking. CYW20820 is Bluetooth-only (Classic + BLE).
    • 

  • Core architecture: nRF5340 dual M33 (network + application separation); CYW20820 single Cortex-M4 with integrated radio.
    • 

  • Automotive qualification: CYW20820 is available in AEC-Q100 qualified variants for automotive applications. nRF5340 is not AEC-Q100 qualified.
    • 

  • Audio codec support: CYW20820 supports SBC, AAC, aptX (via Classic BT A2DP) and CELT. nRF5340 supports LC3 (LE Audio) but not aptX or Classic BT audio profiles.
    • 

  • Security: nRF5340 has TrustZone + CryptoCell-312. CYW20820 has AES-128 hardware but without TrustZone isolation.
    • 

  • Ecosystem: nRF Connect SDK (Zephyr) for nRF5340; Infineon AIROC SDK (ModusToolbox) for CYW20820.
    • 

  • Power: nRF5340 optimizes for IoT duty cycles. CYW20820 optimizes for connected standby in Bluetooth audio and HID devices.
    • 





Use Cases


nRF5340 Strengths


    

  • Pure BLE IoT applications: Sensors, medical devices, wearables, and smart home devices that need BLE 5.3 with LE Audio or Thread/Zigbee.
    • 

  • Mesh networking: BLE Mesh + Thread + Zigbee concurrent operation is a nRF5340 exclusive capability.
    • 

  • Security-critical designs: Hardware dual-core isolation and CryptoCell-312 provide the strongest security architecture.
    • 

  • LE Audio hearing aids and earbuds: nRF5340 is positioned for the next generation of LE Audio hearing devices.
    • 



CYW20820 Strengths


    

  • Classic Bluetooth audio streaming: Products requiring A2DP wireless audio (e.g., speakers, headsets, car audio systems) need Classic Bluetooth BR/EDR, which nRF5340 cannot provide.
    • 

  • Automotive Bluetooth: AEC-Q100 qualified variants make CYW20820 suitable for in-car HFP, A2DP, and BLE profiles in automotive infotainment.
    • 

  • HID peripherals: Keyboards, mice, and game controllers that need the dual-mode Bluetooth profile compatibility with both Classic and BLE hosts.
    • 

  • Hands-free car kits: CYW20820 supports HFP and A2DP simultaneously, making it appropriate for automotive Bluetooth kits.
    • 





Verdict


The nRF5340 and CYW20820 are complementary rather than directly competing. If your product needs Classic Bluetooth audio streaming (A2DP, HFP) or automotive qualification (AEC-Q100), the CYW20820 is the only viable option between these two. If your product is a pure BLE IoT device — especially one requiring LE Audio, multi-protocol mesh, or hardware security isolation — the nRF5340 is the superior choice.


The key decision point is Classic Bluetooth BR/EDR. No firmware configuration or external component can add A2DP or HFP to the nRF5340 — dual-mode Bluetooth requires dual-mode silicon. Similarly, no CYW20820 configuration can participate in a Thread or Zigbee mesh network, run BLE Mesh with hundreds of nodes, or provide the TrustZone-isolated security architecture that nRF5340 offers. Products needing both Classic BT audio and multi-protocol IoT mesh would require separate chips or a fundamentally different SoC strategy, as the two capabilities are served by distinct silicon families. Identify which capability set is truly required by your product before committing to either device.

  

  

  
  

  
  

    




  
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.