Sometimes the end of a product’s production run is surrounded by publicity, a mix of a party atmosphere celebrating its impact either good or bad, and perhaps a tinge of regret at its passing. Think of the last rear-engined Volkswagens rolling off their South American production lines for an example.
Then again, there are the products that die with a whimper, their passing marked only by a barely visible press release in an obscure corner of the Internet. Such as this week’s discontinuances from Intel, in a series of PDFs lodged on a document management server announcing the end of their Galileo (PDF), Joule (PDF), and Edison (PDF) lines. The documents in turn set out a timetable for each of the boards, for now they are still available but the last will have shipped by the end of 2017.
It’s important to remember that this does not mark the end of the semiconductor giant’s forray into the world of IoT development boards, there is no announcement of the demise of their Curie chip, as found in the Arduino 101. But it does mark an ignominious end to their efforts over the past few years in bringing the full power of their x86 platforms to this particular market, the Curie is an extremely limited device in comparison to those being discontinued.
Will the departure of these products affect our community, other than those who have already invested in them? It’s true to say that they haven’t made the impression Intel might have hoped, over the years only a sprinkling of projects featuring them have come our way compared to the flood featuring an Arduino or a Raspberry Pi. They do seem to have found a niche though where there is a necessity for raw computing power rather than a simple microcontroller, so perhaps some of the legion of similarly powerful ARM boards will plug that gap.
So where did Intel get it wrong, how did what were on the face of it such promising products fizzle out in such a disappointing manner? Was the software support not up to scratch, were they too difficult to code for, or were they simply not competitively priced in a world of dirt-cheap boards from China? As always, the comments are open.
Header image: Mwilde2 [CC BY-SA 4.0].
They finally understood that launching a product on the market as if it were to sell itself and make billions … does not work!!!
No, they still don’t understand anything.
The failure of Intel’s IoT stuff was purely related to the documentation. The documentation simply wasn’t there. You couldn’t find a datasheet with a list of registers anywhere. There were zero templates/examples. I know people who had a direct line to Intel engineers that tried to get a simple SPI thing going. Didn’t happen, even with the best help you could have.
So, instead of solving the problem by 1) releasing documentation and 2) putting a few Edison and Galileo boards, sparkfun’s entire sensor inventory and a few interns in a room and telling them to build shit, they just pulled the plug. But before that, they spent millions on two seasons of a reality show to advertise their IoT solution.
But hey, we got a nifty defcon badge out of the whole thing. That was probably the best marketing move they made, but again, poor documentation. I didn’t see anyone successfully (electronically) hack that badge.
This right here. It failed purely because of the lack of documentation.
I looked and looked but couldn’t find a simple picture that detailed what pins are what and where on the breakout board. Ended up mapping the pins by trial and error.
Every now and then, we here at work (small design company) get a call from someone who wants us to try Intel parts in our designs. We invite them in, and the fun begins. No docs unless Intel likes you, and that involves money and annual commitments, multiple NDAs signed in blood, etc.
One does not simply “buy” an Intel part, and design it in. Oh, no. That would be too easy.
I’ve colleagues having similar experience but we want to use Thunderbolt and trying to get specs to even establish if we can was impossible (only licensees had access but given how much that costs, it’s quite an outlay when it may not even be possible and we had our request refused). There is some light on the horizon because Intel is claiming that they are opening the standard to be free for OEMs and device manufacturers (announced May 2017) but we’ll see if Intel actually follow through and allow it to be more widely adopted & used.
I work extensively with both Broadcom and Intel at work, and they’re both absolutely terrible to deal with for the same reasons. And we’re large enough to ship $millions of each of their parts annually. The worst isn’t the number of hoops you have to go through to get docs, it’s not knowing about the existence of some errata, appnote, or subcomponent documentation because you haven’t been granted access to that corner of their library.
…and the difference between this and the Raspberry Pi situation, when one needs all the details and minutiae associated with the machine-level operation of a processor/GPU is, exactly?…
@jawnhenryy Difference is the availability of a compute module, well maintained OS and a forum where you can get quick answers to queries. Is it fully open? No. Is it a better solution than the Edison? Absolutely.
The stupid part about this is that excellent understanding of the standard Intel peripherals going back decades is part of what makes OS development on PCs so much better than on anything else. People know how these things work, nobody needs an NDA on it, they just write the driver. Now we have the Intel that made the IMEI.
Not only that they didn’t originally include a way to talk directly to the hardware and instead expected you to do everything through a slow closed API.
Brian gets it right!
Of all sad words of tongue or pen, the saddest are these: ‘Benchoff was right again’
I think “he’s dead, Jim” is sadder.
+1, sir
+1 on this,
No *useful* documentation for registers, peripherals or layout.
We had a direct line to Intel and could not get any info on doing designs with these devices, no luck with buying them at all.
cool devices with lot sof potetial, but no way for us to put them to use in teh sme weay we use ARM devices .. :(
“The failure of Intel’s IoT stuff was purely related to the documentation.”
…and the difference between this and the Raspberry Pi situation, when one needs all the details and minutiae associated with the machine-level operation of a processor/GPU is, exactly?…
Short $INTC, you heard it here first.
oh well, at this point I will keep my edison in his box for collection purpose.
Wow this really came out of the blue – a three month phaseout period with no replacement is pretty rapid. I know some of these modules made it into a number of commercial products, whose manufacturers are likely rather unhappy right now.
If you design a module into a product that is from a manufacturer with no history/experience in the market and has no declared long term commitment to the product, you have only yourself to blame.
Exactly
It’s pretty much Intel way of doing things (only paranoid survives).
That’s why nobody trust them for long term support outside pc world. Their next failure will be automotive.
Auto makers want 10+years support and don’t believe Intel can (want) to do it.
They’ve already gotten priced out of the automotive game without any major wins. TI, NXP, Renesas, and nVidia are the historical incumbents. And now that Qualcomm and Samsung have dove head-first into automotive, Intel is dead on arrival.
Also Freescale as PPCs are more commonly used in automotive control modules than anything else.
A lot of them used to use 68HC11 and 68000 family processors and they moved to PPC in the mid 2000s.
Freescale/NXP is great about guaranteed availability and long term support. If they could come out with an SoC with even half the horsepower as some of nVidia’s automotive focused Tegras, they would own the self driving car market by default.
I was lumping Freescale in with NXP since there isn’t a Freescale any longer. Yes, NXP e200/300 MCUs are everywhere in automotive, but the MCU space is not relevant to the Intel and competition topic. And even they are slowly pushing ARM CMx series MCUs over their own IP now (PPC & HC11/S*12).
NXP does have many ARM CAx MPUs like Vybrid, i.MX6, etc. But I’m not sure they made a mistake or not by canceling the i.MX7 and initially retreating from the automotive infotainment/ADAS high-ground some years ago. Cell phone makers have a default economy of scale advantage in automotive as that is essentially what is in your dash (in multiple places). Qualcomm has announced some big wins and auto-qualification of Krait SoC. And Samsung’s purchase of Harmon has guaranteed their eventual entry.
There is some room to innovate in the automotive space and pickup new part markets as the architectures evolve. But a generic x86/64 AEC-Q100 compute module from Intel isn’t one of them.
Unless you want to run DOS, there’s a ton of better and cheaper alternatives.
pretty much, or anything that requires x86 or perhaps where its just easier to use x86 than another arch. That being said ARM is pretty much the name when it comes to embedded CPUs in IoT or hell just in general
Exactly, the only thing going for x86 always was that it could run Windows programs, but that is next to irrelevant in the embedded world these days, people are just not that keen on doing the whole WinCE thing all over again with Win10…
Maybe they still believe Windows Phone and their purchase of Nokia will somehow pay off?
The tool-chain is extensive, from free to proprietary. There’s a large pool of people experienced with it. Extensive documentation, of all kinds from beginner to experienced. Yes THIS product is a counter-example, but x86 in general isn’t.
If you’re going to run dos you might as well use PC-104 or a nano-ITX board.
Probably would have an easier time getting the documentation from VIA or AMD anyway.
If they made something that had a basic – slow x86 processor, and full opengl, from an onboard intel GPU, this would be great for many things where you could use a Pi.
Being able to use ordinary drivers, and no OpenGL drivers would certainly have shaved about a month off my last project (as opposed to the Pi with Dispmanx etc).
I can’t see intel hitting the price-point though.
Pi price point? Definitely not.
Pi form factor (or quite close) – take a look at Upboard – not a bad board at all IMO, but it is much more expensive. (but not much more expensive than a complete Edison setup including carrier – probably one big reason Edison is dead)
The thing which always made me steer away from the edison was the insane connector. It’s kinda hard to experiment with something when you need an electron microscope just to deal with its pin pitch
Yeah. Once you included a breakout board, the price/performance of their solution was simply not compelling – ignoring all of the OTHER issues others have brought up.
The only case where it was compelling was if you needed the significantly reduced size – IF one of the smaller breakout boards had the I/O you needed. I know of only one case (the DIYAPS project) where this turned out to be the case.
in the universe of things, there is only one who can survive and it is not by chance that the contestants are open source. And check out how smaller and easier it is to work with Onion, Yun, Raspberry. Intel’s gear was meant to be a failure the moment they did not support developers the way others do.
pretty much, zero documentation or tutorials
… and yes, by the way….. Nifty badge indeed :) :) :) Rest in peace Edison, Galileo , Joule (in order of preference)
While the Galileo doesn’t shock me, nor does the Edison to be honest, I am surprised at how quickly the Joule was resigned to join them in the graveyard!
The Joule must barely have made it into distributors warehouses before it was canned… Out of the 3, that’s the one I had some real applications in mind for. Ah well. Anyone want some Edison modules, going cheap? ;)
I do!. Would you do eBay?
My guess is the ARM boards that are out there are better value and have a bigger community and better available documentation, code (drivers, kernel trees etc) and support and that unless you absolutely need an x86 CPU for some reason the ARM stuff is the better choice.
The raspberry Pi was never the fastest SoC around, but it did have very well documented hardware.
Recall, Broadcom slowly opened up their IP over several years as the bare metal hackers mined the hardware.
This is why my company is doing the transition over to ARM based chips. We were merrily humming along, liked the x86 chipset our products were built on, when suddenly an EOL for the chipset came out. Last time buys were announced and no real “use this as a direct replacement” was offered. At least non that was going to be supported by our stack (Win CE). So we looked at what was going on and found that ARM had a least published availability till dates with most vendors. So we started redesigning for a different architecture.
Intel suddenly saying “and were done” has happened before. Designers just have to accept it and move on/up in the product lines.
Intel/Microsoft are now like a fast food restaurant that always spits in your burger. ;-)
You may find some porting options here:
https://www.yoctoproject.org/downloads/bsps
We had the same happen, except they EOL’d the SoC about the same time we were going to production. Yay.
Ouch. That couldn’t be any worse timing. I feel you there. At least you had time to switch before you had product in the field.
They were good products, but overpriced and outmatched by cheaper AVRs.
This is another proof that marketing is not everything : you can’t spend millions of freebies and prevent people from using them. I saw the boards, WTF ? They don’t understand their market !
Intel was being Intel and now shareholders can breathe again.
” I saw the boards, WTF ? They don’t understand their market ! ” my thoughts as well, when I got mine I thought this is gonna be really hard for makers and beginners to use, let alone understand its potential. Now if you are a full blown engineer with plenty of PCB layout experience the edison could be very useful, the only people I knew of using them were full blow EEs with years of experience.
And it’s a vindication and victory for Free & Open Hardware !!!
I like the fact that Intel gave it an attempt. Market diversity is more important in the long run for an industry than an arduino-raspi monopoly, even if they are more open and have a better design.
Too expensive to soon seemed like a rush out the door to compete with other boards.
Fortunately, they did’nt create Newton, Bhor, Weber n so many other famous peoples from the scientific universe
Maybe Erwin Schrödinger would have been a better choice?
Then, yes. At this point, I think all observers would agree that what we have here is a dead cat.
But if you’re board is still in working order, the cat’s alive!
But if there is scarce documentation, will it continue to live?
Well, as expensive and headaches prone that the Edison was, it was the only computer module I found with the size/power ratio that could fit my project:
https://hackaday.io/project/21453-keymu-open-source-keychain-sized-gaming-console
The console does work but there are always improvements to be made, and it just seems useless now to keep working on it. I guess I have to sit and wait for an equivalent alternative.
Thank you for sharing THE only real project using Edison I have seen so far
Thanks, this news sure isn’t the best one regarding Keymu, but (oh how much) I agree with all the other comments out there: for a computer module designed for everyone, it sure lacks documentation and support from Intel. Getting easy things done with this module was and is A PAIN, and it shouldn’t be!
I still remember how a trivial thing like using SPI with DMA turns out to ba a nightmare on the Edison.
Anyway, it’s sad for the project but it’s for the best really, Keymu as many other projects out there deserve better than the Edison.
Emlid makes RTK positioning systems and the Reach and Reach RS products are designed around Intel Edison: https://reachrs.emlid.com/
Being a small company it seems like this announcement could really hurt.
Quite a few OpenAPS users were running Edison configs: https://github.com/andrew-warrington/Compact-APS
But applications like that are pretty rare.
Land what about an Upboard?
The Edison was too expensive and not marketed to the right group
There are plenty of different ways to control a neo-pixel over wifi, plenty of ways to text you when a motion sensor activates and plenty of ways to make an rc car
They should have aimed at more complex projects … The hardware was there
Plus using a connector never designed to be mated over and over in a device designed to be mated over and over was a bad move
I bought an Edison because it seemingly offered a lot of power in a small package. Apart from a connector that requires a breakout to do anything useful, thus nullifying the size advantage, the problem was just about zero support and documentation. So, after testing the module with a blinking light routine, it now just sits on the shelf. I also bought a Samsung Artik5 module to evaluate, primarily for the same reason, a lot of power in a small package, but also because it has built in crypto hardware. Once again, no support or documentation, especially for the crypto hardware and an almost complete focus on using their centralized cloud makes a nice piece of hardware essentially useless.
+1
I had High hopes of both Edison and Artik , but neither were seen as core business by their makers, so couldn’t command the necessary engineering or documentation resources to help devs make the most of realtively expensive boards.
Why did they fail? Because they were shipping too powerful a product, with too many features, and seriously overpriced as a result. It also lacked any solid documentation, but quite frankly I think that was a side issue. Look at the ESP8266, it flat out had no documentation, but because it was priced correctly the community wrote their own.
The ESP8266 has a fairly complete library that address most majors requirement that Arduino users wants:
https://espressif.com/sites/default/files/documentation/esp8266-technical_reference_en.pdf
It didn’t have on release though. On release the community was left with minimalist chinese documentation. I don’t remember how long it took espressif to realise they had a winner on their hands but at least months, possible over a year.
The Galileo at least was not all that powerful. A 400 Mhz x86. Every ARM out there kicks its butt.
Instructables/Intel gave me like 15 of the Edisons to give away/promote, but I just couldn’t find any good reason to use them. It did some cool stuff in such a small package, but the documentation was terrible, their implementation of BusyBox was non-standard and some coreutils were just broken, so building anything on it became a nightmare. It was expensive for what it did and I’m glad the IoT stuff is being spearheaded by ESP.
Was close to saying the same thing. Tried to build some prototype stuff but kept having to try to build packages from source and giving up because I didn’t have time to solve all the build problems. It was always much quicker to just use a Pi and I was skeptical about the Edison being a solid long-term commercial option.
Also, lol, actually clicked reply without noticing the name.
FiOT, failed Internet of things, welcome intel to the family. I Wonder if all those documents were easier to get with a NDA as that seems to be the trend, no NDA no docs. The one things x86 has never done for me that arm devices has is bare metal code, when you start involving a bios and areas of the board hat have thier own OS + code like IME and i cant look at it. well that just puts me right off.
Sounds a bit like Qualcomm.
thats who i was actually thinking of.
Badges, we don’t need no stinkin’ badges..
Documentation, we don’t need no stinkin’ documentation..
It all depends how much time you are willing to invest. Trust me, you need documentation. I admire your macho attitude, sadly misplaced though it is. I dearly love reverse engineering, but there is no excuse for not providing top quality low level documentation for a product like this. Without it, it is doomed to fail. The poster child in all of this is the 4000+ page technical reference manual for the chip in the Beaglebone Black. That is the way to do things!! Thank you Texas Instruments!!!
On the flip side, I would rather be working with ARM than x86 anyway, so it is a total win to see these die.
Please forgive my ignorance. Why does an x86 board need a ton of documentation? Beyond what IO address is mapped to what pin (they did at least document that right???) isn’t it pretty much the same as the desktop processors which people have been documenting since the 1970s? I thought that was the whole point of having an x86 board? I still have my college textbook about x86 assembler as well as a few assembler books I bought at garage sales in the early 90s with the intention of one day (that still has not come) actually reading them.
My own only purposes for an x86 board would be to make a print server for a printer with no ARM drivers and maybe to serve as a really low end desktop that actually supports shitty internet videos that still haven’t been upgraded from Flash to HTML5. For everything else a much less expensive ARM board serves just fine. Intel’s offerings definitely did not fit my use case!
My own uses for x86 don’t seem like much but had they actually matched ARM on price, power consumption and solderability I would have been saying “x86 does everything I want and is familiar, what do I need ARM for?”. I would have used x86 for everything! I think Intel has really screwed up and thrown away their own monopoly. Am I really alone on this?
In other words, I prefer to keep everything on just one platform. One reason, which I suspect I share with many others is that there is only so much time in a day and I don’t want to learn two. A second reason, which I suspect is rare is that I always dreamed of having all my computers and devices sharing resources per something along the lines of Mosix/Open Mosix/Linux PMI. The fact that a couple little things require me to have x86 while ARM makes so much more sense for everything else really ticks me off.
This is still the best example I’ve seen of someone actually using an Edison or five to do useful work. The author touches on the lack of documentation, but managed to get it to work anyway: http://lcamtuf.coredump.cx/edison_fuzz/
But Intel’s lack of focus on the product comes through.
Wow. That’s a really cool link… it gives all in one a comparison of Edison to e.g. Odroid and shows it was a pretty nice piece of hardware, but some early adopter bumps along the road.
These weren’t PCs. You need significant patches to the kernel to deal with the lack of ACPI / e820 / mptables and standard PC peripheral I/O (no 16550 @ 3f8, no port 80, etc). On Edison at least, all of the I/O was through a coprocessor (i think it was a Quark?) so any flash, SPI, GPIO, or WiFi access was through a mailbox to be serviced by the coprocessor’s RTOS. And Intel barely documented that.
The only advantage would have been if it used a more common Linux distro (Debian, OpenSuSE, etc) since you could install x86 fork packages. But since Intel only pushed Yocto there was no point to the x86 compatibility.
The only thing these boards had going for them was MIPS/W, and that was entirely due to Intel’s heavy investment into process technology and not any innovation whatsoever.
Not too surprised.
Not sure anyone will notice. Our makerspace got one free from MAKE, but Intel’s lack of support of the IDE and libraries made if almost impossible to use.
Too bad…those Edison modules make killer Debian boxes. Guess its time to stock up while i can.
I was really hoping for a Edison-like board with a new HPS variant marrying an x86 core to a high speed Altera programmable fabric. While this announcement doesn’t significantly increase the precipitation chance of raining on my dream, it does start to cloud up the sky.
Any updates on the future of the Quark D1000/2000 and SE C1000 microcontrollers? Does anyone actually use these?
They sure look interesting, they could be ESP32 contenders. I’m specifically eyeballing those hardware neurons for pattern matching, but where is the example code for that?
Something else as well as all of the above. When I design home automation – for my own home – I want to know that whatever prepackaged parts I use will be available in a decade when these fail. No exceptions for “well this is shinier” or “better” or “cheaper” (well, intel fails on that anyway). I don’t even use my own custom PCB’s with PIC uPs like the old days, because…I don’t like having to make more. (I’m not young). This is the real reason I use overpriced/mip arduino or pi – there are so many – and yes, so much support – I’ll be able to buy them 10 years after I’m dead on ebay…
While intel and others have a long, horrible track record of which dropping these is merely the latest example. Can’t count on a vendor? Then don’t count on them. They should not be surprised at the lack of design-ins. They just want the one big score, the lottery win of some huge product – then they’re fine. Pretending they care about the (also enormous) money from we little guys – you’re kidding. They are defined by their actions.
Companies i used to design product for would barely use a PC mobo because of fear they wouldn’t be around forever and they’d be stuck without a product. This few month or a year crap? No way.
So it’s not just us they lose on this behavior. It’s their own badly defined target.
Intel is great but they do this to themselves, a very aggressive bean counter group who plots the ROI on walking to the water cooler, has to be profit or forget it. They will can projects that are 96% finished and on time.
Was @ BAMF a few years ago when the Edison was released. Was out looking for the next core for a significant project at the time. Took one look at the development chain, docs, price and the goofball connector and put it back on the shelf. Went with a beefy Atmel ATMega chip that could be integrated into the design for under $10 single quantity, the docs were right on the website, and a tool chain that was already installed in our dev environment.
On the other hand, don’t forget intel was/is pretty strong in the embedded community for a very long time with the 8085, 80186, and the i960. The i960, in particular was a pretty rocking bit of kit for it’s day.
On the intel NDA front, I get to see some distance into the future on several intel product lines at $DAY_JOB via NDA. These people know what they are doing, technology wise, and have a clear vision. This decision smells like bad marketing to me.
Remember Captain Zilog anyone?
10$ says Microsoft promised specialized .NET frameworks and ongoing support then backed out for no reason.
Microsoft’s present CEO has his head even farther up his rear than Balmer did.
Intel Edison while a neat product, had many flaws:
– Was marketed to the wrong crowd(almost non-existent) crowd.
– Intel forced their build of yocto on everyone instead of going with something straightforward like Debian,
– Had a hard to use connector meaning that the user had to pay at least as much on breakout boards as the darned SBC to be able to do hardware interfacing,
– Had the most obscure GPIO pin multiplexing that I’ve ever seen
I hope Intel learns a lesson from this experience. That lesson should be that they ought to stick to making i3//5/7/Xeon CPUs and forget about the IOT/Hobbyist/SBC space. Their corporate mentality just doesn’t work well within that space.
GoodBye Edison, Gallileo and Joule
For the lower end boards even being able to use Free DOS would have been nice.
The two biggest problems why it failed no clear documentation and no tools that allowed someone to get really low level with the chip.
Other mistakes use of an oddball hirose connector that was difficult to source and work with.
https://software.intel.com/en-us/node/721483 programmer reference. I think it failed for one reason, price. For $225 I would get some older motherboard; This unit would need to cost under $80 for me to even consider it. What are they thinking? try to get super rich from this market of people who recycle and glue things together rather than spend $1?
Does anyone happen to have a discounted or marketing version or kit of any of these boards that I could possibly try?
So Tesla is highly successful and Edison is a total failure? Balance has been restored. ;)
Which AC/DC tune is appropriate?
I have my Galileo in a drawer close by, so I can comment on this with some authority. These things deserved to die.
1) The utter lack of documentation (or miserable nature of it) is certainly a key factor, and has been mentioned many times already. People I know “with clout” could not get questions answered or decent documentation.
2) Beyond that, the miserable price/performance ratio. I benchmarked these relative to an ARM based board, and guess what? The 400 Mhz x86 on the Galileo cranks Dhrystones at about 4/10 the rate of a less expensive and better documented ARM board running at 1Ghz. Why pay more for something that runs 4/10 the speed of something smaller and cleaner? Unless you have some weird nostalgia for Intel and x86.
Dumb question – why are x86 platforms still so bloody expensive? The design is ancient so I would think the silicon would be incredibly cheap by now (for lower end processors anyway). Any time I’ve ever seen an x86 based anything, I’ve assumed that it will be ridiculously expensive compared to its ARM counterpart.
I hope whoever handled their software support staff takes note. Their support was hopeless. One example, just take a look at how one re-flashes a new chip if the initial java script does not work (https://software.intel.com/en-us/flashing-firmware-on-your-intel-edison-board-windows). Can you believe such a run around in 2017. There was one good support person there “Jose” the rest were hopeless. I spend a lot of time with this chip see:-
http://s100computers.com/My%20System%20Pages/Edison%20Board/Edison%20CPU%20Board.htm
in the end I had to figure most of the stuff out myself.
I saw an intel ad the other day that advertised some “deep learning Iot future” muck aimed at small business with no actual advertised product, except for “cool futuristic intel”. It was an effective ad, except for that fact. I think intel is going the way of IBM, they feel their market share is garunteed, so they focus on just keeping in the public attention.
I did an intelligent robot with the Edison, and that´s about it, never the first choice for a project… https://www.instructables.com/id/Red-Neuronal-En-Intel-Edison/
I have two robots using Edison and replaced a Beaglebone with one. Mainly, I gained space. An Edison on the small breakout board on a custom PCB can fit a lot in, with free WiFi. I don’t like Yocto Linux much (contrary to several comments, it doesn’t run DOS!) but the Eclipse-based tool chain was fine. Their mraa library is poorly designed but at least it’s open source. Overall, I’ve had success with it. I’ll buy a couple more before the end of the year and then maybe switch to Beaglebone Blue.