From: "???" <jclin@itri.org.tw>
To: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] MPC823 interrupt problem?
Date: Wed, 04 Apr 2001 06:00:00 -0000 [thread overview]
Message-ID: <00c301c0bd07$26c0bc80$8267608c@e> (raw)
In-Reply-To: <ot66gnn2d1.fsf@thinktwice.zoftcorp.dk>
> >Hi everyone: I am porting eCos on my custom
> >board. The CPU on my board is MPC823. Redboot is
> >ready for my borad. But I try to run hello
> >example using default template, it will stop on
> >undefine code. I use Trace32 to debug the hello
> >program. When the code enable interrupt in
> >cyg_Scheduler::start(), it will stop on undefine
> >code ( at CYGARC_PPC_EXCEPTION_DECREMENT+0x888)
> >What problem may I meet?? or What should I set or
> >unset option at configuration tool??
>
> CYGARC_PPC_EXCEPTION_DECREMENT is a preprocessor symbol which is used
> to adjuste the stack on exceptions. It should never form part of an
> address and I'm surprised that the debugger knows about it at all.
>
> Sounds like the problem is caused by interrupts though, so that's
> probably where you want to be looking.
>
> Jesper
Hi :
I find out the problem. Because I download hello.exe via Trace32.
Hello.exe is a ram_base application. It doesn't install exception vectors.
When the hello.exe code turn on interrupt, it will be down. Sorry I don't
notice the option(copy exception vectors to ram). Turn it on, everything
is OK.
Ken
prev parent reply other threads:[~2001-04-04 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 6:18 林志勝
2001-04-02 1:16 ` Jesper Skov
2001-04-03 14:53 ` Linus Nielsen Feltzing
2001-04-04 6:00 ` ??? [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='00c301c0bd07$26c0bc80$8267608c@e' \
--to=jclin@itri.org.tw \
--cc=ecos-discuss@sources.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).