How to Enable SPI to CAN (MCP2518FD) in AGX ORIN INDUSTRIAL

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
, ,
1

Hi,

I designed the carrier board using the current AGX ORIN INDUSTRIAL module. Currently, the carrier board has implemented a total of 4 CAN communications using SPI to CAN (MCP2518FD). I also enabled it through the “sudo menuconfig” command to use MCP2518 normally. However, there was a problem that the driver was not recognized on the carrier board. How do I solve this?

Image is being created using Jetpack 6.2.1 and installed using the command “sudo./flash.sh jetson-agx-orin-devkit-industrial mmcblk0p1”.

2

*** Please note that this reply is generated by LLM automatically ***

To solve the issue of the driver not being recognized on the carrier board, we need to investigate the possible causes and provide a step-by-step solution.

Possible Causes:

  1. Incorrect configuration: The sudo menuconfig command might not have been executed correctly, or the configuration might not have been saved properly.
  2. Missing dependencies: The MCP2518 driver might require additional dependencies that are not installed on the system.
  3. Driver not enabled in the kernel: The MCP2518 driver might not be enabled in the kernel configuration, which is required for the driver to be recognized.
  4. Hardware issue: There might be a hardware issue with the CAN communication or the MCP2518FD chip.

Step-by-Step Solution:

  1. Verify the configuration: Run the sudo menuconfig command again and ensure that the MCP2518 driver is enabled. Save the configuration and exit.
  2. Check the kernel configuration: Run the zcat /proc/config.gz | grep MCP2518 command to verify that the MCP2518 driver is enabled in the kernel configuration. If it’s not enabled, you’ll need to rebuild the kernel with the correct configuration.
  3. Install dependencies: Run the sudo apt-get install linux-headers-$(uname -r) command to install the necessary dependencies for the MCP2518 driver.
  4. Load the driver: Run the sudo modprobe mcp2518 command to load the MCP2518 driver manually. If the driver is loaded successfully, you should see the MCP2518 device listed in the dmesg output.
  5. Verify the device: Run the dmesg | grep MCP2518 command to verify that the MCP2518 device is recognized by the system.
  6. Test the CAN communication: Use a CAN communication tool, such as candump or cansend, to test the CAN communication on the carrier board.

Comparison with Jetpack 4.6.1:

In Jetpack 4.6.1, the MCP2518 driver was not enabled by default. However, in Jetpack 6.2.1, the driver is enabled by default. If you’re using Jetpack 6.2.1, you should not need to rebuild the kernel or load the driver manually.

Additional Tips:

  • Ensure that the MCP2518FD chip is properly connected to the SPI interface on the carrier board.
  • Verify that the CAN communication is properly configured on the carrier board.
  • If you’re still experiencing issues, try resetting the MCP2518FD chip or reinitializing the CAN communication.

By following these steps, you should be able to resolve the issue with the MCP2518 driver not being recognized on the carrier board.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

Hi jinbim3690,

Please share the full dmesg and device tree for further check.

And also, the result of the following command on your board.

$ zcat /proc/config.gz | grep CONFIG_CAN_MCP251XFD
7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.