2 ms·
TBH for projects that need GPIO I would be inclined to use an RP2040 or similar hooked up to USB, then any machine can be used as the host. That's pretty much h
by jsheard 2y ago
TBH for projects that need GPIO I would be inclined to use an RP2040 or similar hooked up to USB, then any machine can be used as the host. That's pretty much how the Pi5 works anyway, the GPIOs are driven by the RP1 southbridge which is more or less an overgrown RP2040.
- moffkalast 2y agoYeah but why aren't there more boards with a built in coprocessor like that given how cheap they are now? Iirc only Lattepanda and the Pi Foundation make these sort of boards, and the former is overpriced beyond any common sense.
- jsheard 2y agoKeeping the GPIO interface separate does have its advantages, if you accidentally explode a GPIO pin on an external RP2040 board then you've lost a couple of dollars instead of an entire >$50 SBC. It doesn't have to take up much space either: https://www.waveshare.com/product/rp2040-one.htm https://www.waveshare.com/product/rp2040-one.htm
- moffkalast 2y agoIf USB is involved you can't really make a production ready system with it. At least they could put some proper ZH or whatever connectors for UART that don't unplug when you look at them wrong. That's one of the things they did right with the Pi 5 at least.
- Aurornis 2y ago> TBH for projects that need GPIO I would be inclined to use an RP2040 or similar hooked up to USB, then any machine can be used as the host Two separate platforms connected over USB is substantially more complicated, expensive, power hungry, and consumes a lot more space. The value prop of SBCs is that they're compact and you can do low-level work in a single package. Connecting an RP2040 to a PC and writing software for both is the opposite end of the complexity spectrum.