I'm old-school embedded. So yeah, get off my lawn you kids that need an RPi, 700Mhz of clock, and a multitasking O/S to read a GPIO pin and send 10 bytes to a server.
But man, you can pretty much run Linux on a single chip now, so why mess with anything else? You can tangle with some other the other embedded O/Ses out there for months, or spin up something in Linux in an afternoon.
 almost. I've run Linux from an RZ/A1 but with a little bit of external QSPI NOR. I'm guessing the next generation of A9/A15 SoCs will stack more DRAM and NAND flash on top to make this a no-brainer.
Here's a link: http://octavosystems.com/2016/05/09/osd3358-new-era-integrat...
The schematics for all of their reference boards (aka Beaglebone Black/Green) are freely available, the chip has solid documentation, TI has a good Github+Linux repository, and you can make a really nice system out of it.
The Octavio part is nice, I'm also really interested in what NXP (cough cough Freescale) is doing with turning the iMX into a module. These are both pretty rare birds though. When I can get trays from DigiKey, we'll be cooking.
Dual-A9 is overkill for making an IoT device node, but hey if you're going to run Azure/Python/Node.js to send your 10-byte report, what the hell.
I don't think I will ever forgive TI for abandoning the Galaxy Nexus when they decided to abruptly exit the Android business. Since they chose not to update the drivers, Google couldn't update the GNex later Android versions despite being a Nexus phone. Google Glass had a TI chipset and Google managed to deploy a new Android version to it (I guess via some driver-compat work-around) but I hear the setup wasn't stable. I now avoid TI wherever possible.
I've since switched to the NXP/Freescale iMX family and it's pretty similar in a lot of ways.
I hadn't heard of them before, I just noticed the link you posted said octavosystems.com in the url, not octavio.