| Hi, Ian. Yes, there has been considerable discussion regarding both MQTT and LWM2M around Apache Mynewt. I think that there is definitely a path towards inclusion, particularly as IP networking support is solidified (currently, with 0.9, there is BLE 4.2). The discussion needs to occur on the Apache Mynewt ‘dev’ email list so that we can ensure community consensus.
I look forward to seeing iterations of the paper and will be happy to provide some feedback, if useful.
best,
James James, Nice to hear from you. I will certainly add Mynewt as an example IoT OS. Feel free to add comments to the white paper too. We should also look for ways to collaborate. Would it make sense for Eclipse Paho (MQTT) or Eclipse Wakkama (LWM2M) SDKs to be delivered with Mynewt? Hello, Ian, All. This paper is a great start for a broad yet extensive survey of IoT stacks! Under “IoT Operating Systems”, I would also like to point out the Apache Mynewt (incubation) project in the Apache Software Foundation. Apache Mynewt includes the world’s first controller-level open source Bluetooth Low Energy for microcontrollers. Apache Mynewt is notable in a few respects; to name a few: community driven + permissively licensed (Apache 2.0) project embedded work; world’s first open source Bluetooth Low Energy stack for constrained (MCU) environments; a composable OS with a number of services. The OS is composable via a modern, gpm- or npm-like build and package management tool. Components include secure boot loader, flash file system and TLV storage mechanism, rich logging infrastructure, circular buffering schemes, and BLE! Interpreters for Python and Lua are now complete; a _javascript_ interpreter is currently being worked. Specific to the OS with BLE (4.2), the open source approach has obvious benefits to developers: access to source code; better debugging (breakpoints!), avoiding stack smashes, no stolen interrupts, etc.; direct access to peripherals for granular power control; better, precise configurability of concurrent connections and flexibility across central and peripheral roles. It’s still early days, but the community would appreciate the exposure and, even better, love to find a way to collaborate.
Benjamin and I have been working on a new way to talk about the Eclipse IoT community. Our community has come a long way over the last number of years. We typically talk about Eclipse IoT as implementing IoT standards and IoT frameworks. This is certainly still true but I think it does not encompass a lot of our new projects. The new approach we are suggesting is to show how the Eclipse IoT community is implementing 3 different stacks of open source software for IoT solutions. The 3 stacks target: 1) devices, 2) gateways and 3) IoT platforms. We have written the first draft of a white paper to describe each of these stacks. We will also be following up with a presentation and eventually an update web site.
_______________________________________________ iot-wg mailing list iot-wg@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/iot-wg
|
