Hi there,
Well I have a project that involves basic GPS and a smallish (128x128) tft display. Portable with very low power consumption and size are the main constraints. I'm fairly experienced in 8-bit and 16-bit devices, PIC16/18F, AVR etc.. but given the display requires a basic menu system, and the flash to store the pages (and >6kb SRAM for logs, because its lower power than external flash) it looks like it's a job for a 32-bit device, to me it says 'm0'. With so many vendors, devices, as you can tell by the large number of 'which is better?' posts, I too have become overwhelmed by choice.
It is fairly straight forward to narrow down results based on power consumption and peripheral set, but even then, I've ended up with a long list where all devices meet requirements and are fairly low cost to boot. These include:
-Atmel SAML, SAMD series: Good experience with Atmel, only requires a dev board (with on board programmer/debugger) and Atmel studio. I'm familiar with the docs and doesn't seem a great leap from AVR's. Haven't' seen many hobby projects based on these. Seems much more vendor specific than the following.
-LPC11xx: never used NXP devices, but there's a lot of example projects on the web, a big following.
-STM32L, or F0: Again, big following, cheap dev boards (with built in debugger). Plenty of resources, but seems like it requires a lot of set up for the dev enviroment.
-EFM32: Wild card, seems to have the lowest power consumption, plenty of peripherals and fairly cheap, but I have no idea where to start with a toolchain.
-PIC32: seems to be the easiest to get started, but doesn't appear to have the best power consumption, and isn't ARM based so might provide and excuse to 'put off' getting used to using ARM devices.
I'm sure all the above are more than capable, but as always, I get stuck on making decisions because it would be nice to not be completely locked into one vendor (specs change!) which means I'm leaning towards LPC11 or STM32, but the very basic (and common question) is .. where do I start?! I have read plenty of threads that list wildly different setups from 'just buy the IDE' to open source toolchains requiring multiple systems configured. Of course a single all-in-one IDE would be ideal, but there are even quite a few of those it seems. I listed the SAML (or SAMD) first because, well, Atmel is tried and trusted.
So I know I'm probably going to get flamed for this, and there will be those furiously defending their 'choice', and I am acutely aware there is no 'best' vendor. But at the same time, the idea of buying a few dev boards, installing multiple IDE's and trying them one at a time doesn't thrill me. The restrictions are no longer 'cost and availability' but 'time taken to get a reasonably comfortable working environment/flow for 'blink' projects, and regular code modifications.
I may even start developing the main menu and sensor algorithms on an... Arduino... purely because there are many libraries for taking the donkey work out of drivers, and they are just very easy for testing software snippets, basic algorithms and getting used to communicating with external devices. But it is far from ideal for the application (2-3V, low power, and low duty), so I'm using this as an excuse to get a wriggle on, and asking the forum what they would consider the most straight forward (no manually creating makefiles, 'good enough' built in libraries and simple workflow) vendor to go with.
Apologies again, I'll try to ask this again... but I simply don't have time to try them all.