Hello Jetson Community,
I am trying to create a socketcan on the Jetson Nano. For this i have a 3Volt MCP2515 board that uses the SPI protocol. MCP2515 drivers should be included in the linux kernel.
Before i moved to the Jetson, I managed to get everything running on a Raspberry pi. For this i needed to add a few lines to config.txt to manipulate the device tree and i was done.
I assumed i need to do almost the same for my jetsons i am quite shocked at the amount of complicated steps involved. I am not sure if they are still up to date and wanted to verify that the instructions i found also apply to the jetson Nano.
I actually have two Jetsons: One is a Jetson Nano developer board and the other is a TX2 with a XEC2 board.
I read the TX2 has CAN BUS pins already available but on the XEC2 board that i am using they are not part of the breakout. So even for the TX2 i need to use the MCP2515.
Are the steps different for each board? Or can i first try to get it working on the Nano and then move to the TX2? Because the TX2 is much more expensive i wanted to first try everything on the Jetson Nano. Does it even help me if i get the Nano setup first? Is there any transfer knowledge? Maybe i should skip the Nano and go for the TX2 directly? I am not sure about this…
There is an old guide from 2017 that explains how to get the SOCKETCAN working in an TX1 jetson. Can i follow this for the Jetson Nano? The guide mentions that there are problems with the 1.8V output/input on the Jetson and the 3V of the MCP chip. Does the Nano has 1.8V or 3V? They mention a jumper to switch the device to 3V but where can i find this jumper on the Nano?
Here is the old guide:
If you read the guide you will see the line: ‘Old Guide for r24.2’ How do i know if this is still applicable to my board? If i run uname -a i get the following output:
$ uname -a
Linux devnano 4.9.140-tegra #1 SMP PREEMPT Wed Apr 8 18:10:49 PDT 2020 aarch64 aarch64 aarch64 GNU/Linux
What ‘r’ number is that? Can i even follow the guide at all?
Assuming i should follow that guide they mention that i should become familiar with the process of building the kernel. I followed links and ended up with the ‘sdkmanager_1.2.0-6738_amd64.deb’ However i am running arch (manjaro). Is there a way that i can get this to work without access to a debian machine? I assume the PI3 i have is too slow to take over the task of compiling the linux kernel…
This all seems so vague and outdated. I can’t believe this is the right path to use a MCP2515 with a jetson… For the pi it was 3 lines added into config.txt and one reboot. That is why i am thinking i am doing something horribly wrong here. Is there an easier path?