webinar IPXACT banner

Variation: How Can We Survive?

Variation: How Can We Survive?
by Paul McLellan on 12-24-2014 at 12:57 pm

At IEDM last week Coventor hosted a panel session as they do each year. The theme this year was surviving variation. The panel was hosted by someone whose name is familiar round here, Dan Nenni. The panel that Coventor had put together had people from all sorts of different slots in the design/supply chain for semiconductor. Unfortunately the participant companies would not release the slides so this is all from my scribbled notes on the evening.

First up was Rich Wise of Lam Research. He emphasized that variation is really about the limits to semiconductor yield. High variation and yield is poor and you can’t ramp a process to volume. Indeed, ramping a process to volume is largely about getting variation under control.

Next was Jan Hoentschel of GlobalFoundries. Of course keeping variation under control is absolutely key for a fab. Firstly, it is the key component for yielding a new process (or an existing one for that matter, fabs do occasionally “lose” the process). But foundries have another way of dealing with variation other than reducing it. They can put large variation parameters into their PDKs. But this transfers the problem elsewhere and if there is too much variation it simply becomes impossible to design for the process. Since foundries only make money when designs go into production this is economic suicide.


Next was David Fried, Coventor’s CTO. One of the ways to get variation under control is to run lots of wafers. But with a modern process that takes too long and costs too much. So the alternative is to model the process (would that be with Coventor’s SEMulator 3D by chance?) which allows you to add variation at the process step level and then measure the impact on yield, timing and so on without building wafers. In old processes the connection was fairly simple (gate length a little long, slower timing and so on). But a modern process has so many steps and complex multi-pattern lithography, that that is no longer the case and a good physical model feeding into good TCAD models is required.

Jeff Smith, from TEL (Tokyo Electron) America, sells semiconductor equipment (aka tools). He pointed out that it is no longer enough for them to sell equipment and let the customer worry about getting the yield up. They need to work out how to use their own equipment to reduce variation, by things like building sacrificial trenches to cut off some of the more extreme out-of-spec steps.

Tom Dillinger of Oracle said that he felt more like he was in the left-field bleachers trying to call the strike zone accurately while everyone else was up near the plate. He is at the mercy of variation. If the manufacturing processes can’t get it down then it shows up in his technology files and it makes it much harder to actually do a design. Closing timing/power/electrical etc just doesn’t converge if variation is too high. And modern processes, with double patterning in particular, are making things worse.

Last up was Tomasz Brozak of PDF solutions. They sell software for managing process yield, measuring (and thus improving) lithography. And so on. As I said above, improving yield is largely about reducing variation without letting costs get out of control.

The big message of the evening is that you cannot handle variation by worst-casing everything because they you find that having invested billions of dollars in a fab for a new process, and having moved the performance up nicely for the typical values in the center of the distribution, that now the spread (standard-deviation) is so large that worst case has hardly moved at all. Everyone, from equipment manufacturers to foundries to EDA suppliers need to replace worst case with accuracy. Everyone on the panel was making some contribution to that cause, narrowing the spread of the most important parameters so that design and high-yielding manufacturing is possible.


More articles by Paul McLellan…


Is Fab Business The Forte of APAC?

Is Fab Business The Forte of APAC?
by Pawan Fangaria on 12-23-2014 at 6:00 pm

A little ago, I was looking at the top20 semiconductor companies in the world and was surprised to see a couple of large companies in Taiwan and South Korea garnering >34% of total sales (See – Look who is Leading the World Semiconductor Business). This time it’s another surprise, when I look at IC Insights report on global 300mm fab capacity. Is this semiconductor business, considered to be a top high-tech and capital intensive area, becoming the forte of Asia Pacific, more specifically East Asia region? Look at this bar chart representing the share of worldwide 300mm wafer capacity based on fab location as well as fab’s headquarter location –

If we combine the share of Japan, South Korea, Taiwan and China, the combined share of fabs by location sums up to 74% and that by their headquarter location sums up to 72%; that’s massive. Europe’s share looks miniscule compared to others.

South Korea and Taiwan look interesting. Just two companies, Samsungand SK Hynix, in South Korea, not only have 28% share in their home land; they also have fabs outside Korea. In Taiwan, most of the fabs have their headquarters there only. Similarly Japan has 14% fabs with headquarters and 17% fabs located there.

In North America, a wide contrast is visible; while 28% of fabs are owned there, only 15% are located there. The reason is obvious – cost other than fab expertise available in other specific regions; Semiconductor fabrication in one business which cannot be done without requisite long-run expertise, North America gets that with added cost benefit by setting up fabs in other regions.

Again, if we look at the capacity utilization, Bill Jewell’s blog tells the story. The capacity is only rising, TSMCand UMC remaining between 80% to 90% and more utilization. What can explain their capacity utilization being higher than the world average? The foundry services, specifically by the foundries in Taiwan, for the rising world of fabless companies across the world. Today TSMC provides fabrication of chips to its design house customers at top-notch process nodes.

When economic, business and technical forces combine together for a particular domain, then that creates a critical work force, ecosystem and leadership around that domain in the particular region. Are we seeing East Asia at the leading edge of semiconductor fabrication and semiconductor business in general for the next 5-10 years?

More Articles by PawanFangaria…..


Kathryn Kranen at IEDM

Kathryn Kranen at IEDM
by Paul McLellan on 12-23-2014 at 7:00 am

It is the 50th year of IEDM, the International Electron Devices Meeting. The fact that it has been going for so long reveals why it has such an odd name: back in 1964 most “electron devices” were tubes (valves in UK lingo). This year they gave all of us a USB stick with all the papers from all 50 years of the event, something that would have been unbelievable to even think about during the first conference when a few bits of memory would cost a king’s ransom.

This year at lunch on Wednesday there was an IEDM/Women in Engineering co-sponsored lunch. The setup was Kathryn Kranen, most recently CEO of Jasper Design Automation, being interviewed by Thuy Dao of Freescale.

Thuy started by asking Kathryn about the early part of her career. She studied in Texas and then worked for Rockwell, firstly in board design and then in ASIC design. She was then recruited by Daisy Systems (in Texas) and eventually moved to headquarters in Sunnyvale (in what are now Synopsys’s buildings I presume). Initially she was an application engineer. She then moved to Quickturn and learned to be a bag-carrying salesperson with a product that didn’t really work and wasn’t selling well. Technical products simply do not sell themselves. Quickturn went public (and would eventually be acquired by Cadence, the Palladium product line is the descendent of those original products).

Kathryn went to Verisity, at the time an Israeli startup. She ran the US subsidiary and got it profitable. She left when she got pregnant and Moshe Gavrielov (now CEO of Xilinx) took over. Verisity went public so presumably Kathryn made some money and she was retired for 4 years bringing up her children.

In 2002 Jasper recruited her to be CEO. At the time there were 6 people. She closed 2 rounds of funding but after a couple of years the market froze. All 3 big EDA companies had their own formal products (from acquisitions) and so customers stopped being interested since they had a formal product that was “good enough” and bundled into big deals. The founders left Jasper and recruited many of their friends so they ended up with only one of the original software developers. Luckily they had a couple of loyal customers, Sony and Cisco, who kept buying. Then they started to grow again. They opened their Brazil development site that eventually became the largest. And it turned out that their technology really was the best and JasperGold started to become the market leader.

So Jasper needed to decide what to do. They were more profitable and had more revenue than prior EDA IPOs such as Verisity. But post Sarbanes-Oxley that is not enough any more. It would be another 3-5 years to get big enough to go public. So they decided to sell. They had just gone through a failed acquisition when they discovered bad stuff during due diligence. So they decided to spend a lot on cleaning up the books, putting all the documentation online and generally making it so that once an acquisition process started it would go fast. They had regular meetings with two companies, one of which was Cadence (and I don’t think you win any prizes for guessing the second). Cadence made a lowball offer that they turned down, then they grew 35% in one year and Cadence came back with something acceptable. They didn’t use an investment banker.

So, Thuy asked, what are the 3 lessons for a startup from founding to liquidity?

[LIST=1]

  • The real enemy is time. Don’t wait for everything to be perfect or the market will pass you by.
  • It is all about the customers. They need to be willing to pay for your products. Don’t give it for free to early customers. Jasper’s first customers paid more than later ones but they got the entire company including all of engineering working for them. If the customers pay a lot of money they will invest effort to make the product work, whereas if they get it for next to nothing they will walk away.
  • Don’t clling to things that are not working, find people you need and be picky about team members.

    One thing Jasper did is not spread itself thinly. At the time Cadence acquired them they only had 25-30 customers but each on was a $1M customer. A couple of customers paying $1M is much better than 20 customers paying $50K. How hard will they work on a cheap product that is not yet mature and working cleanly?

    Kathryn was asked about whether she was treated differently as a woman. She said that at the time she didn’t think so but now looking back she can see some weirdness. She has recently got involved in STEM mini-course at the middle school that her 8th grade daughter goes to. But it is necessary to have an explicit conversation about the biases and not pretend. For example, there is a recent Barbie book about designing a video-game. Barbie designs it but then when it comes to writing the code she needs to find some men. Not exactly the ideal message!

    Kathryn is currently temporarily retired. And she has no wish to return to EDA (because it is all tiny companies or huge ones) but she would like to work for a 100-150 person company, probably some sort of B2B software since that is what she knows. Expect to see her around soon!


    More articles by Paul McLellan…


  • Components for Wearables, Making the IoT Real

    Components for Wearables, Making the IoT Real
    by Paul McLellan on 12-22-2014 at 4:12 pm

    The screenwriter William Goldman is famous for saying that in Hollywood “Nobody knows anything.” Meaning that there is simply no way for any of the people involved to be able to predict which movies will turn out to be hits and which will be flops. I think the internet of things (IoT) is going to be like that. There will be products that turn out to be big successes and other products that smarter people than me decide to green-light that go nowhere. That is one of the reasons that I don’t think that IoT is a big market for SoC designs, more for microcontrollers and software, at least until it is clear which of the mud thrown against the wall has stuck firmly and so the ROI on doing an SoC is clear.

    One aspect of IoT that will be important is programmability. Obviously at the software level but the capability to repurpose the hardware will also be important. One area that is a special challenge is that at least part of the system needs to be “always on” despite the requirements for low power. A device like a fitbit cannot count your steps if it is not awake to count them. But having the primary microprocessor on all the time will blow the power budget. So there needs to be a divide and conquer approach, with an always on extremely low power device that only occasionally wakes up the main processor to handle the data and, perhaps, upload it into the cloud. For example, a step counter may be awake 25 times per second but only give data to the microprocessor to handle step counts every second or two and only power up the network connection even less frequently.


    Last week Quicklogic announced the TAG-N wearable sensor hub evaluation kit, in collaboration with Nordic Semiconductor. This incorporates the ArcticLink 3 S2 sensor hub, Quicklogic-developed algorithms and a direct connection to a Nordic Semiconductor nRF51 Dk, their all-in-one multiprotocol development kit for ultra-low power wireless development. This enables system designers to test and develop Bluetooth Smart (what used to be called Bluetooth Low Energy) wearable devices. The sensor hub consumes only 150uW of power while processing pedometer, gesture and context. This is a reference design for wearables suitable for fast prototyping as well as a demonstration of the effectiveness of the algorithms.

    Quicklogic will be attending CES in Las Vegas January 6-9th. Their hospitality suite is MP25452, South Hall 2 in the convention center. Meetings are by appointment only. Go here to reserve a time.

    They are also participating in a panel – Getting to Low Power and Maximum Functionality through Sensor Fusion Presented by MEMS Industry Group, Room: Marco Polo 702 (Venetian, Level 1) on Tuesday, Jan. 6, 3:30 – 4:30 p.m. Dr. Tim Saxe, QuickLogic’s CTO, will join panelists from InvenSense, Bosch Sensortec, PNI Sensor and STMicroelectronics to discuss how consumer OEMs and embedded systems integrators can take full advantage of MEMS and sensors for wearable devices.

    But wait, there’s more. And not steak knives. They will also be at the MEMS Alliance Technology Showcase, booth 72032, Tech West, Sands Expo, Level 2.


    More articles by Paul McLellan…


    Last VIP News of 2014

    Last VIP News of 2014
    by Eric Esteve on 12-22-2014 at 11:00 am

    It’s likely that most of the current Semiwiki readers didn’t read this article posted in 2011, comparing Cadence and Synopsys with the Soviet Union and the USA, sharing the world in 1944 during the Yalta Conference. I was explaining in my post that Synopsys’s strong influence was on Design IP when Cadence’s preferred domain was on Verification IP. A kind of “Yalta effect” applied to the electronic design area (not to world regions!). If you missed this article, don’t worry as the content is no more relevant! Synopsys is still dominant in the IP business when excluding the large processor IP core segment (with $342 million revenues in 2013), but the company is also massively investing the VIP business, as we can see on the table below. To be fair, I must say that Cadence is also playing in Synopsys’s garden, investing in the Design IP business. But let’s take a look at the latest VIP news:

    At first we can notice that Synopsys has developed this VIP port-folio around protocol based, Bus functions, like AMBA, OCP, I2C or I2S, and interfaces, starting with Ethernet, Fibre Channel or Interlaken supporting networking, then almost all the popular interfaces like seven MIPI specifications, PCI Express (including NVM Express and M-PCIe), SATA and USB. If you think that it’s easier to develop test suites to support protocol based function, you should take a look at the PCIe Gen4 specification document, a 1,000 pages book! This VIP port-folio probably represents several 100’s of man-year effort. Synopsys is claiming that these VIP have not only been used to verify Synopsys DesignWare Design IP, but also Synopsys’s customers and 3[SUP]rd[/SUP] party IP. These VIP can be exercised to verify customer design at SoC level, when the IP is embedded into an IC.
    The memory VIP list is impressive as well as it cover from LPDDR2 to LPDDR4, UFS (a MIPI joined specification with JEDEC), eMMC, DDR3 and DDR4 both with DFI (the memory controller interface with the PHY) and DDR4-3DS.

    When dealing with VIP, the question about which language being used to develop it quickly surface. These VIP are native 100% SystemVerilog, offering native debug with Verdi and a fast turnaround time for simulations using any popular simulator. Because the test suites are delivered in source code, the design team can accelerate compliance verification and, even more important, be able to use the same source for all SoC, subsystem and IP verification needs.

    Now you should mobilize 100% of your remaining energy available in 2014 and take a look at the above picture. The slide is quite complex, but includes all pieces of information about Synopsys VIP strategy. I recommend starting from the bottom right to identify the USB device IP Device Under Test (DUT). The large grey box (still on the right side) represents the Device environment, and the USB device IP is accessible through a VIP AXI Agent. If you move to the left side of the picture, you will notice the VIP Agent, a VIP USB Host. Just remember that a VIP is to an IP that a glove is to a hand: is you verify a USB Device IP, you will use a USB Host VIP. From this point of view, VIP is just like Design IP. The difference between VIP and IP comes with Test Suites (included into the purple box #2), these set of vectors will be used to verify against the protocol.

    Then you have now the right to read the content of the five purple boxes, labeled from 1 to 5. The first box define the “Verification Plans”, the second the “Test Environments”, the third the “Checks” and so on…

    I have checked a very interesting point about Synopsys VIP business strategy: I was under the impression that Synopsys’s VIP products were included into the DesignWare IP product, thus Synopsys customer would have benefited from “free” VIP. In fact this is completely wrong, as customer have to acquire Synopsys VIP product (different from the DesignWare IP product), thus Synopsys is really valuing VIP as it should be and create a real business around VIP. As far as I am concerned, I am always suspicious about “product for free”. Yes, you don’t pay for it. But you probably can’t expect a high quality level of support for something you don’t pay for… This is not the case with Synopsys VIP: the company heavily invests to develop the various VIP products; you pay for a quality bunch of product and support, allowing the company to develop new products.

    From Eric Esteve from IPNEST


    Results of TSMC’s ECO Fill Flow

    Results of TSMC’s ECO Fill Flow
    by Beth Martin on 12-22-2014 at 7:00 am

    By Jeff Wilson, Mentor Graphics and Anderson Chiu, TSMC

    At this year’s TSMC Open Innovation Platform® (OIP) Ecosystem Forum, Mentor Graphics and TSMC co-presented some results of the ECO Fill flow developed for TSMC customers working at advanced nodes. Here is a summary of the presentation. (TSMC customers can access the presentation at TSMC-Online).

    Metal fill (inactive metal shapes) was originally added to open design areas in layouts because a certain metal density was required to pass the foundry’s density design rule checks (DRC). These foundry density requirements helped reduce wafer thickness variations created during chemical-mechanical polishing (CMP) processes. To avoid creating parasitic capacitance issues, the goal was to add only as much fill as needed to satisfy the minimum and maximum density requirements set by the foundry.

    At 45nm and below, metal fill affects multiple manufacturability issues such as stress, etch response, and rapid thermal annealing, and has an impact on design performance. Foundry fill targets have switched from ensuring a basic minimum density to achieving a maximum density. In addition, density checks for density gradient now require a smooth transition between fill densities in adjacent locations. At 20nm and below, fill requirements must also comply with multi-patterning (MP) restrictions to ensure mask balancing, and designers must begin adding multi-layer fill not just to back-end-of-line (BEOL) metal and via layers, but also to front-end-of-line (FEOL) layers. All of these changing manufacturing requirements impact the complexity of metal fill placement, as well as the number of fill elements in a design.

    These changes in fill require sophisticated new fill types and filling strategies. New techniques such as cell-based and multi-patterning-aware fill were integrated into fill engines to provide an automated fill process that can be called from place and route (P&R) tools to ensure an easy-to-use design flow that produces correct-by-construction results. However, the number of fill shapes in advanced node technologies can exceed a billion objects. So an engineering change order (ECO) that arrives late in the tapeout process and requires fill changes in the surrounding area can be a significant engineering challenge. The complexity of replacing fill and reconfirming timing may negatively affect runtime and timing closure, which can lead to a delayed tapeout delivery.

    To handle these last-minute design changes, TSMC developed an ECO fill reference flow designed to work in concert with their overall design ECO flow. The TSMC ECO fill flow addresses the same range of fill situations that their full fill flow encounters, but concentrates only on the portion of the design affected by the ECO. This flow can account for the timing impact of fill without slowing down the back-end flow.

    The TSMC ECO fill reference flow incorporates Calibre® YieldEnhancer’s SmartFill functionality and Calibre DESIGNrev™ to keep fill shapes in a separate file on disk, similar to the approach that the leading parasitic extraction tools use to
    minimize the size of the design database. This proven “merge when needed” approach provides the proper balance between accuracy and performance. The TSMC ECO fill reference flow (shown in the figure to the right) is currently supported for 16nm and 20nm processes. Users can download all the necessary files from TSMC.

    By removing and replacing only the fill in the surrounding area, and re-verifying timing only in the affected area, designers can reduce runtime, manage file size, and minimize timing impacts (see the following figure). By restricting the ECO fill operation to only the same locations where actual mask-making changes occur, the TSMC ECO fill reference flow limits the size of the region that must be evaluated for errors, edited, and refilled. This area reduction is accomplished by generating exclude regions, and clipping the fillable database to include only the area around the design ECO.

    To reduce the size of the fill database, TSMC uses a cell-based approach to fill the design. If the ECO fill flow does not properly handle fill cells, designers will see an explosion in the fill database. So, to minimize this, Calibre SmartFill only flattens the minimum number of cell instances required to remove existing fill that conflicts with the ECO design shapes. It also removes shapes based only on metal-stack-aware DRC spacings. It then refills only in the areas where ECO changes occurred, rather than refilling the entire chip.

    There is a breakeven point in this reference flow—if the area to be refilled is too large, then the efficiencies of scale may be lost. In general, ECO fill strategies are most efficient when the change affects less than 1% of the design area. For bigger changes, the runtime of the ECO fill flow may exceed that of a regular fill run. Generally, good candidates for ECO fill include small areas of change, such as changes in gate functionality that requires a localized rerouting in a limited area. When changes to an entire block indicate that it would be more efficient to simply refill the design from scratch, a hierarchical fill approach may be more appropriate. However, designers must always consider whether minimizing timing impacts and mask costs offset any runtime disadvantage.

    This table demonstrates a number of advantages to having a specialized ECO Fill flow that uses the exact same fill deck that was used to fill the design originally.


    The results from several real world test cases show that fill runtime was reduced by 34% to 89% by using the ECO fill flow rather than a full refill. In four of the five cases, the number of masks that required changes was reduced, and in one case the ECO fill approach resulted in six fewer masks requiring re-manufacturing. The TSMC ECO Fill reference flow implemented with the SmartFill functionality in Calibre YieldEnhancer provides a push-button solution that can handle any last minute design changes.


    Ensuring Safety Distinctive Design & Verification

    Ensuring Safety Distinctive Design & Verification
    by Pawan Fangaria on 12-21-2014 at 12:00 pm

    In today’s world where every device functions intelligently, it automatically becomes active on any kind of stimulus. The problem with such intelligence is that it can function unfavorably on any kind of bad stimulus. As the devices are complex enough in the form of SoCs (which at advanced process nodes are more susceptible to external exposure such as radiation, static charge etc.) encompassing rich set of multiple functions, it’s essential to condition those to function favourably even in the event of any unexpected stimulus. While the functional safety of these devices are critical in automotive, aerospace, and healthcare applications, other applications such as industrial, home, consumer etc. are not isolated considering financial loss. So, how to make the SoCs immune to unexpected, unplanned or unintended (may be by human itself) stimuli and condition them to work safely in any environment at the chip or system level?

    At the design level, SoCs need to be made fault-tolerant by introducing alternative paths to process at the expense of added redundancy and at the same time special checkers need to be introduced to monitor the system and trigger error response and recovery when needed.

    To verify the system and ensure tool confidence level (TCL), the verification must include safety verification along with functional verification at all levels of abstractions from system to components. The functional tests must be replayed after injecting faults into the system to ensure correct working of alternative paths on correct data and of checkers on erroneous data monitoring and recovery.

    Cadencehas beautifully extended its Incisive functional verification platform for functional safety verification. The platform has demonstrated well in complying with automotive safety standards and has been used in production by several automotive IC suppliers.

    The Incisive verification platform seamlessly augments functional verification plan with Safety Verification Plan that meets complete functional safety assessment, requirements and TCL. The metric-driven verification (read Effective Verification Coverage through UVM & MDV to know more about metric-driven verification) is used to effectively monitor sets of metadata through complete verification flow including functional and safety requirements. The functional safety assessment is done by simulating system behavior (that includes IP, SoC and complete system) through Incisive Functional Safety Simulator (that includes permanent as well as transient fault simulation) under various error conditions. The fault models include manufacturing-time stuck-at-0 and stuck-at-1 faults, as well as single event upset faults and transient faults that can occur while the ICs are functioning in the system.

    Cadence’s functional safety solution is very efficient in providing complete tracing of requirements, safety verification and TCL that conforms to automotive ISO 26262 standard. The automated solution from requirements to verification and TCL reduces ISO 26262 certification effort by ~50%.

    The Incisive Functional Safety Simulator accelerates safety verification by seamlessly reusing functional and mixed-signal verification environment that provides 10X runtime performance compared to traditional Verifault-XL engine used in functional safety simulation. The existing SystemVerilog, UVM or e functional verification environments can be reused as usual. The faults are injected during simulation of DUT and can propagate through SystemC, analog transistor or behavioral models, and assertions.

    The Incisive vManager automatically generates a safety verification regression from the fault dictionary created by the simulator. It can then track millions of detected, potentially detected, and undetected faults introduced into simulation to verify the safety in a design.

    Both the Incisive Functional Safety Simulator and vManager are part of Cadence System Development Suite. They address dependability and reliability of the system which has become a critical criterion (together with PPA) today in the face of nanometer process nodes.

    Cadence continues to expand its functional safety solution portfolio by including more hardware, software and IP components in different application areas. A more detailed view on the automotive functional safety solution is available in a whitepaperat Cadence website, written by Philippe Roche of STMicroelectronicsand Adam Sherer of Cadence.

    More Articles by PawanFangaria…..


    New book untangles the Internet of Things (IoT)!

    New book untangles the Internet of Things (IoT)!
    by Daniel Nenni on 12-21-2014 at 9:00 am

    In 10 years, there will be 50 billion devices connected to the web, said Ericsson CEO Hans Vestberg. Next, Cisco chief John Chambers called IoT a US$ 19 trillion business opportunity in his keynote at the 2014 CES.

    What is this Internet of Things after all? And how is it evolving seamlessly into multiple dimensions? How does it relate to the connected wearable devices like smartwatch? What’s its relationship with the mobile Internet and its prime vehicle: the smartphone? Where do weather balloons, drones, fiber and satellites fit into this twenty-first-century network juggernaut?

    Here comes a new book that provides answers to all these questions and makes the sense of it all. The Next Web of 50 Billion Devices looks into the future—the Internet of Things—by first analyzing the past: mobile Internet. In between these two technology parables, the book delves into the present—native apps vs. web tug of war—and provides a detailed treatment of HTML5 and mobile browser technologies and their business prospects.

    The Next Web of 50 Billion Devices also chronicles prominent efforts to develop infrastructure for this twenty-first-century network—from GPRS to LTE-based 4G—and presents mobile commerce as a case study to demonstrate how this modernistic network establishment is evolving. It also takes a peek into the Internet of Things bandwagon and shows how it’s converging and colliding with another giant shift in mobile computing: connected wearbles. Then it brings forth new dimensions in the mobile Internet realm: The Internet of photos, location, augmented reality and so on.

    While providing the Internet context of the next-generation technologies, the book takes a close look at what tech giants like Amazon, Apple, Facebook and Google are doing to claim their stake in the next Internet gold rush. At the same time, The Next Web of 50 Billion Devicesalso profiles mobile web pioneers such as Mozilla, Nest and Opera.

    In the final analysis, the book shows readers how the two spectacularly unpredictable technologies—computing and telecom—came together to accomplish the ultimate computing milestone: an Internet that is simple, reliable and pervasive. There is a dearth of good books on smartphone and mobile Internet and how they relate to the emerging new worlds such as IoT and connected wearables. There are only a couple of books available on this subject, and they mostly deal with marketing-centric issues.

    The book is written in semi-technical business language to make it easy for managers and tech professionals from diverse backgrounds to absorb content on a crucial industry. The easy-to-read account charts areas of opportunities and challenges facing IoT and wearable markets. And that makes it a valuable read for IT managers tasked with formulating mobile and IoT strategy for their businesses. The Next Web of 50 Billion Devices also differs from other business books in its content presentation of technology where advancements are tied to the history and evolution perspective.

    The Next Web of 50 Billion Devicesis available in both paperbackand e-book on Amazon.


    Is Your FPGA Design Secure? Use Xilinx to Make Sure

    Is Your FPGA Design Secure? Use Xilinx to Make Sure
    by Luke Miller on 12-20-2014 at 7:00 pm

    I hope your Christmas break is starting off well! You know this, but evil takes no break for Christmas. We are seeing more and more the hacking of systems and it seems to have become the norm. Do you get nervous anymore when you hear that your credit card company lost their data? Or I mean your data?

    It’s as if we have given up on the ideas of privacy and security or that they are something that cannot be obtained. North Korea is not as stupid as we thought, eh? Will we actually see market crashes? Power grid failures? Will the ‘news’ be hacked? To say the least these are interesting times and probably will not get better anytime soon.

    More important than ever, depending on your application for your Xilinx FPGA, security and Anti-Tamper (AT) may be more important as ever! Think of applications like High Frequency Trading (HFT), RADAR, Medical, Power Control, and Data Centers which Xilinx will start gobbling up due to their innovative OpenCL solution called SDAccel.

    To start, security and the likes are not seasonings that get sprinkled on at the end of your design. Security is a methodology that must be in lock step with the Xilinx FPGA design and the systems in and around the FPGA. To mess up here is to have a very unsecure, but often a very expensive design. Now is the time to get familiar with what Xilinx has to offer as the leader in FPGA security. To begin, May I recommend reading the Xilinx web page on ‘Design Security Solutions’. Here is just the beginning into the world of Secure Xilinx designs. I will call your attention to three key documents:

    · XAPP1084 – Developing Tamper Resistant Designs with Xilinx Virtex-6 and 7 Series FPGAs
    · WP365 – Solving Today’s Design Security Concerns Using Spartan-3 Generation FPGAs
    · WP412 – The Xilinx Isolation Design Flow for Fault-Tolerant Systems

    There is a lot of meat here, read carefully and slowly. The three areas to keep in mind are prevention, detection and response. For example, we can encrypt the bit stream to prevent a first order attack from being successful. Detection can be very elaborate or very simple by monitoring voltages and temperature. When a attack is detected what do you want to happen? Erase the bit stream? Load a new image to start recording the attack? Some of you may be asking is all this really necessary? Until my eyes were opened, I would of asked the same question years ago. Given the Internet of Things, the ‘Cloud’ and everything flowing over wireless data pipes I would say yes, 100% you need a secure FPGA design. XAPP1084 sums it up best:

    The decision as to how much AT to include primarily depends on three factors:
    • Value: The perceived value of the intellectual property and the damage it might cause either financially and/or to national security if it were to become compromised. Certain AT features can be expensive to implement and that cost must be weighed against the value of the technology being protected.

    • Adversary: Access to the system and the sophistication level/resources available to carry out the attack. For example, will access to the system be prevented by “guns, gates, and guards” or will it be easily obtained in the open market? Is the adversary a garage-based hacker or a nation-state? The adversary’s capabilities could be at these extremes or anywhere in-between.

    • Design Stage: At what point in the system development cycle is the decision made to enable AT for the FPGA design? Xilinx highly recommends that the decision to utilize FPGA AT features is made very early on (i.e., after CT is defined in a system) to help address both schedule and cost concerns. It is always more costly and time consuming to insert AT features later on.

    You can Trust and Count on Xilinx not only for the World’s Finest FPGAs and Tools, but also for your next Secure FPGA design.


    Verilog-AMS connects T-SPICE and Riviera-PRO

    Verilog-AMS connects T-SPICE and Riviera-PRO
    by Don Dingee on 12-20-2014 at 7:00 am

    With advances in available IP, mixed signal design has become much easier. Mixed signal verification on the other hand is becoming more complicated. More complexity means more simulation, and in the analog domain, SPICE-based techniques grinding away on transistor models take a lot of precious time. Event-driven methods like Verilog in the digital domain are very fast, but do little with the analog IP. Continue reading “Verilog-AMS connects T-SPICE and Riviera-PRO”