[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Simulavr-devel] dump manager and special trace options
From: |
Stan Behrens |
Subject: |
Re: [Simulavr-devel] dump manager and special trace options |
Date: |
Sat, 26 Jan 2013 03:22:13 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 |
Hi Klaus,
I used the -c option once, actually it's a while ago but I can remember
that I had to take a look at the source as well.
I still have the details, so hopefully you don't have to look it up
yourself.
The tracing option gives you the exact cpu-cycle-count at which a new
value was set for a specific memory address you are interested in.
I used this to validate timing in a highly interrupt driven piece of
code. This feature is very cool if you like using automated testing ;)
My command line looked like this:
$ simulavr --device atmega128 --cpufrequency 1000000 --file Firmware.elf
--breakpoint abort -c vcd:tracer-input:tracer-output
"tracer-output" is a file that will be written to. I attached a PHP
script that transformes it into the AVR Studio stimuli format which
should be nicer to understand.
My "tracer-input" file was simple, it could be more complex but this was
all I needed:
+ PORTB.PORT
You can get a valid set of options for the "trace-input" file via the -o
option of simulavr:
$ simulavr --device atmega128 -o /dev/stdout
Bye, Stan.
vcddump_to_stimulilog.php
Description: Text document