Hi,
If I run my nRF5340 peripheral BLE NUS service with NCS 1.9.2, I get two different behavior at console.
When I connect from my WIndows PC running nRF Connect for Desktop BLE Standalone 4.0.0 I get
nfc: reader has read NDEF data [00:10:52.196,563] <inf> ble: regular advertising started [00:10:58.488,037] <inf> ble: connected to peer FD:03:CE:CD:AD:C9 (random) [00:10:58.495,635] <inf> ble: connected (1) as peripheral
That's OK.
When I connect from my iPhone running nRF Connect app 2.5.3 I get
nfc: reader has read NDEF data [00:10:34.906,616] <inf> ble: regular advertising started [00:10:38.379,180] <inf> ble: connected to peer 62:B2:8D:57:73:3F (random) [00:10:38.386,840] <inf> ble: connected (1) as peripheral [00:10:38.899,566] <inf> ble: data length updated from peer 62:B2:8D:57:73:3F (random): max tx 27 (2120 us) max rx 27 (2120 us) [00:10:38.959,320] <wrn> bt_l2cap: Ignoring data for unknown channel ID 0x003a
The connection is actually established, however I would like to figure out the reason of the <wrn> message.
prj options for Bluetooth LE are
CONFIG_BT=y CONFIG_BT_PERIPHERAL=y CONFIG_BT_DEVICE_NAME="Mydevice" CONFIG_BT_DEVICE_APPEARANCE=833 CONFIG_BT_MAX_CONN=2 CONFIG_BT_MAX_PAIRED=1 CONFIG_BT_SETTINGS=y CONFIG_BT_NUS=y CONFIG_BT_NUS_SECURITY_ENABLED=y CONFIG_BT_SMP=y CONFIG_BT_SMP_APP_PAIRING_ACCEPT=y CONFIG_BT_NFC_HANDOVER=y CONFIG_BT_USER_DATA_LEN_UPDATE=y CONFIG_BT_L2CAP_TX_MTU=247 CONFIG_BT_BUF_ACL_TX_SIZE=251 CONFIG_BT_BUF_ACL_RX_SIZE=502 CONFIG_BT_DEBUG_LOG=n
Your help is highly appreciated.
