PaulStoffregen
Well-known member
The Raspberry Pi (model B version 1) I use to build Teensyduino for Linux ARM seems to be dying. Well, most likely its SD card may be dying. After several hard lockups while compiling, I managed to finally get a complete build after deleting lots of stuff to free up about 7 GB of space. The build uses under 0.5 GB.
So I'm trying to decide what I'm going to do...
1: Stop supporting Linux ARM / Raspberry Pi. This would be the easiest, but it seems at least some people do use it, right?
2: Just replace the SD card, reinstall and copy or rebuild stuff. Worried some of my current SD card may be corrupted. If I have to redo the setup, I'd like to step up to something faster than this painfully slow version 1 Pi.
3: Replace it with a Raspberry Pi 3 and a (hopefully) faster & more reliable USB disk, and then redo the setup... Here's the hardware I'm considering. Is this hardware a good idea? Do programs compiled on a Raspberry Pi 3 always work when run on Pi Zero or earlier model Pi?
https://www.amazon.com/StarTech-com-Raspberry-Pi-Board-Converter/dp/B01NH2W8NL
https://www.amazon.com/Samsung-850-EVO-Internal-MZ-N5E250BW/dp/B00TGIVZTW
https://www.amazon.com/Raspberry-Model-1-2GHz-64-bit-quad-core/dp/B01CD5VC92
4: Set up cross compiling from my fast desktop. This seems like a great option for building a command line program. But a pair of GUIs which link against custom compiled wxWidgets and FLTK libraries, which in turn have tons of library dependencies on the Raspbian system libs seems like quite a nightmare. Or maybe it's not so hard?
My main goal is to minimize the amount of time I end up pouring into redoing my Raspberry Pi build setup, so I can focus on other stuff that matters for everyone. I've found numerous mentions online that SD card tend to fail on Raspberry Pi after heavy usage, so I'm *really* hoping to get onto more durable hardware to avoid having to redo this all over again in another year.
So I'm trying to decide what I'm going to do...
1: Stop supporting Linux ARM / Raspberry Pi. This would be the easiest, but it seems at least some people do use it, right?
2: Just replace the SD card, reinstall and copy or rebuild stuff. Worried some of my current SD card may be corrupted. If I have to redo the setup, I'd like to step up to something faster than this painfully slow version 1 Pi.
3: Replace it with a Raspberry Pi 3 and a (hopefully) faster & more reliable USB disk, and then redo the setup... Here's the hardware I'm considering. Is this hardware a good idea? Do programs compiled on a Raspberry Pi 3 always work when run on Pi Zero or earlier model Pi?
https://www.amazon.com/StarTech-com-Raspberry-Pi-Board-Converter/dp/B01NH2W8NL
https://www.amazon.com/Samsung-850-EVO-Internal-MZ-N5E250BW/dp/B00TGIVZTW
https://www.amazon.com/Raspberry-Model-1-2GHz-64-bit-quad-core/dp/B01CD5VC92
4: Set up cross compiling from my fast desktop. This seems like a great option for building a command line program. But a pair of GUIs which link against custom compiled wxWidgets and FLTK libraries, which in turn have tons of library dependencies on the Raspbian system libs seems like quite a nightmare. Or maybe it's not so hard?
My main goal is to minimize the amount of time I end up pouring into redoing my Raspberry Pi build setup, so I can focus on other stuff that matters for everyone. I've found numerous mentions online that SD card tend to fail on Raspberry Pi after heavy usage, so I'm *really* hoping to get onto more durable hardware to avoid having to redo this all over again in another year.