editor's blog
Subscribe Now

Micrium’s Spectrum IoT Package

There are a couple of things going on in the world of the Internet of Things (IoT). One is abstraction and reuse: no one wants to re-invent WiFi or security or the many other things that have to be plugged together in order to get a device to connect to the Cloud. So complete packages that include support for all of these basics are becoming more common.

But there’s also a meeting of minds happening (or not): Micrium, a provider of real-time OSes (and supporting goodies) notes that embedded programmers primarily use C, occasionally broadening out into C++ or even Java as needs dictate and as space and performance allow. Cloud programmers, by contrast, tend to use things like HTML, Ruby, and have a much greater reliance on C++ and Java.

So… what happens when the low-level device programmer needs to write code that accesses the Cloud?

This is part of the motivation for Micrium’s Spectrum package. It includes their µC/OS-II (or –III) RTOS and stacks for network and IoT protocols. There’s also a Java virtual machine (VM) for deeply-embedded applications (running about 40K of code) – and an interface to Cloud services.

They’ve structured the Java VM so that it doesn’t require a separate core; it can reside on a single core with other code, which means less hardware is needed.

As to the Cloud interface, they’re working with a company called 2lemetry. The details are a bit vague (welcome to the IoT), but this appears to act as an aggregator for interfacing with the formal Cloud. The way they describe it, the Cloud is set up for relatively few high-bandwidth connections from things like phones and tablets. That’s as distinct from how sensor-enabled Things work, with many low-bandwidth connections. This intermediate layer appears to pull together and pre-digest data for interaction with the Cloud.

I haven’t seen an arrangement like that proposed before for the consumer IoT (CIoT) (although it might be buried implicitly in some of the platforms). It does resemble some of what goes on in the Industrial IoT (IIoT), with its greater reliance on hubs and gateways and brokers (literally or implicitly, via protocols like DDS) to filter data before sending it to the Cloud. But in this case, it would appear that this gateway function actually resides in the cloud, not locally.

The following graphic illustrates the content and relationships between the various Spectrum elements.

IoT-Software-Stack_500.png

Image courtesy Micrium

You can find out more in their announcement.

Leave a Reply

featured blogs
Mar 27, 2020
[From the last episode: We saw how pointers are an important kind of variable, representing data whose location we can'€™t predict in advance.] We saw last time that pointers are used to store the addresses of data stored in memory space that'€™s allocated while the progr...
Mar 27, 2020
Have you ever paused to consider how temptingly tasty electronic circuits would look if their components and copper tracks were mounted on a glass substrate?...
Mar 27, 2020
Solar Power While the cost and benefits of solar power can and have been debated, there'€™s one point that cannot be debated:  the solar energy sector continues to grow.   The solar energy sector has grown 68% over the last decade, and the cost of solar infrastruc...
Mar 26, 2020
Late last week you may have seen the open letter  from our CEO, Tony Hemmelgarn, laying out the steps that Siemens Digital Industries Software is taking to support our customers during the COVID-19 global crisis. All of us are getting use to the “new normal” ...

Featured Video

LE Audio Over Bluetooth with DesignWare Bluetooth IP

Sponsored by Synopsys

The video shows the new LE Audio using Synopsys® DesignWare® Bluetooth 5.2 PHY IP and Link Layer IP with isochronous channels, and ARC® Data Fusion IP Subsystem with ARC EM9D Processor, running the LC3 codec supporting LE Audio.

Click here for more information about Bluetooth, Thread, Zigbee IP Solutions