(tick the boxes after creating this topic): Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
1.9.2.10884
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
When we try to do CAN communication using the 4 GPIO pins as the 2 CAN controllers and using 2 SN65 transceivers from outside by following the CAN documentation.
The communication shows an acknowledgement error between the Jetson CAN controller and the CAN transceiver board, which was connected from outside.
The loopback for the Jetson is working properly but CAN communication between CAN1 and CAN0 is not working
We are using the Jetson Orin RTSO-1002. It is 60 pin(28+22+10) device but the CAN documentation for Jetson is given only for 40 pin device https://docs.nvidia.com/jetson/archives/r34.1/DeveloperGuide/text/SO/JetsonAgxOrin.html
This is the link for the document we are using for CAN:
Thank you for your response
Is there any way we can do CAN, SPI for our carrier board and other protocols using the documentation for the 40-pin header only.
CAN loopback is working using the pins but CAN communication between CAN1 and CAN0 is not working using CAN Transceivers(SN65)
What can be the possible reasons?
Jetson-IO is designed to configure pinmux for the devkit from NVIDIA. If your custom has the similar design as the devkit, you could try to use that too.
Or you should use pinmux spreadsheet to configure pinmux for those pins.
It should not need the password to download BSP package.
You are using the custom carrier board, you should use custom BSP package instead of default BSP package, which is for the devkit only.