[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Simulavr-devel] AVR-GDB inerrupt debugging problem
From: |
Radovid Drobnjak |
Subject: |
[Simulavr-devel] AVR-GDB inerrupt debugging problem |
Date: |
Tue, 06 Feb 2007 17:02:53 +0100 |
User-agent: |
Opera Mail/9.10 (Linux) |
Hi,
I would like to debug a simple PWM program for atmega128, and I cannot
find out why the simulator does not trigger the interrupt function
(TIMER2_OVF_vect).
I've checked the registry settings of the program few times and all seems
OK to me. But the thing what puzzles me even more is that I've tried to
simulate the program in avrora (without GDB, as the support for gdb there
is not so good) observing the OCR2 registry and all seemes to work fine,
as the mentioned registry was updated acording to the expectations (it is
updated inside the interrupt function).
Is it a bug or something, or I've missed something?
here are the last few lines of the -G option:
gdb -> Ack
Recv: "$s#73"
Ack -> gdb
Sent: $T0520:82;21:ff10;22:dc010000;#c0
gdb -> Ack
Recv: "$s#73"
Ack -> gdb
Sent: $T0520:82;21:ff10;22:c6010000;#92
gdb -> Ack
Recv: "$s#73"
Ack -> gdb
Sent: $T0520:82;21:ff10;22:ca010000;#bd
SystemClock::Endless stopped
number of cpu cycles simulated: 8860278
IRQ STATISTIC
FlagSet flagCleared HandlerStarted HandlerFinished
Set->Clear Set->Started Set->Fini
hed
the log file is attached.
THX in advance
Radovid
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
log.txt
Description: Text document
- [Simulavr-devel] AVR-GDB inerrupt debugging problem,
Radovid Drobnjak <=