simavr is a new AVR simulator for linux, or any platform that uses avr-gcc. It usesavr-gcc's own register definition to simplify creating new targets for supported AVRdevices. The core was made to be small and compact, and hackable so allow quickprototyping of an AVR project. The AVR core is now stable for use with partswith <= 128KB flash, and with preliminary support for the bigger parts. Thesimulator loads ELF files directly, and there is even a way to specify simulationparameters directly in the emulated code using an .elf section. You can alsoload multipart HEX files.
On OSX, we recommend using homebrew:
brew tap osx-cross/avr
brew install --HEAD simavr
On Ubuntu, SimAVR is available in the Bionic package source:
apt-get install simavr
(Note that the command is made available under the name simavr
not run_avr
.)
Otherwise, make
is enough to just start using bin/simavr. To install the simavr command system-wide, make install RELEASE=1
.
Patches are always welcome! Please submit your changes via Github pull requests.
simavr can output most of its pins, firmware variables, interrupts and a few otherthings as signals to be dumped into a file that can be plotted using gtkwave forfurther, precise analysis.A firmware can contain instructions for simavr to know what to trace, and the file isautomatically generated.Example:
const struct avr_mmcu_vcd_trace_t _mytrace[] _MMCU_ = {
{ AVR_MCU_VCD_SYMBOL("UDR0"), .what = (void*)&UDR0, },
{ AVR_MCU_VCD_SYMBOL("UDRE0"), .mask = (1 << UDRE0), .what = (void*)&UCSR0A, },
};
Will tell simavr to generate a trace everytime the UDR0 register changes and everytimethe interrupt is raised (in UCSR0A). The MMCU tag tells gcc that it needs compiling,but it won't be linked in your program, so it takes literally zero bytes, this is a codesection that is private to simavr, it's free!A program running with these instructions and writing to the serial port will generatea file that will display:
$ ./simavr/run_avr tests/atmega88_example.axf
AVR_MMCU_TAG_VCD_TRACE 00c6:00 - UDR0
AVR_MMCU_TAG_VCD_TRACE 00c0:20 - UDRE0
Loaded 1780 .text
Loaded 114 .data
Loaded 4 .eeprom
Starting atmega88 - flashend 1fff ramend 04ff e2end 01ff
atmega88 init
avr_eeprom_ioctl: AVR_IOCTL_EEPROM_SET Loaded 4 at offset 0
Creating VCD trace file 'gtkwave_trace.vcd'
Read from eeprom 0xdeadbeef -- should be 0xdeadbeef..
Read from eeprom 0xcafef00d -- should be 0xcafef00d..
simavr: sleeping with interrupts off, quitting gracefully
And when the file is loaded in gtkwave, you see:
You get a very precise timing breakdown of any change that you add to the trace, downto the AVR cycle.
simavr is really made to be the center for emulating your own AVR projects, not justa debugger, but also the emulating the peripherals you will use in your firmware, soyou can test and develop offline, and now and then try it on the hardware.
You can also use simavr to do test units on your shipping firmware to validate itbefore you ship a new version, to prevent regressions or mistakes.
simavr has a few 'complete projects/ that demonstrate this, most of them were madeusing real hardware at some point, and the firmware binary is exactly the one thatran on the hardware. The key here is to emulate the parts or peripherals thatare hooked to the AVR. Of course, you don't have to emulate the full hardware, you justneed to generate the proper stimulus so that the AVR is fooled.
This example board hooks up an Atmega48 to an emulated HD44780 LCD and display a runningcounter in the 'lcd'. Everything is emulated, the firmware runs exactly like thison a real hardware.
And this is a gtkwave trace of what the firmware is doing. You can zoom in, measure, etcin gtkwave, select trades to see etc.
Quite a few other examples are available!