CanBUS error on new Update of NVIDIA Jetson Orin Nano

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

I’ve been working with canbus for the past few months, and it has been working very well on the Jetson Orin Nano. Recently, after updating the firmware, I’ve been experiencing issues with canbus operability. The canbus states that the bus state is off and whenever I ask it to send data and then dump that data back to me, the command candump states that nothing was sent. This comes after recently updating the firmware. The firmware version that I updated to was 36.3.0-gcid-36191598. I am grateful for any help on this issue.

3

Hi AlexN13,

Are you using the devkit or custom board for Orin Nano?

What’s your firmware version before updating to r36.3.0?

Please share the full dmesg for further check.

4

We are using a devkit for the Orin Nano.

Could you please explain to me how we would check what the firmware version was before updating?

Here is the full dmesg:

image
image1297×815 154 KB

5

You can just run cat /etc/nv_tegra_release to check the version.

Please share the full dmesg as file here instead of a screenshot.

Could you also verify with the latest JP6.1(R36.4.0)?

7

Here is the result of cat /etc/nv_tegra_release:

R36 (release), REVISION: 3.0, GCID: 36923193, BOARD: generic, EABI: aarch64, DATE: Fri Jul 19 23:24:25 UTC 2024

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia

Here is the file for dmesg:
dmesg.txt (60.9 KB)

I’m not sure what you are asking for verifying the latest JP6.1(R36.4.0). The jetpack version that I am on is 6.0+b87.

8 
[  737.596282] mttcan c310000.mttcan can0: entered error warning state
[  737.596303] mttcan c310000.mttcan can0: entered error passive state
[  737.596662] mttcan c310000.mttcan can0: entered bus off state

It seems you enter in to Bus-Off state.
We have a patch in the latest release(JP6.1) to fix similar issue.

You are using JP6.0(R36.3.0) which is not the latest release.
For the devkit, you can simply update to the JP6.1(R36.4.0) to verify if it can help for your case.

9

We updated to the Jetpack 6.1, nothing changed. The dmesg still gives the same error with the bus state.

10

Do you mean that there’s no issue with JP5.x but you hit the issue after updating to JP6.x?

I would suggest you creating a new topic and share the block diagram of your connection and the steps to reproduce the issue.

11

It wasn’t an issue with updating from JP5 to JP6. We were always on JP6. Sorry for the confusion. I’m not exactly sure what was updated. When I ran sudo apt update and sudo apt upgrade and rebooted, there was a progress bar on the load-up screen. I’m not exactly sure what was updated because we’ve been on Jetpack 6 since May. Is there anything you’d advise me to do for finding out what exactly was causing the issue or what was updated when we updated the firmware that caused CAN to stop working.

12

Since you are using the devkit, it may do minor release update with those commands.

Please run cat /etc/nv_tegra_release to check the version before and after update.
I would like to know if you were in JP6.0(R36.3.0) and it works well, but you hit the issue in JP6.1(R36.4.0) after update.

13

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