I once worked for a company that had produced one of the first (if not the first) integrated GSM baseband & transceiver chips. From the hardware perspective, it was a crowning technical achievement and would have resulted in significant BOM savings to customers, but they weren't eating it up...why not? Customers didn't want to invest the significant time and resources to change their firmware/software stack. It didn't help that a competitor bought out a critical portion of the software stack either.
The lesson is don't understimate the support costs for hardware.
>If the product was ready to go, then why didn't Renesas go with it?
I don't think it was anything to do with technology or product readiness. Renesas just did not have the fuel run it and they wanted to focus on their core bussiness. Unfortunately mobile chipset was not one of them to give it any time to get the returns.
If the product was ready to go, then why didn't Renesas go with it? Same thing goes for the reported ST/Ericsson design that works. Companies go and get certified, but that does not mean it is a good working product ready for the market. But several companies keep saying they're certified.
@Hughston, personally, i never expected this to happen. As you correctly point out, Broadcom was doing all the LTE demos at the tradeshow, as though nothing had gone wrong. As for Renesas LTE modem, judging from some comments we received from Renesas Mobile engineers on our forum here at www.eetimes.com, the chip -- already certified by several operators -- is ready go, in the hands of a few customers. It appears Broadcom this time around has a real thing...
I was wondering if you ever expected this to happen? Broadcomm was having problems with their design but doing demos at trade shows like everything was ok. Clearly things were not ok. Now I wonder if they are buying a working design this time or not. It seems other companies have gone quiet also about their progress.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.