This is the mail archive of the
mailing list for the crossgcc project.
FYI: gdb-4.18 + target ARM (or Thumb) used with Angel + Debian GNU/Linux
- To: email@example.com
- Subject: FYI: gdb-4.18 + target ARM (or Thumb) used with Angel + Debian GNU/Linux
- From: "Robert J. Brown" <firstname.lastname@example.org>
- Date: Tue, 27 Jul 1999 23:16:58 -0500
- References: <email@example.com>
- Reply-To: firstname.lastname@example.org
>>>>> "Christian" == Christian Ericsson <email@example.com> writes:
Christian> FYI: gdb-4.18 will not work with the configuration
Christian> above, if not patched!
Christian> I have been trying to get target debugging to work with
Christian> Atmel evaluation board featuring the ARM7TDMI
Christian> processor. The command "target rdi /dev/ttyS0" didn't
Christian> work in gdb-4.18.
Christian> The problem was that normal Linux systems use /dev/cua0
Christian> as the first serial port, but Debian GNU/Linux 2.1
Christian> (which I use) use /dev/ttyS0 instead. I did try to make
Christian> a soft link, like: ln -s /dev/ttyS0 /dev/cua0 But, it
Christian> didn't solve the problem. The serial port to use is
Christian> hard coded! So, I changed the right source code file to
Christian> use /dev/ttyS0 instead of /dev/cua0. And, now it works!
It definately needs to be fixed to take the device as a command line
parameter, or in a .gdbrc file.
Christian> If you are using Red Hat Linux, you will not need any
If you are also using mgetty/vgetty on that port, you certainly will
need the patch, as the mgetty lockfile conventions require that ttyS0
be used, and *NEVER* cua0 (or any other name for that same port).
Violating this convention will render dial-in and dial-out on the same
Christian> I'm going to make a bug report to the gdb-team.
-------- "And there came a writing to him from Elijah" [2Ch 21:12] --------
R. J. Brown III firstname.lastname@example.org http://www.elilabs.com/~rj voice 847 543-4060
Elijah Laboratories Inc. 457 Signal Lane, Grayslake IL 60030 fax 847 543-4061
----- M o d e l i n g t h e M e t h o d s o f t h e M i n d ------
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
To remove yourself from the crossgcc list, send
mail to email@example.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.