51–60 of 123 posts
Eh, I'll stick with the PocketBeagle board. It is half the price, very easy to source, doesn't require any special connectors and has those extremely useful PRUs. Slightly larger, slower and no wireless connectivity but that is a worthwhile tradeoff.
Earlier quoted context omitted.
I've always wondered where the line is on a product's FCC certification. Obviously US retailers such as Adafruit and Sparkfun have sold fully assembled unlicensed radio equipment for over a decade. What subtle changes could these companies make with their products that would suddenly gain the interest of the FCC?
Do you have an example? SparkFun even has a blog entry about certification that's a useful read, although not entirely accurate. https://www.sparkfun.com/tutorials/398
There's dozens of SBCs with 2x better specs than a Pi, but the Pi is arguably the most dominant board out there. For makers (for anyone really), documentation is king. Working code, lots of examples, and good forums make the SBC, not the hardware.
As for the other group, "hardware startups": Why on earth would you lock yourself into another startup for the brains of your new project? It makes no sense. Remember what happened to Intel's SBC? If a company that big can't provide decent EOL support, what do you think will happen if Neutis folds? Pick a ARM something core with a certified BT/WiFi module, and choose from several manufacturers with real EOL schedules and a history of following them
Don't get me wrong, the 10 year guarantee is nice, but I don't think anyone can afford to believe it.
What secure element chipset are you using? This could be very interesting for a project I am working on. Does it run JavaCard / GlobalPlatform and are the access keys available?
This thing far exceeds the capacity of that machine, costs several orders of magnitude less, and FITS IN A FUCKING MATCHBOOK. Jeez. Get some perspective.
Eh, I'll stick with the PocketBeagle board. It is half the price, very easy to source, doesn't require any special connectors and has those extremely useful PRUs. Slightly larger, slower and no wireless connectivity but that is a worthwhile tradeoff.
Unless it gets the ecosystem the Pi and the Beagle have, this gets old rather quickly.
What differs is what each chip actually supports. E.g the Pi/BCM2835 doesn't have onboard ethernet MAC/Phy. Neither Pi nor H3 have onboard CAN but maybe neither of those things matter. Point is these days most of the details of the chip are abstracted away; if you have good kernel support there's not a lot to worry about.
This board seems to target people who want to create products with it. I wouldn't place a rasp pi in an end product and certainly wouldn't come near an orange pi even for a prototype.
My flabber is gasted at people complaining about paying a meaty $49 for a quad-core, 64bit, cpu with 8gb of local storage. Twenty years ago I was writing docs for the SGI Challenge[1] with its four MIPS R4000s in a tidy cabinet the size of a two-drawer file (disk drives mounted externally) weighing about 250lbs. This thing far exceeds the capacity of that machine, costs several orders of magnitude less, and FITS IN A…
who would even bother, the rpi zero is $5.
My flabber is gasted at people complaining about paying a meaty $49 for a quad-core, 64bit, cpu with 8gb of local storage. Twenty years ago I was writing docs for the SGI Challenge[1] with its four MIPS R4000s in a tidy cabinet the size of a two-drawer file (disk drives mounted externally) weighing about 250lbs. This thing far exceeds the capacity of that machine, costs several orders of magnitude less, and FITS IN A…
so? $49 is way too expensive for this. i can get a x86 from ebay way more cheaper than this. who would even bother, the rpi zero is $5.
At least $11 and then there's shipping. and limits of one per customer.