Skip to content

BLE Networks

The CC2 supports two types of Bluetooth Low Energy (BLE) networks: BLE (nRF53) and BLE Peripheral (nRF52). Both are defined in the network section of global.json, allocdata.json, or unallocdata.json.


Type Description Hardware
ble Primary BLE GATT service on the nRF53 nRF53
bleperi BLE peripheral (Quuppa / legacy GATT) on the nRF52 nRF52

The nRF53 BLE GATT service is used for:

  • Message and alert passing (GATT characteristics)
  • iBeacon advertising
  • GATT service discovery
{
"data": {
"network": {
"networks": {
"b1": {
"type": "ble",
},
},
"networkOrder": ["b1"],
},
},
}

Behaviour is configured via devcfg.ble — see BLE, Peripheral & Scan Config for the full parameter list (ibIntervalMS, gattIntervalMS, major/minor, txPower, uuid, adname).


The nRF52 BLE peripheral chip is used for:

  • Quuppa location tracking
  • Legacy GATT service (deprecated in favour of the nRF53 GATT)
  • Device DFU over BLE (Nordic DFU app)
{
"data": {
"network": {
"networks": {
"q1": {
"type": "bleperi",
"state": "QB",
},
},
"networkOrder": ["q1"],
},
},
}

The state field selects the nRF52’s operating mode:

Value Mode
QB Quuppa location tracking
GATT Legacy GATT service
IB+GATT iBeacon advertising + GATT service

Behaviour is configured via devcfg.bleperi — see BLE, Peripheral & Scan Config for the full parameter list, including dfu_start (triggers Nordic DFU mode) and reset.