From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17718 invoked by alias); 27 Feb 2014 06:40:14 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 17622 invoked by uid 89); 27 Feb 2014 06:40:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 X-HELO: ip2.televic.com Received: from ip2.televic.com (HELO ip2.televic.com) (81.82.194.222) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 27 Feb 2014 06:40:11 +0000 Received: from SRV-VS06.TELEVIC.COM ([10.0.0.46]) by SRV-VS06.TELEVIC.COM ([10.0.0.46]) with mapi; Thu, 27 Feb 2014 07:40:06 +0100 From: =?iso-8859-1?Q?Lambrecht_J=FCrgen?= To: Michael Jones , ecos discuss Date: Thu, 27 Feb 2014 06:40:00 -0000 Message-ID: Reply-To: =?iso-8859-1?Q?Lambrecht_J=FCrgen?= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Subject: Re: [ECOS] Scheduler startup question X-SW-Source: 2014-02/txt/msg00004.txt.bz2 As far as I know the scheduler is started after cyg_user_start(), used by y= our application to initialize everything. Do you use cyg_user_start? Verzonden vanaf Samsung Mobile -------- Oorspronkelijk bericht -------- Van: Michael Jones Datum: Aan: ecos discuss Onderwerp: [ECOS] Scheduler startup question I have a question about proper scheduler locking startup behavior. The context is I am cleaning up my iMX6 HAL and attempting to make things w= ork without a couple of kernel hacks I added to make it work. The question has to do with sched_lock. By default this has a value of 1, s= o during startup the scheduler is locked. When there is an interrupt, sched_lock is incremented in Vectors.S, and dec= remented in interrupt_end. However, I am getting an assert in sync.h which is part of the BSD stack. T= he assert is because it expects the lock to be zero. The question is, during the startup process, how does the lock get set to z= ero after initialization? Is it supposed to stay 1 while hardware is initia= lized and through all the constructors, etc? Is it cleared by the scheduler= somehow? Is the HAL supposed to zero it at some point during startup? My HAL is part of the ARM hal, so if this is device specific, it is the ARM= HAL I am working with. Mike -- 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