search

larsks / blog.oddbit.com

3 stars 0 forks source link

post/2019-01-22-debugging-attiny-code-pt-3/ #14

Open utterances-bot opened 3 years ago

utterances-bot commented 3 years ago

Debugging attiny85 code, part 3: Tracing with simavr · The Odd Bit

This is the third of three posts about using gdb and simavr to debug AVR code. The complete series is: Part 1: Using GDB A walkthrough of using GDB to manually inspect the behavior of our code. Part 2: Automating GDB with scripts Creating GDB scripts to automatically test the behavior of our code. Part 3: Tracing with simavr Using simavr to collect information about the state of microcontroller pins while our code is running.

https://blog.oddbit.com/post/2019-01-22-debugging-attiny-code-pt-3/

vibrion121 commented 3 years ago

Hi i found your article in the (painful) path to simulate (at least) an ATmega328. VCD files only allows to view output stimulus isnt it? Is there a way to generate input stimulus?. I' ve read several times the examples provided in simavr but i cannot figure out how this is done. Thanks!

vibrion121 commented 3 years ago

PS: using VSCODE as IDE.....

larsks commented 3 years ago

Hi, thanks for reading :).

In terms of generating stimulus inputs, you can see how I do that in the previous article by using GDB to e.g. explicitly set PINB.