Thank you for the quick response by the way.
I ended up going the CAN transceiver route due to time constraints.
Here are answers to your previous questions:
Do you using cansend/cangen command to send can packet after you run candump in background?
Are you testing with internal loopback test? Or you sent can packet from can0 to can1?
I successfully had used cansend and cangen to receive with candump, but this was over an internal loopback test.
Please share the block diagram of your connections for further check.
Jetson AGX Orin DevKit > USB to CAN adapter (USB in, terminal block CAN line out) > CAN line > ODrive S1 motor controller. Nothing is connected to the Jetson pin headers.
Another note is that the CAN to USB adapter automatically creates a can0 interface when plugged into a Pi or PC, so this may be what is conflicting, as the Jetson already has can0 and can1 interfaces created for the pin header.
I renamed the default can0 interface to can2, and when plugging in the USB to CAN adapter, can0 was not created by the adapter.
I ended up going with a CAN tranceiver (Adafruit CAN Pal Tranceiver) using the Jetson pin header rather than the USB to CAN adapter, and have CAN bus working fine now.
If anyone is still interested in pursuing the issue, here is the product link to what I was originally using: