热爱是保持年轻的秘诀 --- 梅耶.马斯克(马斯克母亲)

一个成功的投资者,85%归功于正确的资产配置,10%来自于选择投资目标的功力,5%必须靠上帝的保佑。--威廉·夏普
上路看世界,归家读闲书,陋室观天下,余暇思古今,静坐听音乐,提笔写文章。-- 南半球
有钱不花是穷人。-- 蔡澜
个人资料
正文

Why Do We Need ASIC/SoC Validation

(2019-05-22 15:43:32) 下一个

We do functional verification and timing verification(STA) before we tape out, why then do we still need to do validation after silicon come back?  It should just work, correct?

Well, the reasons are:

1.  The functional verificaion is incomplete (e.g, the Debug/IDE is typically not verified; Not all scenarios were cosidered during verification)

2.  The STA is incomplete (e.g. SDC file did not constrain certain ports like JTAG, or have set incorrect false paths)

3.  (rare) The fab model(CMOS) and/or std/memory models are inaccurate!

So, we need validation to catch the "unexpected" things.

Categories:

1. Sub-system level: check if a lower-level sub-system/module/IP functions correctly

2. System-level: check if top-level behavior is correct or not, often done on the chip hardware with firmware/OS/application together

3.  Electrical: e.g. signal integrity, serial interface speed

4.  Analog: e.g. PLL, LDO, ADC/DAC

5.  PVT:  extreme timing corners

Required Skills

1. Soc/ASIC Architecture

2. Processors

3. Protocols (USB, AMBA, etc)

4. Analog

5. Programming (Shell scripts, Python/Perl)

6. Lab Equipment Knowledge

7. System-level Skills (PCB schematics, typical use-cases)

8.  Debugging Skills

Interesting Stats:

Engineering resources spent on a product: Design/Verification/Implementation/Validation=25/35/20/20

[ 打印 ]
阅读 ()评论 (0)
评论
目前还没有任何评论
登录后才可评论.