public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@redhat.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] forwarded message from ilya kovnatsky
Date: Thu, 09 Aug 2001 23:38:00 -0000	[thread overview]
Message-ID: <15219.33098.385864.147492@zoftcorp.adsl.dk> (raw)

To : "Jesper Skov" <jskov at redhat dot com>
Subject : Re: 22781
From : "ilya kovnatsky" <ilya at ptgroupinc dot com>
Date : Thu, 9 Aug 2001 17:42:00 -0400
References : <15214.33231.491898.183690@zoftcorp.adsl.dk>

Thanks for the help, it was a not properly setup TLB.

New problem:

The code start running ( 2 threads each has a counter in a loop with a
delay) the counters get to 1
and then it sits in the idle loop.

There are no interupts occuring.

I manualy enabled the decrementer interupt and then both the counters got to
2 and stopped.

which interupt does the scheduler use ?
where in the code does it init the interupts to be used by the scheduler /
task switching?

thanks in advance.


Ilya

----- Original Message -----
From: Jesper Skov <jskov@redhat.com>
To: <bugs@cygnus.com>; <ilya@ptgroupinc.com>
Sent: Monday, August 06, 2001 7:38 AM
Subject: Re: 22781


>
> >I have a board I developed which is almost identical to the FADS
> >board. I have build the toolset and ecos. When ecos is triing to
> >setup the interupt vectors and reads from the SIMASK register, I get
> >a 1200 exception (tlb) eventhough all of the mapping registers are
> >disabled. Note: the excepton occurs in the cyg hal when it calls the
> >UNMASK_INTERUPT routine as soon as it tries to read from the SIMASK
> >register
>
> Maybe because the IMM base is not 0xff000000 as eCos expects. You can
> tell by the value in register 638 (only the 16 MSB bits).
>
> Otherwise I have no idea, sorry. Try asking on the mailing list.
>
> Jesper

             reply	other threads:[~2001-08-09 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 23:38 Jesper Skov [this message]
2001-08-10  9:47 ` Jonathan Larmour

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=15219.33098.385864.147492@zoftcorp.adsl.dk \
    --to=jskov@redhat.com \
    --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).