Hi, I encountered the same issue as described in the topic below:
I’m using a custom board with JetPack 6.0 (R36.3). We want to configure pins L5 and L48 to UART function, and we have configured the pinmux accordingly.
I’m using a custom board with JetPack 6.0 (R36.3). We want to configure pins L5 and L48 to UART function, and we have configured the pinmux accordingly.
*** Please note that this reply is generated by LLM automatically ***
The question is related to configuring a custom carrier board for Jetson AGX Orin to use the existing Camera GPIO function as UART instead of the camera function. The user has already configured the pinmux accordingly but is facing issues with the pinmux being overwritten.
To address this issue, we can refer to the topic “Jetson AGX orin CAMERA GPIO dhange to UART” where a similar problem was resolved. The solution involved blocking the CAM0RST and PCIe3V3EN related functions of the Linux SW.
Here are the steps to block these functions:
Disable the regulator-vdd12v-pcie: This can be done by modifying the device tree file (DTS) to disable the regulator-vdd12v-pcie. This will prevent the PH04 pin from being used as a GPIO.
Block the CAM0RST function: The CAM0RST function is used in many camera DTSI files and is compiled as a DTBO. To block this function, you need to modify the device tree file (DTS) to exclude the CAM0RST function.
Modify the Linux SW: After blocking the CAM0RST and PCIe3V3EN functions, you need to modify the Linux SW to use the pins L4 (UART4TX) and L48 (UART4RX) as GPIOs instead of UART.
By following these steps, you should be able to configure the custom carrier board to use the existing Camera GPIO function as UART instead of the camera function.
In comparison to the original topic, the main difference is that the user is using a custom board with JetPack 6.0 R36.3, whereas the original topic was using JetPack 5.0.1. However, the solution remains the same, and the steps outlined above should still apply.
It’s also worth noting that the user has already configured the pinmux accordingly, but is facing issues with the pinmux being overwritten. This suggests that there may be other factors at play, such as conflicts with other device tree files or kernel modules. Therefore, it’s essential to carefully review the device tree files and kernel modules to ensure that there are no conflicts or overwrites.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
I did a test - moved all dtbo files related to camera from /boot to /data and restart the board.
However, the related GPIOs are still occupied by the camera.
I removed the gpio@220000 node in the tegra234-p3737-camera-modules.dtsi file and rebuilt the dtb. The left side shows the gpio node before the change, and the right side shows it after the change. The camera-control-output-low was removed.
