I found a discrepancy between the Jetson Orin Design Checklist and the Design Guide regarding the CAN_DOUT and CAN_DIN signal directions.
According to the Design Guide, CANx_DOUT is output from the Orin module (i.e., Transmit) and CANx_DIN is input to the Orin module (i.e., Receive), which matches the internal naming convention and direction.
However, in the Checklist , it states:
CANx_DOUT connected to input data (RX) pins of CAN device
CANx_DIN connected to output data (TX) pin of CAN device
This seems reversed.
I designed the circuit following the Design Guide’s description, as shown in the attached schematic
Here, CANx_DOUT from Orin goes to the TXD pin of the transceiver, and CANx_DIN is connected to RXD.
Can you please clarify which document is correct? Is my design aligned with the correct interpretation?
Thanks in advance!
*** Please note that this reply is generated by LLM automatically ***
To clarify the discrepancy between the Jetson Orin Design Checklist and the Design Guide regarding the CAN_DOUT and CAN_DIN signal directions, let’s analyze the information provided in the context and the question.
-
Understanding CAN Bus Signals:
- CAN (Controller Area Network) is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer.
- CAN_DOUT (or CAN_TX) typically refers to the transmit signal from a device, which means it is the output from the device to the CAN bus.
- CAN_DIN (or CAN_RX) typically refers to the receive signal to a device, which means it is the input to the device from the CAN bus.
-
Design Guide Description:
- According to the Design Guide, CANx_DOUT is described as output from the Orin module, implying it is the transmit signal (TX).
- CANx_DIN is described as input to the Orin module, implying it is the receive signal (RX).
- This description aligns with standard naming conventions for CAN bus signals, where DOUT/TX is for transmitting data and DIN/RX is for receiving data.
-
Design Checklist Description:
- The Checklist states that CANx_DOUT should be connected to the input data (RX) pins of the CAN device, and CANx_DIN should be connected to the output data (TX) pin of the CAN device.
- This description seems to reverse the roles of DOUT and DIN, which could lead to confusion and incorrect implementation.
-
Analysis and Conclusion:
- Based on standard CAN bus terminology and the description provided in the Design Guide, it appears that the Design Guide’s description of CANx_DOUT as output (TX) and CANx_DIN as input (RX) is correct and aligns with conventional CAN bus signal naming.
- The Checklist’s description seems to be incorrect or misleading, as it reverses the expected roles of DOUT and DIN.
- Given that you designed your circuit following the Design Guide’s description, where CANx_DOUT from the Orin module goes to the TXD pin of the transceiver and CANx_DIN is connected to the RXD pin, your design appears to be aligned with the correct interpretation of CAN bus signal directions.
-
Recommendation:
- To ensure compatibility and correct functionality, it’s recommended to follow the signal direction descriptions provided in the Design Guide for CANx_DOUT and CANx_DIN.
- If there’s any further confusion or discrepancy, it might be beneficial to consult with the document authors or seek clarification from NVIDIA support to confirm the correct implementation.
In summary, based on the information provided and standard CAN bus terminology, the Design Guide’s description of CAN signal directions appears to be correct, and your design, following this guide, should be aligned with the correct interpretation.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
