Bumping on this topic again. A https://www.seeedstudio.com/CAN-BUS-FD-HAT-for-Raspberry-Pi-p-4742.html arrived at my place today. I updated the rpi-0w-1 to latest official packages and it turns out, everything found its way into release and seems to be working fine. There is one thing bugging me though, it runs on different SPIs then Sven's board. My setup is dtoverlay=mcp251xfd,spi0-0,interrupt=25 dtoverlay=mcp251xfd,spi0-1,interrupt=24 SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/platform/soc/*/*/*/spi0.0/net/can?", NAME="mcp0" SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/platform/soc/*/*/*/spi0.1/net/can?", NAME="mcp1" pi@rpi-0w-1:~ $ dmesg | grep -Ei can\|spi [ 30.107770] CAN device driver interface [ 30.280715] spi_master spi0: will run message pump with realtime priority [ 30.316946] mcp251xfd spi0.1 can0: MCP2518FD rev0.0 (-RX_INT -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD c:40.00MHz m:20.00MHz r:17.00MHz e:0.00MHz) successfully initialized. [ 30.379053] mcp251xfd spi0.0 can1: MCP2518FD rev0.0 (-RX_INT -MAB_NO_WARN +CRC_REG +CRC_RX +CRC_TX +ECC -HD c:40.00MHz m:20.00MHz r:17.00MHz e:0.00MHz) successfully initialized. [ 30.528401] mcp251xfd spi0.0 mcp0: renamed from can1 [ 30.613025] mcp251xfd spi0.1 mcp1: renamed from can0 As it happens it runs on a rpi zero w . Is there some sort of stress test I could run to see the platform limits? -- Patrick >>> -----Ursprüngliche Nachricht----- >>> Von: Marc Kleine-Budde <mkl@xxxxxxxxxxxxxx> >>> Gesendet: Mittwoch, 16. Dezember 2020 21:27 >>>> created /etc/udev/rules.d/70-can.rules with >>>> SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/platform/soc/*/*/*/spi0.0/net/can?", NAME="can0" >>>> SUBSYSTEM=="net", ACTION=="add", DEVPATH=="/devices/platform/soc/*/*/*/spi1.0/net/can?", NAME="can1" >>> >>> Note: IFAIK this will not work with newer versions of udev.... >>> >>>> and tadaaaaa: >>>> [ 6.917578] spi_master spi1: will run message pump with realtime priority >>>> [ 6.936957] mcp251xfd spi1.0 can0: MCP2518FD rev0.0 (-RX_... >>>> [ 6.956523] spi_master spi0: will run message pump with realtime priority >>>> [ 6.971942] mcp251xfd spi0.0 can1: MCP2518FD rev0.0 (-RX_... >>>> [ 7.006515] mcp251xfd spi1.0 rename3: renamed from can0 >>>> [ 7.041681] mcp251xfd spi0.0 can0: renamed from can1 >>>> [ 7.091563] mcp251xfd spi1.0 can1: renamed from rename3 >>> >>> ...the "rename" trick doesn't work anymore. Better use a differnet name, e.g.: >>> mcp0 and mcp1. >> >> okay, understood and renamed: >> [ 6.673732] mcp251xfd spi0.0 mcp0: renamed from can0 >> [ 6.716051] mcp251xfd spi1.0 mcp1: renamed from can1 >> >> Thanks! >> >> Sven >>
