|
What is "Daruino"? I do a lot of microcontroller hobby projects using Arduino boards, ATMega chips, and STMicro ARM chips, so I'm a likely customer for your project. I don't think I'd have a use for #1. I am not often performance-limited on the ATMega328, except for applications involving lots of high-resolution PWM, which wouldn't fit on such a device due to its limited array of IO pins. #2 is interesting, though I wonder how long the Dip28 format will remain relevant. The LeafLabs people have tried doing the straight-line upgrade path from Arduino by designing a board with the same form factor, but your idea is even more elegant. I might use a handful of these for prototyping. #3 sounds a lot like the Maple board. The crucial thing here is the growth path from protoboards up to custom circuits. The STM32Discovery board is cheap and capable, but its toolchain story is totally fucked (windows only proprietary uploader, undocumented protocol!), so it ends up being useless for prototyping. The Maple board is good, but it is hampered by the use of the Arduino IDE. It's really easy to outgrow the editor's constraints when you are developing for a Cortex-M3 chip, but it's not easy at all to break your project out into a gcc/makefile/upload type world. At least, I've had no luck making it work. #3+#4 sounds like you're reinventing Arduino shields, no? Again, maple did basically the same thing and it seems to work out ok. I don't think you need to worry about collision with Raspberry Pi, despite the price-point overlap. Not in the near term, at least, simply because of power consumption and complexity. It's a miniature computer, not a beefy microcontroller; I generally don't want an operating system getting in my way when I'm building embedded stuff. Arduino took over because it offered a totally unbeatable development experience and didn't try to box you in. It's about as simple a process as one could possibly expect: you write code, pick a target board, push "upload", and it runs. It's all open standards under the hood, and they document everything you need to know about the board design, so there's no vendor lock-in anywhere. Mimic this strategy and you will go far. In fact I would say that your toolchain is more important than the capabilities of your board! Anyone who is capable of pushing through a dodgy toolchain to get their prototypes working is probably capable of building their own devboards, or of adapting some existing devboard to their needs. The real market opportunity comes from offering a seamless experience to beginners which still allows them a smooth upgrade path out of your environment. Beginners don't stay beginners forever, but the Arduino experience shows that ex-beginners will stick with your brand and buy your products as a convenience even once they've moved on and learned how to design their own, but only if you make it easy for them to outgrow you. |