Atom-Based JaguarBoard To Take On Raspberry Pi (hothardware.com)

MojoKid writes: The tiny single-board PC movement that's leading the Internet of Things (IoT) market is largely dominated by ARM-based processors, and for good reason — they're cheap, low power and capable. However, what if you prefer to work with the x86 architecture? JaguarBoard looks strikingly similar to Raspberry Pi, which is arguably the most popular single-board mini PC. But unlike Raspberry Pi, JaguarBoard allows users to develop for x86, courtesy of its Intel Atom Z3735G (Bay Trail) foundation. The chip is a quad-core part clocked at 1.33GHz to 1.83GHz with 2MB of L2 cache, offering a fair amount of horsepower for IoT applications. In addition to an Atom processor, JaguarBoard also boasts 1GB of DDR3L memory, 16GB of eMMC storage, three USB 2.0 ports, 10/100M LAN port, HDMI 1.4 output, SDIO 3.0 socket, two COM ports, four GPIO pins, and audio ports. It's an interesting device that you could use strictly as a mini PC for general purpose computing, as an embedded system, a learning or research tool, or for whatever DIY projects you can conjure up. It's not the only hobbyist-appropriate x86 board, but those specs are pretty good for $45.

Comments

Not a Raspberry pi competitor.

[goombah99]

4 gpio ports? this is not competing against a raspberry pi. And if I'm looking for something that is a computing device not a hacker board then I can take my $45 and get a Amazon tablet with USB IO for that whihc includes batteries, and a powersource. then I've got usb I/O or wifi I/o to a CHIP, Arduino or Raspberry pi $5. So it hits the sour spot between being under ported as a hacker board and over priced as a cheap computer.

Re:Not a Raspberry pi competitor.

[LarryRiedel]

I don't know of a $45 Amazon tablet that can be a standalone off the shelf x86 Ubuntu system with performance comparable to a netbook which can host VMs running Ubuntu Snappy Core for IoT applications. Since the JaguarBoard also has I2C, COM and GPIO ports, it can in some cases be a replacement for an RPi, depending on the number of units to be deployed in production, and the profit margin and TCO of the target solution.

The RPi's "secret weapon"

[petes_PoV]

Is its following, community and wide range of available software.

Without something comparable, all the SBCs in the world amount to very little. For example, consider the Orange Pi. It's based on a different architecture, it uses a different boot-up process. Sure, it runs Linux, it's probably hardware compatible up to a point, it's cheaper: $15 compared to what? $30 for a RPi (I'm not up to date on US dollar prices). Has it taken the world by storm? No. Can you buy it without sending your money to China and waiting 1 - 2 months? Definitely not.

What it, and all the other SBCs, lack is the ease of use. The wide range of almost-working software. The examples to create your own almost-working software. The documentation about what almost works and the "experts" (those people who can make TWO LEDs flash) who can and will answer questions - preferable with correct answers.

Re:The RPi's "secret weapon"

[goombah99]

Yep. I wasted $20 on an Orange Pi PC. Official distro would not boot, eventually found an unofficial on that would boot linux. Only ran on one of it's CPUs it looks like. And not much support for GPIO modes like SPI. it would not work with any of the bog standard monitors I owned. Did get it to work on an HDMI TV but only in certain modes. Problems with KEy boards. Would not recognize some SIM cards despite their meeting specs.

Sure I could make it work, but would I develop for it? no because if I came back a year later I'd probably fiund anything I created would not work on their unsupported releases and there would be a newer board out. With Rpi I can be productive imediately and know I have path forward for anything I make.

The x86 SBC's "secret weapon"

[chihowa]

The advantage of an x86 based SBC is the ability to take advantage of the maturity and relative uniformity of the x86 platform. The arcane uboot process and the need for specific support for not only different ARM SoCs, but the specific machines built on them, leaves dozens of abandoned ARM based systems stuck on ancient custom-tweaked kernels (and Linux only). Almost all of the problems you list are inherent in any ARM-based system until the equivalent of a uniform and predictable BIOS-type system is implemented for ARM.