BLE Connect Error 133

Hello,

I am developing BLE peripheral Reader FW using nRF Connect SDK v2.0.0 on VSCode

I have developed my application using NRF52840 DK (development board) and it works on it.

I can connect to Mobile client (nRF Connect Application on Samsung S21 phone) and also read BLE ID from the service specific app.

However, when same application I flash on my custom board (got from HW team), the Mobile Client doesn’t seem to connect !!

I used Nrf Connect Application to test .. connect disconnect, here is the log.

Not sure, whats happening if you can give your expertise. See below.

 

On custom platform:

 

nRF Connect, 2022-06-30
rfID (EE:A6:78:9B:3E:37)
D 15:57:44.590 gatt.close()
D 15:57:44.595 wait(200)
V 15:57:44.796 Connecting to EE:A6:78:9B:3E:37...
D 15:57:44.796 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 15:57:49.883 [Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E 15:57:49.884 Error 133 (0x85): GATT ERROR
I 15:57:49.884 Disconnected

 

On nRF52840 DK:

 

nRF Connect, 2022-06-30
rfID (CF:48:4D:88:18:4E)
V 16:00:59.531 Connecting to CF:48:4D:88:18:4E...
D 16:00:59.531 gatt = device.connectGatt(autoConnect = false, TRANSPORT_LE, preferred PHY = LE 1M)
D 16:01:00.240 [Callback] Connection state changed with status: 0 and new state: CONNECTED (2)
I 16:01:00.240 Connected to CF:48:4D:88:18:4E
V 16:01:00.262 Discovering services...
               

Parents
  • Hi

    Error 133 is a generic error on Android and could be caused by multiple different things. However, the most common reason when having this issue only on a custom board, is that the custom board does not implement the external 32.768 kHz crystal the application will try to use it by default and result in crystal drift that can end up like a 133 error when connecting to an Android device.

    If this is the issue, try adding 

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to your prj.conf file.

    Best regards,

    Simon

Reply
  • Hi

    Error 133 is a generic error on Android and could be caused by multiple different things. However, the most common reason when having this issue only on a custom board, is that the custom board does not implement the external 32.768 kHz crystal the application will try to use it by default and result in crystal drift that can end up like a 133 error when connecting to an Android device.

    If this is the issue, try adding 

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to your prj.conf file.

    Best regards,

    Simon

Children
No Data
Related