Hi Alexandra, As far as I remember, I think you need to use "MinorTrace" debug flag and then can use "util/minorview.py" to visualize the trace created by "MinorTrace" flag. Other flags like debug-start can still be used. -Ayaz On Mon, May 8, 2023 at 10:06 PM Alexandra-Nicoleta DAVID via gem5-users < gem5-users@gem5.org> wrote: > Hello! > I am trying to extract some instruction traces containing the following > information: PC (instruction address), instruction type (e.g. ADD, MUL, > DIV, LOAD, STORE, etc.), operand values, and the result (e.g. PC = > 0x7245...0004, ADD, 1, 2, 3) in the HPI model using SE mode simulation. I > was able to extract the traces using the command "./build/ARM/gem5.opt > --debug-flags=O3PipeView --debug-start=<first tick of interest> > --debug-file=trace.out configs/example/se.py --cpu-type=O3CPU --caches -c > <path to binary> -m <last cycle of interest>", but for --cpu-type, I need > to use HPI which is derived from MinorCPU and I'm not exactly sure what > needs to be modified. I will attach the result of the previous command to > make it easier to understand what I am trying to achieve. Thank you very > much! Have a nice day! > > [image: image.png] > > [image: image.png] > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-leave@gem5.org >