I will agree that printk's work great when you are into the 'c' code. I find
the logic analyzer is most useful when I am in the 'S' code of the boot
loader or the initialization files of the kernel. The other place the logic
analyzer is extremely helpful is in debugging device drivers like PCI, USB,
SCSI, PCMCIA and Ethernet.
--George
George France, [EMAIL PROTECTED]
Cambridge Research Laboratory, Compaq Computer Corporation
One Kendall Square, Building 700 MS: CRL
Cambridge, MA 02139 USA
-----Original Message-----
From: David Rusling [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 05, 2000 10:56 AM
To: Russell King - ARM Linux Admin
Cc: Nicolas Pitre; Gaixia Zhang; [EMAIL PROTECTED]
Subject: Re: Debugger / Emulator / Logic Analyzer for EBSA285 clone
board
Russell King - ARM Linux Admin wrote:
> Nicolas Pitre writes:
> > The best strategy is still probably to have a solid knowledge of what
> > should be going on and carefully placed printk's to a serial port.
I would also tend to agree - even with access to in-circuit emulation, I
still
use printk()'s extensively. Mind you, it is somewhat of a luxury to be able
to stop the machine and see where it is...
Dave
----------------------------------------------------------------------
David A Rusling Consulting Engineer
ARM Limited
Liberty House,
Moorbridge Road,
Maidenhead, SL6 8LT
Tel: UK-(0)1628-427754
Fax: UK-(0)1628-780551
e-mail: [EMAIL PROTECTED]
----------------------------------------------------------------------
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for
++
++ kernel-related discussions.
++
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
