Am 24.06.21 um 20:24 schrieb Joshua Quesenberry: > Thanks for the tips Patrick on config.txt cleanup, I'll take a closer look into that. > > Not sure I'm following what you're asking for with regards to i2c. i2c1 is currently is use to communicate with accel, gyro, mag, and a power supervisor MCU that helps us accomplish wake/sleep based on accel or vehicle ignition and some other low-level hardware tasks. Concerning i2c1 afaik it is already set up by the other two lines but I may be wrong about that. >> # typical combination out of raspi-config >> dtparam=i2c_arm=on >> dtparam=i2s=on If you want to wake/sleep according to automotive standards, select a CAN transceiver with a wakeup pin. If I remember right there is even a dt overlay for on/off via pin event. > > I removed the UDEV rules I had that rename can0 and can1, just in case that was causing a race condition or something else odd, but the system is behaving the same. > > Not sure what else to try at this point, any ideas? What does the error number of -110 mean to you all? ... >> [ 146.964971] mcp251xfd spi0.0: SPI transfer timed out [ 146.965023] >> spi_master spi0: failed to transfer one message from queue (ret=-110) >> [ 146.965216] mcp251xfd spi0.0 can0: CRC read error at address 0x0e0c (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965247] mcp251xfd spi0.0 can0: CRC read error at address 0x0e0c (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965277] mcp251xfd spi0.0 can0: CRC read error at address 0x0e0c (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965286] mcp251xfd spi0.0 can0: CRC read error at address 0x0e0c (length=4, data=00 00 00 00, CRC=0x0000). >> [ 146.965331] mcp251xfd spi0.0 can0: CRC read error at address 0x0000 (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965360] mcp251xfd spi0.0 can0: CRC read error at address 0x0000 (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965389] mcp251xfd spi0.0 can0: CRC read error at address 0x0000 (length=4, data=00 00 00 00, CRC=0x0000) retrying. >> [ 146.965397] mcp251xfd spi0.0 can0: CRC read error at address 0x0000 (length=4, data=00 00 00 00, CRC=0x0000). 110 is ETIMEOUT according to your dmesg output, it is raised in a send context from SPI Master and afterwards only zeros are recieved, so may be an issue with the chip select pin. Scope it to be sure. Regards, Patrick
