editor's blog
Subscribe Now

A Vote for Java

I don’t know this for sure, but I can imagine that some marketing folks at STMicroelectronics were less than thrilled by the high-profile Java issues ricocheting through the airwaves a couple weeks ago. My colleague Jim Turley engendered some back-and-forth with his analysis of the appropriateness of Java in embedded systems in particular.

It was not but a few days after this had barely disappeared from the headlines that ST announced their STM32Java development kit for developing Java applications on embedded systems. Such an announcement might have been routine on any other week. (Of course, had it been routine, you might not be reading about it here…)

I just had to check in with ST’s Michael Markowitz; the question was just sitting there like a lonely technical support hotline agent with no calls in the queue: “Ask me!” The issue, of course, is security. Will using Java in white goods ultimately allow the dryer to infect the washing machine? Could a WiFi-enabled cordless drill be instructed by a trench-coat-wearing lurker behind the boxwood to stop drilling the furniture and turn on its master instead? Could a smart showerhead be maliciously configured by an unauthorized plumber to broadcast pictures to the Internet?

OK, I didn’t ask those questions specifically. It’s early, OK? I’m still not far into my cuppa Joe, blundering about a bit in that happy gray zone between waking and sleeping. But I did ask for comment regarding the blaring warnings that were still echoing off the hillsides. Having checked with the team, Michael responded  that, as far as they could tell, the issue wasn’t intrinsic to Java specifically, but rather was related to “a badly programmed library, that… allows a program to access another program on the host machine,… crossing the ‘sand box.’” Having no such concept in its architecture, STM32Java would therefore not be affected.

So the simple answer would then be, “Not an issue.” Of course, this deals specifically with the one vulnerability identified in the latest brouhaha. There are those that take issue with Java generically: this doesn’t address that. But, given the amount of opinion and philosophy that accompanies this debate, I can only conclude that there are no fundamental facts to settle the issue one way or another. It would seem that abandoning Java on computers would be reasonably disruptive; if it migrates onto embedded systems in a universal way, we’ll be just that much more strongly wedded to it.

ST, at the very least, is moving forward undeterred. You can read more about it in their release.

Leave a Reply

featured blogs
Sep 23, 2020
The great canning lid shortage of 75, the great storm of 87, the great snow of 54, the great freeze of 48... will we one day be talking about the great toilet roll shortage of 2020?...
Sep 23, 2020
CadenceLIVE 2020 India, our first digital conference held on 9-10 September and what an event it was! With 75 technical paper presentations, four keynotes, a virtual exhibition area, and fun... [[ Click on the title to access the full blog on the Cadence Community site. ]]...
Sep 22, 2020
I am a child of the 80s.  I grew up when the idea of home computing was very new.  My first experience of any kind of computer was an Apple II that my Dad brought home from work. It was the only computer his company possessed, and every few weeks he would need to cr...
Sep 18, 2020
[From the last episode: We put the various pieces of a memory together to show the whole thing.] Before we finally turn our memory discussion into an AI discussion, let'€™s take on one annoying little detail that I'€™ve referred to a few times, but have kept putting off. ...

Featured Video

AI SoC Chats: Memory Interface IP - DDR, LPDDR, HBM, GDDR

Sponsored by Synopsys

When building AI SoCs, how do you choose the optimal memory interface? Learn about the market trends and challenges for DDR, LPDDR, HBM, and GDDR, and how Synopsys DesignWare IP can help.

Click here for more information about DesignWare IP for Amazing AI

Featured Paper

The Cryptography Handbook

Sponsored by Maxim Integrated

The Cryptography Handbook is designed to be a quick study guide for a product development engineer, taking an engineering rather than theoretical approach. In this series, we start with a general overview and then define the characteristics of a secure cryptographic system. We then describe various cryptographic concepts and provide an implementation-centric explanation of physically unclonable function (PUF) technology. We hope that this approach will give the busy engineer a quick understanding of the basic concepts of cryptography and provide a relatively fast way to integrate security in his/her design.

Click here to download the whitepaper

Featured Chalk Talk

Machine Learning at the Edge

Sponsored by Mouser Electronics and NXP

AI and neural networks are part of almost every new system design these days. But, most system designers are just coming to grips with the implications of designing AI into their systems. In this episode of Chalk Talk, Amelia Dalton chats with Anthony Huereca of NXP about the ins and outs of machine learning and the NXP iEQ Machine Learning Software Development Environment.

Click here for more information about NXP Semiconductors i.MX RT1060 EVK Evaluation Kit (MIMXRT1060-EVK)