Part Number: AM620-Q1
Other Parts Discussed in Thread: CC3301
Hi Team,
We are using a custom AM62xx board with the CC3301 wireless module. The Wi-Fi interface is configured over SDIO and is working correctly and is stable. However, we are facing persistent issues with the Bluetooth/BLE interface over UART. We are using the `k3-am625-sk-m2-cc3351.dtso` overlay.
Issue Description
After enabling BLE on the target using the appropriate command, the board starts advertising successfully. We can discover the device from the SimpleLink Connect application as well as other BLE applications such as nRF Connect and BLE Scanner.
However, when attempting to establish a connection from any of these applications, the connection always fails with a connection timeout. The behavior is consistent across all applications tested.
Additionally, Bluetooth scanning and pairing from the AM62xx board are also not functioning correctly:
* Scanning from the custom board does not detect any nearby Bluetooth devices (mobile phones, laptops, etc.).
* Attempting to pair with a known device using:
pair <Bluetooth_MAC_Address>
reply: Device unavailable
Current Status
* Wi-Fi over SDIO is fully functional and stable.
* Bluetooth HCI interface initializes successfully.
* BLE advertising is visible on external devices.
* BLE connection always times out.
* Pairing with known Bluetooth MAC addresses fails with "Device unavailable."
Previous Support Request : https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1646856/am625-cc3300-ble-not-functioning-properly-on-am62xx-custom-board/6389999
We previously raised a support ticket regarding this issue, but unfortunately it has not helped us resolve the problem. We are still blocked and unable to proceed with Bluetooth integration.
Request
We would greatly appreciate your assistance in identifying the root cause of this issue.
Could you please advise:
1. Are there any known issues or additional configuration required for CC33xx Bluetooth over UART on a custom AM62xx platform?
2. Are there any firmware, UART, or HCI initialization steps that we should verify?
3. Is there any recommended debug procedure or log collection that would help isolate the problem?
4. Are there specific kernel configuration options, Device Tree settings, or BlueZ configurations that should be checked?
5. Since BLE advertising is visible but connection establishment always times out, what could be the possible causes?
We have been investigating this issue for quite some time, and it has become a critical blocker for our project. We need to determine whether the CC33xx solution is suitable for our product requirements.
We would sincerely appreciate your guidance and any recommendations to help resolve this issue.
Thank you for your time and support.
Navami