wiringPi is still maintained on github as a community project, available also for Pi4.WiringPI is deprecated and has been for years.an extra GPIO header would be fine, feat an 8-channel 12bit ADC, driven by a common widespread µC (e.g., MCP3208 or comparable, supported by wiringPi libs) plus 1 or 2 extra i2c ports (as i2c-0 is reserved to HATs and having just i2c-1 is too limited)
Why use an MCP3208 when the in house RP2 could be used?
IIRC more I2C busses are available on 2711/2712 based Pi.
OK.
MCP3208 was just an example, feat easy-to-use Arduino (Wiring) libraries - what do you mean by "in house RP2"? RP2040? ( has just 4 analog ports, no wring/Arduino-like analogRead() IIRC)
Yes, I meant RP2XXX. The lack of an arduino "wiring" library shouldn't be a deal break, rather a learning exercise for the user. IIRC the arduino IDE can be used with it which implies wiring support in that framework.
Pi3 just has 2 i2c busses, so has the Pi4, and bitbang emulation on GPIO reduces their total number for simple I/O purposes.
I2C muxers slow down dataspeed, they significantly complicate access to end devices by Arduino/Wiring standard libs, and can*t run devices by different i2c bus speed (100k, 400k, 1M, perhaps even more)
Is the 3B based on the 2711 or 2012? No? Not relevant then.
You might want to recheck what the 4B has. There are device tree overlays for six I2C buses and they're mentioned in the documentation.
And what's the obsession with "Arduino/Wiring"? Are you unwilling/unable to learn something else?
Statistics: Posted by thagrol — Tue Nov 18, 2025 9:26 pm