Processing Modes#

The SiWx917 supports different processing modes that affect BLE stack implementation and behavior. Understanding these differences is important for selecting the appropriate mode for your application.

Stack setup and initialization are covered in BLE initialization and configuration.

Mode Overview#

Mode

Description

NCP mode

Full BLE stack on the Network Processor (NWP); external host over SPI/SDIO/UART through WiSeConnect SDK host library.

RCP mode

BLE Controller on the NWP; BLE Host on an external host (for example Linux), HCI between them.

SoC/ACP mode

Full BLE stack on the NWP; M4 application processor uses WiSeConnect SDK over AHB and shared memory.

See also: Usage scenarios.

Mode Selection Guidelines#

Choose NCP Mode When:

  • External host has limited processing capability

  • Simple integration is preferred

  • Full BLE stack features needed without host implementation

  • Host doesn't need BLE stack control

Choose RCP Mode When:

  • Host has existing BLE host stack implementation

  • Standard HCI interface preferred

  • Custom host stack features needed

  • Host is capable MPU (Linux, etc.)

Choose SoC/ACP Mode When:

  • Single-chip solution preferred

  • Low latency requirements

  • Integrated M4 + NWP solution

  • Power efficiency is critical

API Compatibility:

  • NCP and SoC modes: Use WiSeConnect SDK BLE APIs (rsi_ble_* functions)

  • RCP mode: Uses standard Bluetooth HCI commands (not WiSeConnect SDK APIs)

  • Implementation details differ but functionality is equivalent

  • Mode-specific considerations mainly affect integration and API access method

Reference: See the WiSeConnect SDK BLE API Reference for API documentation.