[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-gcc-list] Fwd: parallel port debugging, need cyclic function call

From: Torsten Mohr
Subject: [avr-gcc-list] Fwd: parallel port debugging, need cyclic function call
Date: Thu, 2 Jan 2003 17:59:01 +0100
User-agent: KMail/1.4.3

Hi everybody,

what is the state of the JTAG debugging of AVR targets?

I've just mailed this message on the gdb mailing list
to announce the JTAG functionality i've added to gdb-5.3.

I'd be glad to share this code with others, the parallel port
stuff and the JTAG stuff are working fine and are ready
to use, i'm onlly working on the ARM specific stuff.

Best regards,

###########  FORWARDED ###########


i made a new version of a parallel port project available at:


With that library you can debug an ARM7TDMI via the
parallel port.  Now also HW breakpoints and single
stepping is supported.

At the moment i try to port its functionality to gdb-5.3.

I've yet added:

pport.h: function prototypes

write data and control register, read status
register, lowlevel intialisation, set device name,
machine-specific delay routines

provide setting an "inversion mask" for parallel
ports registers, set/clear/read single pins.
Some examples:
"pport invdata 0x02" inverts D1 of the parallel port.
"pport high 5" sets D5 to high level.
"pport low 3" sets D3 level to low.
"pport read 23" reads the BUSY line of the status register.

provide software JTAG over the parallel ports pins.
What pins have what functionality can be set with
commands like.  The delay can also be set.
Some examples:
"ppjtag tms 3" tells the SW JTAG to use D3 as "Test Mode Set".
"ppjtag delay 3" sets a delay of 3 useconds.

ppja.c: (Parallel Port Jtag Arm, stupid name)
All the functionality to debug an ARM via the parallel port.
"ppja info" prints the IDCODE of the attached target.

There isn't yet much working, i'm trying to give gdb
a "struct target_ops *" to tell it how to use the

Is there an entry in "struct target_ops" that is called
cyclically?  I need to check from time to time, if the
targets state has changed.  "target.h" is quite useful,
but i didn't find any functionality like that in it.

Is there a way to tell gdb to cyclically call a certain

Best regards,


avr-gcc-list at http://avr1.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]