However during power up the Jetson seems to bring down the CAN-bus network causing all the other nodes to loose communication and some enter fault mode. I suspect this is because Rx/Tx are configured as GPIO during boot and is not working properly until the register patch is applied.
@shgarg it happens either when booting from scratch or when running sudo reboot. Haven’t tried suspend function since it’s not useable in this application
Hi,
Yes, then pin configurations will go off and they will be back to their original settings. You can do one thing:
As you followed: Enabling CAN on Nvidia Jetson Xavier Developer Kit | by Ramin Nabati | Medium
In enable_CAN.sh: copy below lines at the starting so that after every boot, it configures automatically:
sudo busybox devmem 0x0c303000 32 0x0000C400
sudo busybox devmem 0x0c303008 32 0x0000C458
sudo busybox devmem 0x0c303010 32 0x0000C400
sudo busybox devmem 0x0c303018 32 0x0000C458
I already dis this, CAN configures automatically but the script is loaded too late I suspect. If the tx/rx pins are configured GPIO during initial boot and are low they will be dominant on the CAN bus and disable all other communication. I need to check this with a scope to see if it actually is the problem