You can have a look at our overlay files. They are located in our kernel repository. The overlay for the Core 3(+) / Core S can be found here: https://github.com/RevolutionPi/linux/b ... verlay.dts

Nicolai

Hi Andrea, I'm no can expert, but something I've spotted in your script: os.system("sudo ip link set can0 type can loopback on") Why do you enable the loopback mode if you want to transmit over wire? With loopback enabled RX and TX will be connected internally and no data is transmitted ov...

The CM4S is a module which is only available for (by RPi) selected OEMs in order to overcome the CM3 shortage (/absence).

Nicolai

Hi EduardoH, if you want to use the existing I2C sensors the pico would be a good option. You can connect the pico via USB and send the sensor data via serial. Another cool solution: Use the pico as USB to I2C adapter like this: https://hackaday.com/2022/10/31/need-an-usb-i2c-adapter-use-your-pico/ ...

Hallo Matthias, freut mich zu hören, dass nun alles läuft. Meine Vermutung ist, dass numpy und Konsorten mit der Zeit immer komplexer werden und somit mehr Sourcecode übersetzt werden muss. Auch kommt immer mal wieder etwas an Abhängigkeiten hinzu. Deswegen versuche ich nach Möglichkeit immer mit vo...

The datasheets of the compute module can be downloaded on the Raspberry Pi website. The datasheet for the CM4S is this one: https://datasheets.raspberrypi.com/cm4s ... asheet.pdf

(the GPIO mapping is similar, besides SPI2?)

Nicolai

The eeprom is only part of core se and future models like connect 4. The connect se is similar to the connect 3 / s (without the ethernet part on pibridge).

Nicolai

Is it possible that you selected the Connect SE instead Connect / Connect 3(+) / Connect S ?

Hi Markus, the Connect S uses the same overlay as the "traditional" Connect 3(+). Only the Connect SE requires a different overlay due to the missing ethernet ICs on the PiBridge. Regarding the 1wire I have no idea (yet). The baseboard of Connect S is identicial to Connect 3(+). Does it al...