Bug 8828 - m68k-dBUG target download program times out
Summary: m68k-dBUG target download program times out
Status: RESOLVED OBSOLETE
Alias: None
Product: gdb
Classification: Unclassified
Component: remote (show other bugs)
Version: 6.1
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-29 22:28 UTC by mike
Modified: 2022-12-21 16:12 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mike 2004-07-29 22:28:01 UTC
[Converted from Gnats 1723]

After issuing a "load" command using the m68k dBUG target, gdb times out.  The problem is due to sending two extra '\r's in "load_srec" in dsrec.c.  In Monitor.c "monitor_load" after sending the srec is only expecting one prompt, but in the m68k-dBUG monitor it will get three prompts due to the extra '\r's.  So when the next command to write the program counter is executed some characters can get lost if the remote target is still busy with the '\r's.  This then causes the system to get out of synch an time out.

Release:
gdb 6.1

Environment:
Cygwin

How-To-Repeat:
1. Start GDB
2. Select target dbug DEV (configure gdb with m68k-elf-dbug)
3. load
4. Sometimes it will load other times it will time out.

I am using it at 115200 baud on COM 1 (/dev/ttyS0) on WinXP Home and Cygwin.
Comment 1 mike 2004-07-29 22:28:01 UTC
Fix:
Either don't send the extra '\r's after downloading the srec or expect three prompts.

Comment mentions that only some target monitors require the '\r's - Well dBUG is not one of them!
Comment 2 Tom Tromey 2022-12-21 16:12:43 UTC
This code was deleted by

commit 40e0b27177e747600d3ec186458fe0e482a1cf77
Author: Pedro Alves <palves@redhat.com>
Date:   Mon Aug 24 15:40:26 2015 +0100

    Delete the remaining ROM monitor targets
    
    Ref: https://sourceware.org/ml/gdb/2015-07/msg00011.html