GNU Development Chain for 68HC11/68HC12 - Bugs: bug #3243, GDB feeds characters to the...
You are not allowed to post comments on this tracker with your current authentication level.
bug #3243: GDB feeds characters to the D-Bug12 monitor too fast
Submitter: | Invalid User ID <#18145> | ||
Submitted: | Thu 17 Apr 2003 12:42:14 AM UTC | ||
Category: | gdb | Severity: | 3 - Normal |
Item Group: | sw-bug | Status: | None |
Privacy: | Public | Assigned to: | ciceron |
Open/Closed: | Open |
Tue 05 Apr 2005 02:35:39 PM UTC, comment #2: |
Jefferson Smith <imajeff> |
Wed 23 Apr 2003 08:15:18 PM UTC, comment #1: I agree. I have found a similar problem with HC11
|
Stephane Carrez <ciceron> |
Thu 17 Apr 2003 12:42:14 AM UTC, original submission:
I found the D-Bug monitor will drop characters very easily (at least the one I have does). I worked around this by adding delays in the serial_write routine, but that isn't very portable (or rather, it would overly restrict other debug methods). |
Invalid User ID <#18145> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2003-04-23 | ciceron | Assigned to | None | None |
Powered by Savane 3.13-caa5.
Corresponding source code
Is software flow control enabled (at least to allow the target to pause sending data)? That is important in D-Bug12 v4.x.x
If that is not the problem, I wonder if there is a set number of bytes you could send continuous, then delay long enough to re-sync bit framing, then continue. That would be if the baudrate is slightly off, and there is too many bit's sent with no distinguishable break.