Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tried the test and nothing happened #168

Closed
liborw opened this issue Aug 17, 2016 · 3 comments
Closed

Tried the test and nothing happened #168

liborw opened this issue Aug 17, 2016 · 3 comments

Comments

@liborw
Copy link

liborw commented Aug 17, 2016

Hi, I have tried the test from the README:

$ ./simavr/run_avr tests/atmega88_example.axf
AVR_MMCU_TAG_VCD_TRACE 00c6:00 - UDR0
AVR_MMCU_TAG_VCD_TRACE 00c0:20 - UDRE0
Loaded 1722 .text at address 0x0
Loaded 114 .data
Loaded 4 .eeprom

the produced gtkwave_trace.vcd is empty.

@freez10
Copy link

freez10 commented Aug 18, 2016

the produced gtkwave_trace.vcd is empty.

Try adding signals to the timeline
I was also confused because it does not print further information eg

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

Is it a bug or..? I see in version 1.0 it was ok.

@Lotharyx
Copy link
Contributor

Lotharyx commented Oct 11, 2016

Me too. No output past "loaded 4 .eeprom":

$ simavr/run_avr tests/atmega88_example.axf 
AVR_MMCU_TAG_VCD_TRACE 00c6:00 - UDR0
AVR_MMCU_TAG_VCD_TRACE 00c0:20 - UDRE0
Loaded 1706 .text at address 0x0
Loaded 114 .data
Loaded 4 .eeprom

but the gtkwave_trace.vcd file seems whole. Adding a couple -v flags to the command gave additional output:

$ simavr/run_avr -v -v tests/atmega88_example.axf 
AVR_MMCU_TAG_VCD_TRACE 00c6:00 - UDR0
AVR_MMCU_TAG_VCD_TRACE 00c0:20 - UDRE0
Loaded 1706 .text at address 0x0
Loaded 114 .data
Loaded 4 .eeprom
_avr_vcd_notify trace buffer resized to 51
Read from eeprom 0xdeadbeef -- should be 0xdeadbeef..
Read from eeprom 0xcafef00d -- should be 0xcafef00d..
simavr: sleeping with interrupts off, quitting gracefully

...but still not really the same thing as what's depicted in the README.

@AE1020
Copy link

AE1020 commented Apr 14, 2021

I built on Linux (with plain make), and also do not get a match for what is in the output from the README. Instead I get:

$ ./simavr/run_avr tests/atmega88_example.axf 
Loaded 1760 .text at address 0x0
Loaded 114 .data
Loaded 4 .eeprom
Read from eeprom 0xdeadbeef -- should be 0xdeadbeef..
Read from eeprom 0xcafef00d -- should be 0xcafef00d..

This is in contrast to what the README says; which has additional lines:

$ ./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

The output I got nearly matches for the lines that are present (differs 1760 vs 1780 for .text), but is missing several lines. Adding -v doesn't change it to add more output.

It produces a gtkwave_trace.vcd. But viewing it with gtkwave gtkwave_trace.vcd does not look like the output in the sample. :-/

@buserror buserror closed this on Jan 10, 2018

Was this issue closed in error, or was it believed that a problem was fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants