1 / 10

Ace_Env - Test Flow Package presenter name, Ace Verification

Ace_Env - Test Flow Package presenter name, Ace Verification. Abstract. Background Specman comes with a plethora of method hooks these include: Pre-generate, generate, start, init, run, finalize, check, quit etc. Specman does not include hooks or infrastructure for during the run

presta
Télécharger la présentation

Ace_Env - Test Flow Package presenter name, Ace Verification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ace_Env - Test Flow Packagepresenter name, Ace Verification

  2. Abstract • Background • Specman comes with a plethora of method hooks these include: • Pre-generate, generate, start, init, run, finalize, check, quit etc. • Specman does not include hooks or infrastructure for during the run • Ace_env • A series of built-in method and tcm-hooks which enhance the existing environment • Init_signals, Reset, Init_Dut, Scenario, Idle, Post_test_check etc. • Recursive for all Ace_env’s instantiated under it

  3. Ace_Env Testflow Intuitive Flow m_show_test_modes() t_init_signals() t_reset_dut() t_init_dut() t_start_flow() t_scenario() m_wait_until_idle() t_post_test_checks() t_finalize() t_stop_run() Recursive Designed Easy Hooks Clear Standard Skeleton Template Elegant

  4. Main Features of the Package • Standard way to sequence test flows • Standard way incorporate sub-environments into a single environment • Simulating Common flow behavior • Allows hooks for all standard testing • Allows tests and environments to be standard • Standardized eRM compliant modeling

  5. Advantages • Easier integration • Code:t_init_signal(), t_reset_dut(), and t_init_dut() and you can already see a live design • Standard way to work • All env’s have the same 10 methods • Built-in hooks based on multiple project experience

  6. Using AceEnv Functions • All functions are easy to use • Used in all the environment • Used by tests as test hook (All tests have the same look) Test.e example: extend My_top_env { t_init_dut() @clk is also { write_reg(start_rt, 0x1234); }; t_scenario() @clk is also { sync @rt_done; read_reg(rt_status); }; };

  7. Ace Env Example Sys TXH3000 CPU Sub-System Mac PhyA PhyB Memory Packet Driver PTX PRX PBF Network Regular Units Any Envs Ace Envs

  8. Ace Env Example Cont. • The top Ace Env runs the test flow • Package automatically knows who’s the top • Package automatically knows who its sons are • For each method the test flow executes the method and then executes the methods in each of its sons • Package allows disabling of select children’s functions by constraints

  9. Availability Package is available for download at http://www.aceverification.com/reference.htm Under Component Sharing

  10. Summary • A healthy test flow provides easier overall planning • Structure for the environment • Standard environments • Block -> Cluster -> Full-Chip reuse • Standard test interface • Write your own, or use the Ace-Env shareware

More Related