From: Ormund Williams <ormundw@brainlink.com>
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Problems building stand-alone gdb stub for ARM AEB
Date: Sat, 07 Oct 2000 11:21:00 -0000 [thread overview]
Message-ID: <39DF69A8.81D91556@brainlink.com> (raw)
In-Reply-To: <39DB6970.6BA6C737@brainlink.com>
Ormund Williams wrote:
>
> Gary Thomas wrote:
> >
> > On 04-Oct-2000 Ormund Williams wrote:
> > > Framing errors are my problem. Seems like a hardware problem, so I'll
> > > work on that next. Has any body seen this problem?
> > >
> >
> > Notice that when you connect, the host will be sending you a string of
> > 6 characters or so at full speed. If the target device does not have
> > buffering or isn't quick enough, then this will surely cause framing
> > errors when running at speed.
>
> The UART on the ARM AEB has no FIFO so each character must be read
> before the next arrives, if that fails the Over-run flag is set in the
> Line Status Register. This I have tested by inserting a delay.
>
> The problem I'm seeing though, is the Frame error flag is set. This
> only happens with some character sequences, from that I am concluding
> that the board is malfunctioning, I am going to try a different one,
> I'll let you know how it goes.
>
> PS: There's no need to cc me since I'm subscribed to the list. Thanks
>
> --
> Ormund
Hi
Found the problem! My ARM AEB's serial port 1 is bad. Using a MAX202,
some wire and 0.1u caps, I connected my PC to serial port 0 on the ARM
AEB and !!BANG!! gdb connected, no errors!
Thanks
--
Ormund
prev parent reply other threads:[~2000-10-07 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-29 14:02 [ECOS] Problems building stand-alone gdb stub for ARM AEB board Ormund Williams
2000-10-02 15:25 ` [ECOS] Problems building stand-alone gdb stub for ARM AEB bo Gary Thomas
2000-10-03 20:37 ` [ECOS] Problems building stand-alone gdb stub for ARM AEB Ormund Williams
2000-10-03 21:33 ` Gary Thomas
2000-10-04 10:30 ` Ormund Williams
2000-10-07 11:21 ` Ormund Williams [this message]
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=39DF69A8.81D91556@brainlink.com \
--to=ormundw@brainlink.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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: link
Be 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).