This is the mail archive of the
mailing list for the GDB project.
Re: Problem with GDB5.1.1 on Readhat Linux for DINK32
Thank You Jan,
powerpc-elf-gdb was created in /usr/loca/bin,
but the gdb couldn't communicate with DINK.
If anyone show me the log that gdb communicates
with dink, would you show me?
If you can load file into target board, and you can
save the log, would you show me please?
Thanks and Regards,
----- Original Message -----
From: "Vermeulen Jan" <Jan.Vermeulen@siemens.atea.be>
To: "'Yoichi Kimura'" <R32845@motorola.com>; <email@example.com>
Sent: Wednesday, April 17, 2002 8:52 PM
Subject: RE: Problem with GDB5.1.1 on Readhat Linux for DINK32
> > To installed GDB for DINK32, I used following commands
> > to install GDB on Linux..
> > $> ./configure --target=powerpc-elf
> > $> make
> It might be usefull to do "make install" (as root user) after the make.
> It will then install the debugger to /usr/local/bin.
> > Then, next, I entered following command.
> > $> gdb -b 9600
> > (gdb) target dink32 /dev/ttyS0
> > Then GDB didn't work and few minutes after,
> > GDB indicated as follows.
> > "Timeout reading form remote system."
> By entering "gdb -b 9600", you invoke the local (native) debugger.
> (for x86 I presume).
> If you want to debug powerpc applications, you need the powerpc debugger
> had made earlier.
> You made this debugger with "--target=powerpc-elf", so the debugger will
> called "powerpc-elf-gdb".
> so, try:
> $> powerpc-elf-gdb -b 9600 /dev/ttyS0
> and see if it helps to solve your problem.
> Best regards,
> Jan Vermeulen