How to enable 3110000.serial node in Jetson orin nano devkit for BT

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
, , ,
1

Hi I am trying to enable the Bluetooth on the 3110000.serial node, but It is not working,

image
image936×612 116 KB

fragment@0 {
target-path = “/bus@0/serial@3110000”;

\__overlay_\_ {
    compatible = "nvidia,tegra194-hsuart";
    status = "okay";

    reset-names = "serial";
    resets = <&bpmp TEGRA234_RESET_UARTB>;

    clock-names = "serial";
    clocks = <&bpmp TEGRA234_CLK_UARTB>;

    bluetooth {
        compatible = "infineon,cyw55572-bt";
        brcm,requires-autobaud-mode;

        max-speed = <921600>;

        /\*
         \* IF573 W_DISABLE2#
         \* BT_M2_EN
         \* Jetson GPIO03
         \* GPIO3_PCC.00
         \*/
        shutdown-gpios = <&gpio TEGRA234_MAIN_GPIO(C,0)
            GPIO_ACTIVE_HIGH>;

        status = "okay";
    };
};

};

/*
* Add UART alias for serial@3110000.
* Required by serial-tegra driver.
*/
fragment@1 {
target-path = “/aliases”;

\__overlay_\_ {
    serial3 = "/bus@0/serial@3110000";
};

};

This is the overlay I am using,
Can you provide your input on this, please?

4

Hi trezen.parmar,

What’s the Jetpack version in use?

Are you connecting the serial BT device on M2.Key E port with 3110000.serial?
If so, have you requested the vendor for the porting guide and related resources?

Have you verified UART loopback test working before connecting with BT device?

5

Jetpack 6.2.1
Yes, we are connecting the serial BT device on M2.Key E port with 3110000.serial.

The UART driver is not able to probe, can you give details on why is it happening and what is still remaining to add in the overlay?

6

I think UART driver should be able to be probed by default.
The current error from the screenshot you shared, it looks like that the reset property has been removed in your case.
I’m not clear about your driver and the customization.
Please recover the customization for serial3110000 node in device tree.

7

Hi @trezen.parmar
I found a possible solution for this issue in the following NVIDIA forum thread:

I also found some relevant information in this wiki:

Based on this information, you can use the following commands to check which TTY devices are being detected and are available on the system:

dmesg | grep tty
ls /dev/tty*

Could you please run these commands and share the output? This should help us verify how the UART interfaces are being detected by the system.

Let me know if this helps answer your question. If not, feel free to let me know, and I’ll be happy to help further.
Best Regards
Carlos Quiros Gomez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

10

Hi trezen.parmar,

Please share the loopback result when you recover the customization for serial@3110000.

You may also refer to what carlos.quiros suggests and check if it helps for your case.

11

Is this still an issue to support? Any result can be shared?

12

Yes, you can close this as this is resolved.