We tried to perform the loopback test. The test indicates that the messages are being sent and received by can0 and we can see the prints of candump can0 but still, not output data seen by the probe.
We didn’t short any wires, just followed the loopback steps in the guide order to validate the CAN output data.
What do you mean about “probe”? Is that a device to monitor CAN data?
The steps for loopback test from the guide is for internal loopback test so that you don’t need to wire TX/RX externally.
If you want to perform CAN communication, you can also refer to Jetson/L4T/peripheral/ - eLinux.org for verfication.
You may need to get 2 CAN transceivers for both CAN interfaces.
Thanks that worked.
Last question:
Can I modify some config file prior to flashing in order to set the can0_din and can0_dout data instead of using busybox devmem to set them manually?
Yes, busybox devmem is only valid until shutdown.
You can also refer to Generating the Pinmux dtsi Files to download the pinmux spreadsheet and configure these 2 pins for CAN use case.
according to TRM in order to get value of 0xc400 in dout i need to configure it as pull up. I tried doing so but it result with default value of 0xc0000
Is there an example of selecting suitable settings for the orin nx can0 reg vals from spreadsheet?
I can’t upload it directly. he antivirus blocks it (even if archived). Maybe you can use the default one and tell me how to modify it in order to get the required can bus reg values for orin nx?