Part: nrf52833
Soft Device: SD140 (recently switched from SD 122 because SD140 supports more BLE 5.x features)
Application: Replace legacy Central host device with nrf53833.
Problem: One of our production peripherals will make a connection, but the Characteristic writes fail after to switching from SD 122 to SD 140.
The gstt_status fault code is 0x106. BLE_GATT_STATUS_ATTERR_REQUEST_NOT_SUPPORTED
One of our peripherals gets an error when a Write Characteristic is requested, type_2 passes the request.
This is a high priority to get working? Is there any way to tell why SD122 did not have this issue?
Thanks,
Dan
Customer Sensor Peripheral type 1: gets a gatt_status failure
00> <warning> ble_nus_c: WRITING TO THE AUTH CHAR
00> <debug> app: GATT STATUS FAULT CODE 0x106
Customer sensor Peripheral type 2: no failure, is it possible that sensor 1 does not support the MTU exchange below that sensor 2 shows?
00> <debug> nrf_ble_gatt: Peer on connection 0x0 requested an ATT MTU of 247 bytes.
00> <debug> nrf_ble_gatt: Updating ATT MTU to 23 bytes (desired: 23) on connection 0x0.
00> <info> app: Ble NUS max data length set to 0x14(20)