* FW: remote serial target - "not a typewriter" failure message
@ 2003-11-21 7:27 Backhaus Willy
2003-11-21 19:05 ` Keith Seitz
0 siblings, 1 reply; 4+ messages in thread
From: Backhaus Willy @ 2003-11-21 7:27 UTC (permalink / raw)
To: insight
hello,
maybe it't OT..
I sent this mail to thr gdb people, but I didn't get an answer.
can someone help me with this?
I'm using cygwin dll 1.5.5-1 under win2000.
Regards,
Willy
> -----Original Message-----
> From: Backhaus Willy [mailto:w.backhaus@newage-avkseg.com]
> Sent: Thursday, October 30, 2003 9:24 AM
> To: 'gdb@sources.redhat.com'
> Subject: remote serial target - "not a typewriter"
> failure message
>
> hello,
>
> we are using cygwin and arm-elf-gdb (actually insight) to
> debug our embedded systems.
> when trying to connect (with "target remote COMx") I get the
> message "not a typewriter".
> I read the mailing list archive, it seams that this problem
> in known but I didn't find a wordkaround.
>
> any hints?
>
> Regards.
> Willy
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: FW: remote serial target - "not a typewriter" failure message
2003-11-21 7:27 FW: remote serial target - "not a typewriter" failure message Backhaus Willy
@ 2003-11-21 19:05 ` Keith Seitz
2003-11-27 11:25 ` Backhaus Willy
0 siblings, 1 reply; 4+ messages in thread
From: Keith Seitz @ 2003-11-21 19:05 UTC (permalink / raw)
To: Backhaus Willy; +Cc: insight
On Thu, 2003-11-20 at 23:33, Backhaus Willy wrote:
> > we are using cygwin and arm-elf-gdb (actually insight) to
> > debug our embedded systems.
> > when trying to connect (with "target remote COMx") I get the
> > message "not a typewriter".
Hmmm I've not seen this error myself, but then I don't do embedded work
anymore (much less on Windows).
What version of insight/gdb are you using? Does this happen with vanilla
gdb? (Add -nw flag)
Keith
^ permalink raw reply [flat|nested] 4+ messages in thread
* FW: remote serial target - "not a typewriter" failure message
2003-11-21 19:05 ` Keith Seitz
@ 2003-11-27 11:25 ` Backhaus Willy
2003-11-28 20:37 ` Keith Seitz
0 siblings, 1 reply; 4+ messages in thread
From: Backhaus Willy @ 2003-11-27 11:25 UTC (permalink / raw)
To: insight
hello,
> Hmmm I've not seen this error myself, but then I don't do
> embedded work
> anymore (much less on Windows).
>
> What version of insight/gdb are you using? Does this happen
> with vanilla
> gdb? (Add -nw flag)
it's gdb 6.0.
someone gave me a good hint: to use /dev/ttyS0 instead of COM1.
it works only if I use the "target" and "load" in the console window. the
Insight menu entries "target settings", "connect to target" and "download"
doesn't work.
regards,
Willy
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: FW: remote serial target - "not a typewriter" failure message
2003-11-27 11:25 ` Backhaus Willy
@ 2003-11-28 20:37 ` Keith Seitz
0 siblings, 0 replies; 4+ messages in thread
From: Keith Seitz @ 2003-11-28 20:37 UTC (permalink / raw)
To: Backhaus Willy; +Cc: insight
On Thu, 2003-11-27 at 03:32, Backhaus Willy wrote:
> someone gave me a good hint: to use /dev/ttyS0 instead of COM1.
> it works only if I use the "target" and "load" in the console window. the
> Insight menu entries "target settings", "connect to target" and "download"
> doesn't work.
Historically on cygwin, insight has always used com1, com2, ...
If you really feel like it, you can edit interace.tcl and
targetselection.itb and change cygwin to use /dev/ttyS#, too.
Has a bug report been filed with gdb?
Keith
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-11-28 20:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-21 7:27 FW: remote serial target - "not a typewriter" failure message Backhaus Willy
2003-11-21 19:05 ` Keith Seitz
2003-11-27 11:25 ` Backhaus Willy
2003-11-28 20:37 ` Keith Seitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).