Bluetooth Connectivity Issues with Nordic Semiconductor Chip

Hello everyone, I’m reaching out to seek some guidance on a Bluetooth connectivity issue I’m encountering with a Nordic Semiconductor nRF9160 chip. I’ve been working on establishing a connection between this chip and an Android device, but the connection keeps dropping instantly with an error code 0x3e. I’ve poured through the logs and debug information, and I’m hoping someone with more experience might shed some light on this.

From what I can gather, the connection process starts smoothly. The chip successfully pairs with the Android device, and the initial handshake seems to go through without any issues. However, almost immediately after the connection is established, it drops with the error code. This is frustrating because it prevents any meaningful data transfer from occurring.

I’ve checked the configuration settings multiple times to ensure everything is set up correctly. The nRF SDK is up-to-date, and I’ve tried using different Bluetooth profiles and configurations to see if that makes a difference. Unfortunately, none of these adjustments have resolved the issue.

One thing I’ve noticed is that the problem doesn’t occur consistently. Sometimes, the connection works for a brief moment before dropping, while other times it disconnects immediately. This inconsistency makes it harder to pinpoint the exact cause. I’m starting to suspect that there might be an issue with the radio frequency (RF) environment or perhaps a timing issue within the chip’s configuration.

I’m also considering the possibility that the issue might be related to the clock settings or the power management features of the nRF9160. I’ve read that improper clock configurations can sometimes lead to connectivity problems, so I’m double-checking those settings as well.

If anyone has encountered a similar issue or has any suggestions on how to troubleshoot this further, I would greatly appreciate your insights. Any advice on specific debug logs to review or configuration parameters to adjust would be incredibly helpful. Let’s hope we can get this resolved and have a stable Bluetooth connection working!

Best regards,
GilDev