i think the most likely moves into offering a real world online tool development chain are likely to be cypress with its xml based psoc software framework for everything from 8051 to ARM and possibly Microchip which has a javabeans based environment across its entire mcu family from original 8/16 bitters up to its mips based MCUs.
alex, I have the same impression. With a local tool you can optimize its behavior, add useful plugins, and the like. But I see no reaon that cannot be done on the cloud rather than on your desktop. simply a matter of progamming :-)
I think Bernie is right that a cloud-based IDE is likely to be architecture specific as opposed to being useful for a wide range of microprocessors. But with ARM becoming so widely adopted, you would think that such a tool would have a large enough market. If people would use it, that is.
re rich comment. i agree. that is why i think that such ides will be hardware specific or vendor specific, ie mbed. if a freescale or a ti did it, they could offer a range of online development environments across a broad range of development tools, external and open source, that offers something like what is needed.
@rickmerritt & @richQ: those are actual dev boards (snapdragons, tegra-based etc.) - physical real devices on you can test other things than just apps. And generally what is understood as a fragmentation on Android is not just software related but hardware has lots of things to do with it as well.
ironically with a lot of corporate environments, tools and platforms have been webized to allow their developers to collaborate in real time and to synch up when they are working on code relating to same, ie versioning, other mechanims to keep programmers from stepping on each others toes. ibm is the earliest company i remember doing that. if anything like a real heavy duty online development environment for outside happens it will come out of one of those internal systems.
@Bernie, a similar point was made at the FTC's IoT workshop earlier this week. Someone said that we're going to have to deal with some security disasters before we even understand the problem well enough to come up with solutions.
security is going to be an ongoing problem. not because engineers and developers do not want it and see its need, but because of corporate accountants and "practical business men" who are still reluctant to invest, nor see the need to, invest beyound what they perceive is the bare minumum - until they get wacked, and then everything changes.l
@Berine, security is a concern. One would hope that standard web security practices were in effect, but how about the privacy of your design information? That is a concern some have raised. How can you protect your intellectual property when it is being hosted on someone else's system?
anusure, other use cases might be that the cloud serves as a "co processor" for the embedded device. Collect raw data, pass it to the cloud, get the FFT back, and take action. Slow, but saves cost on the device end.
other than ec2 from amazon, no thought seems to be given at this point to security. suprisingly not even mbed for arm's cortex m0. nothing in book i read, nor online at mbed except for three questions from potential users in the sites forum: one a year ago and two others three years ago. no response to their queries. but that does not mean that mbed did not insitute security. but no indication on the site about that.
cloud services still pretty crappy and uneven not only about reliability but security as well.
One of the things I was wondering was about the loss of control if you do development using web-based tools. What happens if the provider upgrades their tool and what you were doing suddenly no longer works?
Anusure, if you choose a technology that allows TCP/IP all the way to the end node, it is a little easier to manage remotely. Otherwise you have to put in a translation stage somewhere to convert things.
re security, except for amazon's cloud ec2 offering actually gives some thought to security, from what I have heard. Microchip uses it for its most recent "internet of things" tool. But its mainstream free development tool is not offered that way, although since it is based i believe on Java Beans framework could be easily adapted.
rick we could test out our app on multiple MCUs, but in today's embedded development world, that would involve a lot of work porting the C program to reflect different memory maps, then recompiling. Not something folks are willing to do without the promise of a substantial payback. Not worth doing just to find a few percent improvement
Before the so-called cloud eclipsed the use of the terminology "web services," as noted, several embedded software vendors were using online services, including several embedded linux vendors, and fpga tool vendor altium, which i think has its web capability built around Microsoft server framework. Several companies are already halfway there using tools that would allow them to easily up grade - cypress psoc software tools are built on an xml framework, for example.
Not familiar with any remote testing capabilities at present. There have been attempts to do this in the past, but it required scheduling of time on the testbed, and that became a logistics nightmare when scaled to more than a handful of potential users.
Web and apps developers have worked with cloud-based tools for years. Why can't embedded developers do the same? Would they want to?
Join us on a live chat on this topic on Friday, Nov. 22, at 10am Pacific (1pm Eastern or 1800 GMT). If you have experience doing emebdded development using cloud-based development tools, please join in and share your experiences.
My Mom the Radio Star Max MaxfieldPost a comment I've said it before and I'll say it again -- it's a funny old world when you come to think about it. Last Friday lunchtime, for example, I received an email from Tim Levell, the editor for ...
A Book For All Reasons Bernard Cole2 comments Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...