3 ms·

> GPIO: RPI: 40-pin Raspberry Pi GPIO header x86_64: Usually none, only available through USB to GPIO adapters I have a mixture of RPi's, cheap AliXpress ARM

by yardie 2y ago

> GPIO: RPI: 40-pin Raspberry Pi GPIO header x86_64: Usually none, only available through USB to GPIO adapters I have a mixture of RPi's, cheap AliXpress ARM boards, and a stack of Intel NUCs from a decommissioned dev cluster. The only one that consistently works are my Pi's. The GPIO breakout pins are they are used for embedded applications and not try to be desktop PC replacement (though they could do that) And they continue to receive updates for even my oldest. Whitelabel ARM boards might receive the occasionnel update. Finally, I don't trust the thermal management of Intel enough to stick it in a unclimatized closet and expect it to be working a year later. It takes a lot of work to get an Intel chip to run at low power, low thermals. Something the Pi manages to do out the boxx. This is a apple to oranges comparison that fails to take into account what makes the Raspberry Pi the Raspberry Pi.

kube-system 2y ago
> Finally, I don't trust the thermal management of Intel enough to stick it in a unclimatized closet and expect it to be working a year later. I stopped trusting the thermals of the Pi after my experiences with the Pi 4. I swapped it in to some projects where a Pi 3 worked great, and the 4 thermal throttled itself the entire time.
bee_rider 2y ago
I think the solution closes to pi, for x86, is probably… to talk to an Arduino over USB, hahaha. (Closest to the pi in the sense that there’s a healthy maker community behind it).
05 2y ago
You hardly need gpio pins for anything these days, it's usually better to use usb native comms or a uart converter or an i2c bridge etc. The added bonus is that you won't burn the expensive Pi when something goes wrong with the peripheral. ESPHome is usually the non-overkill solution when you just need a few sensors and actuators and don't have to also run the ML inference on the same node :)

by yardie 2y ago

kube-system 2y ago

> Finally, I don't trust the thermal management of Intel enough to stick it in a unclimatized closet and expect it to be working a year later. I stopped trusting the thermals of the Pi after my experiences with the Pi 4. I swapped it in to some projects where a Pi 3 worked great, and the 4 thermal throttled itself the entire time.

bee_rider 2y ago

I think the solution closes to pi, for x86, is probably… to talk to an Arduino over USB, hahaha. (Closest to the pi in the sense that there’s a healthy maker community behind it).

05 2y ago

You hardly need gpio pins for anything these days, it's usually better to use usb native comms or a uart converter or an i2c bridge etc. The added bonus is that you won't burn the expensive Pi when something goes wrong with the peripheral. ESPHome is usually the non-overkill solution when you just need a few sensors and actuators and don't have to also run the ML inference on the same node :)