gatk555

The README does not say that the program you build will produce that output, just "A program running with these instructions ... will display". Evidently an older version of run_avr...

It has been logged before: #168 and #445. The main part of #168 (empty VCD file) is fixed, probably by #440.

I have also looked at this and even written some code. There are at least two other differences: the new processors have different interrupt handling, more flexible, and all interrupts...

The interrupt and register/memory map changes are now in the "main" branch of my fork. No peripheral code so far. All the tests and examples for existing cores seems to...

I think the reason is that it was designed that way: my guess is that it was to keep the code small. To fix this, the code needs to monitor...

Should be fixed [here](https://github.com/gatk555/simavr) where the fast timer was removed and level-triggering handled as described above. Unfortunately it is not easy to make a PR for it, other than one...

1. Have you tried tracing the UDR register? 2. I think it is a design choice that the GPRs can not be traced. Speed was preferred over an arguably pointless...

If you are using a pre-built binary, --trace likely fails silently if tracing is not configured. An error message was added in April. I do not know of any source...

You can attach files here, or if that seems too permanent, email to my associated mailbox: gatk555(at)gmail.com. But if you are using the shared library, why not compile it yourself?...

... a patch into a PR ... PR 439. Trying to learn git, and beginning to like it.