Stats

  • Locked Locked
  • Replies 3
  • Subscribers 48
  • Views 14041
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Xtreme run modes?

archive

In Xtreme, what are the differences between the run, tbrun and autorun modes?

Thanks for the help!

davea


Originally posted in cdnusers.org by davea
Parents

  • Xtreme supports running the design in three modes:

    run mode:
      Run mode is generally used for acceleration testcases, where DUT runs in RCC engine
    and Testbench runs in xsim simulator.The simulation performances in this case is generally determined by software components running in xsim simulator.

    autorun mode:
      autorun mode is mostly used for in-circuit emulation and targetless emulation  modes.In autorun all the modules must be compiled for RCC engine and also all the clocks must be generated from axis_clkgen module.autorun ignores all CLI commands after HW swap, and any control must be done manually by pressing CTRL-C  and typing commands on CLI or through axis tbcall mechanism.

    tbrun:
      tbrun is very similar to autorun(has all the requirements of driving clocks from axis_clkgen and no module can run in XSIM SW) except it enables behavioural
    delay control.This mode is mainly used for TBA(Transaction based acceleration using xtremeTBA libraries) applications.
     i.e C1>##600 $stop; will be honoured.(ignored in autorun mode).

    Please refer to Xtreme documentation for more details.
    Thanks,
    DGill





    Originally posted in cdnusers.org by DGill
Reply

  • Xtreme supports running the design in three modes:

    run mode:
      Run mode is generally used for acceleration testcases, where DUT runs in RCC engine
    and Testbench runs in xsim simulator.The simulation performances in this case is generally determined by software components running in xsim simulator.

    autorun mode:
      autorun mode is mostly used for in-circuit emulation and targetless emulation  modes.In autorun all the modules must be compiled for RCC engine and also all the clocks must be generated from axis_clkgen module.autorun ignores all CLI commands after HW swap, and any control must be done manually by pressing CTRL-C  and typing commands on CLI or through axis tbcall mechanism.

    tbrun:
      tbrun is very similar to autorun(has all the requirements of driving clocks from axis_clkgen and no module can run in XSIM SW) except it enables behavioural
    delay control.This mode is mainly used for TBA(Transaction based acceleration using xtremeTBA libraries) applications.
     i.e C1>##600 $stop; will be honoured.(ignored in autorun mode).

    Please refer to Xtreme documentation for more details.
    Thanks,
    DGill





    Originally posted in cdnusers.org by DGill
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.