On 02/18/2014 05:49 PM, Trevor Woerner wrote: > Hi, > > I'm sure by now everyone has seen the recent ST announcement for their > "nucleo" boards?[1][2][3] How ironic that, just the other day on IRC, we > were talking about higher-layer hardware abstractions and it was > mentioned that, if anything, it would be a good idea to consider a new > fake machine (like arduino did) instead of trying to make it too much > like any existing hardware. > > It'll be interesting to see what ST does with regards to providing > libraries for these devices. I assume they will be ports of the existing > arduino libraries? Or maybe they will just provide mbed interfaces? > > I wonder if there is any interest in making a generic libopencm3 > "arduino" library that would support all the boards currently supported > by this project? >
libmaple is exactly this, and long established. If you want something that probably has a brighter future, mbed apis seem to be what st/mbed are supporting going forward. (Don't mean any disrespect to the maple guys, I wish they'd gotten more traction earlier, but these days, I'd just buy a disco board and use libopencm3, rather than trying to get arduino code to work) I don't really think you're going to see much interest in people writing an arduino compatible layer directly _in_ libopencm3, but it's something you could easily do using libopencm3 as the layer underneath. The _majority_ of existing libopencm3 code is low level, very tied to specific chips, with a few higher level helper functions appearing. We'll probably see more of those higher level functions, and even for the hardware specific code, they'll generally be in a similar _style_ but I personally feel that a fully abstract high level api is something that would generally be another project built on libopencm3. (I think I just repeated myself! oops) Of course, doing that would potentially be lot easier if the licensing was more explicit about the static linking quirks of LGPL ;) (Note, this is just me, don't read too much into this as any sort of "official" direction statement or anything) mbed is going to be supporting freescale, LPC and ST boards, and they've got corporate backing. It's also a lot more appealing now that they properly support using it offline. If you want to see a common api, mbed is probably who I'd be backing. Cheers, Karl P ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list libopencm3-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
