Bluetooth cannot receive file on our custom carrier board

Hi nvidia,

Jetpack: JP 6.0 (R36.3)

Current Status:
✓ Bluetooth connection between Orin and mobile phone: Working
✓ Orin to phone file transfer: Working
✗ Phone to Orin file transfer: Failed - Device not discoverable

Issue:
On our custom carrier board, while Orin can connect to and send files to mobile phones, it cannot receive files because the device is not discoverable when phones attempt to send files.

We referenced the following link, but the issue remains unresolved.

Can’t receive file via Bluetooth on Jetson AGX Orin with JetPack 6 - Jetson & Embedded Systems / Jetson AGX Orin - NVIDIA Developer Forums

*** Please note that this reply is generated by LLM automatically ***

The issue you’re facing is related to Bluetooth connectivity and file transfer between the Jetson AGX Orin and a mobile phone. Specifically, while the Orin can connect to and send files to mobile phones, it cannot receive files because the device is not discoverable when phones attempt to send files.

To address this issue, let’s break down the possible causes and solutions:

  1. Bluetooth Configuration: Ensure that Bluetooth is properly configured on the Jetson AGX Orin. You can check the Bluetooth settings using the bluetoothctl command. Verify that the Bluetooth adapter is enabled and set to discoverable mode.
  2. Device Visibility: Check if the Orin is visible to other devices. You can use the bluetoothctl command to set the device to visible mode. Use the scan on command to scan for nearby devices and verify that the Orin is visible.
  3. File Transfer Protocol: Ensure that the file transfer protocol (FTP) is properly configured on the Orin. You can use the bluetoothctl command to set up an FTP server on the Orin.
  4. Permissions: Verify that the necessary permissions are set for Bluetooth file transfer. You can check the permissions using the getfacl command.
  5. Custom Carrier Board: Since you’re using a custom carrier board, it’s possible that the Bluetooth module is not properly configured or is experiencing hardware issues. Verify that the Bluetooth module is properly connected and configured on the carrier board.

Comparing your issue to the referenced link, it seems that the issue is similar, but the solution provided in the link did not resolve the issue. In this case, you may want to try additional troubleshooting steps, such as:

  • Checking the kernel logs for any Bluetooth-related errors
  • Verifying that the Bluetooth firmware is up-to-date
  • Testing Bluetooth connectivity with a different device or mobile phone
  • Checking the power management settings to ensure that the Bluetooth module is not being powered down

Additionally, you can try using the bluetoothctl command to set up a Bluetooth connection and transfer files manually. This can help you identify if the issue is related to the Bluetooth configuration or the file transfer protocol.

In summary, to resolve the issue, you should:

  • Verify Bluetooth configuration and device visibility
  • Check file transfer protocol and permissions
  • Investigate custom carrier board hardware and configuration
  • Perform additional troubleshooting steps to identify the root cause of the issue

If none of these steps resolve the issue, you may want to consider seeking further assistance from NVIDIA support or the Jetson developer community.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Hi,
Please try above suggestion. Furthermore please install blueman and try.

Hi Dannel,

There are no OBEX File Transfer and OBEX Object Push UUID.

Fixed. Added necessary config:
CONFIG_RFKILL=y

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.