Hi, > I'd love your thoughts on something, as it seems like you've played > with Arduino a bunch.
Just a bit of 7 years or so. One conference I went to they made a wanted poster of me with the caption “Playing with toys when he should be working" :-) > Is it the hardware platform, or the wiring interface that you see most > appealing? There are a few things that appeal: 1. The community 2. The availability of hardware and cheap prototyping shields/boards 3. Easy to upload programs via the IDE (via USB) 4. Build in libraries for most common tasks 5. Large amount of existing code out there 6. The simplicity of the language / framework and IDE Al of that makes for a good prototyping platform, and given smaller form factor boards you can quickly turn a breadboard prototype into usable working prototype often without having to make your own boards. Also a lot of people coming to it the platform have little C (or in some cases modern IDE) experience so they see more complex stuff as very difficult so it works for them. That being said it’s certainly not a a solution that fits everything. As soon as you want to do anything more complex particularly involving scheduling or multiple tasks at once it can become very difficult quit quickly. > As I'm sure you're aware, the wiring > interfaces are somewhat limited for more complex functions that you > might want to perform (i.e. responding quickly to a change in state on > multiple GPIO.) I’ve not actually run into this issue, it generally fast enough for bit banging, controlling displays and the like but there are probably a few situations where's it is too slow. > Do you think that providing a matching interface (or a port of wiring > to our RTOS) will likely bring a lot of people in? Not sure what would be best here, but: 1. Porting Mynewt to common arduino hardware would mean there’s more cheap hardware out there that people are familiar with. 2. Being able to use the many arduino libraries inside Mynewt would be advantage. I can’t see that as being too difficult for most of them as they tend to be C and there’s a simple HAL i.e. you tell it what pins to use and it calls a few simple functions to use GPIOs and analog inputs. Thanks, Justin
