From: Gary Thomas <gthomas@redhat.com>
To: "Chris C." <phchang@programmer.net>
Cc: regsoft@sinaman.com, ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] RedBoot Problems!
Date: Mon, 30 Jul 2001 07:20:00 -0000 [thread overview]
Message-ID: <XFMail.20010730082024.gthomas@redhat.com> (raw)
In-Reply-To: <20010730141020.9735.qmail@mail.com>
On 30-Jul-2001 Chris C. wrote:
> Hi
>
> Here are some questions I want to ask:
>
> 1. I have selected the redboot template in the config. tool and then I select ROM startup, import
> all the necessary packages, without changing the redboot default setting, debug serial port and
> diagnostic serial port are same (0). After that, I generated the bin file and download to the
> target board and use the hyper terminal to connect the target board. I saw a string like this
> -> $T0540:fff05cd8;01:00004664;#92 and I can use the gdb to connect the target board and
> display the value of the registers. My problem is that I didn't see the "Redboot>"
> at the hyper terminal [com1 and com2], so what is the problem?
>
This means that RedBoot crashed during it's initialization. Obviously a lot got
running, hence GDB being able to run.
In order to help more, you'll have to tell us:
What platform (architecture, board)?
What tools did you use to build with?
What extra options (if any) you selected?
> 2. Which one is the redboot used to communicate with hyper terminal?
> The device driver in packages\devs\serial or the function in hal_diag.c
RedBoot only uses the HAL diag I/O routines.
BTW - exclamatories(!) in the subject will often send your message directly
to the "round file", especially mine :-)
next prev parent reply other threads:[~2001-07-30 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 7:10 Chris C.
2001-07-30 7:20 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 3:07 Chris C.
2001-07-25 3:21 ` Jesper Skov
2001-07-25 5:29 ` Gary Thomas
2001-07-24 22:12 Chris C.
2001-07-25 1:14 ` Jesper Skov
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=XFMail.20010730082024.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=phchang@programmer.net \
--cc=regsoft@sinaman.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).