From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16097 invoked by alias); 23 Oct 2003 12:03:26 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 16074 invoked from network); 23 Oct 2003 12:03:25 -0000 Received: from unknown (HELO hermes.chez-thomas.org) (63.225.98.241) by sources.redhat.com with SMTP; 23 Oct 2003 12:03:25 -0000 Received: by hermes.chez-thomas.org (Postfix, from userid 2000) id CE75550E0DB; Thu, 23 Oct 2003 06:03:24 -0600 (MDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by hermes.chez-thomas.org (Postfix) with ESMTP id E791150D93B; Thu, 23 Oct 2003 06:03:23 -0600 (MDT) From: Gary Thomas To: James Yates Cc: "Ecos Discuss (E-mail)" In-Reply-To: References: Content-Type: text/plain Organization: MLB Associates Message-Id: <1066910603.29481.351.camel@hermes> Mime-Version: 1.0 Date: Thu, 23 Oct 2003 12:03:00 -0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_XIMIAN autolearn=ham version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: [ECOS] Real Time Clock X-SW-Source: 2003-10/txt/msg00411.txt.bz2 On Thu, 2003-10-23 at 05:44, James Yates wrote: > I have a platform which when boots, copies code that was placed to be run from RAM, from a flash device to the correct location in RAM. The VBR is then modified correctly and a jump is made to the first address contained in the first entry of the vector table. > > The app I have built which I store in flash is a simple eCos app consisting of 2 threads and I am trying to get timeslicing working. I am a bit unsure of the build options I should set since although this is running from RAM it is not running through a debug stub or rom monitor. > > Should I disable all ROM Monitor Support in this case and link it as if it was to be placed in ROM but modify the corresponding memory layouts to actualy place it in RAM? This is a bit of a special scenario for eCos but unfortunately I have to build it this way. > I seem to get an exception when the scheduler is started, I think the RTC is getting an interrupt but the VSR doesn't have an entry in. So when the interrupt happens, it atempts to jump to a routine that doesn't exist. Provided the HAL_CLOCK_INITIALIZE, HAL_CLOCK_RESET, HAL_CLOCK_VAR_INITIALIZE and HAL_CLOCK_READ macros are valid, should the realtime clock code in the kernel handle everything else for me or do I need to make any special calls to setup the RTC isr? If you don't have an [eCos compatible] ROM monitor running, then set your application thusly. Make sure that CYGSEM_HAL_USE_ROM_MONITOR is not set and it should take over everything, including all of the interrupt & exception processing. This is invariant of the ROM/RAM startup type setting (although RAM mode often implies USE_ROM_MONITOR) -- Gary Thomas MLB Associates -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss