Hi all!
I am new to jetson and I am trying to connect can bus (mcp2515 8000000hz) to jetson nano dev kit. But I can’t get the jetson-io.py script to see my dtbo file. There was already a similar topic on the forum (https://forums.developer.nvidia.com/t/jetson-io-py-cant-find-dtb-file-on-jetson-nano-dev-kit-a02/248328), I updated to jetpack 4.6.4, but the trick that is given there did not work. But there was a clue:
cat …/compatible - “nvidia,p3449-0000-b00+p3448-0000-b00nvidia,jetson-nanonvidia,tegra210”
The system already had a pre-installed file - tegra210-p3448-0000-p3449-0000-a02-mcp251x.dtbo, and it is miraculously visible to the jetson-io script, however with it I have an error:
MCP251x didnt enter in conf mode after reset.
Probe failed, err=16.
I tried to uncompile it to find out the secret of its success, but the DTC throws an error in the process. This guy’s solution - (https://forums.developer.nvidia.com/t/jetson-nano-and-mcp2515-can-module/112271/288) seemed to be the most workable, (he is often referenced in other topics) but also failed here. Please answer my prayer.
Here is some information about me:
NVIDIA NVIDIA Jetson Nano Developer Kit
L4T 32.7.4 [ JetPack UNKNOWN ] - don’t know if this is normal?
Ubuntu 18.04.6LTS
Kernel Version: 4.9.337-tegra
anyway here are the versions of the jetpacks
Good afternoon, yes jetson-io.py does not see my dtbo files that I offer it to the /boot/ folder. I compile all dtbo files here (https://github.com/Seeed-Studio/seeed-linux-dtoverlays). Please tell us more about the SPI loopback test.
If you are using the custom board for Jetson Nano, Jetson-IO might not work for your board.
You could refer to the following thread step-by-step for SPI loopback test. Jetson Nano SPI Bus Not Working - #10 by KevinFFF
I apologize for my sluggishness, but I have the same problem as the user jcl9309, I uncompiled the entire contents of the /boot/ folder and even /boot/dtb , but I did not find the part with such content:
gpio_default: default {
gpio-input = <
TEGRA_GPIO(BB, 0)
TEGRA_GPIO(B, 4)
TEGRA_GPIO(B, 5)
TEGRA_GPIO(B, 6)
TEGRA_GPIO(B, 7)
TEGRA_GPIO(DD, 0)
TEGRA_GPIO(E, 6)
TEGRA_GPIO(S, 5)
TEGRA_GPIO(A, 5)
@@ -49,11 +44,6 @@
TEGRA_GPIO(J, 7)
TEGRA_GPIO(G, 2)
TEGRA_GPIO(G, 3)
TEGRA_GPIO(C, 0)
TEGRA_GPIO(C, 1)
TEGRA_GPIO(C, 2)
TEGRA_GPIO(C, 3)
TEGRA_GPIO(C, 4)
TEGRA_GPIO(H, 2)
TEGRA_GPIO(H, 5)
TEGRA_GPIO(H, 6)
Could something have changed since you posted this step by step guide?
I figured out a little in the code of my tegra210-p3448-0000-p3449-0000-b00.dtb and found that gpio_default in my case is in this form:
default {
gpio-input = <0xd8 0xc 0xd 0xe 0xf 0xe8 0x26 0x95 0x5 0xbc 0xbd 0xbe 0xc1 0xc2 0xa8 0xc8 0xca 0x4d 0x4e 0x4c 0x4f 0x32 0x33 0x10 0 x11 0x12 0x13 0x14 0x3a 0x3d 0x3e 0x41 0xe4>;
Only I do not understand how to correlate their HEX number with the one you provided in order to delete it correctly.
I did all the steps you suggested on a freshly installed system and still I see this output from spidev_test:
sudo ./spidev_test -D /dev/spidev0.0 -v -p “HelloWorld123456789abcdef”
spi mode: 0x0
bits per word: 8
max speed: 500000 Hz (500 KHz)
TX | 48 65 6C 6C 6F 57 6F 72 6C 64 31 32 33 34 35 36 37 38 39 61 62 63 64 65 66
__ | HelloWorld123456789abcdef
Rx | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 __ | …
I even got an oscilloscope and checked it (just in case), but still no result.
I solved my problem by making a UART to SPI adapter using an arduino nano board. I was afraid that this would not work, but I managed to send frames to CAN every 100ms. I think it can be even faster. If someone needs this life hack, I can attach instructions.