public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001802] New: serial high water mark (serial.c) Date: Tue, 19 Mar 2013 19:11:00 -0000 [thread overview] Message-ID: <bug-1001802-13@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email, use the link below. http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001802 Bug ID: 1001802 Summary: serial high water mark (serial.c) Product: eCos Version: unknown Target: nios2_stratix2_2s60_rohs_tseplus (Stratix II, TSE+ design) Architecture/Host Nios II OS: Status: UNCONFIRMED Severity: normal Priority: low Component: Serial Assignee: unassigned@bugs.ecos.sourceware.org Reporter: praveenrai@ge.com CC: ecos-bugs@ecos.sourceware.org We have Rs232 port on our board to print debug messages, stderr. We can also type commands from terminal (putty, hyper-term, minicom etc) for diagnostics and debugging. Every character typed is echoed back. But for some reason if I do an extensive cycling of command say "switch mode", after 1000 cycles (basically typing "switch mode" for 1000 times at some interval) the text gets truncated and instead of "switch mode" I see "switch mo" and after approx 1 min of this happening I high hit serial high water mark in serial_rcv_char() in serial.c. The condition ( cbuf->nb >= cbuf->high_water ) is true. So far, from debugging, it seems if number of bytes exceed 84 this condition becomes true. I am using eCosPro 2.0.69 release. Any help is appreciated. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-03-19 19:11 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-19 19:11 bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2013-03-19 19:11 bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001802-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).