The gpio pee.02 can not generate interrupts when pin level changes

Robotics & Edge Computing Jetson Systems Jetson Orin NX
, ,
27

the scope capture is just used to illustrate that the voltage is correct,and It has nothing to do with pull-up resistors

28

If you read the GPIO, do you get correct logic level being read? If yes, then it is down to SW configuration which you would need to update. Check if it is being used by any of the drivers/devices in your SW code/setup.

30

1、If you read the GPIO, do you get correct logic level being read?

yes

2、Check if it is being used by any of the drivers/devices in your SW code/setup

I had checked many times, this pin is not used by other drivers/devices. so hoping you checking on the devkit board.

32

Hi @ruanguowei ,

Could you try adding the following line in <Linux_for_Tegra>/bootloader/generic/BCT/tegra234-mb1-bct-gpioint-p3767-0000.dts and reflash the board to check if PEE.02 can work as interrupt in your case?

        port@EE {
            pin-0-int-line = <4>; // GPIO EE0 to INT0
            pin-1-int-line = <4>; // GPIO EE1 to INT0
+           pin-2-int-line = <4>; // GPIO EE2 to INT4
            pin-3-int-line = <4>; // GPIO EE3 to INT0
            pin-4-int-line = <4>; // GPIO EE4 to INT0
            pin-5-int-line = <4>; // GPIO EE5 to INT0
            pin-6-int-line = <4>; // GPIO EE6 to INT0
            pin-7-int-line = <4>; // GPIO EE7 to INT0
         };
33

uha, this suggestion is trustworthy, and I had tested again, the problem has been solved perfectly，thank you very much.