- set breakpoint when the assertion was happened
- like GDB methodology
- forward, backward, force signal, release signal
- tip
- forcing the error signal value to your expect signal value when the simulation assertion was happened. if the signal was forced, then continuous go through it without rerun again. that can save the interrater running times
- dump the error time window waveform without whole simulation time dump
- tip
- using the interactive method to dump waveform.
- 1. find the error happened time
- 2. set breakpoint
- 3. jumping the previous time window via backward breakpoint
- 4. open interactive dump waveform command
- 5. start dumping until the next breakpoint was happened
- using assertion
- using verification IPs
- sub IP test (selftest)
- functional test, coverage test, Direct/Random pattern test
- sub system test (sub system test)
- protocol test, transaction path test, performance test
- whole system test (H/S test)
- OS boot, H/S correlation test
2013年9月27日 星期五
fast debug key notes
these are my tips for fast debug.
訂閱:
張貼留言 (Atom)
沒有留言:
張貼留言