I have a non-devkit closed source carrier board for Jetson Orin Nano. It seems that they did not implement properly the OTG function on the debug type-c USB port. I can force usb into the device mode manually this way:
echo "device" | sudo tee -a /sys/class/usb_role/usb2-0-role-switch/role
It does not seem robust enough to me. Could you please suggest how to edit the device tree to effectively hardcode the only possible mode - the device mode?
*** Please note that this reply is generated by LLM automatically ***
To address your concern about the OTG function on the debug Type-C USB port not being properly implemented on your non-devkit closed source carrier board for Jetson Orin Nano, and to suggest a method to edit the device tree to hardcode the device mode, we’ll need to delve into the specifics of device tree modifications and the OTG functionality.
Understanding OTG and Device Tree
OTG (On-The-Go) is a feature of USB that allows a device to act as either a host or a peripheral. The Jetson Orin Nano, like many other embedded systems, uses a device tree to describe the hardware components of the system. The device tree is a data structure that describes the hardware components of the system, including the USB ports and their configurations.
Editing the Device Tree for Hardcoding Device Mode
To hardcode the device mode for the debug Type-C USB port, you would typically need to modify the device tree source (DTS) files. However, since you’re working with a closed-source carrier board, accessing and modifying the DTS files might be challenging. Assuming you have access to the device tree source or can modify the compiled device tree binary (DTB), here’s a general approach:
Identify the Relevant Node: In the device tree source, you need to identify the node that corresponds to the debug Type-C USB port. This node will likely be under the USB controller node and might be named something like “usb@…” or have a specific label indicating it’s the OTG port.
Modify the Node Properties: Once you’ve identified the correct node, you’ll need to modify its properties to force the device mode. The exact properties to modify can vary depending on the specific hardware and device tree configuration. Common properties related to OTG and device mode include:
dr_mode: This property specifies the default mode of the USB port. You might need to set this to “peripheral” or “device” to force device mode.otg_mode: This could be used to specify the OTG mode, but it might not be present in all configurations.usb-role-switch: This property might be used in some configurations to control the USB role.Recompile the Device Tree: After modifying the device tree source, you’ll need to recompile it into a device tree binary (DTB) that the kernel can understand. The process for recompiling the device tree depends on your development environment and the tools available.
Flash the New Device Tree: Once you have the new DTB, you’ll need to flash it to your device. This process varies depending on the device and the flashing tools available.
Important Considerations
Conclusion
While the steps above provide a general guideline for hardcoding the device mode for the debug Type-C USB port on your Jetson Orin Nano carrier board, the specifics can vary widely depending on the board’s design and the device tree configuration. Given the closed-source nature of your carrier board, it’s recommended to seek support from the manufacturer or a developer community familiar with the Jetson Orin Nano and device tree modifications.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
document in below could guide how to modify the device tree.
However, if that is closed source, then might not be able to fully update such thing.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.