How to invoke the Xcelium Design Browser from Command Line?

There's no tool called "Xcelium Design Browser" - but there is a design browser in SimVision, it should be there on the left side of the waveform window or open a new design browser via the SimVision "Windows" menu item. 

Hello, if I have succefully finished the 'elabobration' process, and if I haven't run the simulation yet, isn't there any way I can just 'browse' the design? I tried xmbrowse but it expects to receive a log file. I'm running simulation for a testbench, and after fixing some design, and after doing the elab for the top testbench module, the simulator complaints I have put a scope in the $recordvars command which doesn't exist. But it looks like the scope exsists in the hierarchy from the top testbench so I wanted to browse the design. So how can I do it me not being able to run the simulation?

Assuming that you used the xrun command to build your simulation snapshot, then this should allow you to explore the design hierarchy without running a simulation:
xrun -R -ppe -gui

The -R option means "run the last compiled design", and -ppe means post-process environment, i.e. load the design information for debugging only.

Hi Stephen, Yes I could see the elaborated design (just the module of my interest) and could see the lower modules are not there.  Now I want to see if the lower modules are in the work library.  is there a way to brows what modules have been compiled into the work library? (I'm sorry to ask without reading the manual, I was doing hardware but for more than 10 years I'm doing software now so didn't have the time to read the Cadence manuals..)  Thank you. Chan Kim

Hi Stephen, Yes I could see the elaborated design (just the module of my interest) and could see the lower modules are not there.  Now I want to see if the lower modules are in the work library.  is there a way to brows what modules have been compiled into the work library? (I'm sorry to ask without reading the manual, I was doing hardware but for more than 10 years I'm doing software now so didn't have the time to read the Cadence manuals..)  Thank you. Chan Kim

If the lower modules are not there, then your design isn't instantiating them, i.e. you need to modify the RTL code to create the instances.
The simulator would not be able to elaborate the design and give you a simulation snapshot to load in the GUI, without all the necessary modules having been compiled.

Note also that unless you have a -top argument to xrun, any compiled but not instantiated modules automatically become top-level instances parallel to the testbench top, so that should give you another visual clue in the GUI.

Failing that, at the Linux command line you can run a command to list the contents of the compiled libraries:

xrun -R -xmls_all -xmls_so

the resulting output lists all the compiled objects and the source files that the objects were defined in.