From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32372 invoked by alias); 21 Jul 2005 17:41:14 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 32361 invoked by uid 22791); 21 Jul 2005 17:41:11 -0000 Received: from bonn.shuttle.de (HELO bonn.shuttle.de) (194.95.249.247) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 21 Jul 2005 17:41:11 +0000 Received: by bonn.shuttle.de (Postfix, from userid 10) id CB0746C48B; Thu, 21 Jul 2005 19:41:09 +0200 (CEST) Received: from nullnullsix (nullnullsix.mikrom.local [192.168.0.32]) by mikrom.de (Postfix) with SMTP id 858678CC12 for ; Thu, 21 Jul 2005 19:38:17 +0200 (CEST) Message-ID: <008101c58e1a$fadb5820$152ca8c0@nullnullsix> From: "Stefan Sommerfeld" To: References: <006101c58df8$ffd915f0$152ca8c0@nullnullsix> <20050721163955.GS15048@lunn.ch> <007401c58e17$5823cb60$152ca8c0@nullnullsix> <1121966353.12697.164.camel@hermes> Date: Thu, 21 Jul 2005 17:41:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Subject: Re: [ECOS] RedBoot/Basic test working... context not? X-SW-Source: 2005-07/txt/msg00226.txt.bz2 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