From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gthomas@cambridge.redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RedBoot serial rx interrupts
Date: Sat, 13 Jan 2001 12:57:00 -0000 [thread overview]
Message-ID: <20010113150104.A32083@visi.com> (raw)
In-Reply-To: <XFMail.20010113135227.gthomas@cambridge.redhat.com>
> >> It should not. Where are you seeing this [which file/line]?
> >
> > hal/common/src/hal_if.c line 419 (at end of hal_ctrlc_isr_init()).
> >
> > I suspect this appears to be happening because
> > CYGSEM_HAL_ROM_MONITOR == 0 (because CYG_HAL_STARTUP == RAM ?)
>
> You should _not_ have the options required to include this code set.
> The options CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT and CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT
> should only be enabled for "normal" eCos applications.
>
> > I there a list of what the values for all of the configuration flags
> > need to be in order for RedBoot to work?
>
> The best/simplest way is to use the template.
> % ecosconfig new PLATFORM redboot
> % ecosconfig tree
That is exactly what I'm doing:
$ ecosconfig new rpsh2 redboot
U CYGHWR_HAL_ARM_BIGENDIAN, new inferred value 1
U CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT, new inferred value 1
U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
U CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT, new inferred value 0
U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
I guess there must be something wrong with my HAL cdl file.
I'll go back and compare it to one of the others.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-01-13 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 15:09 Grant Edwards
2001-01-13 7:17 ` Gary Thomas
2001-01-13 12:37 ` Grant Edwards
2001-01-13 12:52 ` Gary Thomas
2001-01-13 12:57 ` Grant Edwards [this message]
2001-01-13 13:45 ` Grant Edwards
2001-01-13 14:11 ` Gary Thomas
2001-01-13 14:31 ` Grant Edwards
2001-01-13 15:13 ` Gary Thomas
2001-01-13 15:32 ` Grant Edwards
2001-01-15 4:02 ` Nick Garnett
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=20010113150104.A32083@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@cambridge.redhat.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).