RussSchultz
> -[TSMC 0.13] Yield is now very good (better than [TSMC .18u])
This statement needs some context. Nevertheless, I assume this statement compares TSMC's 'general' logic process (not low-power, not low-voltage.) Yield rates are difficult to calculate. Someone showed me a bunch of tables and formulas TSMC gives to its customers. Using the tables, you can 'estimate' your design's expected-yield rate, based on what process-features (RAMs, logic, # metal-layers, etc.) the design uses. (RAMs are still yield killers on just about any process.)
Pete
> Can another fab have that much trouble producing a proven chip on the same process
well that's the thing. TSMC and UMC are physically different production lines, with different process characteristics. Even moving a design from 1 line to a different production line (both running the same foundry recipe) within the same building can cause yield changes! (In a well-maintained foundry, differences should be *minimal.*) The fact that a design has been 'proven' at TSMC (or UMC), has no bearing on another company's foundry process. They use different materials, formulas, equipment, etc. I suppose if they were physically identical in every way, then the transfer would have no risk.
There is one thing working to ATI's advantage. TSMC and UMC have very similar overall 'design-flows.' (from Verilog source-code all the way to 'tapeout') ATI must re-run the back-end (synthesis, gate placement, interconnect routing, parasitic timing extraction, etc.) each time they target a different foundry-process. In ATI's case, TSMC and UMC are supported by the same CAD tool vendors (Cadence, Synopsys, but I'm guessing ATI use specialized tools from others, too.)
So if TSMC and UMC cell libraries are similar enough spped/performance-wise, ATI might not even have to make any design-changes, just 'recompile' the chip for the new process.
...
Why is a similar 'design-flow' so helpful?
Let's pretend ATI were to re-target a UMC design for IBM. As far as I know, a lot of steps in IBM's back-end design-flow require proprietary IBM software, or customer-handoff to IBM's internal engineering teams. Basically, ATI's engineers can't use their own (familiar) design-environment, they have to either handoff some work to IBM's crew (and cross their fingers!), or import/learn/debug a new IBM software package. Imagine writing a library-DLL in C, and then having to rewrite it in Pascal because your customer asked you to
(Thanks to IBM's new focus on their foundry-business, IBM is exposing more of their design-flow to third-party CAD tools, but it remains to be seen if this 'shift' from internal to third-party really works. My guess is that most potential customers will wait for IBM to demonstrate succsesful tapeout on a chip-designed with COT (customer-owned tooling), before signing-off on a multimillion dollar prototyping run.)