If you read the description it says it has its own ide called maple, they claim it is code compatible with Arduino. This means you can grab the blink example and paste it on maple ide, and it will compile.

I just bought one of those mini maple leafs, at only a few quid it is worth the risk just to find out how it flies.

Me too (the Maple clone, not the original item I posted)

The Maple documentation & IDE seems reasonably good. Lets hope these clones are not significantly different in any important respect. The only differences the vendor mentions is related to power supply and board layers. This may mean we won't get the 11~12 bits accuracy of the original Maple on the analog inputs.

Shame the Maple forum is a graveyard compared to Arduino forum! Sounds like LeafLabs may be abandoning support, or at least future development for the Mini.

I just bought one of those mini maple leafs, at only a few quid it is worth the risk just to find out how it flies.

And me too - marginally cheaper again on the Australian site. The seller (I figure one seller frequently operates under a number of names; they come with the same postmark!) might wonder about/ be amused by the sudden "blip" in sales of one item.

It's sort of a beefed-up Nano, as is Crossroads' device. Runs at 3.3V so you really, really don't want to stress the regulator. And the clone is very much stripped-down from the original, missing the analog noise minimisation features.

But in general, the ARM 32-bit is just another processor. In most of the projects that I cloned from the Arduino world, the 8-bit Arduino worked equally as well as the 32-bit ARM. The Cypress PSoC has some great hardware features such as OpAmps, Configurable digital blocks, and way cool PWM. But, the downside is the community... small communities mean more work for me (you) as you must research, implement, write, lots of support software.

Personally, except for specific things such as FFT or native 32-bit algorithms, I think the Arduino 8-bit and Due 32-bit environments are more productive. Although the GUI is a sad excuse when compared to what professional tools can provide.

In my case, it comes down to fun. I learned a lots with the 32-bit ARM but I also used a lots of 4-letter words from my old Air Force days.

Here is the last sentence of my blog:

Quote

Hurry-up and wait in the Arduino translated to hurry-up and wait longer in the PSoC.

1. The community is often the most important component for getting a project working! It was/is true of the PicAxe forum and its true here.

2. Simpler is often better for the hobbyist. That's why Arduino has been successful. When the hobbyist outgrows the 8-bit AVRs, the need is often simply for more speed, ram and/or flash.

Megas, Bobuinos and the like only really provide 2 of those 3. The 16 (or 20) MHz limit, combined with 8-bit architecture, can become the next bottleneck.

Having said that, and before anyone else comments, I expect 4 out of 5 Arduino users hit those limits because of inefficiencies in their own sketch. Learning to make better use of those limited resources is where they should probably focus, rather than immediately reaching for more powerful hardware, because that will only result in their sketch becoming even more inefficient!

You probably remember my fascination with Conway's Game of Life. I would still like to adapt my algorithm for a larger matrix. For that I would need more ram. Currently it maxes out the ram on a mega328 processing a 128x64 matrix. A Mega644/1284 would allow that, but to keep up the speed on that larger matrix, I would need more processing speed too. So that's one thing I would like to try out on this ARM-thing one day.