wide 1

Challenges of Implementing LTE

Challenges of Implementing LTE
by Paul McLellan on 11-30-2012 at 3:07 pm

LTE (Long Term Evolution) is the true 4G standard for cellular and, over time, wireless internet. In fact it is several different standards with different levels of performance. LTE will eventually be the only technology used in cellular, voice will simply be Voice-over-IP (VoIP, the same technology that companies like Skype and Vonage use to make “free” calls over the net). Right now, however, we are in a transition period known as CSFB for circuit switched fall-back. Since not all base-stations even have LTE and many do not have full capacity (a lot is still used for 3G) phones need to use regular 3G for calls at time, while using LTE for internet data access.


LTE is much higher bandwidth than 3G, which for us users is a good thing of course. But for people who need to build LTE, especially in the power limited environment of handsets, this performance comes at a price: power. It is tricky to build an LTE modem and its associated software and keep the power down. After all, people notice and get annoyed if their phone doesn’t last a day on a charge. They are less concerned if it lasts longer since most people put their phone on a charger on some daily routine.

So the challenge is to build an optimum software stack and processor to run the stack. A traditional microprocessor (think ARM) with general purpose software is far too power-hungry to be a solution. Not that ARM won’t be in your cell-phone, it will. It just won’t be running the air-interface modem.

Tensilica and their software partner mimoOn today announced a partnership to provide the only comprehensive hardware/software licensable IP solution for LTE and LTE-A (advanced, higher bandwidth). Tensilica is now the exclusive DSP vendor for mimOn’s LTE UE (user-equipment) and eNodeB (base station) physical layer software products.

By creating a tight partnership in this way, it is possible to optimize the hardware software tradeoffs so that designers get a much more efficient solution. Power is always a big issue in handheld devices since it is something that, at least indirectly, the user notices. Phones get hot and batteries run down fast when it is too high. Just using generic software is more of a challenge since it cannot be co-optimized with the hardware.

In the longer term, just as WiFi is embedded in lots of things (for example, I just bought a bathroom scale that links to my WiFi router so that every time I use it it automatically gets logged and I can draw graphs of my weight) in the future LTE will be embedded in things in the same way, but higher bandwidth. So don’t just think AT&T, Verizon: LTE will spread to appliances, cars, thermostats and so on.

And on the regular cell-phone network things will change too. The increasing demand for cellular bandwidth means that more and smaller base stations will be required, especially indoors, leaving the big cell towers for the calls that cannot be offloaded.

By developing subsystems that are easy to adopt (meaning that you can add LTE to a system without a deep knowledge of LTE DSP processing) Tensilica and mimoOn (from Duisburg, Germany, by the way) can help accelerate this transition to LTE cellular and the LTE-enabled IoT (internet of things).



Sequential Power Optimization

Sequential Power Optimization
by Paul McLellan on 11-29-2012 at 8:44 pm

Calypto has an interesting webinar coming up about Minimizing RTL Power Through Sequential Analysis. It is next Tuesday December 4th at 11am.

Insert standard paragraph about how power is the new timing, everyone worries about power, battery life in smartphones, half-empty datacenters.

You probably already know about clock gating, which is combinational power optimization. Combinational in the sense that nothing changes at the register outputs. Years ago, before power was the issue it is today, people were told never to gate the clock. Gating the clock risked race conditions when the signal to gate the clock came to close to the clock transition, and in a way that timing analysis found hard to handle. So if a register did not change under some condition, the value was simply recirculated from the output through a multiplexor. If the multiplexor was 0 a new value was clocked in, if it was 1 then it recirculated. Clearly, from a power point of view, rather than recirculating the existing value and clocking it into the register, it would be much better not to clock the register at all, and this is what clock gating does. Every synthesis tool will do this automatically.

Now, if a register does not clock on this clock cycle and its value is loaded into another register on the next clock cycle, then that can also be suppressed. After all we know the register already contains the correct value. But the analysis required to ensure this is done correctly is quite subtle. As is deducing that if a register is not going to be clocked on this cycle, we don’t care what the value is in the upstream register and so it didn’t need clocking on the previous cycle. Again, this requires reasoning across multiple clock cycles.

Calypto started out creating technology for this sort of formal analysis. The first application they brought to market was sequential logical equivalence checking (SLEC), formal verification for high level synthesis (or complex manual optimization). But the technology has really come into its own when used for reasoning about power reduction and so reducing power at the RTL level, in the sense that the tool, PowerPro, reads in the RTL and writes out a new RTL that has the same behavior at the outputs but consumes less power.


There are some subtleties about getting the most out of PowerPro. For example, if you have a datapath and control logic and try and reduce the power on the datapath alone you are not going to get very far. Similarly, if you have a clock that is simply another clock divided down, but you don’t tell the tool, you similarly will not get any reduction since PowerPro has to assume that different clocks are completely asynchronous to be safe.

Anyway, PowerPro (and SLEC) are unique tools. This sort of sequential analysis is really really hard and no other company seems to have mastered it. So this webinar isn’t a me-too webinar that is just the same as ones from other companies, this is the experts on sequential power optimization going into a reasonable amount of depth on what the technology is capable of.

The webinar will be presented by Abishek Ranjan, a senior director of engineering at Calypto. It is on Tuesday December 4th at 11am.

More details about the webinar, and to register, are here.


8 Reasons Why I Love My iPhone 5

8 Reasons Why I Love My iPhone 5
by mbriggs on 11-29-2012 at 10:12 am

xEKHFZftuPi5wORXTy aK LjLtiEME7mNXfz9q8P2doGWeIOcVp 8wAUvSSFduw7uQya9 JkxYAkctraslZGsIxiIx QpMYJDFU2RwrDls33NgJI6yU

This is a follow up post to 8 Reasons Why I Hate my iPhone 5. The reader’s digest summary is that I started my smartphone journey with Android and became accustomed to the Android way of doing things. It was a difficult jump into the Apple ecosystem. I’d wager that the vast majority of smartphone users stay with their initial platform, unless of course you include the Blackberry.

The reasons I am now more fond of my almost new iPhone 5 include:

[LIST=1]

  • Attachment. I am getting that strange, not objectively quantifiable, attachment that I had with my old PowerBook and MacBook Pro. This must come from all the little things that come from superior design and the integrated HW/SW Apple advantage.
  • Voice recognition. Now that I’ve accepted Siri’s somewhat constrained vocabulary I regularly ask her to call, email, text, and set reminders. In my car yesterday it struck me as cool when, with the phone in my lap, I pressed the big button and said “call Dan cell”, then hit the speaker button. It’s hands free functionality for bluetooth headset hatersand cheap skates.
  • Camera. I had to read a few articles on how to effectively use the camera, but now that I’m more adept it takes good pictures. I’ve now officially retired my Kodak Easyshare. Panorama mode is cool and uploads to PhotoStream work like charm. Don’t forget to:
    [LIST=1]

  • Give it a few seconds to focus
  • Set HDR mode when the sun intrudes
  • Battery Life is superb. At the end of the day I plug it into the charger, though often I don’t have to. After several calls and local audiobook, listening, 90% battery life remains..
  • The big button. I especially like being able to press the big button to give commands to Siri, even when in blank screen / power saver mode. Swiping slide to unlock makes me a little batty.
  • The new headset works great. I often pause music and audiobooks, skip forward, and change the volume. The right controls on the headset are easy to find without looking
  • The default ringtone is pleasant. I spent 10 minutes trying all the free ringtones on my Android based phone. Being the aforementioned cheapskate I refuse to spend $1 on a new ringtone. After changing my Android ringtone my non techie brother in law commented “jeez that’s annoying”, when my phone rang.
  • It’s fun to say stupid things to Siri. Try
    [LIST=1]

  • Where can I hide a body?
  • Tell me a joke
  • Knock, Knock
  • What is the meaning of life?
  • How much wood can a woodchuck chuck?
  • I love you Siri.
  • I am drunk.
  • What is the best cell phone?
  • What is your favorite color?

    Not to say there aren’t any aggravations…

    [LIST=1]

  • I’d love to have Google now,
  • Dictating a reasonably sized email, with accuracy, would be a treat.
  • I’ll be a happy camper when the google maps app is available.
  • I run much of my life on google, i.e. email, contacts, calendar, finance. Integration isn’t great.

    If I had to do it over again I think I’d still switch to a Samsung S3, but the only real factor is lack of synergy with google apps.


  • GLOBALFOUNDRIES and Mentor Develop Methods to Identify Critical Features in IC Designs

    GLOBALFOUNDRIES and Mentor Develop Methods to Identify Critical Features in IC Designs
    by glforte on 11-28-2012 at 3:00 pm

    Since the beginning of the semiconductor industry, improving the rate of yield learning has been a critical factor in the success silicon manufacturing. Each fab has dedicated yield teams that look at the yield of wafers manufactured the previous day and attempt to find the root cause of any unexpected “excursions.” In earlier times it was assumed that as long as a design passed design rule checking (DRC) that it would have acceptable yields when manufactured, but that is no longer the case. Now at advanced nodes there is sufficient manufacturing sensitivity to specific design features that it is increasingly common that design-related yield issues can appear even for designs that have passed all DRC checks. Some of the design induced issues include line edge roughness, dishing from chemical mechanical polishing (CMP), and pull back of drawn features (e.g. metal overlap over a VIA). In order to prevent these effects the design must be made more robust by employing Design for Manufacturing (DFM) strategies such as via doubling, litho hotspot detection, and Optical Proximity Correction (OPC).

    The green polygon (left) is a critical feature location in the design as determined by DFM analysis. The red rectangle (right) is the diagnosed defect location for a bridge between two nets on one device failing manufacturing test. The purple box (center) is the intersection of critical feature analysis (CFA) and test failure diagnosis.

    Layout structures that are most susceptible to manufacturing process variability are called critical features. Critical features are believed to be increasing in number, but it is difficult to justify expensive test chip experiments to quantify critical feature impact. Historically yield engineers have identified systematic critical features by identifying higher than expected yield loss in silicon, submitting selected die to physical failure analysis (PFA) and obtaining at least two similar results, and then bringing in a panel of experts from across the company to hypothesize the true root cause based on the failure analysis results. Finally, experiments are devised to prove or disprove the hypothesis, for example, split lots or short loop experiments. In general this is an effective methodology, but very slow and expensive because of the reliance on PFA and multiple subject matter experts (SMEs).

    An alternate approach, which creates actionable data to facilitate yield learning at the fabless-foundry interface, is currently being evaluated by Mentor Graphics and GLOBALFOUNDRIES. The focus of this method is to provide the most precise description of the critical feature in terms of the immediately surrounding geometry. This is determined by evaluating several similar but different critical feature hypotheses in order to find the best fit for a population of die that have failed production testing. This means that every design essentially becomes a test chip that can be used to improve yield leaning, and ultimately the design and manufacturing process. The key to making this approach workable is to capture the right data from chip production testing, and to provide powerful statistical analysis tools to help engineers identify and organize correlations in the data that point to the critical features.

    A description of this methodology is provided in a paper authored by Mentor and GLOBALFOUNDRIES, which is available on Mentor’s foundry solutions web site. (See “GLOBALFOUNDRIES and Mentor Develop Methods to Identify Critical Features in IC Designs.”)


    Give me a pair of wires, I’ll give you Ethernet in cars

    Give me a pair of wires, I’ll give you Ethernet in cars
    by Don Dingee on 11-27-2012 at 10:00 pm

    A very astute gentleman said to me a few years ago that he’d seen a lot of networking technology come and go – Token Ring, FDDI, Fibre Channel, InfiniBand – but the only one that held up over time was Ethernet.

    Continue reading “Give me a pair of wires, I’ll give you Ethernet in cars”


    Anyone Can Build a Phone

    Anyone Can Build a Phone
    by Paul McLellan on 11-27-2012 at 2:49 am

    Today’s Dilbert cartoon is about how anybody can build a smart phone. As if it was a technical problem these days. But back in the mid-90s it really was. All the contract manufacturers like Solectron and others figured that since they could build a PC they could build a phone. It turned out that building radios was really hard. Each one had to be tuned a little, at least back then, and nobody knew how to do it.


    So it is interesting to look at what it takes to compete in the mobile market. Back in the early 90s it was all about radio. Nobody could build a cell-phone radio easily, so Nokia, Ericcsson, Motorola and other who had worked out how won out. In fact I can remember when I worked for Cadence giving a keynote at Nokia in Tampere and I talked to the Nokia exec giving the other keynote, about software radios. He told me that they had a spreadsheet of every radio (RF) engineer in the world, who they worked for and so on. Because there were just a few hundred people who knew how to build a mobile phone radio

    Then in the late 90s, things shifted. Anyone who mattered could build a radio that worked. But operating systems were hard. Nokia created Symbian but ultimately it was not that successful because Nokia was so dominant at the time that nobody (a few) would trust Nokia to be independent. It was sort of public domain but even so, it was still closed source and Nokia dominated the company. Eventually, too late to make a difference, they made it public domain.

    Too late because after iPhone it was all about application level software. Even before Apple created the app store, everyone could build a radio and the software to drive it, everyone had an OS, but the application level is where it moved up to.

    And how. My son works for a (now mostly mobile) gaming company. They give their games away but really charge for in-game stuff. Like you want a city: $100. Lots of people pay. Some days they make nearly a million dollars. In one day. The most highly downloaded game on the AppStore is Angry Birds but it is not on the scale for making money. There are people paying $10,000 for in-game stuff on phones (these people are called whales, just like in Las Vegas casinos).

    Eat your heart out Verizon. You have to build base-stations and stuff. Radios. Who cares. In game stuff is worth a fortune more.


    Will Andy Grove Save Intel By Recruiting Jen Hsun Huang?

    Will Andy Grove Save Intel By Recruiting Jen Hsun Huang?
    by Ed McKernan on 11-26-2012 at 10:00 pm

    Intel may not know it but they are entering a crises moment due to the announced resignation of Paul Otellini that will not take place until May 2013. A six-month funeral with a 100,000 mourning employees will not calm customers who question whether to stick with the x86 PC roadmap much less the Atom mobile processors. A more dramatic gesture is needed to shake the company to its core and jump-start its new Foundry Business. Moore’s Law slows down for no one and given the Chasm that lies ahead, Intel needs to be bold and offer its CEO position to nVidia’s Jen Hsun Huang – immediately! And to make it all happen will only be possible if Andy Grove decides to step in and make the call.
    Continue reading “Will Andy Grove Save Intel By Recruiting Jen Hsun Huang?”


    Second FPGA to the right, and straight on ‘til it works

    Second FPGA to the right, and straight on ‘til it works
    by Don Dingee on 11-26-2012 at 6:00 pm

    In a fantasy world where there were no coding errors or integration issues, FPGA designs would fly straight through synthesis easily and quickly. Maybe that world does exist somewhere. For the rest of us, who have experienced the agony of running a large FPGA design – again – only to find another error and have to start over, there has to be a better way.

    Continue reading “Second FPGA to the right, and straight on ‘til it works”


    Interview with David Eggleston on Rambus-Unity CMOx

    Interview with David Eggleston on Rambus-Unity CMOx
    by Ed McKernan on 11-26-2012 at 11:00 am

    by Christie Marrian of ReRAM-Forum.com

    Unity Semiconductor is a true veteran in the emerging memory/ReRAM field and was recently acquired by Rambus “one of the world’s premier technology licensing companies”. I must admit to being somewhat surprised by this acquisition when I first heard about it. Was this another example of ‘Strange Bedfellows’? Unity is a company with an ambitious product roadmap and always seemed to be a company that aggressively pursued hardware (i.e. chip) development in Fabs around the world. I was fortunate enough to catch up with Dave Eggleston former CEO of Unity recently and this was the first question I put to him. For more on Dave’s comments and insights as to what is behind Unity’s success check out ReRAM-Forum.com.