Ask HN: How will it go for Raspberry Pi in the coming years?
In the consumer and the small business markets, we are having computing power being more and more shifted from desktops or laptops to tablets and smartphones, we are even seeing full computing watches these days. In your opinion, what about DIY, IoT, small robotics, etc. and the generalist barebone computers they use, like Arduino, Raspberry, etc.? Will they become more and more powerful for a new race to bigger, maybe embedded systems or will they stay small, open, very cheap and marginally energy-hungry?
77 comments
[ 3.1 ms ] story [ 127 ms ] threadI sent several mails and got no reply.
The email address <ahoyahoy@nextthing.co> is now bouncing mails: "Recipient address rejected: User unknown".
I'm doing quite a few of low volume (mostly bussiness/industrial helpers) arm linux projects on Pis now. Some of them stay on Pis, if rebooting the board every 2 hours is feasible, some move to custom boards after the prototyping is done. Still, it's very nice to have an off the shelf documented board to start stuff on.
Stability was one of my concerns with my last Pi project, so during development I basically never powered it off or rebooted (except to test power-up behavior) so I could see if I encountered any problems. No problems came up, but others' experiences are always good to learn from.
Is it possible your Pi was suspending USB as part of power management? I've had that problem with some other devices.
I shipped an RPi-based project a few months ago that was a one-off. Could have been done with Arduino, but it was far easier (read: less expensive to develop) on a Pi because it needed a touchscreen UI. I'm unlikely to ever build more than one more unit like it.
I'm currently quoting a design I'd like to use the Pi on because it will need to be connected to WiFi or Ethernet and I doubt I will build more than 20 or so. No way in hell I could make back the board design cost at that quantity. Were it not for the networking, it wouldn't even need a CPU!
RPi and BeagleBone hit a sweet spot for a certain type & quantity of designs that nothing else (of that popularity) meets.
Programmable via the arduino-studio, widely-supported, and very reliable. I've built a bunch of projects with them, and couldn't be happier.
https://libre.computer/2017/12/06/raspberry-pi-3x-raspberry-...
Money quote:
> We expect the Raspberry Pi 4 to be based on a new Broadcom SoC based on Cortex-A55 built on < 28nm fabrication process. We can call this BCM2839 and it will feature the much alluded to VC5 GPU and a new form factor. Since that hardware is more than two years away, it is difficult to predict the direction of the industry and thus the exact specifications. We expect such a Raspberry Pi 4 board to utilize dual 32-bit LPDDR3 or LPDDR4 to cope with the bandwidth requirements of OpenCL and neural network acceleration. The exact release date for such a specimen can vary dramatically depending on Broadcom’s tapeout schedule. It should be relatively soon if the Raspberry Pi Foundation expects to release hardware in 2019.
> We expect the Raspberry Pi 4 to be based on a new Broadcom SoC based on Cortex-A55 built on < 28nm fabrication process. We can call this BCM2839 and it will feature the much alluded to VC5 GPU and a new form factor. Since that hardware is more than two years away, it is difficult to predict the direction of the industry and thus the exact specifications. We expect such a Raspberry Pi 4 board to utilize dual 32-bit LPDDR3 or LPDDR4 to cope with the bandwidth requirements of OpenCL and neural network acceleration. The exact release date for such a specimen can vary dramatically depending on Broadcom’s tapeout schedule. It should be relatively soon if the Raspberry Pi Foundation expects to release hardware in 2019.
I'm curious, which part of their 3B+ prediction was accurate? It all seems totally wrong and looks like they forgot why the thing exists in the first place. The VC4 doesn't even have hardware support for H.265 decode (I assume they mean decode). You can do it in software with a much faster clocked ARM but that's not what they are saying and you won't get 4k. Why RPF would even care about 4k support I have no idea. I'm also not sure where they got the idea that power consumption is important either. 2GB of RAM is a fantasy considering the substantial cost brings little gain. Making these sort of predictions is so difficult but they really were way off.
The sadness I have about the bone is that it is a means to an end. Purchase bone, insert into host board. Voila, IoT. It gets you to an MVP really fast, but limits your design to that form factor. Migrating away is difficult.
The Arduino, at least, served as training wheels. The end goal was to design an atmega328 into your circuit board, not glue another pcb on top. (Just remembering, there is some progress here with the pocket beagle... Though it does raise supply chain concerns.)
Also unlike the bone, the Arduino opened up a pathway for many other architectures and families of microprocessor, lowering the barrier to entry for 32 bit processors and ARM, keeping the platform relevant.
The bone CPU is getting a little long in the tooth, and there doesn't seem to be a path forward to the next generation of processors in the same SWaP C space. There are others, but the cost or power consumption tripples. The bone is at a real sweet point for price and capabilities. I'd love to see a lower power generation with some fixes to annoying problems (like the RTC).
In their defense, there are two or three orders of magnitude more complexity to an ARM SoC than an 8bit micro. The bone community really is on point with making a stable platform with regular releases, especially given the complexity of supporting a SoC+peripherals with the kernel, device tree, U-Boot, Debian, etc.
[1] https://octavosystems.com/
as a lead automotive mechanic for a semi truck shop, I bought about 5 pi's for our techs. We use them for reading OBD diagnostics and doing resets or long-term vehicle observation for certain problems. Theyre cheaper than most of the commercial rent-seeking computer tools we use and if a tech accidentally crushes one, its cheaper than dirt to replace.
We even have a customer who keeps long term backups of log books and GPS data on a pi running off her cigar lighter, as well as her favorite audio books. Trucking companies dont care if you whine the most about your miles, but send them a ZIP file of 6 years of logs and the CEO himself will write you a pay raise. best of all, she tucks the pi in her shirt when she switches trucks. Try doing that with a qualcomm or a laptop!
It's a dream, but I would love to see some open-source software that would be equivalent to the diagnostic tablets from some of the tool trucks.
https://www.cowfishstudios.com/blog/obd-pi-raspberry-pi-disp...
Also a search for "reading OBD diagnostics with raspberry pi" brings back some promising results.
* Random userspace crashes (most recent one was a reproduceable crash in the bowels of the python runtime) happen with greater frequency
* (Usually in the process of debugging the above) strange filesystem artifacts show up (files disappearing after reboot, etc)
* Booting ends up taking 5+ minutes, if it succeeds at all.
The solution to the above ends up being 'rebuild the box on a new SD card'. This is usually on 'brand name' (Kingston, etc) SD cards bought through proper retail channels, so while they're not high end cards, they're at least not (likely) counterfeit either. I still don't have enough data to know if simply dd'ing the old card over is sufficient, or if a full ground-up rebuild is sufficient.
Would love advice on this, especially around brands of cards with known good lifetimes in similar environments.
It really doesn't matter where else they "go" until they fix that right there.
(Why? Because on my workbench right now is the pi, instead of a pi; and that makes all the difference.)
It looks like "$10 wifi computer" was more of an add (loss-leader) than a real product. There still seems to be a gap between ESP32/8266 wifi enabled micros and $20 linux SBC's with built-in wifi that needs filling.
This was explicitly a response to the rise of smartphones(/smart-whatevers) which turned computing into magic by sealing off all the components and preventing any hands-on work - students were enrolling in to computer science degrees with nearly no understanding of how a computer is fundamentally put together.
There is no reason for RPi to change from their very successful mission - they will keep putting out the best hardware they can squeeze into their fixed price point.
For me, doing embedded consulting, the Pi is a cheap, simple way to get a touchscreen and/or network capability without jumping through the hoops of Arduino add-ons.
That said, Arduino (the company) has released more boards with faster, more powerful processors over the years, and I wonder if they'll ever give up the flagship Uno model. I sure hope not, since as bjt2n3904 mentioned, it's a great stepping stone for small, cheap, efficient microcontrollers. It's kind of like learning a programming language and realizing how that knowledge applies to most/all other programming languages, whereas so much of the RPi is abstracted behind Linux.
http://microbit.org/
rPI has spawned a whole ecosystem of hacker-friendly hardware. Like Arduino, it generated demand for a particular form-factor - a lot of people bought rPIs simply because they were cool and cheap, then figured out how they could be useful.
The rPI has clearly moved towards being more powerful and power-hungry, with the latest model drawing about twice the power under load than the original. Documentation and kernel support remain a sticking point, especially for the off-brand PIalikes with Chinese chipsets.
The development of these boards is really dictated by the rest of the market. Nobody is spinning silicon specifically for dev boards, so they'll continue to use whatever cheap chips are on the market. A lot will depend on how well the foundries cope with <14nm process nodes.