05.08.2014 Views

ug900-vivado-logic-simulation

ug900-vivado-logic-simulation

ug900-vivado-logic-simulation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2: Understanding Simulation Components in Vivado<br />

Table 2-9 shows the string options you can use with SIM_COLLISION_CHECK to control<br />

<strong>simulation</strong> behavior in the event of a collision.<br />

Table 2-9:<br />

String<br />

SIM_COLLISION_CHECK Strings<br />

Write Collision<br />

Messages<br />

ALL Yes Yes<br />

Write Xs on the Output<br />

WARNING_ONLY Yes No. Applies only at the time of collision.<br />

Subsequent reads of the same address space could<br />

produce Xs on the output.<br />

GENERATE_X_ONLY No Yes<br />

None No No. Applies only at the time of collision.<br />

Subsequent reads of the same address space could<br />

produce Xs on the output.<br />

Apply the SIM_COLLISION_CHECK at an instance level so you can change the setting for<br />

each block RAM instance.<br />

Dumping the Switching Activity Interchange<br />

Format File for Power Analysis<br />

The Switching Activity Interchange Format (SAIF) is an ASCII report that assists in extracting<br />

and storing switching activity information generated by simulator tools.<br />

This switching activity can be back-annotated into the Xilinx power analysis and<br />

optimization tools for the power measurements and estimations.<br />

See the information about the respective simulator for more detail:<br />

• Vivado simulator: Power Analysis Using Vivado Simulator, page 126<br />

• Dumping SAIF in QuestaSim/ModelSim, page 140<br />

• Dumping SAIF for Power Analysis in IES, page 148<br />

• Dumping SAIF for Power Analysis for VCS, page 155<br />

Logic Simulation www.xilinx.com<br />

Send Feedback<br />

40<br />

UG900 (v2014.1) April 23, 2014

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!