public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Stefan Sommerfeld" <sommerfeld@mikrom.de>
To: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] RedBoot/Basic test working... context not?
Date: Fri, 22 Jul 2005 21:05:00 -0000	[thread overview]
Message-ID: <005e01c58f00$a194e970$152ca8c0@nullnullsix> (raw)
In-Reply-To: <008101c58e1a$fadb5820$152ca8c0@nullnullsix>

Hi,

found it. It was a pending GPIO edge detect IRQ. The LOAD_CONTEXT activated 
the IRQ's and crashed the system.

Bye...

----- Original Message ----- 
From: "Stefan Sommerfeld" <sommerfeld@mikrom.de>
To: <ecos-discuss@ecos.sourceware.org>
Sent: Donnerstag, 21. Juli 2005 19:38
Subject: Re: [ECOS] RedBoot/Basic test working... context not?


> Hi,
>>> >>
>>> >> I'm using a  XScale SO-DIMM module (Ka-Ro Triton270) and moving from 
>>> >> the
>>> >> development board to the destination plattform. If I run 'basic' or
>>> >> 'cache'
>>> >> test on the destination plattform, it works, but context does not. I
>>> >> guess
>>> >> context switching doesn't work, but i wonder what is the cause of 
>>> >> this.
>>> >> What is needed for context switching? I would think it's only 
>>> >> timer/cpu
>>> >> related stuff, so there couldn't be any influence from GPIO's.
>>> >>
>>> >> Any hints why context switch doesn't work?
>>> >
>>> > What do you mean by doesn't work? Does it give an error message? Does
>>> > an assert fail? Send out smoke signals as the SO-DIMM modules melts?
>>>
>>> I added some debug output and found the position where it stops:
>>>
>>>  HAL_THREAD_LOAD_CONTEXT( &sp[0] );
>>>
>>> 'context' executes this macro and stopped working (no output anymore).
>>> There's also no output from entry0. I sure it's some hardware 
>>> influence,
>>> but why does the threading doesn't work?
>>
>> Because this is much more complicated than the tests that you've
>> already run!  The biggest difference is that interrupts are normally
>> enabled as part of the change of context.  If you've got some I/O
>> misconfigured (based on your query about GPIO), this could be the
>> problem.
>>
> I agress with you, it sounds like an IRQ problem due to incorrect GPIO 
> config, but why does the program start work and the new threads not. 
> Event a program with a main() function doesn't work. Some test are 
> working, like thread0 or intr0, others not like thread1. Is there a test 
> where i can come a little closer to the problem?
>
> Bye...
>
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2005-07-22 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 13:35 Stefan Sommerfeld
2005-07-21 17:03 ` Andrew Lunn
2005-07-21 17:14   ` Stefan Sommerfeld
2005-07-21 17:19     ` Gary Thomas
2005-07-21 17:41       ` Stefan Sommerfeld
2005-07-22 21:05         ` Stefan Sommerfeld [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='005e01c58f00$a194e970$152ca8c0@nullnullsix' \
    --to=sommerfeld@mikrom.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).