Hey Markus, after a long while, I am finally trying to catch up a bit with simulavr development. I originally wrote the VCD code. Thank you for the detailed description! I remember correctly, the 'range' feature for the list of traced variables is to specify a range of variables, not a range the variable is in. For example all of PORTB 0 .. 7.
I also like to add that I also implemented code (I actually have to check whether it suffered any bitrot), that allows you to hook simulavr into a Verilog simulator (such as Icarus Verilog). That way, it was very easy to model multiple AVRs and also additional logic. Icarus verilog can produce .vcd files as well. Cheers, Onno On 11/20/2013 01:16 PM, Markus Hitter wrote: > Hey, did I blow away everybody else with all my writing already? It's so > quiet here. Ha ha. > > > Anyways. After another few days of wrestling with the source code I > found out on how to capture signals in VCD files to be viewed in > GTKWave. Not only for my fellow RepRappers, but also to save everybody > else from this hide and seek nightmare, I've written down the basics in > the RepRap wiki: > > http://reprap.org/wiki/SimulAVR#Advanced_signal_tracing > > Once you know how it works, it's very simple. Unlike for accessing UART, > no need to program a wrapper application. Actually it's so simple I > postponed to add this to the SIMINFO strategy for now. > > > Enjoy! > Markus > > > P.S.: if you feel like editing these instructions, the RepRap wiki is > open for everybody. Just create an account an edit away. _______________________________________________ Simulavr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/simulavr-devel
