OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [or1ksim/] [doc/] [or1ksim.texi] - Diff between revs 442 and 443

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 442 Rev 443
Line 640... Line 640...
 
 
@node Trace Generation
@node Trace Generation
@section Trace Generation
@section Trace Generation
@cindex trace generation of @value{OR1KSIM}
@cindex trace generation of @value{OR1KSIM}
 
 
An execution trace can be generated at run time with options passed by the command line, or via the operating system's signal passing mechanism.
An execution trace can be generated at run time with options passed by
 
the command line, or via the operating system's signal passing
 
mechanism.
 
 
The following, passed at run time, can be used to create an execution dump.
The following, passed at run time, can be used to create an execution dump.
 
 
@table @code
@table @code
 
 
Line 654... Line 656...
@cindex @code{--trace}
@cindex @code{--trace}
Dump instruction just executed and any register/memory location chaged
Dump instruction just executed and any register/memory location chaged
after each instruction (one line per instruction).
after each instruction (one line per instruction).
@end table
@end table
 
 
Passing a signal @code{SIGUSR1} while the simulator is running toggles trace generation. This can be done with the following command, assuming @value{OR1KSIM}'s executable name is @code{or32-elf-sim}:
Passing a signal @code{SIGUSR1} while the simulator is running toggles
 
trace generation. This can be done with the following command, assuming
 
@value{OR1KSIM}'s executable name is @code{or32-elf-sim}:
 
 
@example
@example
pkill -SIGUSR1 or32-elf-sim
pkill -SIGUSR1 or32-elf-sim
@end example
@end example
 
 
This is useful in the case where trace output is desired after a significant amount of simulation time, where it would be inconvenient to generate trace up to that point.
This is useful in the case where trace output is desired after a
 
significant amount of simulation time, where it would be inconvenient to
If the @code{pkill} utility is not available, the @code{kill} utility can be used if @value{OR1KSIM}'s process number is known. Use the following to determine the process ID of the @code{or32-elf-sim} and then send the @code{SIGUSR1} command to toggle execution trace generation:
generate trace up to that point.
 
 
 
If the @code{pkill} utility is not available, the @code{kill} utility
 
can be used if @value{OR1KSIM}'s process number is known. Use the
 
following to determine the process ID of the @code{or32-elf-sim} and
 
then send the @code{SIGUSR1} command to toggle execution trace
 
generation:
 
 
@example
@example
ps a | grep or32-elf-sim
ps a | grep or32-elf-sim
kill -SIGUSR1 @emph{process-number}
kill -SIGUSR1 @emph{process-number}
@end example
@end example

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.